There is a subscribe button, it’s directly below the channel name. Up until recently there was a bug in invidious preventing it working but it looks like that’s been resolved now.
There is a subscribe button, it’s directly below the channel name. Up until recently there was a bug in invidious preventing it working but it looks like that’s been resolved now.
It’d be worth checking out Borg as an alternative to rsync. Borg will handle snapshotting, and automatically de-dupe on a block-by-block basis.
I use it for all of my remote backups, and it provides a lot of quality of life stuff that rsync isn’t going to handle.
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, 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.
5 gallons per.hour? The article says 4-6 litres - a little over a gallon.
But their internet is down, so it’ll fail to send to telegram. Realistically it needs to be an external system that is tracking when it receives pings from the home network, so it can show periods where the bash script didn’t ping for a while.
Yep, the app is by far the easiest way to deal with it, and it’s got a great amount of troubleshooting options too.
It’s absurd how much better it makes the vacuums to use. Interaction through the Web UI is just instant, instead of having to bounce to servers halfway around the world before acting on it. It’s the primary decider of which vacuum I consider now.
There are speed and developer experience improvements, and a whole bunch of it is there to optimise for mobile. They have some info in the FAQ on jmap.io. It’s something I won’t 100% take without any consideration - it is written by the fastmail Devs - but a modern stateless protocol is no bad thing.
I’m also on Migadu for email, and I can say the experience has been pretty excellent. They have good instructions for setup stuff, and their pricing model is great. The pricing model has things in common with rsync.net, where they impose a soft limit on storage and reach out if you start exceeding it to talk about upgrading.
I do wonder if other mail providers will at some stage support jmap, it seems like it could take away some frustrations.
ZigBee devices are often able to be used with a 3rd party hub. For instance, all the IKEA stuff works with any standard ZigBee hub. They don’t have a line to the internet if you control the hub.
Yeah, I can second tinycam. It’s very good, and let’s you keep multiple streams available to switch between easily. Great for 3d printer monitoring too.
If you’re just looking to view a stream, mpv on Android should be less glitchy than vlc.
You can use any matrix client you want with it. The closed source one is just making bridging more straightward and adding some little quality of life features.
Luckily, the DMA has a heap of requirements around what their messaging interoperability will have do. For one thing, it will enforce the providers to not downgrade any encryption along the way, so FB etc will have to handle messages without them being decrypted first. There are some great videos that the matrix foundation put on their YouTube channel of talks that go over much of this.
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.
Yeah, I should have clarified that. Hopefully the EU regulation regarding messaging interoperability removes this (currently unavoidable) flaw.
This is using matrix. You can even connect to it from any matrix client.
You can use any matrix client with beeper according to their FAQ. It’s frustrating that they forked element and kept the source code closed, but it is Apache 2.0, so it’s not against the licence terms.
Are you not logged in? You need to have an account logged in, subscriptions are stored server-side.
Edit: Ah, I see that you’ve found that out. Good you got it sorted!