That work has already started with Fediseer. It’s not automatic, but it’s really easy, which is probably the best we’ll get for a while.
My ISP says my IP is technically dynamic, but it hasn’t changed once in the 6 years I’ve had their service. But that’s for the best, since they’re the only choice for symmetrical gigabit and their only option for static IPs is for business accounts.
So I continue to trust that they won’t change it. Fingers crossed.
Holy hell Java on a Smartwatch?
WearOS is based on Android, which uses Android Runtime (ART) as the application runtime. ART uses Java (or any other JVM-compatible language, such as Kotlin) as the development language, but compiles the app to native code when it’s installed on a client device.
So… Kind of?
Also, are the images even federated? I know the current line of thinking is that they are, but I could not find them in my local pictrs volume. Not that I wanted to, mind you. But I looked and only saw one picture in there from the problematic time period, and it happened to be one of my user’s avatars. And one of the CSAM posts federated with me, I know for a fact, because I saw the comments even though I couldn’t see the picture (and I feel horrible for those users who saw it, some of them were obviously traumatized).
I’m keeping a close eye on my pictrs volume and really scrutinizing who I allow on my instance after this whole thing, but on the whole, I’m not overly concerned, even as a US-based self-hoster. I registered with the DMCA and will fully comply with any and all takedown requests, even silly ones like copyright. I don’t have the finances or time for prolonged legal battles.
Edit: Figured it out. My pictrs container didn’t have an external network definition, so it was timing out while retrieving external images.
I agree with your last statement, but I actually really enjoyed the puzzles in Spider-Man 1. The story-based ones were never difficult, and for the optional ones, I just waited until I was in the mood for some puzzles, and then blew through them all in one go.
But if you don’t like puzzles at all, I understand turning them off.
You want yt-dlp
. It’s a command line app, but it’s pretty simple to use. For example, to download a whole playlist to best quality audio, regardless of if the main URL is pointing to a video or playlist, you can do
yt-dlp --yes-playlist -x <url>
If you specifically want mp3 format, you could do
yt-dlp --yes-playlist -x --audio-format mp3 <url>
You can see in this image that the meme I’m currently looking at is hosted on lemmy.world even though I’m on my own Lemmy instance.
Text is copied to your instance’s database, but any images are hosted on the other instances and simply linked to. Worst case scenario, you get told to delete something that’s illegal in the country in which you host the instance, you comply, and everything’s peachy.
Edit: That being said, I’m currently hosting an instance for myself and a few friends, and it’s been smooth-sailing. Just make sure to require email verification or admin approval for new sign-ups (or disable them entirely) if you don’t want to be overrun with bots.
Not vice-versa, oddly enough. I don’t know if this is the norm for the fediverse, but on Lemmy, instance blocking goes one-way. So users on those instances can federate with Beehaw and see communities, posts, and comments, and even post their own stuff, but users on Beehaw won’t see it.
Edit: Ah, correction, this only applies to things on instances that are still federated to the defederated instances. The two instances defederated from Beehaw will no longer get any updates directly from Beehaw, but will still see Beehaw users’ comments on posts on other instances.
I could go in-depth, but really, the best way I can describe my docker usage is as a simple and agnostic service manager. Let me explain.
Docker is a container system. A container is essentially an operating system installation in a box. It’s not really a full installation, but it’s close enough that understanding it like that is fine.
So what the service devs do is build a container (operating system image) with their service and all the required dependencies - and essentially nothing else (in order to keep the image as small as possible). A user can then use Docker to run this image on their system and have a running service in just a few terminal commands. It works the same across all distributions. So I can install whatever distro I need on the server for whatever purpose and not have to worry that it won’t run my Docker services. This also means I can test services locally on my desktop without messing with my server environment. If it works on my local Docker, it will work on my server Docker.
There are a lot of other uses for it, like isolated development environments and testing applications using other Linux distro libraries, to name a couple, but again, I personally mostly just use it as a simple service manager.
tldr + eli5 - App devs said “works on my machine”, so Docker lets them ship their machine.