• 0 Posts
  • 20 Comments
Joined 3 months ago
cake
Cake day: August 15th, 2024

help-circle
  • My true hell would be instances only federating explicitly through whitelist. If what the other reply I received about Mastodon is correct, and if Lemmy behaves similary, then they operate on an implicit auto-federation with every other instance. Actual transaction of data needs to be triggered by some user on that instance reaching out to the other instance, but there’s no need for the instances involved to whitelist one another first. They just do it. To stop the transfer, they have to explicitly defed, which effectively makes it an opt-out system.

    The root comment I initially replied to made it sound, to me, like Mastodon instances choose not to federate with one another. Obviously they aren’t preemptively banning one another, so, I interpreted that to mean Mastodon instances must whitelist one another to connect. But apparently what they actually meant was, “users of Mastodon instances rarely explore outward”? The instances would auto-federate, but in practice, the “crawlers” (the users) aren’t leaving their bubbles often enough to create a critical mass of interconnectedness across the Fediverse?

    The fact we have to have this discussion at all is more proof to my original point regardless. Federation is pure faffery to people who just want a platform that has everything in one place.


  • That sounds worse than I thought it was. I just assumed Mastodon was like Lemmy, where every instance federates with every other instance basically by default and there’s only some high-profile defed exceptions.

    A Fediverse where federations are opt-in instead of opt-out sounds like actual hell. Yeah, more control to instances, hooray, but far less seamless usability for people. The only people you will attract with that model are the ones who think having upwards of seven alts for being in seven different communities isn’t remotely strange or cumbersome. That, and/or self-hosting your own individual instances. Neither of these describe the behavior of the vast majority of Internet users who want to sign up on a platform that just works with one account that can see and interact with everything.




  • pixelscript@lemm.eetoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    17
    arrow-down
    2
    ·
    14 days ago

    I’m pretty sure they’re referring to the concept of defederation and how that can splinter the platform.

    Bluesky is ““federated”” in largely the same ways as Mastodon, but there’s basically one and only one instance anyone cares about. The federation capability is just lip service to the minority of dorks like us who care.

    To the vast majority of Twitter refugees, federation as a concept is not a feature, it’s an irritation.


  • Happy Debian daily driver here. I would never ever recommend raw Debian to a garden variety would-be Linux convert.

    If you think something like Debian is something a Linux illiterate can just pick up and start using proficiently, you’re severely out of touch with how most computer users actually think about their machines. If you even so much as know the name of your file explorer program, you’re in a completely different league.

    Debian prides itself on being a lean, no bloat, and stable environment made only of truly free software (with the ability to opt-in to nonfree software). To people like us, that’s a clean, blank canvas on a rock-solid, reliable foundation that won’t enshittify. But to most people, it’s an austere, outdated, and unfashionable wasteland full of flaky, ugly tooling.

    Debian can be polished to any standard one likes, but you’re expected to do it yourself. Most people just aren’t in the game to play it like that. Debian saddles questions of choice almost no one is asking, or frankly, even knew was a question that was ask*-able*. Mandatory customizeability is a flaw, not a feature.

    I am absolutely team “just steer them to Mint”. All the goodness of Debian snuck into their OS like medicine in a kid’s dessert, wrapped up in something they might actually find palatable. Debian itself can be saved for when, or shall I say if, the user eventually goes poking under the hood to discover how the machine actually ticks.


  • Everything works the same, times of website incompatibility are long gone.

    Not completely true. It’s mostly true. I’ve daily driven Firefox for years, and the number of websites I’ve crossed that wouldn’t function in it correctly but would work just fine in Chrome was very slim… but not zero. Definitely not comparable to the complete shitshow of the 90’s and 00’s. That’s true. But it’s not a completely solved problem.

    And with Mozilla’s leadership practically looking for footguns to play with combined with the threat of Google’s sugar daddy checks drying up soon due to the antitrust suit (how utterly ironic that busting up the monopoly would actually harm the only competition…), that gap can get much worse in very little time if resources to keep full time devs paid disappear.


  • I recently had a rather baffling experience trying to preemptively avoid this by downloading the stupid app right away, only to discover I needed the website version anyway.

    I was attempting to add my Known Traveler Number to an already booked trip with Southwest Airlines, booked by someone else. I was able to link the trip to my account right away in the app, no issue. And I could see the KTN field for my ticket sitting there, empty, greyed-out, and not interactible. I opened up the moble version of their website, completely unsurprised to find it was identical to the app, except for the detail that the KTN field there was functional. Put in the information, changes reflected in the app instantly, and I was in the TAS-pre line that afternoon.

    Why did the two versions obviously built from the same codebase have two different sets of capabilities? Why was the website the more capable of the two this time? I have no clue. All I know is I never want to be a developer at a corporation where I’d have to be responsible for this flavor of trash.







  • The other day I learned that you can just grep an unmounted filesystem device. It will read the entire disk sequentially like it’s one huuuuge file. And it will reveal everything on that disk… whether a file inode points to it or not.

    Used it to recover data from a file I accidentally clobbered with an errant mv command. It’s not reliable, but when you delete a file, it’s usually not truly gone yet… With a little luck, as long as you know a unique snippet that was in it, you can find it again before the space gets something else written there. Don’t even need special recovery tools to do it, just use dd in a for loop to read the disc in chunks that fit in RAM, and grep -a for your data.







  • For me, multimedia is a non-negotiable part of the web experience.

    Yes, I get as annoyed as the next guy when I want, say, a simple tutorial written in a couple paragraphs, but the only ones anyone seem to want to make are eight minute long videos filled with fluff. That sucks. But purposefully excluding it from your protocol because it burned you a fee times is a gross overcorrection in my view.

    I appreciate the Gemini project, I respect its goals, and I am happy that it meets the needs of several people such as yourself. But for me, and I think for a great majority of people who would be potentially interested in its broader goal of simplifying the web but are dealbroken by lack of multimedia capabilities, Gemini will never be anything more than a toy. A quirky little curiosity that will never expand beyond a tiny clique of people who accept Gemini for what it is and are content to only ever see content from that same small pool of people.