• 2 Posts
  • 26 Comments
Joined 1 year ago
cake
Cake day: July 9th, 2023

help-circle



  • From a technical point of view, I’d rather Lemmy didn’t federate except with itself, and maybe possibly also with similar networks, but only as long as that doesn’t hold Lemmy back from doing its own thing.

    Getting ActivityPub federation to work reliably between Lemmy instances alone is already proving challenging for developers.

    From a personal point of view, I have zero interest in what I consider a shit paradigm of social communication. The “micro” lie in micro-blogging, as you quickly conceded, is long gone. The interface is horrible for effective exchange of well-thought ideas. The social networks formed are hypernormalized echo chambers of unhinged ranting faux intellectuals and champagne activists, usually led by a cult of personality or two who are tasked with making sure the one-upping posturing game continues forever.

    When you are about to "micro"blog, presumably you will be writing something coherent enough that it relates to a certain subject of interest to a section of the public. It is also presumably meant to be viewable by the public since you’re not sharing it in a private group chat.

    If that’s the case, there should be a community in Lemmy where those interested in that subject congregate. That community would either be low-traffic, then you can make your "micro"blog a post there breathing more live into it. Or it would be a high-traffic one, in that case a lounge/chat/MegaThread post should exist where you can chat with people interested in that subject, in an interface that actually facilitates good discussion.



  • Imagine if media in Lemmy was all hosted in a distributed network filesystem like Iroh, where instances only function as inserters and exit nodes for that media.

    This way, smaller instances can have a smaller cache corresponding to the media that was actually needed by it (recently). And independent peers can help by participating in the distributed file-system network without running instances themselves.







  • Good, because I speak Rust, so, if there is an itch to scratch, I will scratch it, even though I’m not a UI guy.

    I tried running the UI yesterday standalone and had ‘error loading’ message or something like that.

    btw, mentioning needing ‘…/lemmy’ available in path, and needing the wasm target installed (via rustup target install wasm32-unknown-unknown) may help non-rustaceans in particular, if added to the contributing instructions.

    Also, the UI was listening on *:1237, not just localhost, so maybe a WARNING regarding that is advisable, together with explaining the purpose behind leptos also listening to port 3001.









  • Your information is a few years outdated. lineageOS neither comes rooted, nor does it offer a native way to root anymore. Magisk became a thing with a whole community around it. It’s an unlocked bootloader hider, root manager (and hider), and a system patcher, all wrapped up in one tool.

    With Magisk, you give root access to the apps that need it, hide root ability from apps that require non-root devices (those apps do that by pretending to need root). Also, the Magisk app can rename itself, which is important as some apps check against the name itself.

    The future challenge is with Google trying to force hardware identification (Apple style). I have not been following developments regarding that though, since as others mentioned, my X years old phone is still serving me perfectly, and I have no intention to upgrade any time soon.