Well they will finally sit down and give 1984 a listen. The book was quite strange but it definitely felt like the lengths that our current regime is going to in order to change things and the perception of what has occurred in the past, the double think, the changing of words and verbage in order to change how individuals think about and perceive certain events in real-time it's definitely worth a read.

We are at an infliction point. These next 18 to 24 months will define Bitcoin forever.

It's a world of big blockers or third parties. It can't be both, not in the long run anyway.

I get a total of 15, what’s yours? 😂🫂💜

A good intro 🤙

Nostr, how do you make grilled cheese sandwiches? With butter, olive oil, or mayonnaise? I'm a butter maxi, myself.

I like how Nintendo systems from the 1990s could be put in a shed without air conditioning and survive for five years and still play games. Simple, optimized, robust engineering.

I like how cars from more than ten years ago just work, rather than being a nanny to you while you drive.

Cars, TVs, and all sorts of devices just whine today about problems. We’ve gone backward in some sense.

I’m willing to support brands that make more physical stuff. Already doing that with my next car choice.

The 🇩🇪 German government has officially burned through over half of its original #Bitcoin stack.

Their holdings now stand at 23,800 #Bitcoin 👀

1,000,000 sats bounty to whoever gets amethyst to have the IG UX.

I want to click new post, click the "add image/video button", have the camera open, take the picture or video, have it added to the post. Even better if you bypass the "add to message" step (assume users default file server and not sensitive content).

Another million if you can check the limits on the user's default file server and select a resolution, quality, and frame rate to meet those limits, which bypasses the need to use something like YouCut to compress. Also would give half if once the image/video is taken via amethyst, there's some option to open it in YouCut to do that editing there before going back to amethyst for upload.

We can't expect to draw content creators if the UX remains this shitty.

Must get code merged into release branch and working on graphene. If someone wants to take this up, I'd gladly help with breaking these into smaller chunks as I have PM and dev skills.

I'm sure this will get lost in the typical feed, so if there's a better place to post this, lmk.

What the hell im doing here?

#introductions

Yeah honestly I haven’t thought it through or looked at the old delegation implementation. Was just the first thing in my head, so posed the question.

In a state full central database it’s doable but in nostr it’s way more complicated. Poopies…

people always propose this like an obvious and easy thing, but when you get into the weeds its not. How does querying work? Delegation was something like this, but nostr devs deprecated it because they claimed the query complexity was too high. you had to not only look up a single key, but look up N keys for every possible child key that was used for a users profile.

I personally thought delegation solved it elegantly, as it’s the only way i can think of querying actually working in a multi-key setup, and it doesn’t require clients to change anything to make it work.

password managers generate a unique password for each website. this means if one of your passwords leaks it won't compromise any of your other website logins.

nostr-login is a regression: if you leak your nsec then they have access to every website that you've ever logged in to.

using your npub for logging into everything is a really bad idea security wise, please be conscious of this before implementing or pushing this as a login solution to websites which may contain sensitive information.