You could also have a relay that only exists on your church's wifi. Those community events could be synced once a week, then people could get in touch directly the rest of the week.
It always happens, you release a new version, and you immediately find terrible bugs lurking. Coracle 0.4.14 is now out, which includes some significant fixes for DM deliverability.
Come to the PNW, it's great here.
nostr:nevent1qvzqqqqqqypzq6y8l09206fssndxg4h8an5pv3hnuagdmfreaf3zl6hvn783d5ncqyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpp4mhxue69uhkyunz9e5k7tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgnwaehxw309ahkvenrdpskjm3wwp6kytcqyq37klcl2ne3zny47xc5ngu5zkdg6s3lgxv9jpwwfeq5hlwjr2txgrkt7gg
Coracle version 0.4.13 has arrived, hopefully with more bugfixes than new bugs. Let me know if you run into any issues with it!
- [x] Add support for nip05 urls
- [x] Re-work notification rendering and loading
- [x] Fix slight NIP 17 incompatibility with 0xChat DMs/group chats
- [x] Use Intl api for list formatting (zmjohnson)
- [x] Update nostr signer version to support app icon url (chebizarro)
This is super cool! I'm not sure it counts as MFA, since it's really only one factor, but I could definitely see it being used in multisig or xor key creation
As I've read more about the history of the internet and digital spaces, I am beginning to think that there's something inherently leftist about the internet. Or at least, the dominant culture of nostr isn't traditional right, it's more of a libertarian right, which creates lots of problems that can only be solved either through top-down structures or grassroots collectivism. Of course the former is not palatable in our current authoritarian political context, and so resorting to traditionally collectivist institutions for taming wild individualism is all that's left.
I've always strongly identified as firmly right-wing, but I find myself embracing my inner classical liberal more and more, as I grow in my appreciation of natural law and individual liberty. But "embracing the chaos" creates a vacuum of structure that has to be filled somehow. Authoritarianism naturally fills that vacuum by means of power. I'd much rather be under a right-authoritarian regime than a left-authoritarian regime, but what if avoiding authoritarianism is an option? I'm not sure the bottom-right-hand corner of the political compass can actually exist, because it will always result in a tragedy of the commons, and/or a different kind of authoritarianism (e.g. corporatism). Solving social problems with technology at first seems to lead to technocracy, which is just another kind of authoritarianism that arises out of right-libertarianism. But maybe sufficiently decentralized technologies are a leftist mechanism that moves the center of gravity away from authoritarianism? But of course many past efforts at using technology to fix social problems either collapse into centralization, or have flaws that have to be fixed with social solutions, which only lasts until the ones providing the social capital burn out (cf yesterweb).
You can tell I'm thinking out loud here because I have no paragraph breaks.
Funny, I would have said the opposite. The right wants law and justice, the left wants freedom. But it all depends on the definition of those terms, which makes it hard to even talk about. I think a better distinction is that the left is visionary/utopian while the right is stagnant/realistic. Utopianism tests new ideas, but the thesis always collapses as reality modulates it. Leftism is unstable and dangerous if it fails to learn from history, but the progressive impulse is really a valuable thing. Maybe China has it right; they are extremely authoritarian and stable in the mainland, but use Hong Kong as a playground for economic innovation, that they can then import as it proves itself.
We do algorithms differently here. Try browsing coracle.social/feeds. Here's one to get started with:
nostr:naddr1qvzqqqrujgpzp978pfzrv6n9xhq5tvenl9e74pklmskh4xw6vxxyp3j8qkke3cezqydhwumn8ghj7un9d3shjtnhv4ehgetjde38gcewvdhk6tcpr3mhxue69uhksmmyd33x7epwvdhhyctrd3jjuar0dak8xtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszymhwden5te0wp6hyurvv4cxzeewv4ej7qgkwaehxw309ac82unsd3jhyetvv9ujucm0d5hsqypjxvcnvvf3xymrgvfj8ymrwv335ev6lw
Totally, discovery is the same sort of thing. Make lists, feeds, and share them with people. Primal is adding stuff like this too, and Damus is working on its own approach.
The term "trust" in "web of trust" refers to authentication, not to authorization. In other words, web of trust provides an attestation of the authenticity of a given identity, independent of application. Follow lists do a great job of this.
Only leveraging the authenticity of a given pubkey relative to yourself for a particular purpose other than fetching and displaying social content (the explicit intention behind "follows") requires additional information. Often this can be provided by the user through common sense (e.g. identifying a satire account), or addition attestations (I fully/partially trust this person for purpose x, and transitively trust them to make the same kind of attestations about other accounts).
Follow-based web of trust authentication is a substrate upon which unqualified and qualified web of trust application-specific authorization can be built.
This thought courtesy of my reading of Ashish Gulhati's essay "Secure Communication: The Technology of Freedom" in "Beautiful Code" this fine Sunday afternoon.
Not only that, but all the generic meta-nips automatically apply to all new kinds. For example, you can register a nip 89 handler for anything, or advertise relay support for any kind. Kinds are so awesome.
Relay probing is becoming a reality (I know nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgnwaehxw309ac82unsd3jhqct89ejhxtcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcppemhxue69uhkummn9ekx7mp0qyf8wumn8ghj7mn0wd68yat99e3k7mf0qqswwud0pvzu362lehm0av6sq4zd97cue5uy0z8f7jgtk0hz368dvmceue66m nostr.watch has probably been doing this for decades now)
https://video.nostr.build/b462b6568e3cb10410cd5c25a41f61407895d09ad806f354657140c15ddab36d.mp4
nostr:nprofile1qyghwumn8ghj7mn0wd68ytnhd9hx2tcpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxmhwden5te0w35x2en0wfjhxapwdehhxarjxyhxxmmd9uq3vamnwvaz7tmwd9jkctnwdaehgu339e3k7mf0qqs2js6wu9j76qdjs6lvlsnhrmchqhf4xlg9rvu89zyf3nqq6hygt0sn7ufqp I wager
Not me actually, it's by nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpz9mhxue69uhkummnw3ezuamfdejj7qg7waehxw309ahx7um5wgkhqatz9emk2mrvdaexgetj9ehx2ap0qyd8wumn8ghj7un9d3shjtnndp5hgen0wf3k2tn0dejj7qpqxdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30ws52n6k3
Yep, when you click "create space" it sends you to relay.tools. "Rooms" are also a concept in flotilla, but they're really barebones topic-like things that are tied to a relay.
People seem to be excited about my new project, Flotilla. It's still very much a WIP (probably a month out from MVP), but since it's been discovered I figured I'd go ahead and introduce it.
https://image.nostr.build/b9842d89fdc786ad3e86d692c4b52adce47e1bdd9daaf7d39cbf4806ecb75bc2.png
My goal for Coracle has for a long time been to support local in-person communities by replicating Facebook's events, groups, and marketplace. I've come to realize a few things about this project:
- Facebook is not the gold standard. In fact, people hate Facebook.
- There are many kinds of groups, for many different use cases.
- Very small chat groups work for most use cases.
- For almost all other groups, good moderation is key.
- Decentralization for groups works differently from decentralization for microblogging. Microblogging use cases benefit from simultaneous use of multiple relays. Community group use cases (in contrast to reddit-style groups) benefit from a single relay per group.
This is just the barest summary of what I've learned. But it's all in line with my long-held intuition that relays are, and should be, special. To that end, I'm creating a new client built around the dumbest form of communities that can be created: relays as communities.
Lots of code and specs need to be written to make this work, and as with Coracle, it'll be possible to host your own flotilla instance that only talks to a single relay, as well as use flotilla on desktop and mobile as a PWA and APK.
See the dev preview at https://flotilla.coracle.social. If you're interested in contributing, I've created several issues on the repository that should be good for first-time contributors: https://github.com/coracle-social/flotilla/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgwwaehxw309ahx7uewd3hkctcpzpmhxue69uhkummnw3ezumt0d5hsz3thwden5te0vf5hgcm0d9h8ydnyv56kc6mk0q68gurhv3kh5unyvej8qmrpx4ehjcfjv9n8wurrv93x5atsxfu8q6f4v36kccnpvshx7mnfdahz7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctcqyp6hjpmdntls5n8aa7n7ypzlyjrv0ewch33ml3452wtjx0smhl93j6nhxg8 is this on citrine's roadmap? Or already done?
It does make it more complex, mostly because you then need to coordinate which relays constitute a group, and/or deal with missing context when relays don't actively replicate content between them, and when members only join one or the other. My plan is the go between the horns of the dilemma and support multiple relays, but in serial rather than in parallel through migration events.
Yeah, I've thought a lot about it. In theory, there's nothing you can really do to keep private data private once it's published — someone can always take a screenshot of your note. There are a variety of techniques that can help in practice though:
- Use AUTH to implement read access
- Use NIP 70 to ask other relays not to store your events
- Strip signatures (this is the nuclear option, it basically breaks nostr, but could be used in specific situations)
- Encrypt your content
- Use clients that are smart about replicating stuff
- Include relay urls in events and have both relays and clients validate that the event came from the designated relay (this isn't done anywhere, but I may use it for flotilla).
Yes, with the usual caveats about it being software connected to the internet, etc. But from my understanding it's FOSS and the key is stored in your browser.
Oddbean new post about login | logout
Notes by hodlbod | export