Came up with this last night after seeing this, but it might work. Reminds me of relays being listed in your profile.

Contribute —> recognition from people who appreciate the contributions —> get added to a “bitcoin square” section on the profiles of many devs and public figures —> become more visible to plebs on the Bitcoin Square.

It incentivize people to contribute real value, else they may not be seen as much in the bitcoin square. Seems better than admins banning voices of dissent.

Mastodon, Discord, and IRC face a common challenge: requiring admins to govern. They resemble private clubs rather than open public squares. 🐣

To solve this problem, we could create a communities section similar to Twitter’s called Squares. The Squares are open and leaderless, unlike Twitter communities. Squares would be another part of your profile e.g. [Posts, Replies, Squares, Media].

Squares can be joined by anyone.

For the 1st example let’s simulate the Bitcoin Square. 🐝

1. Once you join a square, you can list it and your favorite members from that square on your profile.

2. If you want to join the Bitcoin square for the first time, go to the profiles of people you admire or follow to see if they are part of that square.

3. See which users in the Bitcoin Square they have listed on their profile. Each user will be listed by their public key.

4. Add the public keys of the users you want to see on the Bitcoin Square to a private list on the app.

5. This private list becomes “the viewing algorithm” for the Bitcoin Square on your local device. Now your device will only display posts in the Bitcoin Square if they are signed by those selected public keys, ignoring all other posts in the Square.

This approach enables client-side filtering without a server admin while still allowing users to maintain a private club environment in a public way. Could work for any type of square, beyond bitcoin… 📣

“The Internet is a firehose and we haven’t learned how to adjust the spigot.” ~Andrew Ruiz

How so

Seems like the rough consensus is that the text is harder for your brain to parse for some reason, although the full bleed images are nice (once cropping issue is fixed).

Will keep tweaking, perhaps there’s a way to keep the old style while retaining full bleed images.

Simplified the Sybil-resistant discovery.

Is there a nostrich symbol that is plain & simple like this?

Wish more clients had a built-in wallet for SPV proofs (not just Lightning invoices) like Current does. Nostr 2.0 will rely on these lightwallet SPV proofs, so it being built into the app is much more efficient.

Seems like Damus is no longer planning on a mobile wallet alas. Current’s feed needs to feel more like Twitter.

Yes nostr is moving in lightspeed⚡️

Initially, I thought ION allowed unique URL registration like (did://bob.com), but Daniel clarified that it generates IDs in the format: "ChosenWord-RandomWord-RandomWord" (e.g., "Colby-Purple-Bee").

These trust-minimized IDs are more memorable than npubs or Bitcoin addresses and could function as usernames or domains atop Bitcoin.

Daniel and I discussed Web5 and Nostr 2.0 as co-protocols:

• Nostr 2.0 provides hosting for websites across hundreds of untrusted relays without the risks of content tampering, thanks to a tamper-evident Merkle root that's on-chain.

• Web5 enables self-hosting websites across local devices. This combination offers the best of both worlds: decentralized hosting with Nostr 2.0 and local self-hosting with Web5.

𝐾𝑒𝑦 𝑝𝑜𝑖𝑛𝑡𝑠 𝑓𝑟𝑜𝑚 𝑜𝑢𝑟 𝑑𝑖𝑠𝑐𝑢𝑠𝑠𝑖𝑜𝑛 𝑜𝑛 𝑁𝑜𝑠𝑡𝑟 𝟐.𝟎 𝑎𝑛𝑑 𝑊𝑒𝑏𝟓 𝑎𝑠 𝑐𝑜-𝑝𝑟𝑜𝑡𝑜𝑐𝑜𝑙𝑠:

1. Web5 allows website owners to self-host websites locally with decentralized domains, while Nostr 2.0 enables distributed hosting across hundreds of untrusted relays. This offers flexibility depending on the owner's needs.

2. Web5 provides resilient backup solutions for users decentralizing their website with Nostr 2.0, ensuring local copies across their trusted devices.

3. Web5 facilitates direct, encrypted communication between website owners and users. Visitors can browse decentralized websites hosted on many Nostr 2.0 relays and establish a direct connection with the website owners through Web5, all thanks to using the same DID system for domains.

We encourage the Web5 TBD team to develop an ION middlelayer for Nostr 2.0, making ION a middlelayer similar to the decentralized GitHub we are building for the bounty started by #[7]

This modular structure means the Nostr 2.0 base layer for storage ossifies into a standard. This encourages people to build new middlelayers and a diversity of clients for each middlelayer atop the universal, hash-organized off-chain storage. 🧱

Unlike IPFS, Nostr 2.0 lets people browse and verify websites without hosting them. Users don’t need to rely on public IPFS gateways to verify the data either — thanks to the on-chain Merkle roots Nostr 2.0 utilizes for syncing any off-chain data, identical to the type of on-chain Merkle roots ION uses. We aimed for the same Merkle DAGs and content addressing standards that ION already uses in order to be interoperable.

Most importantly, making all Nostr 2.0 nodes become ION nodes offers a significant advantage: When users type in a DID URL into a browser, the conjoined node would resolve the URL and deliver the tamper-evident website files to the user. 🖖

Replacing IPFS with Nostr 2.0 achieves this all-in-one package for a decentralized web powered by Bitcoin, where users can resolve URLs and browse decentralized websites through one type of modular node. If hundreds or thousands of operators run this conjoined node (Nostr 2.0+ION+Bitcoin full-node), the decentralized web becomes a reality. Anytime they want to host specific Twitter profiles or a GitHub repo, they simply add those middlelayers to their node stack and configure their hosting preferences.