• 0 Posts
  • 120 Comments
Joined 1 year ago
cake
Cake day: December 29th, 2023

help-circle







  • and that all requires organisation, and organisation isn’t free - in fact the structures required to organise things like that are more expensive than the cost actually spent on the problem … you don’t just up and build houses - that’s not how any of this works… ask anyone that’s built a house, and they’re not even doing it on a large scale where complexity goes up significantly, or dealing with distributing money in a manner that they have to makes sure their expenditures are justified rather than just being able to make decisions for themselves









  • i mean, mastodon has also been around for a while… i think there are other things that people have raised - relays being expensive etc - that make it less practically decentralised, however even if you have a single mastodon instance that doesn’t make mastodon not federated

    the potential is there for less centralisation than currently exists, because they’ve been quickly growing and want to control the roll-out (which is why they had closed sign ups for ages)… i don’t think that necessarily makes it bad - we will have to see how things progress

    worth noting too that there’s bridgy fed, so in the future if bsky becomes trash, it should be far easier for people to move to AP

    it’s at least a step up, with enough open that it’ll be easier to convince people to make good (ActivityPub) choices in the future - probably when we stop complaining about why everyone is rushing to bsky and start fixing the UX issues with the fediverse that led to them not using mastodon etc instead


  • Pup Biru@aussie.zonetoLinux@lemmy.mlWhat now as a bcachefs user?
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    2
    ·
    edit-2
    29 days ago

    this is absolutely the issue… the specific thing he did is irrelevant: you play by the rules, or you gtfo… it doesn’t matter how valuable your contributions are, if you can’t treat people with respect that leads to a toxic culture that eats at the project from the inside

    linus was renowned for his insults… he realised (or was told; doesn’t matter at this point) that that behaviour was inappropriate, and his behaviour is now more tempered because it’s important to be able to ensure everyone feels like their work is valued and they’re not just shoveling shit for someone else

    and i say this all as someone who is absolutely ecstatic about the prospect of bcachefs and think that his code is among the most important being contributed in the past years and for the next few years: WE NEED A NEW STABLE FILESYSTEM more than almost anything… but if you allow bad behaviour, it erodes the collaborative culture and you just can not allow that in the largest collaborative software project humanity has ever created


  • I don’t know enough about btrfs to know whether this is feasible but perhaps it could be made a bit more log-structured such that old data is overwritten first which would allow you to simply roll back the filesystem state to a wide range of previous generations, of which some are hopefully not corrupted. You’d then discard the newer generations which would allow you to keep using the filesystem.

    i’m not sure i understand quite what you’re suggesting, but BTRFD is a copy on write filesystem

    so when you write a block, you’re not writing over the old data: you’re writing to empty space, and then BTRFS is marking the old space as unused - or in the case of snapshots, marking it to be kept as old data