• 0 Posts
  • 306 Comments
Joined 3 months ago
cake
Cake day: February 5th, 2025

help-circle

  • To put this into perspective for you, if your NAS sits at idle for 90% of the time (probably true) and an older CPU is 50w (kinda high, but maybe) and a newer CPU is 15w, over an entire year it will save you around 305.76 kWh. Average price per kWh in the USA is 12.89¢. So over a year a new CPU can reasonably save you around $39.41. So it’s not nothing, but it’s nothing crazy, but lower idle wattage = lower temp = components last longer, which is the real savings.

    If an older CPU is only gonna last you 5 years, when a new might last 10, you’re going to save almost $400 in energy and generally a CPU today is going to be cheaper than a CPU in 10 years (probably). So it makes sense to spend an extra $200 on a newer CPU and still net a $200 savings over 10 years vs the older CPU.








  • In your experience, what is the best way to go about this?

    RSS feeds are static files with formatted XML list items. When a feed is updated to include a new XML list item, the reader application notifies users who are subscribed that there’s been a change. There are actually no moving parts to RSS feeds, which is what makes them so popular. RSS feed applications simply loads an XML feed and counts the number of XML objects. When the application checks again, if there are new objects, then the feed has been updated and you get your little notification.

    That’s it. It’s a static file (like HTML), and it works like magic. You don’t need any software or libraries to create an RSS feed over and above being able to serve static XML.

    So unless you’re updating your feed several times per day, I would just do it by hand. Maybe write a little helper script to scratch out the formatted XML based on input.

    Do I have to make them myself by hand and put them in an /rss/ directory in the root of my blog?

    You can, but it’s really not necessary. If you check around github you can find a ton of projects that help you create RSS feeds.


  • Because that download would still be illegal

    Of course its still illegal. I’m not saying it’s using a seedbox makes it legal to download illegal torrents. It’s just legal in the country of your seedbox. So if your seedbox provider gets a DMCA notice, they’re going to throw it directly in the trash.

    Additionally, between my seedbox and me, is encrypted. So how would anyone know what I download from my private seedbox? There’s realistically no way to get “caught.” Copyright holders pay people to monitor torrent traffic for people to prosecute and hassle–but the same isn’t true for private servers which encrypt traffic.




  • I paid $100 to play Forza Horizon on my own device too - should that have been free?

    This is a complete false equivalence and I feel that you know that. The idea of a console is to expand it by buying new games. That’s not unexpected.

    Your entire argument seems to be that software should be free

    I am a software developer. The argument isn’t that software should be free. The argument is that this is an exceptionally poor business model and as a developer I’m disgusted that people are defending it. The VC which owns Plex and other VCs will use this “logic” that you have to move the goal posts further, and further, and further, and further until there’s no such thing as free software anymore. And I think that’s fucked up.

    At the end of the day you’re paying twice to avoid buying IP. Just fucking buy the IP if you’re going to be stupid. Movies are like $12. At $250 you’re paying $2.10/mo in addition to your hosting costs.

    Just go buy 20 movies for the same price. It’s so dumb.



  • No other solution exists that is as easy as Plex and as secure as Plex.

    Entrenchment. This is a profoundly absurd statement.

    I paid like $100 for a lifetime Plex Pass like 10 years ago.

    You paid $100 to access software hosted on your own devices. That’s wonderful you think that’s a great idea. I’m sure the Plex devs love you and would kiss you right on the mouth.

    They sign in and they can stream from everyones libraries. No VPNs needed, no other hoops.

    Because you’re vendor locked in… lol.




  • There are two schools of thought, and one of them is insanely wrong.

    The current preferred method (by youngins) for pirating is by using a VPN provider to “hide” your torrent traffic, which is generally valid, but it’s not a silver bullet and it’s a wrong way to think.

    The other is to use a seedbox, which is a remote server hosted in a country that doesn’t recognize piracy as a crime to begin with…

    The choice is clear. Especially when you consider to get a good private VPN you’ll have to pay $5-10/mo. You may as well pay $5-10/mo to commit a crime where no one thinks its a crime, then you never have to worry about it. Using a VPN you can still get caught, it’s just exceptionally rare because conditions have to line up perfectly. But what if your VPN is down, and you accidentally begin a download? You willing to get a $100,000 fine for that?

    Just use a damn seedbox.



  • I started to follow a guide (& doing a bunch of googling + chatGPT) for setting Jellyfin remote access for my parents. And this is where I’m a bit out of my depth […] I have a dynamic IP […] duckDNS path

    Stay away from DuckDNS. Used to be fabulous but now it’s incredibly overused and very unstable. Works, then just stops for a period of time. Check out HurricaneElectric. Any A record can be enabled as DDNS that you can update with just curl. It’s great. I’ve been using them for about 10 years now without issues. They were down one time like… 5 years ago for several hours, and that was it.

    Also as a side note: I see people talk about Caddy as a reverse proxy for extra security, but what does it do?

    This option is nice if you self-host a web server with no bandwidth restriction. You setup caddy, update your DNS to register your home IP on X domain. Point jelly.x.domain to whatever your public IP is, with the port as a reverse proxy, then your IP is reachable via jelly.x.domain but it’s not a great setup for you because of the dynamic IP unless you do a bunch of setup to ensure it routes.

    IMO the best option would be;

    1. Install jellyfin server
    2. Open port 8096 on your router for your jellyfin server IP
    3. Create a jellyfin user for your parents, and enable remote connection
    4. Setup DDNS (I highly suggest he.net) and point your domain to your IP
    5. Setup cron job to update your DDNS record with he.net every hour or so using curl
    6. Setup jellyfin for your parents TV or whatever device they’ll use to watch it
    7. Login and enjoy