Selfhosted

I am glad to see more people selfhosting their own. Makes me feel less out. Had the same issues.

I use a Dell Wyse 5060 Thin Client as my file server and the reason for that is I needed something that is low powered as electricity isn't cheap in my country . My backup solution is really simple and cheap. I use a HDD docking station (only has one slot) as the main and a laptop HDD enclosure as secondary.

I've configured a script that would mirror the main drive to the laptop HDD. This executes every midnight. Then every week or two, i perform a cold storage backup to another laptop hard drive. This way, I keep a third snapshot in case either one of those two hard drives go out. Or if i need to restore a file to the original.

My thin client runs Windows 11 and I'll probably get crucified for it but in all honesty, it works just fine. It doesn't connect to the internet since I restricted it to only LAN on my router. If it needs an update, I simply just download the latest patch from Microsoft on another computer and then transferring it over to the server. File transfer speeds are what i expect from a mechanical HDD.

I was having issues searching as well until I added a network to the docker-compose and then adding it to my lemmy image.

networks:
  lemmybridge:

services:
  lemmy:
    networks:
      - lemmybridge

Have you tried searching for the communities first? As I understand it from some other posts, if you try to access a remote community via URL through your home instance before it "knows" about it, you'll get the 404 error. Someone (you) on your instance has to make your instance "aware" of the remote community by searching for it first. Then, after your instance is aware of the community and federating it, you can access it via URL as you posted above.

@sdg@lemmy.world Maybe edit the post with the solution, it will be useful to others.

Wish it would at least copy the instance list when federating, or have it as an option
Feels so empty browsing All when it’s identical to Subscribed

What I do is:

• I take the name "!selfhosted@lemmy.world"
• copy and paste it into the search in my instance
• press "search"
• it shows "No results."
• I go to Communities on my instance
• I click on "All"
• At the bottom of the list I can see "!selfhosted@lemmy.world" and the Subscribe button

I guess it is some kind of a bug. If I post a url of a post, it also takes qute some time, several seconds, until it shows up.

Thanks for the post and resources, this is the first time I’ve seen this explained clearly in one place

I also got very excited when I found out you can edit thread titles haha. such a handy feature.

I wrote a post on my instance about how to add remote communities.

https://lemmy.comfysnug.space/post/21762

Is there a description like this for kbin.social? Not sure if it's just because of some cloudfare issues but for example communities on the Lemmy instance feddit.de do not show up for me on kbin.social. Some of their posts do, though.

But if I search for e.g. !ich_iel@feddit.de on kbin.social it won't show up and therefore I can't subscribe to it from kbin's side.

EDIT

Now it suddenly shows up under Magazines on kbin.social. How often do new communities on Lemmy instances get federated to kbin?

I'd also like to know how it works. I switched to sh.itjust.works because it's a lot faster than lemmy.world, but trying to migrate my subscriptions, lemmy.ca doesn't show up, nor does lemmygrad.ml.

Lemmy guide and F.A.Q.

At the moment it's a bit convoluted, but you'll need to go to the search page (https://tortoisewrath.com/search) and then search for the name of the community, in this case [!selfhosted@lemmy.world](/c/selfhosted@lemmy.world). This will at first say no results but should eventually show the community (5-10 seconds in my case).