You know what'd be a cool idea for an eCash wallet?
When you check the details page to see where all the sources of funds are, if there is one that has more funds than your comfortable with trusting, then there would be a button that you can press which would read distribute those funds to different sources, to help decrease the risk of losing a bunch of your funds if one goes down or rogue.
Freakoverse
nABCeAbsurd
npub18n4y...zk9r
I guess I'm one of those #vtubers.
Having fun talking about general topics, vrchat/similar, and games. Also #indiedev #gamedev. You can call me: Freak فْرِيكٌ フリク (still learning Nihongo).
#envtuber #podcast #gaming #gamedev
I started thinking "how would a link shortner work on nostr / not have it as a centralized server or domain, where it can be add on all nostr clients and not rely on a service"
The first idea that came to mind is to take an event address of an original post, take the first 10 digits and last 5 plus the first and last digits of the author that posted it, and have that as the identifier, like: naddr1qvzqqqrkcgkwnw2npub18n4yszzk9r
Still link, but definitely better than:
naddr1qvzqqqrkcgpzpcy2r8zym7el900fxtgk9hcpf5scu5fd05fpsvgvqqa2dqqez4e6qp4nxvp5xqer5efs8psnzwtrxs6xgenzxdnrycnyv5unxvnyxymryerxxqcngepjxyux2df3xfjrwep3xgcnsve3xp3nqvpnv9snvwpsxyunzdfhxdsn5efexq6r2vej8qkkxd33xqkngvtzxyknsetxxcknqvfhxejnqdf4xejxydslzgaul
So users that open a URL with that on clients that support this, would trigger a search on relays for this identifier, which would then find the actual event id and load it in.
Thoughts? #asknostr #nostr
The web of trust system on nostr made me think of how we used to deal with bad actors in games like World of Warcraft, where the more bad shit you do, the more people know about you and your on every bodies block list and shit list, and nobody would play with you.
The web of trust system is basically an advanced and more automated version of, and considering how developers are always dealing with cheaters and games, and yet gamers are always unhappy with the colonel level access and anti cheat systems, I'd imagine having a web of trust like system presented as a anti cheat mechanism for players to utilize, would be a great solution to all of this. You're still find cheaters, but less and less as you play and form connections.
If I ever make an online multiplayer game, I'd strongly consider this and implement it.
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 →
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 →