Avatar
YODL
d28413712171c33e117d4bd0930ac05b2c51b30eb3021ef8d4f1233f02c90a2b
YODL-AY-HEE-HOO

I see draft, I go to see details, at bottom is a sign button which takes me here (see pic). I expect bottom has a button but I can't scroll to it

Yes yes, I just remember assuring people that they always do this and it's no big deal, only to be proven very wrong.

What I don't understand is I never see any input from the mythical Chinese bitcoiners on these things. I have to rely on some clickbait headline and wonder.

Wasn't so funny may 19,2021 😭

#Wordle 1,506 3/6

β¬›πŸŸ¨β¬›πŸŸ¨β¬›

πŸŸ¨β¬›πŸŸ¨β¬›πŸŸ©

🟩🟩🟩🟩🟩

You have any idea how hard to follow these threads are on primal?!

Pretty sure it was a Freudian slip. All good, all are welcome

Replying to Avatar node

Where?

Mahdoods comment

We found the member of the group πŸ‘€

Laylay bitches. I got newer, better, richer friends now

I used to say this ironically in the past but now I think it's true, "you have the best meme folder"

Damn dude, I don't know if it's the new AirPods, but the sound is great

Replying to Avatar :P

We playing

I didn't have energy to set up account and do on chain stuff just to play for an hour

How about a slightly less black pfp? Something that contrasts with my background a bit more

Replying to .

https://open.spotify.com/track/53xewIrCGfDpY3Xld2Nd9h

Gentlemen. I'm almost certain you'll both like this tune, it is incredibly complex. Layer upon layer upon layer, it's a fucking belterπŸ™πŸ».

I am liking it. Not sure who "both of you" in OP refers to, but glad I stumbled on it

#orly #devstr #progressreport

so, i got it done... again the damn configurations, but also in this case i forgot to put in a label in an outer for loop so it actually worked

the replication path is now this:

try the replicas one by one

if success, done

if fail, try another

all of the replicas do the same thing, in addition to not sending to relays that have their key listed in the X-Pubkeys header and voila. 3 replicas, 3 messages, 100% propagation.

if for whatever reason one of the replicas can't connect to one of them but the others can, it will be gotten to.

this will mean that replication can scale at O(1) so message delay of propagation is linear to the number of replicas. which is much better than the previous uncivilised format.

so now ORLY can set up as a cluster or replicator, either option is possible, and two or more relays can now automatically push their new events to the other peers and instantly any subs on the other peers will also get their events. if any of the relays ded, then the message won't get to them but no user would be on them either.

in theory, the main reason for ded replica would be connectivity. but of course it could be bug, but i'll never mind that for now. still more tasks to complete on this one, but mainly just the reverse proxy and the DNS configuration and then writing a configuration system that generates the necessary configurations for a cluster deployment and voila. the world will have high availability ORLY relays that behave almost like a single big relay on a faster connection.

this will be great for censorship resistance since it would be easy for multiple individuals across jurisdictions to use the config tool to set up their own relay identity and then share their address and key to the other members and no single person can be a target for a total takedown.

and yes, it would work as equally with relays at different addresses as it would for a round robin DNS, the difference being that with different geographical locations, users could be selective for the local replica but users in other locations can use their local one... so, optimising local latency while enabling propagation at not too much slower speed.

this will be very useful for business deployments.

TLDR

Buy a sub to ChatGPT or use that anonymous one, you can pay in sats, forget name