Avatar
Mitch
6251161373387b4508b70b379cb5e236dd8c1aea070bebfa053b3fbb6af55e71
Survivin' & Vibin'

Damned the Nile river, which apparently has shifted in the last few thousand years. I've seen good estimates that the Nile was at most a few kms away, at best a few hundred meters. They floated it all into position and used ropes and pulleys for fine tune control.

Short answer: hydraulics

Can someone not just fork core from the previous version and just merge all the other maintenance without the op_return configuration removed?

Fuck around and find meaning

Replying to Avatar waxwing

What surprises me about the tech and developer discussion around embedding data onchain (and OP_RETURN is just a corner of that), is how little of the discussion refers to the ethics.

There's an obvious point, and an obvious (in my opinion, incorrect) counterpoint.

The obvious point is that permissionlessness is central to Bitcoin's nature, and that implies *ethically* you cannot tell people what kinds of transactions are OK, and what are not. There are very substantial *technical* arguments as to why it can't really be prevented, but they are secondary to the ethical one: you don't have the *right* to tell people what transactions they can do.

The obvious counterpoint is that posting anything to the blockchain has a cost for *all* users. That's why we spent 4 years arguing about the limit on the size of blocks. I have no ethical right to tell someone not to publish or mine a block of size 10GB, but it doesn't take long to realize that the costs this imposes on other participants, is too large. In case you think, this argument was straightforward, the big blockers were wrong, don't forget that the resolution, for better or worse, was a compromise: average block size today is often 2x the size before. It was a really difficult argument.

So the counterpoint wins and we have to discuss whether embedding data should be allowed? I say, no, this a fundamentally different discussion. It is not a discussion of *how much computational resource is used in total*, but rather a discussion of *what individual users are using the computational resource FOR*, and that crosses the line into being ethically unacceptable, unequivocally.

I say that the technical awkwardness, or even impossibility, of restricting this behavior in the Bitcoin system is just a byproduct of trying to make Bitcoin do the opposite of what Bitcoin was designed for - censorship resistance.

Best take I've read yet.

I mainly think in pictures. I think being able to communicate without needing language may be the opposite of what you're fearing here.

Often I find myself thinking that many I interact with, myself included, have more to articulate but are unable. That's something that excites me.

Replying to Avatar fiatjaf

In the middle of this interview the host, beginning to grasp the idea of Nostr, says something like: "I like this separation of powers".

It is interesting that it's not hard for people to realize that that a big corporation controlling the "public square" isn't a good thing, but many will have an immediate impulse of trying to fix that situation by coming up with a protocol in which not one company controls everything, but multiple companies.

This seems to be the mindset behind Mastodon, Matrix, Farcaster and Bluesky. They all assume users will be immediately subject to one server, one company, but that there is room for other companies to join and compete for users, or something like that (there are differences in how this plays out between all these protocols). So instead of one "corporate square" controlled by one company you end up (in the best case) with a bunch of private squares that may or may not have communication between them.

Nostr is different because it tries to create a single square that is actually public and infinite in size where any company can open a stand, but also anyone can go and speak to whoever wants to hear without asking for permission from any of these companies, simultaneously any person or organization can find a corner (there are infinite corners) and talk only to a smaller group and so on.

nostr:nevent1qvzqqqqqqypzqh4yvjqytwcl7g3x2hwaxmndemwugdvscfsfp3yxhmecaazsmfdaqydhwumn8ghj7un9d3shjtnhv4ehgetjde38gcewvdhk6tcpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcprpmhxue69uhhyetvv9ujucm4wfex2mn59en8j6f0qqstygzumpxsv2nred6zdamycngfv87v99mvwzn384hshpy7d2vy2fg972myl

Wow

Definitely an understandable take. However, I think Asimov hasany examples of how to do this well-ish. Granted it was for his career but I still feel he stands out. Oddly I find much of his character understanding comes from the main plot of the short story being unfolded as a mystery. We discover both the plot and the character at the same time which makes it feel deeper.

Replying to Avatar MK Fain

All Book Data pulls from Open Library API (https://openlibrary.org/developers/api), and I'm not storing book data to relays besides ISBNs as identifiers on events.

User's events (ex. "Add book to my TBR") are basically a list of the relevant ISBNs, then the app uses the ISBN to fetch the book data from Open library. I am heavily caching the Open Library responses to ISBN lookups in cloudflare to prevent havign to do too many lookups, though.

Its not a perfect system by any means, still lots of issues with searching, etc., but they provide a great service making all their data available to the public for free!

Ah very cool. Thanks for the explanation. Looking forward to using this!

It makes sense if you're the one implementing it/ the one who stands to benefit.

Now those same people must also have a view not longer than their own lifetime and voila you have a justification for the system we have been stuck in.

We are meming our way to the foundation of the most prosperous period in human history.