wiped the iris.to cache storage

*posts on Nostr* *gets a like* someone loves me 💞 *checks who it is* bot: hello, human!

i don't know why, but #[0] does this weird thing where it'll tell you there are X new messages in your feed but when you click it, no new messages appear. is it notifying me of bot spam that i blocked or...?

what is the correct Nostr terminology for a share/reblog/boost?

maybe nostr-proxy was working properly after all, and the network went almost completely silent JUST as i was testing it? it's very late in America right now, and Nostr doesn't appear to be super popular in Europe. same with Mastodon, really. they're both fairly slow to catch on here.

if you keep seeing me boost this anonymous user with no profile, you need to add wss://relay.mostr.pub because those are my Mastodon posts and you don't get any info on Mastodon users unless you add that.

technically speaking, we could all just agree to use one huge relay. i realise this would ruin the entire idea of Nostr, but we're not *far* from just using one huge relay already. there's about a dozen relays that every client talks to by default, so it's fairly centralised. and seeing as relays don't talk to each other, you pretty much *have* to add those relays to get some reach.

Nostr begs you to self-host infrastructure even more so than Mastodon does. my devices get very warm from running Nostr clients, so that's going to eat up your battery pretty quickly, and it's probably not great for your phone data bill either. if i could just offload all the heavy lifting (talking to relays, caching data) to an application server that i can put on one of my Linux machines and connect to it with a lightweight client, that would be nice.

a more advanced version of nostr-proxy would work more like an IRC bouncer where it basically acts like a full client and caches data that it can quickly deliver to you when you connect to it.

nope, i don't think nostr-proxy is working properly for me. something is broken. says it's connected but i'm not seeing all traffic when i use it. going back to regular list of relays for now.

ahh, iris.to talks to a built-in list of proxies to figure out what proxies you're using, lol

trying out nostr-proxy right now

#[0] my NPM seems too new for nostr-proxy. complaining about "link:" being an invalid URL and Google tells me it's been replaced with "file:" in newer NPM versions.

is anybody using this relay proxy, and is it reliable or is it buggy?

GitHub

GitHub - Dolu89/nostr-proxy: Nostr proxy: save you WS connections

Nostr proxy: save you WS connections. Contribute to Dolu89/nostr-proxy development by creating an account on GitHub.

i remember when i tried to sound cool, but it's so much easier to just talk plainly. this probably makes me a boring adult.

would DNS still lack the ability to push updates downstream if we had designed it from scratch today? if an industry committee sat down to redesign it today, i think they'd make a few changes. with that said, DNS is a very versatile protocol.

if you're curious why i own a domain name tigerville.no, it's for the media stuff i make, so it's an unofficial label - Tigerville Entertainment. the name is from the Norwegian nickname of the city of Oslo - Tigerstaden - the tiger city - it's an old name and was originally used in a negative sense (tigers are ferocious) but nowadays it's more like "eyyy it's tiger town!"

there, now i should be appearing as thor@tigerville.no. not quite working locally yet because i accidentally performed a DNS query from my ISP before setting the correct A record, but i can see that it works on 5G from my phone.

setting up NIP-05 on my own domain right now.

oh man, iris.to is pretty storage hungry indeed