as with F------k, R----t, T-----r

My dude. My gal. Sibling of my Fediverse. We are in the Fediverse. You don’t need to tiktok-censorship yourself like that. You don’t need to fallback to 2000s cringe. Embrace the Fediverse. Embrace the truth.

That’s quite senseful yes. In the cases where I want to host somewhere that already has a Postgres service going, I just up and use that.

…How come so few people are using SQLite?

It’s on poob. Poob has it for you.

Someone is projecting, I see.

You don’t need to. Content is perfectly discoverable without them. Just about the only real benefit is having the “extra storage”. And nowadays it’s pretty dangerous, as at least Youtube hallucinates edits for uploaded casts and stuff without the creators’s consent or knowledge.

Rather than encourage people to leave, we should encourage more enlightened people to move there, and change the political climate

You want to put those “more enlightened people” at risk of being Gestapo’d or killed? We need them where they can actually do a net positive effect!

First clean up the shit in Texas (or any other fascist shithole) and make it livable, then live there.

Fair enough. In that case I wish you a very successful revolt, that you or those aligned with it hunt down and eliminate the fascists so they can’t come for you never, nowhere.

Woudn’t it be smarter to just leave the hellhole that is Texas? Either to the north or to the south, leaving is a win.

You intendeth to mean Beowulf? I would mayhaps have seen one ere the break of my college time. Wouldst you tell me more about it?

Why would it affect their bottom line other than positively? Corporations love fascism because it can make it mandatory for people to buy from them, among other things.

and keep fighting it in court

> implying those neofash sites would fight against orders to tHiNk Of thE cHiLdReN

Me: [connects a mouse]
Windows: “please wait we are searching for drivers so the mouse works”
Me: [drags the mouse over to the popup to close it]
Me: jaquer

Ethernet is the way.

A central relay/proxy is even worse than your current approach. People are obviously free to set up their own Lemmy/Mastodon server if they want a relay.

Lemmy/Mastodon are quite heavy to set up if all you want is to proxy outbound connections. Just using any available proxy you have (which could very well be eg.: a SOCKS proxy set up on FoxyProxxy) is quite nimble and takes up at most a few kbs of RAM.

That said, for anonymizing the IP origin this only mostly works if enough people use the same general relays (basically the same principle as TOR, VPNs), which means this only becomes effective once enough people use this plugin that it becomes worthwhile to position such infrastructure.

The only part that is wrong TMK is the “indivisible” one; and perhaps the last item because I recall that PulseAudio and Wayland were pushed this way worse than systemd was.

Because it was not always the case that sysvinit was supported - things were sorta “accidentally hazy” for a while. There was a time (I think during Debian 9 and 10) that systemd not only was the default, but was also enforcedly linked against a large part of the stack (you couldn’t have a desktop environment, PulseAudio or NetworkManager without systemd, for example).

This led to the rise of projects like Devuan, that provide a working system that installs without systemd by default; Antix’s nosystemd repo, which allows to install components of the Debian stack without the enforced systemd dependency; and later libam-elogind-compat which aided shimming some of systemd’s requirements under elogind.

Nowadays at least, the only hard part of not using systemd in Debian is 1.- switching (from or to) seems to require rescue mode and 2.- you lose some of the container management goodies (for eg.: Podman services).

None. On Alpine you can only use OpenRC and on Debian you can only use systemd. Most distros don’t let you change out the init system. If you want systemdless Debian look into Devuan.

Fake news. On Debian you can use both sysvinit and openrc (I have six servers on sysvinit, tho I do actually intend to shift them to systemd later mostly because of the container management goodies).

Judging from this post, I would say you should not be looking to change out your init system

Mostly agreeing here. For selfhosting the init system matters barely any, since past the default distro setup one would be doing most of everything with Docker, Podman, etc. At that point, none of the usual Linux religious wars matter much (you can perfectl edit a compose file with nano).

Sending the current URL and directly from your own IP too is quite the privacy hurdle already. I’ve already posted on what kind of things could be done to improve this, but first, a notice.

Your README says in the Privacy section:

Does not track your browsing

On the current implementation, this should be changed to:

Enables unverified third parties to track your browsing data

As that honesty is quite important.

As for measures that could be taken to improve on this issue, I have three suggestions (I might Issue Tracker them to the codeberg later, if I can find my credentials XD)

• Set up a uBO-stye control pane that allows to set this on or off per-domain or per-site. Bonus points if it allows for per-site specific on which lemmy instances to use the same way as uBO’s “3p” Custom Rules does. This already prevents a number of undesirable use cases, such as automatically sending LAN / non-DNS names to third parties when they can’t really be searched for anyways.
• Anonimyzing assist: Allow for sending only the global context of the visited site (eg.: only the domain) instead of the full URL.
• Anonimyzing assist: Allow to cache requests to send them later / send them in batches, to avoid clock-based / timezone-based tracking attacks.
• Anonimyzing assist: Allow for the browser-specific request being sent through a proxy or relay, so that IP origin information is not leaked. (I think this only really makes sense for users not logged-in?)

Yeah. Interesting to think if there are ways to get around that problem.

At a first flance, perhaps a uBlockOrigin-style control pane with per-domain toggle, so that for example you can send the info only when browsing a specific domain (let’s say, a news site; that’d be interesting to find discussion in Lemmy of). This would also prevent the issue of sending URLs that are not internet-wide (eg.: are on a localnet resolver, or an intranet).

As well as the abiity with an option send the request through a relay or proxy, to remove IP origin information that can be used to build the profile.