Every time a social media site has offered, pleaded, cajoled or forced me to take a non-chronological timeline, I've refused. And if that refusal eventually becomes impossible (no option, addons no longer work, etc), I take my eyeballs elsewhere.
You're not an edge case. :)
TT-RSS is fantastic, providing you hold your nose and wear as asbestos suit if you ever dare ask a question or raise a valid issue. The dev is... well, I'm not a fan. I won't use it out of principle.
FreshRSS is a good-looking and skinnable alternative with a good Docker image, but I had issues with the inability to flush old items. Has a decent web UI.
These days I'm using Sismics and the web UI.
I migrated away from Evernote a few years ago, where I kept my "paperless life" (PDFs of receipts, bills, etc) and general notes (work, study, etc). Opting to self-host most of the things I can, I moved the notes to Dokuwiki and the rest to what is now Paperless-ngx.
This year I realised that Obsidian suits my needs better than a wiki, so migrated the notes to that. If it's just for your stuff, I'd recommend the same. (Though if you collaborate with anyone, I've heard Notion is a better option specifically for that.) Obsidian has a lot of extensibility, which will steepen the learning curve, but it's worth it.
I sync Obsidian's Vault using my Synology NAS's "Drive" client, and Obsidian works perfectly with Windows, Mac, Linux, and Android. The only shortcoming is iOS (because iOS), though I believe you can work around it using Obsidian Sync or at least one other tool I've seen mentioned. It might also be possible via the Obsidian Git extension, but I've not tried it with iOS and requires (from a self-hosting perspective) that you have a local Git server (for example).
Exposed is the right term. Other than my Wireguard VPN port, everything I have exposed is HTTPS behind Authelia MFA and SWAG.
I'm tempted to switch Wireguard for Tailscale, as the level of logging with WG has always bothered me. Maybe one day.
I used Linuxserver's Docker container of Dokuwiki when I migrated my notes from Evernote a few years ago. It was easy to setup and configure, has a number of plugins that further improve it, and it did the job really well.
I ended up migrating it all to Obsidian this year, as it serves my needs better, but otherwise I'd still be using Dokuwiki.
The Honeynet Project, related to the SANS Institute when I last checked, has a lot of resources on honeypots that are worth a look, if you haven't already.
FWIW, I have an LG LED smart TV (2xHDMI, 1xDVB-S2, WiFi, NIC, etc) and it's only been connected to my network once, for a post-purchase firmware update through my AdGuard Home. WiFi and Ethernet is disabled, and I use it with my Nvidia ShieldTV (Plex*, Netflix, ChromeCast, etc).
I won't let it go online as I expect it already phones home if you let it, and don't imagine LG will be able to resist ad injection into content, like Samsung and others do. So it's an excellent quality dumb TV, which meets my needs perfectly.
*Plex Media Server runs on my NAS. The Shield and my mobile devices are Plex clients.
This is what I did, too. Used Pi-Hole for a year or so, and it required regular tinkering and repairing. Planned to test AGH for a short time in Docker container on a Pi4B, and it's been running that way for 2 years without any issues.
Easier to administer, more functionality and rock solid. I've never looked back.
This last sentence is the crux of the matter. People don't like change, but quickly forget that they spent time learning the site that they're so familiar with.
I've had gitlab/gitlab-ce running on my NAS for 6+ months and it's been reliable, mostly as a central repository and off-device backup. It has CI/CD and other capabilities (gitlab/gitlab-runner, etc), but I've not implemented them.
I have zero problem with curated or algorithmic timelines. I have a 100% problem when there isn't a chronology timeline option.
It's simple really: give me the permanent option of chronological without the dark pattern fuckery of having to reset it periodically, or fuck off forever.
This is pretty much what I'm doing.
If sub.rehab shows 5 threadiverse alternatives for a subreddit, I'll have a look at each and often sub to 2-3 with the highest subscriber count/posts I like. I'll then monitor them over time to see which, if any, to unsub from.
This is what I do. I find keeping 20-odd docker-compose files (almost always static content) backed up to be straightforward.
Each is configured to bring up/down the whole stack in the right order, so any Watchtower-triggered update is seamless. My Gotify container sends me an update every time one changes. I use Portainer to manage them across two devices, but that's just about convenience.
I disable Watchtower for twitchy containers, and handle them manually. For the rest, the only issue I've seen is if there's a major change in how the container/stack is built (a change in database, etc), but that's happened twice and I've been able to recover.
DNS-O-Matic (recommended by CloudFlare, among others) combined with SWAG and Authelia will handle dynamic DNS, reverse proxying, SSL certificates, and MFA. SWAG (nginx, Let's Encrypt and Certbot) and Authelia (MFA) run nicely in a 2 container Docker stack.
Mine have been running for ~18 months on my NAS, though I have a fixed IP so no longer use a DDNS provider.
This is how I do it. It works internally and externally, though it's more than OP needs. :)
To add to what's been said (in case it's useful to others), it's worth looking at SWAG and Authelia to do the proxying for services visible to the Internet. I run them in a Docker container and it does all the proxying, takes care of the SSL certificate and auto-renews it, and adds MFA to the services you run that support it (all browsing, MFA-aware apps, etc).
Another thing I like about SWAG's setup is that you select which services/hostnames you want to expose, name them in the SUBDOMAINS environment variable in Docker (easy to remove one if you take a service down, for maintenance, etc), and then each has its own config file in Nginx's proxy-confs directory that does the https://name.domain -> http://IP:port redirection for that service (e.g. wordpress.subdomain.conf), assuming the traffic has met whatever MFA and geo-whitelisting stuff you have set up.
I also have Cloudflare protecting the traffic (proxying the domain's A record and the wildcard CNAME) to my public address, which adds another layer.
I'm on mas.to. Chose it because it's got a decent UK presence (but isn't a UK-specific server), is quite popular, and the admin runs it well.
Yeah, the container I used requires your Steam ID as an environment variable.
Oops, I think you're right.
Searched "tdr" before replying, and was inexplicably happy. :)
It would be good, but I'm not sure if the expected Multireddit-style behaviour will ever appear on the threadiverse - at least not in the way I use them (I don't subscribe to any sub in a multireddit) - for the same reason that Lists are limited in value on Mastodon: there appears to be a "safety and privacy" policy in place that prevents you from adding accounts to a List that you're not subscribed to.
The only reason I use them is to remove their noise from my feed/timeline. Looking at you, Cory Doctorow... 👀
Maybe it will change, or maybe it will be different here (threadiverse) compared to Mastodon. I guess we'll see.
"Webring".... good lord, that takes me back. :)
Do you have a NAS? It can be a good way to get decent functionality without extra hardware, especially if you're doing proof of concept or temporary stuff.
My self-hosting Docker setup is split between 12 permanent stacks on a Synology DS920+ NAS (with upgraded RAM) and 4 on a Raspberry Pi 4B, using Portainer and its agent on the Pi to manage them. The NAS is also using Synology's Drive (like Dropbox or GDrive) and Photos (like Google Photos).
I've had the NAS running servers for Valheim and VRising in the past, but they require that fewer containers be running, as game servers running on Linux usually have no optimisation and/or are emulating Windows.
If I decide to host a game server again, I'll probably look at a NUC. I've done the DIY mini-ITX route in the past (for an XBMC-based media centre with HDMI output) and it was great, so that's another option.
Yeah, it make for a nice workflow, doesn't it. It doesn't give you the "fully automated" achievement, but it's not much of a chore. :)
Have you considered something like borgbackup? It does good deduplication, so you won't have umpteen copies of unchanged files.
I use it mostly for my daily driver laptop to backup to my NAS, and the Gitlab CE container running on the NAS acts as the equivalent for its local Git repos, which are then straightforward to copy elsewhere. Though haven't got it scripting anything like bouncing containers or DB dumps.
That's a really open-ended question. Depends purely upon your interests and appetite for risk, etc.
Might be worth looking at, from a Docker perspective:
I have in the past run a Valheim server and a VRising server, too. FWIW.