• 4 Posts
  • 111 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2025

help-circle
  • despite how they don’t block the triad - but at least PieFed.zip allows individual users to do so, if they wish. And after they figure out how, and that there is a need for such, which nobody it seems will officially recommend to them

    On piefed.zip a new user has hexbear, grad and lemmynsfw put in their account filter. And the welcome DM that is being sent includes info that we do this and how to manage account filters. So as long as the new users read the DM, they from the start have the info how to block instances for themselves

    We don’t defederate often. I think it has been the selling point for some of our users. But PieFed offers much better blocking (compared to Lemmy at the time when I migrated), so we can have an instance for both - those who want everything, and those who don’t

    And btw, effectively speaking we don’t do vote quota on PieFed.zip


  • Migration of user with joined communities etc works. But if you want to migrate whole instance, that won’t be so easy. Mainly because other instances will still think yours is Lemmy. I think that in the long perspective what would be the easiest would be to

    1. create subdomain something(usually people put piefed here).downonthestreet.eu
    2. set up piefed on it (basically a separate instance)
    3. mirror everything from downonthestreeteu (I don’t know how it’s done but it was done for lemm.ee)
    4. migrate your user

    Technically it’s a migration to another instance but you’d keep your history etc








  • I guess you might want to ask this question in one of the self-hosting communities (there’s a bunch that are active, so I’m not linking one)

    But getting back to the topic:

    • jellyfin needs very little
      I’m running mine on a laptop with 4 threads at 2.6GHz and on 8GB of RAM it was fine with a bunch of other stuff running
    • OwnCast
      IDK but for personal use I’d expect to also have low requirements
    • Minecraft server
      That part I’m not sure about. I’d expect it to be a bit more demanding
    • play some steam games
      I understand you’ll be running those on another computer and only streaming via OwnCast, so that goes back to earlier point




  • I think it’s because of the frame reaching half a mm or so above the screen and the battery cover opening up when I drop it.

    I don’t know where and I don’t remember when but I’ve seen some investigation that phones with detachable covers and batteries survive falls better because those moving parts disperse the energy of the fall better, instead of all the shock going into the next stress point - the screen or the glass on the back


  • I don’t intend to overly nit-pick, but since OP said themselves they are new to this: Wine doesn’t translate the exe. It translates system calls from Windows ones to Linux ones. So to have an example: opening a file would be some system call in both systems. But, of course, different because the OSes are different. An exe would be calling Windows one. What WINE/Proton do is get that call and translate it into Linux system call, so that .exe can still open a file, as if it was running in Windows

    As for OPs question: AFAIK when using dx11 you will still in the end be using Vulkan, just through DXVK (as this comment said, translates dx calls into Vulkan calls). Theoretically setting to use Vulkan in the game itself might have less overhead (no DXVK in the middle) but it’s a mixed bag in my experience. I think that Windows Vulkan support is just not yet there, so the in-game code for Vulkan is so-so.
    I second this: you have to check on which setting each game works better



  • 2nd DB would be on the NAS but its not being used by the app, so as long as it’s asynchronous writes, you should be okay

    But then I have to maintain it too. And it will be using RAM that was supposed to only be for servicing RAID. On a platform where RAM can’t grow

    For sure my setup will be growing and changing with time. But ATM this “prod” db lives only on laptop’s SSD


  • replication in the database it self

    AFAIK db replication would require running another db on NAS. Which I tried to avoid

    I have another cronjob that takes a backup into the first database docker init folder. Older backups end with -date so they won’t get picked up by the init script. You can do similar with just docker.

    Yeah, that’s why I’m thinking to do. Have a container that watches changes to db data and rsyncs those into the NAS for safekeeping. My main goal in all of this is so db data won’t die with laptop’s SSD