Adam

Given the topic, the response and the location I’m going to go with “because it seems neat and could be fun”.

Now, since I now know if it I’m going to give it a crack. 😆

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.

• Shows me all replies to any post I happen to come across.
• Lets me see all posts about things I happen to search/look for, including hashtags.
• I don’t have to worry about being unable to see content I haven’t personally blocked (not so much of an issue on a small/single server like mine though).
• I can repost things (not actually too bothered with this one but many people want it).
• I can set per post reply permissions to a very granular level (no-one, mentioned, followers, specific followers)
• It handles video in a way that works i.e. I can post them, and people can watch them with minimal buffering/waiting.
• Gives me access to community built collections/algorithms that expose the content I want to see.
• It defaults to providing an additional feed driven by what the people I’m following are liking/interacting with.
• Finally, a big one for new users, it provided a default feed of content when I first logged in so that I had something to look at.

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)

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.

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?

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’ve not used dockge so it may be great but at least for this case portainer puts all the stack (docker-compose) files on disk. It’s very easy to grab them if the app is unavailable.

I use a single Portainer service to manage 5 servers, 3 local and 2 VPS. I didn’t have to relearn anything beyond my management tool of choice (compose, swarm, k8s etc)

I’ve not tried it but have been keep tabs.

The two main problems appear to still be ongoing PRs/issues; magazine/community sidebar content doesn’t update and doesn’t federate out at all to lemmy, and moderation actions don’t federate at all (any of the various types) - which is particularly problematic.

• https://github.com/MbinOrg/mbin/issues/248
• https://github.com/MbinOrg/mbin/pull/694

If only k/mbin federated better - I’d be all over it :(

We use them quite extensively. They work great.

You’ve not factored in egress costs. Which on Amazon can add up quite quickly.

There’s a couple of caveats with it, but I think neither are worse than your proposed flow.

1. After putting things in an album you’ll need to manually run the migration job to have immich reorganise into album folders.
2. Images in multiple albums will only be migrated to the path of the newest album.

Immich does support folders?

https://immich.app/docs/administration/storage-template/

With this you can store your photos in whatever structure you want.

Yes.

Docker will have only exposed container ports if you told it to.

If you used -p 8080:80 (cli) or - 8080:80 (docker-compose) then docker will have dutifully NAT’d those ports through your firewall. You can either not do either of those if it’s a port you don’t want exposed or as @moonpiedumplings@programming.dev says below you can ensure it’s only mapped to localhost (or an otherwise non-public) IP.

Documentation people don’t read

Too bad people don’t read that advice

Sure, I get it, this stuff should be accessible for all. Easy to use with sane defaults and all that. But at the end of the day anyone wanting to using this stuff is exposing potential/actual vulnerabilites to the internet (via the OS, the software stack, the configuration, … ad nauseum), and the management and ultimate responsibility for that falls on their shoulders.

If they’re not doing the absolute minimum of R’ingTFM for something as complex as Docker then what else has been missed?

People expect, that, like most other services, docker binds to ports/addresses behind the firewall

Unless you tell it otherwise that’s exactly what it does. If you don’t bind ports good luck accessing your NAT’d 172.17.0.x:3001 service from the internet. Podman has the exact same functionality.