Izax

Try soaking it again overnight but with dishwasher detergent instead of normal dish soap

It also supports about:config settings with the AutoConfig feature. Does this help? https://support.mozilla.org/en-US/kb/customizing-firefox-using-autoconfig

I would just go with Debian personally since it’s not updated very often.

• You can add Firefox to startup applications several ways, such as startup apps GUI on any desktop environment.
• Most desktop environments have an “automatic login” option you can configure. You can also disable or remove the login manager
• You can configure some desktop environments (xfce I know for sure) to not launch the panel. Don’t forget to also look up how to disable your TTY hotkeys!
• Install the unattended-upgrades package and Debian/Ubuntu will update automatically. I hardly ever have to touch the updates on my Debian machines
• You can make Firefox’s config directory read only and it won’t be able to write to it

Nice to haves:

• Plymouth can be installed on Debian, and has a few themes that are simple spinners
• You can do this. Look up how to do the policies.json file. Since the Firefox directory will be read only, it won’t be able to be changed by the user
• I think you can still install add-ons like an ad blocker with policies.json, but not 100% dure
• Do a preseed install or similar https://wiki.debian.org/DebianInstaller/Preseed

And now it looks like a gas station bathroom!

Nah. As long as your instance is federating with all the ones that you want to interact with, there isn’t much of a reason to have multiple accounts. However, if you want to see and interact with content that your main instance has blocked, you might then make another account.

Fish flavored fries? Yuck! No thanks!

The only exception is if one of the two servers has chosen not to federate with the other. In that case, you would want one on each account. However, that’s pretty rare as of right now.

Looks like it can be self-hosted. You should be able to install Docker and run it with the docker run command it shows (then go to localhost:8080). Here’s a link to it on GitHub: https://github.com/rystaf/mlmym

But isn’t Jupiter all gas?

Even though Lemmy and Kbin use two completely different software platforms, they are both based on a technology called ActivityPub. This allows different servers (instances) to talk to each other using a process known as Federation.

At the moment, Kbin is federating (meaning talking to other servers, including Lemmy), so you can view and interact with Kbin magazines from Lemmy. I am not sure how it works on Kbin, but for us Lemmy users, we copy paste the Kbin link into our search bar.

So no, you don’t really need to make separate accounts unless the instance (website) has blocked yours or vice versa.

I have seen others explain it like email. Email accounts will still exist regardless of if, say, Gmail shuts down. Same with fediverse instances. Unlike traditional social medias like Facebook and Twitter, people can talk to people on other sites. Imagine if people on Twitter and Facebook could reply to each other

Right? I can’t wait to see how it improves as time on. I didn’t have any real problems with joining on my end, though. When you signed up, was it the approval process on your instance, or just confusing? If it was the approval process, that’s probably specific to lemmy.ca.