It’s the “change your password often odyssey” 2.0. If it is safe, it is safe, it doesn’t become unsafe after an arbitrary period of time (if the admin takes care and revokes compromised certs). If it is unsafe by design, the design flaw should be fixed, no?
Or am I missing the point?
But what is their motivation to buy servers and rent bandwidth if they already got the money but can’t expect another payment?
Death of the universe? No, more like the end of civilization if things around us change too much too fast.
What do they gain if they get paid once but have to provide services forever? What is their business plan/ model?
Thanks. I looked into the demo. When would you recommend pdfding over paperless ngx? It looks like easy sharing and annotations are focused. Tagging is a feature which both tools share.
At first I thought it would be a tool like pdf24 (cutting, merging, editing PDFs).
I would get some cheap maybe even used X86 hardware to start with. Depending on your backup needs, you might need more than one M2 or SATA port. If you plan to use it as an always on device, I would keep the power consumption in mind. A celeron N could be the way. The cpu processing power is, in my experience, not the limiting factor for a self-hosted environment. Give it lots of RAM, every virtual machine and every running service needs space.
Using arm, like a Raspberry Pi, is not bad if you can find all your Docker images and binaries, compiled for this platform. I went away from it.
There are many possible distributions and software you could use, it really depends on personal preference.
Thanks.:)
Stoat.
https://stoat.chat/
https://github.com/stoatchat
Looks like a self hostable chat server. The server is written in rust and the clients in typescript and nodejs. It has client implementations for android, iOS, web, electron (win, linux, macos; x64 + arm). Text only, voice is planned.
I would have appreciated a short description about the product in op, neither stoat nor revolt are particularly helpful to guess what’s it used for.
You can never be sure. Regressions do happen.
First evaluate it on your test setup.
— useless hint of the day
Some fs can do snapshotting (btrfs, zfs,…). Second best would be a current backup to restore from.
rsnapshot is a script for the purpose of repeatedly creating deduplicated copies (hardlinks) for one or more directories. You can chose how many hourly, daily, weekly,… copies you’d like to keep and it removes outdated copies automatically. It wraps rsync and ssh (public key auth) which need to be configured before.
Docker and docker compose should work within macos, or not? (its a unix after all) you could setup a test environment there (jellyfin, navidrome, nextcloud and the like). I’m not sure which iMac… they use arm and RISC processors in some of them I heard. It is possible you won’t find docker-images which are made for these processors. Amd64 (Intel, amd) is the least problematic in this regard.
For always on services (like filesharing or nas) a low power device would be good (a used raspberry. or celeron n powered all-in-one device if you want to have an UEFI capable and amd64 compatible platform with sata, more LAN ports and m.2.)
VPN and maybe a parrot are recommended too. ;)
Edit:
For streaming maybe a VPN / anonymizing proxy is sufficient. In some countries even this shouldn’t be necessary but it doesn’t hurt. If you pay for illegal streaming they might catch you via the money trail when the platform is seized. But i doubt it that they care about the customers, they should just be after the providing party.
Debian + LVM + Incus :)
If your box isn’t globally addressable (because of NAT), your box can’t be connected to. It works one way only, from the inside out - because the NAT-router keeps track of the connections your box makes to globally addressable hosts and forwards reply packages back to your box.
You could use IPv6 which because of the vast amounts of ipv6-addresses, eliminates the need for NAT. Or you could use a VPN or a tunneling service which gives you a dedicated IP. Or port forwarding from a globally addressable host. Either self hosted or as a service. Switch to an ISP which doesn’t do CGNAT.
In short: ipv6 is easiest.:)
Edit: does anybody know if a non addressable seed box gets info about interested and globally addressable peers somehow (either tracker or tracker-less) so it can initiate a TCP connection to those peers? Are there resources to read up in that topic?
They rent you DVDs and Blu-rays via postal delivery. I think.
The h4 already can be a managed switch itself (2" 2,5gbit + 4*1gbit with the nic addon.) if you want it to be one. Linux as the host OS (VLANs, bridges) - netplan works well for me. Some VMs and containers on top (lxd, incus, some use proxmox) for router/ firewall/ vpn-gateway (opnsense, ipfire,…) and other functionality which you don’t want to run on the host OS directly. The cpu is fast enough to run all your services at once. It all comes down to RAM.
IMO there is not one right way. It all depends on what you want to achieve. Also a lot depends on, whether you want results fast or if you enjoy the tinkering while learning.
clippy profile picture
So that I will get ads for office products?
Arr-ight.
Moot point!
You could still get certificates for other people’s domains from Honest Ahmed 's used cars and totally trustworthy CA or so. But that’s another story. (there are A LOT of trusted CAs in everybody OS and browser. Do you know and trust them all?)