Avatar
eric
520830c334a3f79f88cac934580d26f91a7832c6b21fb9625690ea2ed81b5626
peace. freedom. open source. proof of work. damus contributor

i’m addicted to making this omelette

what a match 🎾

una cerveza no hace daño

the only #datechain I use is my calendar

Ironically nostr will have succeeded when the majority of users dont know what it is

Replying to Avatar signal_and_rage

If you hypothetically could raise $5m to purchase this domain, what would you do with it?

nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj pointing out that the subdomains might be of great value for the nostr protocol/community is interesting nostr:note1vafcer4kv58928x986lph6krjtmml2j6zn25lxz7yaygg79tustq6u6tan

the same thing I do with all my other domains, absolutely nothing.

love how chaotic this song is ⬆️

i’ll run my changes and end up scrolling the timeline on the simulator and forget to check what I changed 😂

just a reminder that relays are like horcruxes

decentralized dating done in the open, if you’re a creep the whole network will know and there’s no delete, rizz accordingly

Replying to Avatar elsat

nostr:npub1mc20uche0cy599vpl850aschpu7wteundgsnf0msep79lu3fu5aq3r4ptv try this solution for fixing your relays: revert to 1.6 Damus build (1), and remove the relays you dont want.

Was also able to delete in 1.6 (10) didn’t work in 1.6 (11) and above

no haven’t used other clients with this nsec. I can delete them in 1.6 (1) gonna try and find which build broke it

I somehow managed to add “wss:” and now i’m stuck with it lol two of the japanese relays I added also can’t remove

damn had code for breakfast and lunch today