Indeed. My comment was based on Lemmy. Not sure about what service OP was talking.

I don’t know about Mastodon. I run my own Lemmy server, single user. I sometimes run a discovery script honger my “all” populated and I’m good to go.

Not sure how tech savvy you are, but hosting your own server costs a few euros per month, you decide how long it stays up and you are chief in command.

You can find info here: https://ecosia.helpscoutdocs.com/category/314-privacy-friendly-search-engine

TLDR they have ads, but related to your current search, not your profile. And they are Bing based.

Downvoted from my own (Lemmy) instance waste-of.space

I do understand it. These are browsers that they decided during development that are not supported. Not supported means not tested by a full QA team for months. And users are generally stupid, soba simple warning (use at your own risk) is something that does not work.

So they decide to just not support the other browsers.

To be clear, I am definitely not a fan of Adobe of this mechanism, just explaining.

I’m using Ecosia. Planting trees FTW!

Hello there!

I’m running Lemmy via Lemmy-easy-deploy on Hetzner (so self-hosted as in: via a provider). E-mail is working via smtp2go and is indeed active :)

Even decided to run my own instance! Power to the people!

Jokes aside, my server can handle 10 or so more people. So if someone is looking for a new home… waste-of.space.

May I suggest Covfefe as the new name?

Please add waste-of.space. Thnx!

By no means an expert but how do you want to set it up? Different subdomains or folders?

I think subdomains are actual FQDN’s and will not cause issues. Folders might be an interesting experiment.

Oh! Now it is running, I think. Should I just leave it on, or put it on for a few hours per day? or just once for a few hours?

sorry for the wall of questions! overly enthusiastic about Lemmy and the community that makes it great!

I’m getting this error from the docker container when I try to do the initial run:

root@lemmy-server:~/lemmybot# docker run --name lemmy-subscriber-bot --restart always -dt --env 'LEMMY_USERNAME=subscriber_bot' --env 'LEMMY_PASSWORD=mypwd123' --env 'LEMMY_DOMAIN=waste-of.space' lflare/lemmy-subscriber-bot .

c6bce2ed69f7a9745e7b98157b5765d20ddebe22cd1b9e5b0558a9057bb7b71f
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: ".": executable file not found in $PATH: unknown.

Tried it, failed to get it running! Do you have a place where I can ask for assistance? A “home” post or a specific community for it? By any chance? :)

So, that works in a funny way, and this is one of the quirks that belong to the current state of the fediverse. I see you are on lemmy.world, so you should not be impacted that much by it, but still… Let me explain.

You can easily search for all communities in lemmy.world (your “home” instance) by switching the toggle in your search screen. By default, you can’t search for communities on other instances, UNLESS someone on lemmy.world has already done so (or, I’m not sure about this one, is subscribed to that community). If you do so, lemmy.world will federate with that community and keep it “in the loop”.

If you should stumble on a community that you want to subscribe to, but it is not yet federated by lemmy.world, you can just use !communityname@instancename.ltd to search for it. The search takes some time, or you need to try a second time. If you subscribe, that community will be federated with your home server.

Not that big of a deal for instances like lemmy.world as I said, but a bigger thing for small instances (like my own).