Checking out the Lemmy side of the sea—

  • 0 Posts
  • 29 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 use the AmazFit Band 7, the last sensibly sized watch that exists it often feels like.

    Weather fails to sync, but then it’s probably the least important feature on a watch. The only feature I really wish Gadgetbridge could do that even the official stack can’t is “nap mode”

    As a narcoleptic person still recovering from major depression, I wish I could either press a button to silence the watch and set a “smart alarm” for 30 minutes. Even better if it would turn on automatically if it detects me sleeping during the day!

    The only other thing GB can’t do is stand in for the phone-side ZeppOS API functionality, but who needs that, let’s be honest!

    Fantastic battery life to boot. I have gone two weeks after forgetting to charge it while wearing it almost 24×7!








  • I did in fact use to add large padding to the menus back when it was possible, so I couse use my drawing tablet to navigate bookmarks! But alas…

    I think it’s a bug specific to how Firefox handles menus though. Case in point, it only does this some of the times, usually after two levels. Just a single level, and it stays open, except when the second level is too wide to fit to the space available to the right—

    As I was typing this I realized that is it. It doesn’t work if the new level cannot open to the right of the menu. Then, moving the mouse away slightly closes it. But now that I’ve moved the bookmark menu button to the left, it stays open for four or five levels deep!

    Gotta get used to the new location, but good enough!!

    (I know, I need to sort out my mess of a bookmarks collection. It’s almost two decade old, cut me some slack!)