Geronimo Wenja

  • 0 Posts
  • 36 Comments
Joined 1 year ago
cake
Cake day: June 5th, 2023

help-circle



  • I had a reasonably good time with it. I had issues with btrfs, which is why I moved off it and went to Fedora IoT for pretty much the same benefits.

    For me, btrfs caused multiple drive corruptions because of unexpected power offs, and I didn’t feel like trying to fix that on the fly - it might have been drives that were incompatible with CoW because of firmware “optimisations” that break if a write isn’t completed prior to power off.

    In general, outside of that, it was pretty solid. I didn’t find much use for the orchestration/setup tooling they include, and I found their documentation pretty sporadic unfortunately. Fedora IoT has the advantage of basically being silverblue, with rpm-ostree, so it’s easy to find people using it and discussing it.


  • Are you expecting sonarr to go after historical stuff? You have to manually request a search for anything added that isn’t being released in the future. Sonarr only automatically checks for new episodes, not old ones. Like others have said, season searches and interactive searches are useful for anything that’s not airing in the future.




  • The existing feature is that only subscribers will see it in feeds, but it can still be searched for or viewed manually. It’s not a private community feature. I’m just planning to add front-end access for the feature that already exists, so that admins don’t have to do API calls to use it.

    I’ll see if there’s any existing discussions about private communities while I’m at it though, it might be something the main devs have an opinion on or plan for.











  • Most of that extra stuff is there to handle user contact privacy and security with the bridges, which is fair. I don’t have any interest in self hosting beepers full setup, I want to get the functionality of multiple messaging services in one client - which I have, with my self-hosted matrix instance and the bridges they help develop and maintain.

    I wish all of it was open source, but I did feel it necessary to head off comments that imply that the entire thing is closed source. Their implementation around dynamic servers and isolated containers spinning up isn’t really the bit that seems relevant regarding user privacy with regards to data scraping or anything. There are a lot of comments in here implying it’s fully proprietary, but there’s a lot more nuance to it than that, as you point out.

    Personally, I think it’d be nice if you could self-host just the bridge instances and connect them with beeper yourself, so that the part that isn’t e2e encrypted is running on software you can validate and hardware you control.