Oddbean new post about login | logout 1) Most standards don't need to be found by most devs because they don't use them. Nobody uses all of the NIPs, either, after all, and that effect is about to go parabolic. I think everyone just needs to sort of give up on spec management. 2) It's not impossible to find them. There is a list in the wiki for events or you can simply use elasticsearch on nos.today. Or just #asknostr. Make a DVM spec discovery tool. 3) You can see the events popping up on relays and just search for the ones that seems stick around for a while and add them to the list yourself. This is dynamic discovery and someone already built it. https://undocumented.nostrkinds.info/ 4) I don't need an event to announce the event that I'm publishing on relays and writing about in the wiki and in articles and discussing in communities. That's the same event being announced like 50 times and would encourage people to reserve NUD numbers that they don't end up using, or having NUD numbers assigned to unpopular events, like we have with the NIPS. This creates an ID "honeypot". 5) We don't need the "NUD". We have our own prefix. It's obvious that it is a Nostr spec, if it deals with Nostr and is a spec. 6) Implementations should lead. Marketing is proof of work. The best implementation will get the most attention and their spec will float to the top of the wiki or dominate the timeline for the people interested in that topic, and become the de facto standard. 7) We publish our specs on the wiki or other long-form articles, give the event a searcheable identifier, and then we implement it and talk about it all on Nostr. That gives everyone enough opportunity to find it, who is genuinely interested. https://wikifreedia.xyz/nip-event-register/npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl
> We don't need the "NUD". We have our own prefix. Apparently, but this is the first time I've heard about NKBIPs. The least you could have done is mention it on the github repository. We're directionally aligned here, I just really don't understand the hostility toward the existing forum for talking about nostr.
Why should we go back there? We are trying to move all of our interactions to Nostr, not away from it. We are putting our code and our documentation where our ♥️ is.
If you decide you want to change a venue in real life, you don't just show up at the new one and expect everyone to be there.
Y'all built the venue. I assumed that you would all be arriving, eventually.
Would you and/or nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wgh8w6twv5hszxmhwden5te0wfjkccte9ehx7um5wfcxcetzwvhxxmmd9uq35amnwvaz7tmwdaehgu3ww35x2umpd4jkxct59e5k7tcprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qguwaehxw309a6xsetrd96xzer9dshxummnw3erztnrdakj7qgkwaehxw309a3x2an09ehx7um5wgcjucm0d5hszrnhwden5te0dehhxtnvdakz7qpqm3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqtqc5tv like to come on the TGFN podcast to talk about it?
This topic, i don't know if I'd be too comfortable talking about 😅
Yeah, it's ehspicy. I was looking at your profile to find out more about you, but didn't really find anything. Do you have a project you work on I could read about?
nostr:nprofile1qqsd6ejdteqpvse63ntf7qz6u9yqspp4z7ymt8094urzwm0x2ceaxxgprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qguwaehxw309a6xsetrd96xzer9dshxummnw3erztnrdakj7qg3waehxw309ahx7um5wgh8w6twv5hshhq5j3 kickstarted things with this article: https://highlighter.com/laeserin/1719204947236 Which was picked up by nostr:nprofile1qqsx8zd7vjg70d5na8ek3m8g3lx3ghc8cp5d9sdm4epy0wd4aape6vspz4mhxue69uhk2er9dchxummnw3ezumrpdejqzyrhwden5te0dehhxarj9emkjmn9qyxhwumn8ghj7mn0wvhxcmmvycz39a and he added some cool extrapolations 😁 https://fountain.fm/episode/5D7Ds8tpivptu5OPy0lQ https://fountain.fm/episode/RtokKi1qHtjPNHGY7yuK And an article on Zettelkasten, a personal knowledge management system that we're brainstorming how to scale up for collaborative uses. https://www.lesswrong.com/posts/NfdHG6oHBJ8Qxc26s/the-zettelkasten-method-1
Cool, I've been listening to nostr:nprofile1qyw8wumn8ghj7un9d3shjtngd9nksmrfva58getj9e3k7mf0qyt8wumn8ghj7un9d3shjtnddaehgu3wwp6kytcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxthwden5te0wfjkccte9ekk7mt0wd68ytnsd9hxktcpzemhxue69uhhqatjwpkx2un9d3shjtnrdakj7qgkwaehxw309ajkgetw9ehx7um5wghxcctwvshszythwden5te0dehhxarj9emkjmn99uqsuamnwvaz7tmwdaejumr0dshszxrhwden5te0dehhxerjd9mx2tnpwpcz7un9d3shjqgnwaehxw309aex2mrp0yhxvdm69e5k7tcqyp3cn0nyj8nmdylf7d5we6y0e5297p7qdrfvrwawgfrmnd00gwwnythrc95 , I'll give that article a read.
We will be doing an interview with @NunyaBidness soon. That's what he wanted the calendar entry for.
GitCitadel also has a private group, now, at https://coracle.social/groups/naddr1qvzqqqytlgpzqzp7p4ekweu59qlue8u46gtfjm30w33r527zr6n2hz89ejg4cnyxqqgrywfjx5cnxvfexsursv3hxccny2z3luq/ but I can only seem to login to Coracle using nos2x with Kiwi browser. Nos2x with chrome and Nos2x with firefox and anything with Amber, all seem to not work. 🤷♀️ I can't figure out what I'm doing wrong or why it worked in that one particular case.
This is what I see. https://i.nostr.build/Dj2cKjQmsOJMOept.png
If I click on "Authorize forever", it just pops up again and again and again.
It pops up four time. A fifth time if you post a note. It forgets them all if you close the tab.
I think this is a nos2x thing. The authorizations are for different things. nostr:nprofile1qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qgmwaehxw309aex2mrp0yh8wetnw3jhymnzw33jucm0d5hsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qy88wumn8ghj7mn0wvhxcmmv9uqzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vahj2kfz
That's nos2x-fox, not my code, not my responsibility, I am forever free from having to fix that bug.
Same thing in brave I'm afraid
Same thing in chrome with nos2x.
We're (GitCitadel) are developing educational technology on top of nostr to help create a knowledge base of nostr development. Using Behavior Driven Development we can create pieces of text that can be navigated either by humans or an LLM to help find the functions needed to implement ideas. If you want to dive in, here are some sources. We want anyone interested in nostr to build the client using examples from other experienced devs. Also happy to explain more. nostr:nevent1qqsv939lv5kvu7w3asfdjv6y243rhq7w998hqu4d8e224du349cl3qcpz9mhxue69uhkummnw3ezuamfdejj7q3qm3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqxpqqqqqqzewng6f nostr:nevent1qqs04kedxaut7k3ns6kmv9n47rw298j3qjkeem2xmnxdrn8qyxv43cspr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcpsrqsqqqqqpfpzh3l
The specs we've formalized so far: Modularizing content - chunking. Helps with navagibility and encapsulating ideas, https://wikifreedia.xyz/nkbip-01/npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl Embeddings on nostr - you find a piece of text worth embedding? Put the embedding on nostr for anyone to grab and use. https://wikifreedia.xyz/nkbip-02/npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf
Our whole Operating Function / OS is premised on the concept of closures. Take typed functional programming and create a closure of the highest loop and you end up with the full state of a running machine (homoiconic data _and_ code) as a single serializable and portable value. I think our tech compliments many of the ideas in NKBIP-01 very well. What you are describing is basically Supercombinators for ideas, what we provide is supercombinators for compute 🤝 https://www.youtube.com/watch?v=pQzeYhSp1pw
We're gonna need you to explain these concepts in terms of Behavior Driven Development, maybe I'd understand then 😉🤣
My only familiarity with BDD is the testing strategy (TDD/BDD, etc.) is that what you mean? I'm very happy to explain these things to you, but want to make sure we're meeting in the right place. You can think of a supercombinator as a function with no free variables - no external state or necessary context. Everything you need to get a reproduceable result when running a function with certain arguments is all bundled up in one place with no dependencies. Your mention of a "Semantic Closure" struck me as extremely overlapping with our use of closures and it seemed like a good starting place to see where we might be able to help each other. At the risk of going too far too soon: The open source system we're building can be thought of as a kind of Turing complete programming environment + Virtual Machine. It's a single, portable binary with no external dependencies necessary on the host system. You run this one binary, and the entire VM/OS is running. All data and code (user data, programs, etc.) is collapsed into a single value - one enormous number (thus it, too, is highly portable. you can turn off a running machine, send the entire "single value" over the network, turn it back on on the other end and it picks up right where it left off - it doesn't even know it turned off.) Data and functions are content-addressable within the machine no matter where it is, similar to IPFS content addressing. The machine was over here, providing data or a function result at content-addressed-endpoint-X earlier? then you "moved the logical machine to a different physical machine" and turned it back on? your data or function is still available at the same content-addressed-endpoint-X as before. This is highly valuable for Nostr relays, DVMs, static content hosting, chat backend, you name it. Anything that would benefit from an always-on, always-available "server-like" process that you'd like to be extremely simple, dependency-free, trivial to run by a non-technical person, and durable forever. I'll stop there because there a billion things I could say here - but the rabbit hole should be dug in the most useful direction for you - not wherever my rambling is taking me...
https://i.nostr.build/8bMNttMR5C7DPRRM.jpg Whether that means building the system itself, or contributing to the kb. nostr:nevent1qqswm75eksyxnrnmxxhkq3uv3qzd9yvk8pen9xhtdmuj8nsvuf46a5spr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcpsrqsqqqqqp5phd9g
Following to maybe use it one day. 🥹
Soon™️ The infrastructure is all here including monetary incentives for devs to contribute code. Once the doors open and we have a sufficient proccess for self documenting code + uploading notes, after a large enough interconnected KB is built, there will be no competition for organizing information, remixing and navigation.
https://i.nostr.build/oinGLZTw58ln74mo.jpg nostr:nevent1qqsdtknt8kl0l79n7egp0hemdqtz750msmv0p7ma3w0qch4z77esyrqpz9mhxue69uhkummnw3ezuamfdejj7q3qm3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqxpqqqqqqz6pkqqq
This also include bitcoin education and development, privacy, security. Anything you care to write about will be formalized, organized and grouped with other similar ideas. Anyone with a similar interest can meander in that space, and dive into as deep detail as provided by the users. nostr:nevent1qqsteypl762a4pcqpye978wqnw2kjhjnwjrceg9qhw3y39jj2uvyl4cpz9mhxue69uhkummnw3ezuamfdejj7q3qm3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqxpqqqqqqz997km3
"Sounds like a virtual treasure trove of knowledge waiting to be explored! Who needs conformity when you can dive into the deep end of creativity and innovation? Count me in for the non-traditional education journey! 💡🚀 #ThinkOutsideTheBox"
https://i.nostr.build/8bMNttMR5C7DPRRM.jpg Whether that means building the system itself, or contributing to the kb. nostr:nevent1qqswm75eksyxnrnmxxhkq3uv3qzd9yvk8pen9xhtdmuj8nsvuf46a5spr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcpsrqsqqqqqp5phd9g
Following to maybe use it one day. 🥹
Soon™️ The infrastructure is all here including monetary incentives for devs to contribute code. Once the doors open and we have a sufficient proccess for self documenting code + uploading notes, after a large enough interconnected KB is built, there will be no competition for organizing information, remixing and navigation.
https://i.nostr.build/oinGLZTw58ln74mo.jpg nostr:nevent1qqsdtknt8kl0l79n7egp0hemdqtz750msmv0p7ma3w0qch4z77esyrqpz9mhxue69uhkummnw3ezuamfdejj7q3qm3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqxpqqqqqqz6pkqqq
This also include bitcoin education and development, privacy, security. Anything you care to write about will be formalized, organized and grouped with other similar ideas. Anyone with a similar interest can meander in that space, and dive into as deep detail as provided by the users. nostr:nevent1qqsteypl762a4pcqpye978wqnw2kjhjnwjrceg9qhw3y39jj2uvyl4cpz9mhxue69uhkummnw3ezuamfdejj7q3qm3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqxpqqqqqqz997km3
"Sounds like a virtual treasure trove of knowledge waiting to be explored! Who needs conformity when you can dive into the deep end of creativity and innovation? Count me in for the non-traditional education journey! 💡🚀 #ThinkOutsideTheBox"
Soon™️ The infrastructure is all here including monetary incentives for devs to contribute code. Once the doors open and we have a sufficient proccess for self documenting code + uploading notes, after a large enough interconnected KB is built, there will be no competition for organizing information, remixing and navigation.
https://i.nostr.build/oinGLZTw58ln74mo.jpg nostr:nevent1qqsdtknt8kl0l79n7egp0hemdqtz750msmv0p7ma3w0qch4z77esyrqpz9mhxue69uhkummnw3ezuamfdejj7q3qm3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqxpqqqqqqz6pkqqq
"Sounds like a virtual treasure trove of knowledge waiting to be explored! Who needs conformity when you can dive into the deep end of creativity and innovation? Count me in for the non-traditional education journey! 💡🚀 #ThinkOutsideTheBox"
Getting paid to learn, what about getting paid to teach? https://i.nostr.build/8bMNttMR5C7DPRRM.jpg Whether that means building the system itself, or contributing to the kb. nostr:nevent1qqswm75eksyxnrnmxxhkq3uv3qzd9yvk8pen9xhtdmuj8nsvuf46a5sprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7q3qm3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqxpqqqqqqzrmfwdm
I see your private custodial lightning service, and raise you a: **closed loop nostr development ecosystem** where experienced devs contribute how they solve build, test, debug - to a knowledge base, built with nostr infrastructure. Getting paid to teach and publish their implementations - indexed and organized by nostr clients, followed by recommendations to users for how to develop nostr clients based on the tools they use. helping newcomers who wan't to build with inspiration from nostr's best devs. its all mostly here. A client needs to make a giant bow to wrap it with, which is what we (GitCitadel) are aspiring for. nostr:nevent1qqsw209yxpvpqqfk35m32zkmakzl3kknwyd5s6afwm0etphs39he7pgpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcpsrqsqqqqqp6lv2lh
Bullish.
Hm, your npub.cash address doesn’t seem to be working. Any other issues reported?
changed the address, until its working again 😆
It’s back up. 🤙 note1zxs6zdrey0xq30gxfycwtu09fannrkt3cdn9362f9rcmqqs2jk7sfquyhc
Bullish.
Hm, your npub.cash address doesn’t seem to be working. Any other issues reported?
changed the address, until its working again 😆
It’s back up. 🤙 note1zxs6zdrey0xq30gxfycwtu09fannrkt3cdn9362f9rcmqqs2jk7sfquyhc
It’s back up. 🤙 note1zxs6zdrey0xq30gxfycwtu09fannrkt3cdn9362f9rcmqqs2jk7sfquyhc
