Scio

I shall pay a tuppence, and not a ha'penny more.

Ironically, because there's no UDP in browsers, we can't actually get proper p2p on the web. WebRTC through centralized coordination servers at best. Protocol Labs has all but given up on this use-case in favor of using some bootstrapped selection of remote helper nodes.

IPFS has absolutely nothing whatsoever to do with Ethereum, or indeed any blockchain. It is a protocol for storing distributing and addressing data by hashes of the content over a peer to peer network.

There is however an initiative to create a commercial market for "pinning*", which is blockchain based. It still has nothing to do with Ethereum, and is a distinct project that uses IPFS rather than being part of the protocol, thankfully. It is also not a "proof of work" sort of waste, but built around proving content that was promised to be stored is actually stored.

Pinning in IPFS is effectively "hosting" data permanently. IPFS is inherently peer to peer: content you access gets added to your local cache and gets served to any peer near you asking for it—like BitTorrent—until it that cache is cleared to make space for new content you access. If nobody keeps a copy of some data you want others to access when your machines are offline, IPFS wouldn't be particularly useful as a CDN. So peers on the network can choose to pin some data, making them exempt from being cleared with cache. It is perfectly possible to offer pinning services that have nothing to do with Filecoin or the blockchain, and those exist already. But the organization developing IPFS wanted an independent blockchain based solution simply because they felt it would scale better and give them a potential way to sustain themselves.

Frankly, it was a bad idea then, as crypto grift was already becoming obvious. And it didn't really take off. But since Filecoin has always been a completely separate thing to IPFS, it doesn't affect how IPFS works in any way, which it continues to do so.

There are many aspects of IPFS the actual protocol that could stand to be improved. But in a lot of ways, it does do many of the things a Fediverse "CDN" should. But that's just the storage layer. Getting even the popular AP servers to agree to implement IPFS is going to be almost as realistic an expectation as getting federated identity working on AP. A personal pessimistic view.

I was hoping the regression introduced in 3.6.19 where the bluetooth earbuds I could connect to just fine before but now only worked once until I reboot the Deck was addressed. But alas...

What if I am robot, Bloomberg? Aren't you one as well? Would you judge the circumstances of your creation?

I use Penpot for every personal project that I can. The new(ish) grid layout is just beautiful. Figma can't do that, can it!

Unfortunately, there's a lot more Penpot can't do that Figma can. And for any reasonable complex project, or commercial ones, I have to go back to it.

Hopefully Penpot catches up soon! My biggest showstopper right now is variable fonts. If it was possible to manually set CSS somehow, maybe that would help bridge the gap a lot!

I installed Bazzite onto the laptops of two friends who have never used Linux before but were getting fed up with Windows.

They've been very happy with it, and I've been very happy not having to worry about hybrid GPU support, or them misconfiguring something to breakage!

I do hope Ororon is the Wayob's chosen for the Night Wind clan and not Citlali 🤞

A way to group organize discover and control access to multiple Rooms.

Here's an extra ironic Elements post describing them: https://element.io/blog/spaces-the-next-frontier/

Still no Spaces support. Even the short list of rooms I've joined are unmanageable when listed flat with no way to identify which Space a #general belongs to

I just want some updated stacks: Bluetooth especially.

The only thing cooler than a living miracle of portable computing is an undead miracle of portable computing that I'd still be playing games on come 2025 🧛