I missed the explanation about this. Can you give more details or indicate where I can read about this project?

Pay attention to the specs on the carrier board. Mine can't do GPS and air quality at the same time even though the addon boards fit.

I couldn’t understand where they were going with all this Hitler stuff until I just overheard someone say, “If you could go back in time and stop Hitler and his atrocities by rigging the election wouldn’t you do it?”

This timeline is crazy y’all.

**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.

Good morning ☕️ ☁️ 🌊 you wonderful Nostr people 🫂💜

#Bitcoin #Coffeechain

Gm #nostr fam

Wishing everyone a beautiful Monday 🤘🏼🫂

#gm #goodmorning #plebchain

Why do they want people to be poor.

The people who print money out of thin air don’t like #bitcoin because they hate you and want you to be poor.

Anyway, good morning.

Gm,

Noticed after asking for feedback, pretty much everyone wants different stuff in an algorithm.

But maybe more importantly, I didn't ask the 99% of people who tried nostr and left, I only asked the 1% of people who stayed and self selected for the current UX

Current nostriches (myself included) like the way nostr works - and so I will focus on building the algos for the people who don't like what we currently have, then people can choose their own UX.

BREAKING 🚨

Donald Trump at McDonalds, says if he doesn’t win can they please reserve a spot for him at the fries station

Nostr needs key rotation like Bluesky, where you can rotate your compromised client key using your compromised master key to a new key, all by just clicking buttons that will instruct a compromised cloud server to perform signatures that no one will ever see and that no other user will ever check.

Without that it will remain an absolute joke.

You can do this with using APRS with a Btech UV-PRO or similar walkie talkie.