Also at @me@social.k3can.us on Mastodon.

  • 2 Posts
  • 80 Comments
Joined 3 years ago
cake
Cake day: June 21st, 2023

help-circle


  • K3CAN@lemmy.radiotoSelfhosted@lemmy.worldRevisiting Rule #3
    link
    fedilink
    English
    arrow-up
    6
    ·
    15 days ago

    I’m a bit torn on the hardware bit, myself.

    On one hand, hardware is a fundamental aspect of self hosting. There’s already a portion of the community who considers self-hosting to include using commercially-hosted cloud services (as long as it’s not Google), so prohibiting hardware discussion just reinforces that concept. Plus, it can be really fun to see what creative hardware people come up. I’m pretty sure I posted about my Fediverse server running on a WiFi router here, for example. The focus was on the unusual hardware, but it was also clearly related to self-hosting.

    On the other hand, looking at what is posted in other communities, I don’t think there’s a ton of value in seeing a dozen photos of a bone-stock rpi or a closed laptop sitting on a desk. Same with the nth post asking if their 30-year-old 1u would be a good choice for Jellyfin; so I see why the rule exists.

    Overall, though, I think hardware should be allowed, but maybe add a rule along the lines of “if you’re posting a question, please include what resources you’ve already reviewed or troubleshooting steps you’ve already taken.”

    Heck, that might be a good rule for all questions, regardless of topic…












  • I’ll second that

    Jellyfin can function as a music server, but it’s definitely a video server first. All the other media (music, books, podcasts, etc) are basically still treated like TV shows when it comes to how they need to be rigidly organized.

    Navidrome on the other hand, can just take a pile of mp3s and sort everything out based on tags. Navidrome can also handle additional artists, so it can understand that “Eminem feat Elton John” isn’t a single artist. That was ultimately what made me switch from Jellyfin.



  • I’m not sure what Steady is, but it sounds like FreshRSS can do what you want. If you can read the articles on the website, then you should be able to use FreshRSS to scrape the site and create a feed from it. For content behind a login, I’m pretty sure FreshRSS can handle basic-auth or you can provide it cookies.

    There’s also KillTheNewsLetter which does what you want the other way, by just converting the emails into an RSS feed. It can be self-hosted, but I haven’t tried it myself, though.