Btw, I'd imagine a 'pinned post' on nostr would be, well, another nip/kind, or include it in profile meta data. I'd imagine the first option would be better in the long run

I think I mentioned this before, but looking forward to the day where @Zapstore provides a tab for browser extensions and people can just publish their browser extensions there. Don't see why not.

Considering what @spacestr is making, and what I thought of in the past regarding mailing client on nostr, I'm wondering if it's a good idea to have a different nip for emails specifically? It'd be basically a DM but a different kind and other added bells and whistles for an email UX. I'd imagine people want DMs for DMs and not for getting emails. #nostr #asknostr

@HORNETS I hope you guys still use normal wordings that were used in the past with what you're making with a github alt for nostr (like how gitea has): Master/Slave, Whitelist/Blacklist, etc

Web 1: Static websites Web 2: Dynamic content Web 3: Censorship resistance Since we already have Bitcoin (freedom money) and Nostr (freedom of information communication), the completion of Web 3, for me, would be the growing trend of mesh networking internet (everyone is an internet service provider), though that probably won't happen in my lifetime (we got @TollGate for now tho =3)

So finally, this one update is up. Basically, if a post is found, it wouldn't be missed again, and because of the database, this is also now possible: To the discussion of 'centralization' with the inclusion of 'servers', it's still decentralized. The repo for the server will be up so anyone can spin one up and add their own Events Aggregator Server to the site: And you can even simply turn it off by leaving it blank, where it'll just go back to hitting up nostr relays normally, though the reliability is good, of course, if you do that. Because of budget constraints, the code for the server is pretty much focused for DEG Mods, though when there are no constraints, the idea is to eventually redevelop this in a way that can be used for any nostr client and easily support different and new NIPs, and combine it with normal 'dumb' relays to have it as one package/system, to end up with 'reliable' relays instead and hopefully have everyone use that instead (perhaps a toggle 'keep it dumb' for those who don't want to have a proper DB for some reason). But ya, the user is still fully in control and no central point of failure to properly bring things down (even the 'central' part, just find another or spin up your own server if something goes wrong and you still want a good experience) =3 View quoted note →

"Discord hires former Activision boss to take over as CEO" Guys, we need to speed up development xD