odd, not having that issue at all, What client are you using?

yes

You do need to ssh into the server to install simpleproxy but it explains it well in the directions on the application

Just used the about tab on the application and Bitcoin Mechanics note from a few days ago

Got my BitAxe connected up to my DATUM Gateway on my Start9 server. Pretty freaking cool.

Getting zap ⚡️ notifications?

Got my BitAxe connected up to my DATUM Gateway on my Start9 server. Pretty freaking cool.

Picked up more Bitcoin miners. I'm bullish.

Testing out a couple Bitcoin miners I picked up p2p thanks to Bitcoin meetups. No kcy miners, hashing for no kyc sats! These will be used for a canola oil immersion hot water heater and a hot air evaporative air conditioner. I've got my work cut out for me this winter. Best way, in my opinion, to use leverage in Bitcoin is with miners. I'm longing my longs.

#bitcoin #bitcoinmining #bitcoinmeetup #bitcoinculture #plebminer #meshtadel #homemining

What is Pokey? Can you share link please?

Did this help? Did you get a notification?

**Security Update**

I've got some bad news for you guys. This morning, as I was adding error handling to flotilla, I discovered that Coracle has been sending user session objects to bugsnag when reporting errors.

Who is affected: Users who triggered an error in Coracle while signed in with their private key, since December 5th 2023.

What I've done:

- I immediately released a new version of Coracle, both to web and to zap.store

- I have deleted the affected apks from my releases

- I have deleted all my error data from bugsnag

- I have deleted my bugsnag project and rotated my api key, so lingering error reports will be dropped

- I have audited my code for use of the session object to ensure nothing else like this is happening

What you should do:

- If you're logged in with your private key, log out

- Hard refresh the page to ensure you have the latest version of Coracle

The bottom line is that if you signed in to Coracle with your private key, it has been shared with me and with bugsnag. In practical terms, your keys should still be secure, since they were sent over TLS, and have been deleted. But there is no guarantee I can offer that they are in fact gone.

I take my users' privacy seriously. My error reporting implementation doesn't record user IPs, it redacts identifying data, and it allows users to opt-out. I also warn the user when they attempt to enter an nsec into a text field. In this case, I simply screwed up, and I sincerely apologize. Reply to this note if you have any questions.

You dish out love like you knew you only had a few months left with us.

Farewell.

May your next life be filled with love like this one.

The two types of people when I explain how Amethyst works

What if nostr had a halving like bitcoin?

A crazy thought experiment

(And I know it'll probably never happen - for a variety of reasons - but still fun to think about)

What if nostr following the same code as bitcoin and half the npubs got cut in half every four years?

The bottom 50% of activity gets snipped

Making npubs scarce and valuable

Imagine a scarce communication layer combined with a scarce money layer

Scarcity creates abundance