Avatar
🤦🏼‍♀️
2f3391fe9799eaa8f59401cc059b447f4922da54d3723a77944f30be809acd4d
nine queers in a trenchcoat, luddite

highlighting Bitcoin is drastic editorializing (obviously). the original study focuses on crypto trading, and does not single out Bitcoin except as an example asset.

the only piece of it that at all correlates with my understanding of Bitcoiners is Machiavellian low time preference.

and Solana is where the real psychopaths are.

GDP is the gotcha. it doesn't measure production, it measures surplus, which is convenient for all those countries that can abuse trade and labor dynamics.

this would be likely different in a fixed money world, but then continuing to think in terms of GDP doesn't make sense.

changing your NIP-05 domain from nosterplebs.com to jesw.xyz seems to me like the best option.

there's some work required on your site, not sure about your hosting situation, but here's a guide that seems to hit all the steps for a few different setups:

https://orangepill.dev/nostr-guides/guide-to-verify-nostr-profile-nip05-identifier-with-your-domain/

what you want to happen is for a client to find what is currently served at https://nostrplebs.com/.well-known/nostr.json?name=mrjakewoodhouse but at your domain.

the name associated with your hex pubkey can be anything, if you also wanted to change that from "mrjakewoodhouse".

i'm not against changing my mind, but LN would have to work drastically differently than it does now.

i can't see that happening, but my disagreement is not with LN users. enjoy your zaps!

Replying to Avatar Guy Swann

Of course. To say one isn’t to concede the other. I think the major trade offs mostly happen at the protocol layer, which much of those issues are being solved very well, it’s simply about extending them up to those who can use them properly.

Again nsec bunker like tools are a great example. Literally all of the tools are there, it’s just never been made intuitive and the edges haven’t been cleaned up. And if that doesn’t happen then there’s no demand from clients to support it. Circular problem.

I think it’s less of a problem of trade offs for a lot of these, and more a problem of people excited to build a tool that they can use, but not interested in building it for someone who doesn’t understand anything about it. Devs I think get lost in chasing the next awesome thing, rather than doing the slow, difficult process of making the last thing built really streamlined, intuitive, and reliable.

Not saying I am not guilty of the same. It’s like building a house but never painting it or putting up trim. It’s just the annoying part of building because it’s slower and it feels like progress isn’t moving at all. But it makes all the difference in the world from the user’s perspective.

I also don’t think we should depend on the devs to do this. I think we need “another layer” of developers, who work with this stuff and try to clean it up for the regular user.

Part of the direction I’m trying to take our team is related to that. Hoping I can help, but I also know how much harder it is to get it done vs *wanting* to make it happen.

you build your own house, and it takes longer than buying a house, and you don't paint it for a good long while and maybe people don't understand the type of person that would live in such a house.

but you're the user of the house. it serves your needs. you can see a lot of people from your windows, and that is fun and exciting.

and then when you have time you can paint it and filigree the edges., or not.

even better, the house that Nostr built has blueprints, that anyone can look at and copy and use, without restriction.

i honestly don't give many fucks about usability beyond this sort of use, as a tool for people that need a Nostr.

if you don't like the state of the tool, or you so very much want it to be better for your needs, great. build your house.

this isn't particularly aimed at you, but i've recognized, or just recently discovered, a trend where some Nostr folks look to a desired future when we'll have more users, more content, more zaps, better users, better content, better UX, better steaks, more steaks, etc.

today i realized exactly how much the nak cli does. it's not hard to use, it's just typing into a program i already have on my computer.

Rabbit exclusively for actual use, posting etc:

https://rabbit.syusui.net

i dabble in other clients but with throwaway npubs.

Replying to Avatar rabble

nostr:npub1gz7uczyg3kvdf8grlwfmllguc3kehrcc05yvnlypkjklptgql5kqa0zkqj yes but not in a way that’s easy to use and makes sense to the users. And we don’t have easy ways to discover them either. Our DVM feeds are slow and only work in a couple of apps. We don’t have good follower suggestions that go beyond showing the most popular people on Nostr.

It’s not about making sure the feature exists, but making sure it’s usable.

the ease of use of bsky has a cost.

good for you.

perhaps you'll notice i am not using LN here either. i *could* take some time to tell you why, but i don't think it would be worth it.

your website shows your NIP-05 identifier--mrjakewoodhouse@nostrplebs.com--but you don't have it attached to your Nostr profile. you should add it.

not sure what client you're using but you should be able to edit your profile and add it.

also IMO it is better to show your raw npub from your personal site. it is easier to search for that on Nostr. the NIP-05 identifier is an extra layer of identification that client software validate for users.

to be completely honest, before i manually validated your NIP-05, i thought this npub was an imposter bot.

Replying to 21823843...

nostr has no global source of truth, and that is a good thing

Out of interest, I follow the progress of a lot of other projects similar to nostr, and a couple links surfaced today:

BlueSky has a big "firehose" connection that streams all updates (new posts, reactions, etc) to subscribers. Unsurprisingly, this is difficult to process except on beefy servers with lots of bandwidth. So, one proposed solution is to strip out all that pesky cryptography (signatures, merkle tree data, etc): https://jazco.dev/2024/09/24/jetstream/

And over on Farcaster, keeping their hubs in sync is too difficult, so they want to make all posts globally sequenced, like a blockchain. The details are still being worked out, but I think it's safe to assume there will be a privileged global sequencer who decides on this ordering (and possibly which posts are included at all): https://github.com/farcasterxyz/protocol/discussions/193

In my opinion, both of these issues are symptoms of an underlying errant philosophy. These projects both want there to be a global source of truth: A single place you can go to guarantee you're seeing all the posts on a thread, from a particular user, etc. On BlueSky that is https://bluesky.app and on Farcaster that is https://warpcast.com .

Advocates of each of these projects of course would dispute this, pointing out that you could always self-host, or somehow avoid depending on their semi-official infrastructure, but the truth is that if you're not on bluesky.app or warpcast.com, you don't exist, and nobody cares that you don't exist.

nostr has eschewed the concept of global source of truth. You can't necessarily be sure you are seeing everything. Conversations may sometimes get fragmented, posts may disappear, and there may be the occasional bout of confusion and chaos. There is no official or semi-official nostr website, app, or relay, and this is a good thing. It means we are actually building a decentralised protocol, not just acting out decentralisation theatre, or pretending we'll get there eventually and that the ends justify the means.

Back when computers were primitive and professional data-centres didn't exist, it was impossible to build mega-apps like Twitter. Protocols had to be decentralised by default -- there was simply no other way. We can learn a lot by looking back to protocols of yesteryear, like Usenet and IRC, and still-popular protocols like email and HTTP. None of these assume global sources of truth, and they are stronger and better for it, as is nostr.

tl;dr of the bsky / Jetstream article:

> If consumers already trust the provider to do validation on their end, they could get by with a much more lightweight data stream.

"the provider" is currently Bluesky. exclusively.

trust?