That's good on both accounts. I guess if I have to speak of what I've observed within myself for like 2 decades, purpose seems to be incredibly important to me.

Hmmmm. Not sure about that. But you seem pretty certain and set on it?!

Enjoyment is meaningless and isn't a purpose. Purpose can be enjoyed but enjoyment isn't purpose, it's a trap

I think a new event kind that specifies edges between events could be valuable. Different npubs could specify different sets of edges, creating different "overlays" on the underlying event data.

This could be used to build graph databases. One might use embeddings to determine where to draw connections, and how to weight them. This unlocks semantic navigation journeys embedded in an events context. Think how you can jump from one page to the next on Wikipedia almost endlessly, now apply that flow to just about any Nostr event.

How so? The only downside i see is that it's not actually trivial to release events based on future timestamp. Do you see this as enough for ddos? Or what's the angle?

What do I wanna do with my life? #mood

This is a test, does it work?

new wheels 😂

😆😆😆😆

Let me check. Maybe your npub got wrapped in one of the WoT filters for shitposting or too many GM posts 😆

Standby

Nostr is already much better than 4chan

You are reminded that doing with a seditious intention an act or acts that have a seditious intention is a serious offence!

- Hong Kong Police Force

I also want to note, whenever I am arguing about design decisions I don't talk about Nostr usecas, I talk about the general usecase of web 1.0 (excluding Web 2.0 with its aggregation and indexing, because i am skeptical we can fix that).

So when someone smart says that the cloud is a shitcoin, my reaction is, hold on why go that far? Servers are cool, people like to know their data is safe? Why give up on these parts of the web usecases? Not everything is a broadcasting app, we need data integrity too.

I'm not sure what im doing wrong but I can't even login to Notedeck. Using Windows version.

Why does he look fat? Seems like he would be ultra fit.

its caches all the way down

correct

Have both. They solve their own use cases.

When you want to search the world’s largest library that’s the tradeoff you are making.

But once you find it, or get a book from a friend for example, you put it in your indexedDB database and congrats.

I personally envision the hierarchy ad follows

- Indexers, that have almost everything. They are the Google of Nostr. People push their events here and others find them.

- Large relays, which serve large communities. Think Nostr.land, Damus, etc. These are hubs for retrieving content in bulk.

- Community relays. These can be self-hosted or hosted in the cloud. People push from here to large relays and from large relays to here, what they care about.

- Local cache. This is the user’s own space and that is it.

The ideal relays would be:

- indexer: custom software

- large relays: strfry on medium end, NFDB and possible other options at large end

- community relays: could be a mix of strfry, NFDB, realy, nostrdb-based

- local relays: nostrdb, indexedDB-based

People are underestimating how big of a threat cloud providers are to internet freedom.

Please continue killing them!

You are describing local first apps, however they still need a server to help syncing when p2p doesn't suffice, which is often the case, but that is assuming you don't also need a datastore.

There is only so much apps you can build without a reliable storage for user data, even if that storage is a laptop operated by one of their family... it doesn't matter.

Then if you want to have large search indexes you need centralisation, but at least we shouldn't take a step backwards from WebDav, we should make it better; check Peergos for that, you probably will like it.

Anyone ask him if he looked into Nostr?

Are you looking at writing Java-Canvas files to stream into Obsidian to se and interact with there or are you consuming canvas files directly in the nostr client? What are you finding useful to render the canvas... Something like D3 or somethingore simple?

seeing the edge spec in your image reminds me of a former life working on a knowledge graph. rdf comes to mind. what if you include the type of edge - the predicate. you could also attach arbitrary properties to the edges, either tags or content json blob.

👍cool stuff!

gm nostr…

onboarding the first few Square sellers to our new native bitcoin acceptance experience today

lets go

AI translations i’m assuming?