Constant

Zero-JS Hypermedia Browser

avatar
Constant
Constant@techno-ethica.com
npub1t6jx...ksrw
Writing a book about Nostr Ceterum censeo NIP-03 omnibus esse utendum

Notes (10)

nostr:npub1equrmqway3qxw3dkssymusxkwgwrqypfgeqx0lx9pgjam7gnj4ysaqhkj6 what can you tell me and the rest of Nostr about the exam and certificate for 'influencers' in Belgium?
2025-11-29 23:23:30 from 1 relay(s) View Thread →
This note was created with the Graphical User Interface of NAK, on a windows computer, best UI/UX ever. All hail vnak.exe
2025-11-29 10:14:54 from 1 relay(s) View Thread →
''Don't be one of these people'' nostr:naddr1qvzqqqr4gupzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqqyrqd3sx93nzcmp4kcwz6
2025-11-26 15:43:24 from 1 relay(s) View Thread →
On a panel the question was asked why Nostr did not exist before, and why its special. Due to time i did not get a shot at answering but let me do it now. TL:DR; all the other protocols are a bunch of pussies. Nostr is somewhat an offshoot of secure scuttlebud(SSB), a protocol that already embraced putting cryptography at its core, despite all its apparent issues. Many other protocols never dared to do this, afraid of keyloss, issues with names and what not. Unapologetically putting keypairs at the center will guarantee you will have a hard time to reach mass appeal initially, but with Bitcoin being around for a while, atleast there is a group of people who are comfortable enough with such a setup. But Nostr is unapologetic about another thing that even SSB's designers could not seem to let go off, and thats in the realm of consistency, and il throw data availability in the mix there as well irt other protocols out there. Nostr guarentees fuck all, leaving room for other systems on top of it to pretend to guarantee things where ever such pretence is appropriate. Lastly it kept itself accessible by picking JSON for its data format, making sure to rub puritanical assholes such as myself the wrong way. For however much we hate the inefficiency, it just is straightforward and legible to most regular humans. The result is a protocol that is so basic, it more or less only points in the direction of a new paradigm without explaining that new paradigm to you. The less you define, the more you imply, which was my first Nostr presentation at Nostriga 2024 (see below). As such, most are still gathered somewhere just passed the entrance unsure of where they actually are, begging for familiarity (muh UI/UX, muh onboarding, muh normies), while more and more realize there is endless new ground to explore and started doing so. I don't think the point is the protocol really. A standard for what cryptography to use, what dataformat and how to interact with servers, nothing about it is impressive. From a technical perspective it is minimal viable. The only reason this minimal viable thing is enough, is becasue 'we' were ready for it. Bitcoiners, comfortable with all the rough edges, understanding of the need, capable enough to build and many years of training their conviction muscle. To attack central banking head on with a complete grass-roots approach is madness; attacking an already conquered web in the same way is not much different. And the fuck you money helps, especially the larger sums from one Bitcoiner in particular. I'd like to pretend Nostr is this path depend systems view of history destiny thing that was merely sped up a bit; but i am not above admitting the great men viewpoint of historical development might had a hand in this thing, for which i am thankfull to the extend that is the case. An idea whose time has come, regardless, as they say. And there we are, an answer i would have never been able to fit in a short panel discussion anyway, and looking back, also too large for a kind1, but it is what it is. nostr:nevent1qqsp5uws0ynh72df789yn3y8zyctz4lk7y55tmyn35udpxrzxsjtfdcpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgq3qt6jxfqz9hv0lygn9thwndekuahwyxkgvycyscjrtauuw73gd5k7sxpqqqqqqzrcfu9r nostr:nevent1qqsqfezwpl4jeulrhytap7jx0y68hpyem6d8ldeqmswwu6htfj8kgacpp4mhxue69uhkummn9ekx7mqzyp02geyqgka3lu3zv4wa6dhxmnkacs6epsnqjrzgd0hn3m69pkjm6qcyqqqqqqgq4car3
2025-11-26 15:35:40 from 1 relay(s) View Thread →
Anyone who wants to know what went on at the Manchester Bitfest conference, nostr:npub1pkhzm90462y3cfat45m25nmz6p9ku0lw0ak4fqjttpy8qvfhrymqjlln8r is doing an excellent job documenting the event. Take a look at his posts, great way to catch up on whats happening.
2025-11-23 14:38:56 from 1 relay(s) View Thread →
image nostr:note1zwmtld6hvyxkavy357d4424fs4ajjemjke7e4vnu2tnhweqzxmqqr36adw
2025-11-23 13:26:16 from 1 relay(s) View Thread →
Live now nostr:note1m6ae53zlqj05p2sd4yl7nrua7kw7n79ks2yn5atlkzl3egc3n4usgkdgkq
2025-11-21 17:32:09 from 1 relay(s) View Thread →
A Dutchman arrived on British shores; time for another glorious revolution.
2025-11-20 08:36:24 from 1 relay(s) View Thread →
What do the wise sages of Nostr think of the following terrible grugbrain idea: What if you create an ncryptsec and just put it in an event and on some relay somewhere. Then you could go to lets say a fresh amber install, fetch that event, decrypt it and just set up your new system while only needing a password. The hash of the password could be included in the same event as the ncryptsec, and then u could use that to query your ncryptsec-event. This allows you to sign the ncryptsec-event with some random throwaway keypair. This way it is not appearent who's ncryptsec is tied to. Other than 'what if the password is too weak' and 'QuAntUm' and 'how do you fix spam': why would this be a bad idea?
2025-11-17 11:27:50 from 1 relay(s) View Thread →