At least one great thing about bitwarden, the passwords are stored on each device, so you kind of already have backups. That being said backups for vaultwarden is still beneficial.
At least one great thing about bitwarden, the passwords are stored on each device, so you kind of already have backups. That being said backups for vaultwarden is still beneficial.
I used Google lens. Got stuck afterwards on a chess rule. The captcha rule used the notation for the chess one to complicate it further haha
You can do a few things to reduce interference if the device broadcasting the signal supports it. Unifi APs support these settings. Most routers with WiFi probably do not support transmit power.
Look I’m not a tube expert jeesh.
The internet is just a series of pipes!
Looks like tesla offers a premium subscription for most things and a separate one for the fancy cruise control… So I assume you have an old model or your being a troll?
My car has 6 or 7 subscriptions I believe? I lost count.
Other notable resources:
Hardware accelerated Machine learning requirements
Hardware accelerated Transcoding for videos
You’ll need a stronger CPU (or maybe multiple since you can run machine learning multiple machines) handle the load if not using a supported discrete GPU. Also for transcoding videos if you want to do that you’ll have to look at compatibility of the CPU with what it can encode/decode and what format you want to store.
That being said , it barely use CPU resources with immich 99% of the time with the exception when media is backing up to it.
The client sets up its transcoding profile (like what it supports for direct play, etc for auto transcoding) or the client has to specifically request a different quality. Findroid has had PRs for the second one and I did one of them updating based off the older PRs.
This is because it doesnt support transcoding. It does direct streams only.
There are forejo runners and they seem compatible with a bunch of github actions. I created one that builds a docker image and publishes it on the repo.
Well initial setup was definitely interesting. I didn’t want to expose 8090 and wanted it behind a web proxy and I finally got that working and actually received my first remote crawl overnight. I had to change to 80/443 internally so it would map correctly for p2p connections, public port setting doesn’t apparently cut it. I kinda dislike the whole setup with it micromanaging CPU load, but otherwise it doesn’t seem atrocious for a new peer at least, I guess this and the web proxy problems are likely awkward due to the age of the software.
Lidarr to download music, has Spotify playlist integration, only problem is it pulls by alblum not by song.
LMS to play music, it supports selecting tags to use.
Picard to tag the music. Kinda optional, but using plugins it can pull genre, moods, and BPM, which I liked using to make a smart playlist to get songs I like the sound of without 100% hand picking out of thousands.
There also seems to be a lot of settings so perhaps they had it misconfigured. It also is Java so I wouldn’t put it past it for such a monolith of a Java program to require so much to be performant. Perhaps I’ll try a cluster of them then and see how it fares.
Besides yacy, there is a project to build decentralized apps with search listed as an example. Its very early and nothing is built off of it yet though.
I really want to use this, but from what I read it basically requires a minimum of 20-30GB of RAM to be performant. Also the documentation appears to be a mess and highly outdated. I’d also want to cluster it internally and connect with outside peers still which seems possible, but with the large resource requirement not as feasible with my setup.
Looks like Google cast is the protocol and it’s proprietary, while they offer a SDK, it does not appear to be open source. There is an open source alternative though. https://github.com/MayaPosch/NymphCast/
Isn’t Chromecast proprietary though?
The only time I use caddy is to serve static files… I then put a nginx proxy in front of it to expose it lol
I believe this is one of those Google “F it I am going to make this protocol my own way without anyone else’s input” which results in security concerns and also Mozilla prioritizes it being a browser more.
Searching serial looks like this is still the case. There are security and privacy concerns over it.
https://mozilla.github.io/standards-positions/