68k gang incoming

On Nostr lately seeing alot of BitKorn YT "influencers" with 100K plus visitors who still have no clue that YT is about to pull the plug on them.

I am being shadow banned on YouTube. I still have yet to figure out the best option for censorship resistant video hosting that:

-has reach (need to teach newcomers)

-is resilient

-can host large files (both size and length)

Please let me know your thoughts and potential solutions.

68k gang incoming

GM

GM. Nostr CEO caught on camera last night drinking a Pina Colada at Madison Square Garden.

$69,420 plunge protection team reporting for duty 🫡

That theme song lives rent free in my head. Loved that show! He made it 😆

I wanna run a small experiment just because I can and because this is my way to help. My sister found this little fella on her way home crying and not being able to move. Because her heart is too big she took him and got him to a veterinarian who said that the dogo needed to be operated.

My sister and her friends then posted his photo online for funds people would be willing to donate. The operation will cost 776k sats of which they were already able to gather half of it.

I really don't know if I can help with this post but at least I'll try. Every zap I get will be forwarded to the dogo 🐕.

I'll also ask my sister for more pictures so that people don't believe I'm here to milk sats. I'm also zapping myself for visibility.

Thank you fellow nostriches!

Right on schedule! 🫂 stacking freedom 🔮✨️🎶 Pura Vida 💜🎉🐸 Fren & Dan don't forget #Roastr 🙏 Have Fun 🫡🤏

That is not Dan 🫂🔮 #Onlydans 💜🤎 Happy #Nostween 🥂🎶🎃👻🧡💊

that rape sign in the background...

BLOCKFI

ROCKETSHIP

GET ON BOARD

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

I think Bitcoin is going to catch on