Thinking about locking 1 BTC in my nsec as a proof of key safety. If somebody gets my key, they can steal the 1BTC. And if they do, I will know my key has leaked.

On Nostr, unless you monitor your own posts VERY closely, you never know if your key has leaked or not. That creates lots of liabilities for businesses and some risks for users. Adding a value that is appropriate to the size of the account could work as attack notifier. And business might even be able to insure that amount with cyber insurance. 🤔

not sure why I never thought of this before, but the tongue is not the *main* taste sensor. I only just realized this when I held my breath when I accidently drank an old cup of coffee and tasted nothing. smell seems to be the most important thing when it comes to taste.

I mean I get that most people know that holding your breath changes the taste but am I wrong thinking most people think the tongue is used as the main taste sensor.

can't tell if I'm retarded or a genius for this observation

It works via the DHT, like BitTorrent. Basically it’s kinda like a broadcast network hunting for the other user.

So let’s say I connect to 8 random peers on my mobile. Then my hosting machine connects to 8 random peers. When we start up an instance we announce to our peers what our keys are and they add it to their DHT (big hash table of peers basically).

Then when I scan the QR of my hosting machine, I ping out to my nearest 8 peers for anyone who has seen the hosting key. If we share no peers in common, then they pass it on to the next set of peers that they are connected to, then through “6 degrees of Kevin Bacon” we eventually cross on a peer that has heard my request, and also heard the hosting machine’s key earlier. (This might realistically only need one or two hops, maybe the DHT of my nearest node already has the update from the host, but not necessary)

Then when I find my host via mobile (this is where I’m less certain about specifics) then both machines do a “hole punching” method where the host and the mobile both try to establish connections from either direction using any available port. Again, a kind of “guess and check” method not so unlike finding a peer with random broadcasting. Then the connection is established, keys exchanged, and viola, P2P direct encrypted connection for whatever you want to do.

There are probably more specifics that I’m missing, but as I understand it, this is the general idea. Hope this helps.

Starlink

“Yes I’m happy” ? wtf kind of evil is this?

Plex is slowly turning into being more reliant on their own central services. I'm a lifetime member, but it made sense to move to Jellyfin.

I was thinking the app could also include a tool to reduce the size of a pfp and then you could send it to the person and ask them to update their profile

Has anyone made an app that displays the size of the profile pics of everyone you follow? nostr:note1uhqcavg3mea97zl5uxmkyf5h295judrj9pk9wmumv34npwxem2tqr9pr4t

Folks, check the size of your profile image. Many folks are using massive 10MB gifs, some 50MB gifs.

This takes seconds to load on mobile if it loads at all.

Your readers are wasting a lot of data simply trying to download your profile picture before reading your post.

Just as a reference, my profile pic is 800x800 pixels (which is super high resolution) and only consumes 57kb.

genuinely curious why, i haven’t met anyone who likes inapp browsers before

Informal poll: my auto insurance premium just renewed, and 2x’d almost to the bip over last year. Anyone else in the US seeing this, or did I get rugged?

This is a known capability issue between CLN and Phoenix.

I'm using the new 0.8.5 (so not the beta) but it claims to handle Bolt 12. The offer is begin found from your TXT record, but Core Lightning is complaining when it tries to decode the offer:

offer: Unparsable offer: Offer does not contain a description: invalid token "lno1zrxq8pjw7qjlm68mtp7e3yvxee4y5xrgjhhyf2fxhlphpckrvevh50u0qv269gw5jl4r3tzduka09pps9rufy7dw8rjl957m6g3t5d5e8gyhcqsrxaemp0q929hz2869l23tgrftggk7wry08aptcu2ccey93xhesefqqvev8d3kh0yk2m3w7xc5fn3h9pkvmj20u53rhakpzuge5e7ccy52gcq7hpf5y866vlkpculf38mn4lyrqkyvqtmrz3hy0desrnzrpvjgm6d57t5y24h97ls2xme3nwk8rrz4dqp52qqsy25a00kv770lqyd9qdj3nu7665"

I also tried it directly from lightning-cli to make sure it was not a Zeus issue.