Fedegenerate

@Fedegenerate@lemmynsfw.com

• ⁨Comment⁩ on ⁨Meta claims torrenting pirated books isn’t illegal without proof of seeding⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  Me? None. But I left room for someone who might.

• ⁨Comment⁩ on ⁨Meta claims torrenting pirated books isn’t illegal without proof of seeding⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  Seeding to ratios is self correcting, in my inexperienced opinion as I only share ISOs.

  Unpopular thing sits on someone’s computer (not mine) for ages just happily waiting until it’s useful. Popular thing is in and out. Purely for files intended to be churned; try a distro (in facebooks case a book) use it, and delete it.

  1:3 could be said to be a minimum (1 for to pay back, 1 to pay forward, and 1 to pay for a leecher)

  Things that are going to be archived can be set as limitless as long as strain on hardware can be tolerated.

• ⁨Comment⁩ on ⁨Amazon is changing what is written in books⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  I’m glad I’ve already pulled my audible library, didn’t have many ebooks. I’m moving to librofm this month I think.

• ⁨Comment⁩ on ⁨are terfs actual feminists or do most transphobic women just call themselves that?⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  History is what it is. Reality is what it is. It won’t be productive while you imagine to only be a tune in my head and result to insults.

• ⁨Comment⁩ on ⁨are terfs actual feminists or do most transphobic women just call themselves that?⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  As predicted, not going to be a productive conversation.

• ⁨Comment⁩ on ⁨are terfs actual feminists or do most transphobic women just call themselves that?⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  Same with those civil rights people, they were always marching, and shouting, and angry at an unjust system, and scared of police beatings. Always complaining about lynchings and how they were oppressed. So scared and hate filled.

  Funny how history rhymes.

• ⁨Comment⁩ on ⁨Introducing Pi-hole v6⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  Update went fine on a bare metal install. Customising the webUI port is a little easier now, instead of editing lighttdp.conf I think you can do it in the UI.

  I struggled to find some settings, I looked for ages for the API token. Found it in all settings: expert scroll for half a mile down the webUI API section.

  I have an lxc and docker container to go.

  Also, struggled with adding CNAMES in bulk, I thought you could do that in the old UI. You might be able to in the new UI. I just 'one by one’d them.

• ⁨Comment⁩ on ⁨What does the 3-2-1 rule look like for you?⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  My main storage is a mirrored pair of HDD. Versioning is handled here.

  It Syncthings an “important” folder to a local back up only 1 HDD.

  The local Backup Syncthings to my parents house with 1 SSD.

  My setup can be better, if I put the versioning on my local backup it’d free space on my main storage. I could migrate to a dedicated backup software, Borg maybe, over syncthing. But Syncthing I knew and understood when I was slapdashing this together. It’s a problem for future me.

• ⁨Comment⁩ on ⁨What's up, selfhosters? - Sunday thread⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

  My big problem is remote stuff. None of my users have aftermarket routers to easily manipulate their DNS. One has an android modem thing which is hot garbage.

  Chrome, the people’s browser of choice, really, really hates http so I’m putting them on my garbage ######.xyz domain. I had plans to one day deal with Https, just not this day. Locally I just use the domain for vaultwarden so the domain didn’t matter. But if people are going to be using it then I’ll have to get a more memorable one.

  System updates have been a faff. I’m 'ssh’ing over tailscale. When tailscale updates it kicks me out, naturally. Which interrupts the session, naturally. Which stops the update, naturally. Also, it fucks up dkpg. I’ll learn to update in background one day, or include tailscale in the unattended-upgrades. Honestly, I should put everything into unattended-upgrades.

  Locally works as intended though, so that’s nice.

• ⁨Comment⁩ on ⁨Landing page for all my services⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

  In that case. Homarr is awesome, no complaints.

  I probably won’t retroact this, my family aren’t going to explore and it was more to keep them on their specific homepage and stop them getting lost. New users will be locked to their specific page, I don’t expect they’ll ever go exploring to find out.

• ⁨Comment⁩ on ⁨Landing page for all my services⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

  +1 for Homarr. I didn’t need to learn how to write any configs. Everything can be setup in realtime, in the GUI, and is immediately testable. Homarr brought a homepage down to my skill level.

  My only wish is to lock homepages behind user permissions but it’s fine, my family friends don’t intend to explore, just to get to where they’re going.

• ⁨Comment⁩ on ⁨How do you keep up?⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:

  That was my conclusion as well, however I am at work and it’s not appropriate to be reading docker documentation. Thank you for the write up.

• ⁨Comment⁩ on ⁨How do you keep up?⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:

  I am not the person to be asking, I am no docker expert. It’s is my understanding depends_on: defines starting order. Once a service is started, it’s started. If it has an internal check for “healthy” I believe watchtower will restart unhealthy containers.

  This is blind leading the blind though, I would check the documentation if using watchtower. We should both go read the “depends on” documents as we both use it.

• ⁨Comment⁩ on ⁨How do you keep up?⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:

  It’s Watchtower that I had problems with because of what you described. Watchtower will drop your microservice, say a database to update it and then not reset the things that are dependent on it. It can be great just not in the ham fisted way I used it.

  Uptime Kuma can alert you when a service goes down. I am constantly in my Homarr homepage that tells me if it can’t ping a service, then I go investigating.

  I get that it’s scary, and after my Watchtower trauma I was hesitant to go automatic too. But, I’m managing 5 machines now, and scaling by getting more so I have to think about scale.

• ⁨Comment⁩ on ⁨How do you keep up?⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:

  I’ve encountered that before with Watchtower updating parts of a serrvice and breaking everything the whole stack. But automating a stack update, as opposed to a service update, should mitigate all of that.

  Most of my stacks are stable so aside from breaking changes I should be fine. If I hit a breaking change, I keep backups, I’ll rebuild and update manually. I think that’ll be a net time save over all.

  I keep two docker lxcs, one for arrs and one for everything else. I might make a third lxc for things that currently require manual updates. Immich is my only one currently.

• ⁨Comment⁩ on ⁨Japan could finally face its own #MeToo crisis⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:

  “#MeToo crisis” is a strange way of putting “sexual assaulters experiencing any consequences at all”. Like it’s blaming the people saying #metoo instead of the sex pests.

• ⁨Comment⁩ on ⁨How do you keep up?⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:

  Release: stable

  Keep the updates as hands off as possible. Docker compose, TTecks lxc updater.

  I come through once a week or so to update the stacks, I come through once a month or so to update the machines. Total time updating is 3hrs a month, I could drop that a lot when I get around to writing some scripts to update docker images.

  Minimise attack surface and outsource security. I have nothing at all open to the internet, I use Tailscale to create tunnels. I’m trusting my security to Tailscale but they are much, much, better at it than I am.

• ⁨Comment⁩ on ⁨What do you use for notes?⁩ ⁨⁨4⁩ ⁨weeks⁩ ago⁩:

  I use Joplin for day-to-day: to-dos, journals etc. I like Joplin, but I haven’t tried the others. I tend to be sticky with services, if something “works” I don’t go looking for better. Only when I have a specific problem I can’t solve do I branch out.

  I use bookstack for documentation on the server, faqs guides, updates etc. perhaps that works for others. The lack of android app is what moved me to Joplin.

• ⁨Comment⁩ on ⁨What are your Homelab goals for 2025?⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Momentum really. I’m on NPM now, it works and it’s great. I didn’t much thought into it. I’m generally happy with npm, it’s mostly just something to learn next and plain nginx made sense.

• ⁨Comment⁩ on ⁨AI Generated X⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  AI doesn’t need to be “hallucinationless” to be useful. It just needs to make less mistakes than the average creator. Which isn’t that high a bar.

• ⁨Comment⁩ on ⁨What are your Homelab goals for 2025?⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Get a domain and set about moving over to HTTPS with Let’s encrypt and Nginx.

  Learn to write an Nginx config. NPM just works so good though.

  Fix my permission issues. I have my media zpool on 777 so all the LXCs work and I have to run Libation in a VM as root. I’ve been banging my head against this on and off for a while.

  Figure out why paperless isn’t saving to the correct place. Also, figure out where Paperless is saving to.

  Containerise Libation.

  I give friends and family access to my server via a relay, just a raspberry pi 0 with Tailscale, pihole and nginx on it. I have reasons for going this route. Anyways, get a couple more of those into the wild. Also streamline the process somewhat.

• ⁨Comment⁩ on ⁨Post your setup. no matter how uggo⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  A mini pc, a raspberry pi 4, 3usb HDD (28tb mirrored and a 1tb for local back up), some Netgear router, a whole lot of spaghetti.

• ⁨Comment⁩ on ⁨Set up Tailscale with NGINX Proxy Manager⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  Oh, routing, I remember watching an “off site back up” video where they set up IP tables, or IP forwarding, or some such, so when their parents tried to access jellyfin locally it was routed over tailscale. Maybe I’m misremembering though, I’m not confident enough to start thinking about it seriously, so I logged it as “that’s possible” and moved on.

  That way I just have to keep one instance of jellyfin/immich/etc up to date. It’s all a bit beyond my ken currently but it’s the way I’m trying to head. At least until I learn a better way.

  Ideally, I give someone a pi all set up. They plug it in go to service.domain.xyz and it routes to me. Or even IP:Port would be fine, I’ll write them down and stick it to their fridge.

  My parents and I run each others’ off-site back up (tailscale-syncthing), but their photo and media services are independent from mine. I just back up their important data, and they return the favour, but we can’t access or share anything.

  Guides like yours are great for showing what’s possible. I often find myself not knowing what I don’t know so don’t really know where to start learning what I need to learn.

• ⁨Comment⁩ on ⁨Set up Tailscale with NGINX Proxy Manager⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  What a write up, thank you for documenting this.

  I understand a lot of people in this hobby do it professionally too, so a lot is assumed to be common knowledge us outsiders just don’t have.

  While my system of using tailscale’s magic dns to use lxc:port works fine for my fiancée and I, expanding this a family wide system would prove challenging.

  So this guide is next step. I could send my fiancée to <home.domain.xyz> and it’ll take her to homarr, or <jellyseerr.domain.xyz>

  The ultimate dream would be to give family members a pi zero and a <home.domain.xyz> and then run a family jellyfin/immich.

• ⁨Comment⁩ on ⁨How to talk about the PM of the UK.⁩ ⁨⁨7⁩ ⁨months⁩ ago⁩:

  You gotta TAWK TUAH to get to know 'er.

• ⁨Comment⁩ on ⁨Looking for MiTV box replacement⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  The firestick is what I chose as my TV’s, a 10yo LG, jellyfin client. Works as intended, better really. One day I’ll block the stick’s internet connection, and it’ll be the almost perfect device, in that it plays almost anything natively. My server is a rpi4 so anything I can do to stop transcoding, I do.

• ⁨Comment⁩ on ⁨Recommendations for Hardware for Physical Media/Jellyfin Server⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  Aoostar n100 2 Bay nas is what I’m currently thinking about. Or the same device but rebadged.

  Pros: n100 for quicksync. 2 bays of HDD for media storage. Low power @ idle. Cheap for a box with av1 encoding + sata storage. All relevant codes included. High WAF compared to other HTPCs

  Downsides: Unknown brand for build quality and bios updates. General Chinese security anxieties. Idle power, while low, is higher than other n100 options. Fan isn’t pwm. Personally don’t like the aesthetics.

• ⁨Comment⁩ on ⁨Recommendations for RaspberryPI 4B case?⁩ ⁨⁨10⁩ ⁨months⁩ ago⁩:

  Personally running an Argon Neo on the pi 4, zero complaints. Flirc is better looking by half (imho), but the Neo out performs it thermally (with the cover off).

  I’m running it as a pihole/jellyfin&servarr passively cooled with zero problems.

• ⁨Comment⁩ on ⁨What's the deal with Docker?⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  I guessed it was a “once bitten twice shy” kind of thing. This is all a hobby to me so the cost-benefit, I think, is vastly different, nothing on my setup is critical. Keeping all those records and up to date on what version everything is on, and when updates are available and what those updates do and… sound like a whole lot of effort when currently my efforts can be better spent in other areas.

  In my arrogance I just installed Watchtower, accepted it can all come crashing down. When that happens I’ll probably realise it’s not so much effort after all.

  That said I’m currently learning, so if something is going to be breaking my stuff, it’s probably going to be me and not an update. Not to discredit your comment, it was informative and useful.

• ⁨Comment⁩ on ⁨What's the deal with Docker?⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  When I asked this question"

  So there are many reasons, and this is something I nowadays almost always do. But keep in mind that some of us have used Docker for our applications at work for over half a decade now. Some of these points might be relevant to you, others might seem or be unimportant.

  • The first and most important thing you gain is a declarative way to describe the environment (OS, dependencies, environment variables, configuration).

  • Then there is the packaging format. Containers are a way to package an application with its dependencies, and distribute it easily through the docker hub (or other registries). Redeploying is a matter of running a script and specifying the image and the tag (never use latest) of the image. You will never ask yourself again “What did I need to do to install this again? Run some random install.sh script off a github URL?”.

  • Networking with docker is a bit hit and miss, but the big thing about it is that you can have whatever software running on any port inside the container, and expose it on another port on the host. Eg two apps run on port :8080 natively, and one of them will fail to start due to the port being taken. You can keep them running on their preferred ports, but expose one on 18080 and another on 19080 instead.

  • You keep your host simple and empty of installed software and packages. Less of a problem with apps that come packaged as native executables, but there are languages out there which will require you to install a runtime to be able to start the app. Think .NET, Java but there is also Python out there which requires you to install it on the host and have the versions be compatible (there are virtual environments for that but im going into too much detail already).