Hugo can be as simple as installing it, configuring a site with some yaml that points at a really available theme and writing your markdown content.
It gets admittedly more complex if you're wanting to write your own theme though.
But I think this realistically applies to most all static site generators.
I wonder if they'll replicate the feature where a strange voice whispers your name (amongst other odd sounds) if you're playing in the early hours.
Scared the crap out of me when that happened.
Edit. Evidence https://www.ttlg.com/forums/showthread.php?t=6529 to show I'm not mad.
How about you assume less? I spent 40+ minutes looking for this here, here, here and here and I'm already fairly familiar having done work on two other ActivityPub based projects.
In addition public-addressing (or the lack of use thereof) in no way claims to achieve what you've stated - which is probably why it's not the answer to my query.
Ahh, didn't even know there was a flag for that. I don't suppose you could link to the relevant w3c or FEP for it?
All votes are public, they're literally broadcast to the Fediverse writ large. You vote on something on your server, your server then tells the server owning the thing you voted on and that server then tells anyone who is interested (subscribers on other servers). That way everyone knows that this comment was voted on, but that information is indelibly tied to you - an entity on the Fediverse.
Lemmy devs just chose not to a) show that information in a UI (plenty of other software out there does) and b) not inform people that was the case. Which leads to the whole point of the thread, hiding this from users merely gives a false sense of security.
You say that, but you simply have to be using something that isn't Lemmy and that information is there (doubly so if you're an admin on any of these systems)
Except, if you're using anything other than Lemmy at this point that information is already about. The Likes/Dislikes are considered public information by the protocol. Lemmy devs probably just didn't get around to building out the UI for that before the Reddit APIcolypse.
All your followers would see it and sometimes you don't want replies?
I work for the UK government. Everything my organisation does is licensed in either MIT or OGL (https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/)
Developing code in the open really helps ensure you nail down your secure coding practices.
blocked part of url because I have Kagi rewrite url to redirect to my private Redlib instance
I had no idea this was a thing. Thats going straight on my self-host todo list.
It's the multiple volumes that are throwing it.
You want to mount the drive at /media/HDD1:/media or something like that and configure Radarr to use /media/movies and /media/downloads as it's storage locations.
Hardlinks only work on the same volume, which technically they are, but the environment inside the container has no way of knowing that.
I'm dabbling in Bluesky atm. Having run my own Masto server for over a year at this point. Here's things I've found that Bluesky does just plain better - mostly cause it's not beholden to the whims of the ActivityPub protocol.
The first two are huge on a small/single user server. By default we get nothing, following a single account will get us the content of just that account and the replies that they happen to reply to. A post may get 200 replies, but unless I go looking on the original server I will see a fraction of that. Technical solutions exist to help with this but the Fediverse's penchant for privacy and control (quite rightly) limits the effectiveness (Fedifetcher, GetMoarFedi).
3 is something most people won't think about. But if they become aware they're not seeing something they thought they'd be able to they then have to deep dive into who's defederating who and why.
Most all the other points just make the whole thing a much more seamless experience for your average user. Bootstrapping a list of people to follow on a small server is hard (I'd absolutely recommend creating a Fediverse account somewhere large first to build up some sort of list before migrating)