Personally I’m not enormously worried about SSH, because I’m behind NAT anyway, but yeah it’s definitely still something I’d rather keep off if not in use.

Is there a way to get a terminal on the Synology itself, or is SSH from my PC the only way?

I would love to containerise it. I worked with Docker in a previous job, but honestly I’ve forgotten most of how to work with it. Would be a nice refresher to try and relearn how to create Dockerfiles and docker-compose.yamls.

Unfortunately I currently have two problems. First: I seem to be completely unable to test this on my desktop. When I open Docker on my PC, it complains that I need to run wsl --shutdown, but despite doing that many times, it still complains, before immediately closing.

So I was going to try doing it entirely on the Synology. And then I ran into the issue that…I have no idea how to even start with that. When I search for Docker in the Package Manager the only thing that comes up is Synology’s own container manager, and I have no idea how to work with that.

Yeah I’m pretty sure my Synology should be able to run containers. It’s a DS923+. But unfortunately when I search for Docker in the Package Manager the only thing that comes up is Synology’s own container manager, and I have no idea how to work with that.

How do you run a docker container on Synology? I have a DS923+ which AFAIK should be able to run it, but when I search for Docker in the Package Manager the only thing that comes up is Synology’s own container manager, and I have no idea how to work with that.

other instances like lemm.ee, sh.itjust.works, and lemmy.dbzer0.com would have been fine too

Ok. Why not lemm.ee or db0 then, given both of those are much less likely to affect users who do not have access to LW?

This is an unfortunate issue that we were not aware of at the time of transfer

That…shows that you are clearly not equipped to be running a large community in the fediverse. This is basic knowledge that you would have become aware of had you done even the most cursory amount of research or consultation with the community. It comes back to the problem of you springing this on the community without warning. It shows a complete lack of respect or regard for the community. If you didn’t know, ok, maybe that can be excused as just being happy in your own little bubble and not of consequence. But the fact that you never even cared enough to consider how it might affect your users is a major indictment upon you all.

We’re not sure what the solution is, but want to make our community as accessible as possible. Community solutions are welcome.

If you’re absolutely not willing to move back to blahaj, at least consider giving up on LW and moving to .ee. There is no solution to this problem while you remain on LW.

Our agreement with Ruud predated the now-rescinded policy changes

In the last thread you were saying that it was very much a last-minute thing, and that’s why Ada was not given more of a heads up. What’s the truth here? The full timeline?

Before you write me off as a hater, I’d like you to know that my initial reaction to the news was pretty neutral. I enjoy posts in the 196 community and have posted a few times myself, but have never been super dedicated to it. I saw the move was happening and thought “a bit weird, but ok”. Then I followed the updates and your response to feedback. It was you throwing Ada under the bus in the comments, and demonstrating that you had failed to even consider how the community would feel about things, that turned me against this.