#[0] Please force people to add their recommended relay to their account so Nostr can resolve posts as good as ActivityPub
It’s called Ditto. It’s a Nostr-first backend, but it will introduce an API to obtain a NIP-05 address on the domain it’s hosted on, and if you do it will enable ActivityPub support on your account. And of course it supports Mastodon API.
My prototype is a pure client to a relay pool (no database), but I plan to support Gossip model and I’m trying to figure out how to make user feeds consistent. I know I’ll need to store some data. I want to build it in a way that the database is a cache that can expire and be rebuilt from relays. I’m tempted to use Redis because it will be a lot easier than LMDB, but I’m torn because it would increase installation complexity. Depending on how much data we store it might need to become a relay itself, then I can do advanced queries. I’m still mulling on the various technical/product trade offs, but the core idea is Ditto.
I have a small proof-of-concept prototype. It’s been difficult to build something strictly experimental, so I did some soul searching about it and developed a vision. Now it’s just a matter of time.
You know what’s peak web development? Forms. Forms and form validation. Once you’re spending 90% of your time doing that, you know you’ve made it.
sigh #[0]
👻
Wait Hitler was real?? I thought he was just an internet meme.
I reset the strfry database and suddenly relay.mostr.pub is working again.
Something is wrong with relay.mostr.pub
Key management Key invalidation Antispam measures Incentives to run a relay
Okay Nostrbros, I created a really good system for strfry policy management. See updated readme here: https://gitlab.com/soapbox-pub/strfry-policies
I have IP rate limiting and anti-duplication running on relay.mostr.pub now and it’s working to stop the spammers.
I’m working on antispam measures for the mostr bridge. I’m also setting up a VM with 1TB of space.
I submitted a NIP to deal with this. Take a look please #[0]
I’ve already created a small server that does this, although it needs to be self-hosted. Can handle thousands of keys easily: https://gitlab.com/soapbox-pub/plan-b
A better solution is to let Kind 5 events delete pubkeys and have relays handle it. I’ve been meaning to propose it.
I’ve already created a small server that does this, although it needs to be self-hosted. Can handle thousands of keys easily: https://gitlab.com/soapbox-pub/plan-b
Do you have to run a full Bitcoin node to run a lightning node? Not looking forward to syncing for 3 days.
It was meant to be.
That’s a great idea. I might just finish the job.
