Ok.

Both support stronger safety features in chromium and criminals and bullies got equated to kicking puppies. That’s why it’s a shoddy attempt at illustrating their reasoning.

There’s some massive misunderstanding about my comment.

I called it a false equivalency because it’s comparing both the measures (“stronger safety”) and the thing is supposed to prevent (doxing and bullying) to puppy kicking.

That’s just emotional manipulation done badly. We all call it out when politicians use pedophiles to warrant Internet surveillance, and now apply it ourselves? I don’t know about you, but when I see bad reasoning, I’ll call it out. Even if it’s done by “my side”.

Kick a puppy

If you have to resort to false equivalences like these, you’re not really making the anti-WEI crowd look good.

*Edit: * There’s some massive misunderstanding about my comment.

I called it a false equivalency because it’s comparing both the measures (“stronger safety”) and the thing is supposed to prevent (doxing and bullying) to puppy kicking.

That’s just emotional manipulation done badly. We all call it out when politicians use pedophiles to warrant Internet surveillance, and now apply it ourselves? I don’t know about you, but when I see bad reasoning, I’ll call it out. Even if it’s done by “my side”.

Storage on the vm won’t be too much of an issue, as long as you make sure to use Object Storage (s3) for pict-rs from the start. For Lemmit (just a few users, but hundreds of communities and over 150k posts) I’m doing fine with just 2 GB of memory, 1 vcpu, and 2 GB of disk storage for postgres. The storage bucket is sitting at 36 GB.

You might want to scale up cpu and memory for more users as you grow, but you’d be surprise with how little resources you can get away.

I switched to 18.1 this weekend, and the cpu is basically bored now ;)

What the Wandermeister over here said.

Object storage generally is much cheaper than vm disk space (I got 1TB for $5/month at vultr). And the sooner you do it, the better - the migration process took 3 hours for me yesterday, transferring just over 102k files (34 GB).

Hole in their pocket?

Use rsync to get the bulk of the data over (even if it’s mid write) one or more times, then stop the stack on the origin server, and run rsync again. It should be much faster.

1. I started out with the og Lemmy.ml.
2. Then created my own instance/bot Lemmit.
3. Thought Lemmy.ml was to slow/unstable, so created an account on Lemmy.world
4. Gotta have a separate account for grown up stuff, so signed up on LemmyNSFW.com
5. Gee… Lemmy.world is kinda slow/unstable… Better sign up on lemm.ee…

I’ll probably retire the lemmy.ml and world accounts though.

🤔 The server spits out html when it cannot reach the backend. So one could argue it’s a configuration issue because the admin didn’t provide enough capacity / didn’t set up a proper generic json error for backend failures.

FWIW, Liftoff doesn’t handle these super gracefully either.

At any rate I think it’s kinda awesome that we get to witness these kinds of infancy problems.

Is that a roundabout way of saying you’re getting a divorce? Does she know?

BTW, what’s the difference between this and Pythörhead (apart from being easier to type? :p)