Spinning up a Blossom server for self-hosting doesn’t seem realistic either. Do you have ideas for removing the centralized point of failure and scaling nostr hosting in a decentralized way?

I still don’t understand why people and clients rely mostly on nostr.build that can be shut down within seconds 🤷‍♂️

I wonder if any relay operators or client dev received an ofcom letter.

Yes, we need more than Knots which is a soft fork of core with as few hundred setting changed.

I always think of Linux with its almost infinite array of distro's, all of which are essentially the same, but each one different in its own unique way.

Using nostr.band as a baseline but in a more cohesive dashboard, more server redundancy, plus more individualized data for users. It’s the kind of thing that would benefit from either a subscription service or zapwalls but you’d still need a free tier.

I need metrics and trending content via API. I don’t think anything else has this.

It is disgusting. They didn’t even ask for our passports upon reentering the US, until we tried to enter the baggage carousel. They will not let you pass through the glass doors/gate until you remove your sunglasses and hat, for their handy facial recog entrapment.

Dear God!

Where do they get your fingerprint? I don’t remember being printed…

it is over the moment you give them your passport anyway

And you do not receive your passport back.

I’ve never seen so many angry people just for suggesting not having amber support.

Damus Android’s chrome is being designed as the signer, and our hosted micro apps will communicate with the chrome for signing. This is no different than a browser with a signing extension, except the signer is embedded in damus in an isolated fashion.

We’re designing damus so that it can securely host multiple micro-apps for multiple platforms, and it will not depend on any external apps for its core function.

nostr.land is 108k sats for 2 years not 1

100 bucks a year?

I see it in damus ios?

I see it and not connected to your relay 🤔

So I could only see this event if you quoted it and Im connected directly to nostr.land?

Their cheapest dedicated server is 30 Euros, I think OVH has some for 20 Euros.

It's still a good price. Anything over 30 euros is too much especially since it's just my hobby and I'm not making money off my sites. A dedicated server is the best. I don't like shared or VPS.

If you have more than one miner (Bitaxe, NerdQaxe++, etc.) in a multi-rig setup and not using a gateway:

❌ The Inefficient "Old Way"

1. Work Duplication: Each miner would be working on its own separate block template. They are all solving different puzzles, not collaborating on the same one. This dramatically reduces your collective chance of finding a block, as hashrate is not focused on a single solution.

2. Management Overhead: You'd need to manually configure and monitor each miner individually. This is a time sink and a point of failure.

3. Network Spam: Each miner maintains its own individual connection to the Bitcoin network or a pool, increasing unnecessary network traffic and resource usage on your node.

4. No Cohesive Strategy: There's no unified view or control. You can't easily direct all your hashpower strategically.

In essence: It's like having four construction crews each building a different house when you need them all building one mansion together.

✅ With the Datum Gateway (The Efficient Way)

1. Unified Hashpower: The Gateway makes all your miners work together on the same block template. Your entire hashrate is focused on solving one puzzle, massively increasing your odds of finding a block. This is the single biggest advantage.

2. Single Point of Management: You configure and monitor everything from one interface. It's efficient, simple, and clean.

3. Optimized Resources: One central unit handles the communication with your node or pool. Your miners just focus on what they do best: hashing.

4. Strategic Flexibility: You can easily direct all your power to solo mine, or to a specific pool, with a few clicks.

In essence: The Gateway is the foreman that coordinates all your crews to work in unison on a single project, eliminating wasted effort.

you first need to use relay hints to find the 10002, then check the 10002 is up to date, then get kind 0 profile and the reply, and then get if they have a nut”zap” crap to see if you want to use nutzaps, then check if they support specialized relays for the sole fucking purpose of reaction counting so on

we just need read/write and a public/private distinction

sure but the point stands. basic metadata has been exploded across kinds. coupled with the fact it’s on a distributed network makes the complexity so high for basic stuff. it’s like splitting your simple backend into 100 nano services 😂

kind 3 is a bad idea due to large following lists, but 10002 was enough. more than enough.

Do you have a visualization?

cc nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s

Is there really so much data to store?

Wait, so this is blockable from the ethyst client?

What is the tag?

Then only send NOTIFY for accounts that have paid before, which is a much smaller set. This is not supposed to be for new users anyway which will need more handholding into what they are buying.

I am not saying that it needs no changes. I am happy to code whatever is needed. But this "ohh this is too hard for my server to handle" excuse of sounds just lazy.

Agreed, and I think a better way of discussing it, is the integrity contract. When I purchase from a hosted service I assume there is generally a contract that my data isn't going to disappear because the service had an oopsie.

I would like to offer the integrity of servicing customers that expect similear guaruntees.

Nostr as a whole, as a network, can and does function from plebs and a 10 y/o laptop and a generic brand SSD. That's great, but not the integrity contract I personally want to sell.