Avatar
NOSTRPUNK
9e69e420e60df69cd945510882cfe44d91757a2c58d1c21c027a7977d12360c2
Future Dystopian Warlord, & Amateur Boogie Boarder from a timeline where heelys are still cool.

Yes on 3 Florida.

nostr:naddr1qq95zmt9dejx6etww30nxq3qne57gg8xphmfek292yyg9nlyfkgh273vtrguy8qz0fuh05frvrpqxpqqqp65w9naweu

Some asshole was yelling this at 7am at a music festival I was at 15 yrs ago while everyone was trying to recover from the day before.

I guess I never figured out what he meant but maybe you can extrapolate from that context.

google

(original definition)

verb

to throw a girl to the ground and tickle her until she pees (or pukes)

https://www.urbandictionary.com/define.php?term=google

Wake up and

RAGE!!!!!!?

Replying to Avatar hodlbod

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

This is why I burned my doxed/ compromised key to start fresh with this one. Don't be afraid to start over. We are still early. It's easier to rebuild 600 follows now then 1000000 in 10 years.

nostr:nevent1qqsrz6g5ds3dfht4a6zgdt7k593ujhnrz4njn6mke2fmpwxjc3sgafcpzdmhxue69uhhwmm59e6hg7r09ehkuef0qgsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgsrqsqqqqqpahkpn0

My 3-year-old wanted to be a pirate for Halloween.

And I couldn't be more proud.

https://v.nostr.build/WiTsQEBZuyW72HMp.mp4

Before you sign that note, ask yourself: "does this belong in a manifesto?"

If the answer is "no" then you're probably reading this as a screenshot on X or Facebook.

21 sat zaps feels like some empirical bullshit.

Let's go metric and make it a πŸ’―

Only dank notes allowed on my feed.

We must never forget he was doxed by coinbase. Right before he mysteriously died of a heart attack. Healthy and in his mid-thirties.

KYC is murder.

WAKE UP AND RAGE!!!!

Amber it's like a condom for your nsec. You can fuck all these apps without consequences.

I'm writing an article on it now.

Check back later tonight maybe tomorrow.

For some reason I can't view load this post from amethyst. Are you able to read it? From what client?

nostr:naddr1qq9yv6tjwd6zqmn0w3jsygy7d8jzpesd76wdj323pzpvlezdj96h5tzc68ppcqn609mazgmqcgpsgqqqw4rs57fvss

None of these resources about NOSTR were actually ON NOSTR. So I did a thing...

nostr:naddr1qqzkuethvfesygy7d8jzpesd76wdj323pzpvlezdj96h5tzc68ppcqn609mazgmqcgpsgqqqw4rsy7ymu0

Im just a random guy on the internet and I say that's hogwash.

It was just a crutch anyways. We need more businesses to accept the Bitcoin.

Pray for me.

Nothing's wrong except they ate a bag of Takis last night and now it's time to shit. 🌢️🌢️🌢️

Caliente booty hole.

I woke up to an interesting message in my DMs this morning.

Apparently yesterday I answered a question that was meant to be rhetorical. The author of the note took offense as if I was mansplaining to her. Says she's been here for years and I shouldn't open my mouth up to her majesty. As if I was supposed to hear her voice inflection and see her facial expressions through her note on nostr. I was just trying to help. Some of you would know that I've also been here for quite some time under a different npub...

(I rotated keys because I liked The idea of having my key but backed up with a mnemonic phrase which wasn't available when I started as well as the fact I had put my nsec into all these different apps to test them out and wanted to start fresh with an uncompromised key now that Amber is a thing.)

Anyway, I don't think there should be any rules for nostr but a personal rule of mine is rule #62: "Don't take yourself so damn seriously". She's clearly got some things going on so I didn't engage further (every bully has a bully). I just muted the wench & went about my day. Live and let die.

Here's a pair of tits for attention:

You can request it be deleted in some clients.

Most relays will do it. Some may not.

It's the wild West out here.

:peace:

Replying to Avatar Gigi

:peace: just here to test out custom emojis on Yana.

But yeah bitcoin's pretty neat.