Checking out the Lemmy side of the sea—

  • 0 Posts
  • 56 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle

  • 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 can’t directly answer the question, as I don’t use one. But I would like to mention that I put on a pair of joystick caps which are frankly pretty thin layers of silicon all things considered, and now the Deck won’t fit inside the case unless I firmly hold it closed and then pull the zipper.

    The case is designed to fit it very snugly, it would seem! But third-party cases usually have more give inside for covers and joystick caps etc.







  • I use it almost daily when in bed and thinking of some project or the other—I like to think in text—but don’t want to bring up my notetaker and getting even more distracted.

    And I often get friends and family open one up while troubleshooting their problems. What else would I use, Notepad?

    Ultimately, why not? Why do people make little standalone tools like this? For fun, probably. Or because they can. As a learning exercise? And when it has no cost to the developer to maintain, or the user to use. Why would I even try to second-guess their motivation?




  • The city (and district) I live in still has its name spelled incredibly wrong, and has had so for the past decade.

    You cannot select a municipality name. They’re not buildings or roads marked by mere mortals. And what you can’t select you can’t correct. It is just believed that they are always correct. Immaculate. Immutable.

    Every attempt to fix it has failed, from contacting support (as a “premium Google One customer”) or looking for senior Google Maps contributors (all of whom lost all their contacts with “higher up” Googlers when the old map transitioned into new, or just vanished once the forums closed).

    In a country where last mile location is often ambiguous, that Google manages to fail at it on a scale large enough to be visible from space says volumes about how worthless their services are.

    P.S: Yes, of course it’s correctly marked on OSM. And a lot more.