Yes, and I don’t know if it could even be classed as a collaboration. They just buy them and resell them with different firmware, basically?
I assume some part of acceptance is required for that in practice, but it isn’t like Fairphone ever advertised them as an official option (as far as I can tell or saw).
The arch package has to be built somehow. You could look at that packages source to figure out how to manually do it on your system, or wait/hope the deb is being maintained and gets fixed.
It’s likely mostly some plumbing, like a systemd service with it’s configuration, to get the audio routed properly.
If you’re using a keepass database, Keepass2Android can natively sync with many cloud options including self hosted and generic ones, even without specific “companion” apps. That’s what I use. In my case, it’s backed by my NextCloud, but it used to be Google drive before.
Just also sync the file on your PC, merging changes from different clients is part of the keepass database format and “just works”.
Also VaultWarden works great if your can self host it, but I prefer keepass for a variety of features and integrations.
Forgejo was soft forked from Gitea after they went commercial and changed the license (I think). If there aren’t any so far, expect pay walled features eventually.
Forgejo turned into a hard fork after communication issues between the teams. I haven’t looked too deeply into it (as I don’t really care about the fact that it’s a hard fork now). This means while it used to be a drop-in replacement allowing you to go back and forth between the two, it’s now an active conversion, I think.
All normal PCs run CachyOS, includes gaming PCs, laptops and media PCs. All servers run some form of Debian (includes Proxmox) or a dedicated distro for their use (TRUE WAS, technically also Debian based).
Maybe look onto OwnCloud. That’s the project NextCloud was forked from many years ago. It’s very much still around and had a very different philosophy, a much more minimalistic approach with focus on stability. That’s actually the reason the people behind NextCloud had to fork it, cause all their additional features (bloat) wasn’t accepted upstream.
If you just want file sync, the obvious option is SyncThing. It’s established and highly regarded.
I think it’s about printers being required by law to (covertly) watermark copies as such, and make it somewhat traceable. This is supposedly to prevent duplication of protected works (books?) but also to prevent someone just using it to print money (badly, probably).
To my knowledge all major brands incorporate something like this.
The one point that has basically been solved is NAT traversal. Thanks to Wire guard, Tailscale and the like. The relevant parts are open source and can be used basically as a library.
I wish there was one. Thunderbird has given me nothing but issues. KMail is lacking basic features, as does evolution. I obviously haven’t tried them all, but this already took long enough and I’m tired of it.
First my context: I’m also running multiple Proxmox hosts (personal and professional), and havea paperless-ngx instance (personal/family). I tried Firefly, but the effort required to get it to a point where it would be if use to me was too high, so I dropped it. Haven’t used n8n.
For the setup I’d just use the Proxmox community scripts, if you haven’t heard of them. Makes updates trivial and lowers the bar to just trying something to basically zero.
Paperless-ngx I actually use, cause it means I can find something when i need it. It’s all automatically ocr’d and all you have to do is categorize them. With time, it’ll learn and do this for you. You can (manually) setup your scanner to just directly upload files to the “consume” folder and it just works. PC/server power is near irrelevant, it just means OCR takes slightly longer, otherwise it’s a web server. You can run this just fine on a raspberry pi.
I don’t have any real automation setup, so I can’t really comment on that. My advice is to just install it, see what it does and how it feels. Try to anticipate if and how much automation you need. Many aspects of all this are of the “setup once” variety, where once it’s working, you don’t have to touch it again. Try to gauge if the one time effort is worth it for you, then go from there. As I said, it was fine for paperless for me, but not for Firefly (but I might need to revisit this).
DuckDNS had been unreliable when I used it, but it’s been a while. I swapped over to desec.io but their signups aren’t always open. Can highly recommend them though, and they offer many paths to update the IP, including DynDNS(2) protocol or just ddclient.
Also works with certbot for Let’s encrypt certificates using dns challenge.
Never run something like Vaultwarden with unencrypted traffic. Throwing in a self signed cert is basically free insurance. You never know when even in your “trusted network” something starts listening in. Just why risk it?
Yes, but it isn’t available (yet). The pebble 2 duo does not, but it has already shipped. I don’t know how many are still available and/or will be made.
Currently the app also has zero support for anything health-related, including sleep. If that will be fixed by the time the pt2 is shipping, who knows. This is probably not a huge problem for op, as he’s explicitly searching for a watch without smartphone reliance.
Even in the old app and on the old pebble watches, anything health related was an afterthought at best, and it also isn’t a focus of it officially. The new ones are using the same OS, so are incredibly similar. Which is generally a good thing, but also includes the lack of features related to anything “health”.
The modern Pebble has no heart rate sensor, and generally no useful exercise monitoring.
Ssh over Internet is fine as long as it’s properly setup (no password auth, root not allowed, etc.). Obviously a VPN is even better.
Or if you have separated your devices into subnets/VLANs. Which becomes more important as your get more hardware that you don’t really trust.
Tailscale is WireGuard under the hood, if you didn’t know. It’s an overlay network that uses WireGuard to make the actual connections, and has some very clever “stuff” to get the clients actually to connect, even if behind firewalls without needing port forwarding.
Using WireGuard directly basically just changes the app you use, which may or may not help with your issues. But the connecting technology is the exact same.
I’d suggest looking into TeamSpeak, like others have mentioned. Trivial to self host, too.
Edit: to be clear, this would cover the voice call aspect of discord, not the chat channels and other community tools. While it’s can do text chat, it’s more of a side feature rather than core. I didn’t think it does images or video, but it’s been a hot minute.
Until very recently, I exclusively used the /56 prefix I get from my ISP exclusively. This is still relatively annoying in my case as this prefix changes at least daily for some reason. Clients get their IP via SLAAC.
I’ve added ULA literally less than a week ago as I have a local reverse proxy I want to handle both local and external request, in both v6 and v4. Obviously more hosts should be accessible from local clients. But I can’t tell local clients apart except by IP, and since the prefix is unstable this would require some sort of hook to update the proxy with that new prefix (might be possible, but seems like a real hassle). So here we are.