mr47

Depends what you’re transcoding to… show me a CPU (without a built in encoder like recent ones) that can handle a 4K HDR transcode…

That awesomebudget looks nice! I’m more of a beancont/fava guy, and too invested in my setup to try something vastly different - but it sure looks like a cool option for people starting out.

That’s a really nice setup! I run most of my things on a docker swarm (the docker hosts are VMs running on Proxmox hosts), though that was an overkill in retrospect, and causes more problems with no practical advantages.

The range of services I run is similar to yours, but I also have a bunch of services for personal finance (beancont/fava, as well as automatic importers and such), a more extensive media setup (with qBitTorrent and *arr apps), a gitea server, and a vaultwarden instance.

Not OP, but similar setup (Proxmox with docker on a VM). The VM (plus a few LXCs) are backed up daily using the backup built into Proxmox, and those backups are mirrored to the cloud with rclone.

Proxmox backs up the VMs -> backups are uploaded to the cloud.

Hear me out. Why don’t we create a paywalled API for 3rd party apps (like Threads), that will end up costing, say, $20 million annually to use at Meta’s rate… And then use the proceeds to keep all the instances running, and for other shenanigan.

DDR5 is a waste of money in this build. You’re better off switching to DDR4 and using the savings to get a PCIe 4.0 NVMe, such as the 980 Pro. Also, depending on what you do with the PC, 64GB is a complete overkill.

No, you couldn’t. Why are you spreading misinformation? You are posting to your instance, and that’s federated to Threads. Threads isn’t getting any information about you that isn’t publicly available.

If it’s a gaming computer - loading times will be faster. Generally speaking, doubling the rate of an SSD in such a case will provide more tangible benefits than faster RAM or faster CPU. You wouldn’t notice a few FPS difference in a game, but you would notice it loading quicker. In all seriousness, if Zen 4 doesn’t support DDR4 as you say - maybe going with an older gen CPU is a better value for money. I’m sure the performance advantages are not significant (they usually aren’t between subsequent generations), while the savings are - and they can be used to upgrade other parts while staying under budget. I suggested storage, but FWIW this money can just as well go towards better peripherals or a screen.

Yep - and in that case, what you interact is, is your instance. You have no direct interaction with the Threads server, whatsoever. Your instance pulls that content (which is publicly available!), and shows it to you. If you comment on it, you do so on your instance, and it federates that comment back to the Threads instance (where the data federated is publicly available - it’s the content of your comment, and your handle). There’s nothing malicious going on here.

That’s not to say that something bad can’t happen in the long run. E.g., if people get used to content from Threads, and then Threads suddenly stops supporting ActivityPub (or forks it with negative changes), many people might be lured to start using Threads in order to keep accessing its content. That’s definitely a potential issue. But the technical side of federating with Threads is absolutely benign.