Okay interesting thank you. I'm curious about running a blossom server. Can this really scale as nostr grows? I'm imaging at some point in the future there ought to be some incentive to hold all this data. Like each upload needing some zaps with it.

How has Nostr approached the data hosting aspect? I'm thinking of some sort of system involving torrents and seeders could be paid in sats. Thoughts? #freedomtech #asknostr

at my job, real yolo coding happens in nano on a production server

Beyond vibe coding is yolo coding.

#goose & #claude-opus-4

yes I see, this is something that I considered too. still seems imperfect and non-deterministic. You could still end up in case 1 or 2 of my initial post, though it is an optimisation I agree, the cost of the implementation on the client is still unknown.

To limit bandwidth and ressource usage, I think the best should be to spin up one large request with a set of predetermined relay (that the end user could eventually change on the fly), and have a service on the background, that will run an EOSE request for 10 user at once, and roll it over the entire followlist. It would feed your cache, and forward all missing event to your frontend.

That service could either run on the client, or be hosted as a DVM, or just an API endpoint.

I have been reading through. Here is my understanding.

- lists is one big requests with a set of relays that cover each authors (each author connect to at least one relay in the list)

- JIT is used to query the notes for specific user, that uses different relays than the listed ones.

we couldn't agree either and have two solutions.

Lists:

get the nip65 data and calculate the best relays to connect to with a given coverage

pro: gets the theoretical ideal set of relays

con: does not work well on threads

JIT:

figures out relays just in time with a scoring of usefulness

pro: works in a lot of cases

con: not as accurate

I doubt this is implemented anywhere. For a profile page or note reactions, replies, zaps. YES, it works.

For the main feed, it becomes very hard, you have only 2 options. Each with their pro and cons.

Option 1: Fetch each user with its set of write relays in a separate request

Pros:

- Don't use too much bandwidth

Cons:

- Create a lot of requests, Some popular relays will reject your query for doing too many requests.

- The client handle potentially thousand of relay subscriptions all at once.

Option 2: Get all the relays for your entire FollowList, deduplicate them.

Pros:

- Create only one fat request, easy on the client, popular relays have just one request coming in.

- You won't miss a single note.

Cons:

- Use a shitload of bandwidth, up to 1gigabyte after just a few reloads in my tests.

- Connect to an infinite amount of relays at all times.

Thabks for invite not much of a dev just a lunatic trying out everything noatt

I WAS REQUESTED TO DELETE A POST I SENT TO NOSTR LOL

hi

#olas rejection #2 of the week

Fuck Apple

Shutdown of my server (shotgun KYC)

Fuck Vultr

Haha, yes. Usually, if I write a long text, I ask llms to refine it. English is my second language, so I make a lot of mistakes.

Today is Children’s Day, and my life changed exactly 15 years ago on this very day.

Every April 23rd, TV channels air children’s movies. Fifteen years ago, I watched Charlie and the Chocolate Factory. That film showed me what a director truly does: they create worlds and tell stories. That day, I realized I wanted to do the same.

Since then, I’ve never let go of that dream. I studied cinema in university and spent years learning, observing, and experiencing. For 15 years, I’ve grown with a single purpose: to become a storyteller.

Today, I had a brief moment of panic, but it reminded me not to take life for granted.

Now, I have everything I need to begin. I have the tools to create and experiment with my first short films. And I have Nostr—a platform that perfectly reflects my values and vision. I know myself, and I know there’s no better place to share my very first film.

I’m alive to fulfill my childhood dream. And after 15 years of preparation, I’m finally ready to bring the stories in my mind to life.

I’m sharing this post as a promise to myself: no more hiding. It’s time to put my stories out into the world.

Hi everyone! I’m Aylin. I’m excited to be part of the Nostr protocol. I’ll be sharing my training updates and thoughts here. Looking forward to connecting with you all! #introductions

This is my experience too. I guess AI doesn't know much about kotlin and jetpack compose too.

It gets lost very easily

The only thing I found its good is for writing messages like a validation or some text I need in the ui

why is it possible? like launch on a third party appstore?