Gull

joined 1 year ago
[–] Gull@kbin.social 1 points 1 year ago

They fired Victoria because they were trying to aggressively monetize IAmAs in ways that were going to fuck community interests, and Victoria pushed back. Think Rampart, except companies can pay to ensure that it doesn't become a PR fiasco, so it's guaranteed astroturf.

Reddit has been classy ever since.

[–] Gull@kbin.social 1 points 1 year ago* (last edited 1 year ago)

The mob boss who wants $8/mo for a lame service but won't harm you if you don't want it?

[–] Gull@kbin.social 1 points 1 year ago

How about affordable housing?

[–] Gull@kbin.social 3 points 1 year ago

This post is helpful for highlighting some of the reasons the migration is slow. People who want to chart the future of the Fediverse need to listen to this kind of feedback and think about how to fix the pipeline.

[–] Gull@kbin.social 1 points 1 year ago (2 children)

I support the Fediverse but here is one of its problems that needs to be negotiated.

As an individual poster, if an instance bans you or defederates instances that you would like to communicate with, you can wander off to another instance. It's bad, but it's not the worst.

As a (prospective) moderator, you have to recognize the danger that an overactive instance admin will crack down on your sub or remove you as a moderator for editorial reasons.

Reddit is pretty slimy, but for years they were broadly hands-off from a moderator perspective. Reddit's recent actions show that a moderator can put decades of sweat equity into building and maintaining a community - and then get shut out capriciously, without communications channels or other tools to migrate any significant portion of that community. Start over from scratch.

The question for a prospective moderator is whether you can really trust the instance you're basing your new mag on. Most communities of any size will want insurance of having an instance they control or at least an instance that makes fairly strong assurances about moderator ownership.

If you're just driving by and you want to own the espresso machine universe on a particular instance, you can create /m/EspressoMachines and arbitrarily name a few other moderators and then wander off, but this kind of moderator is doing very little to grow or maintain the community. It's arguably irrational to commit to that kind of labor when the rug is likely to be pulled out from under you at any time.

[–] Gull@kbin.social 7 points 1 year ago (4 children)

There are existing communities and there is an exodus, so it shouldn't be necessary for the entire process to repeat from scratch.

[–] Gull@kbin.social 2 points 1 year ago

Twitter was already shit under Dorsey.

[–] Gull@kbin.social 1 points 1 year ago

The medium structures and drives the interactions. Decisions about the medium are amplified in effect. (Some) people have always been bad, but what they do and what effect it has varies with the medium.

[–] Gull@kbin.social 5 points 1 year ago (1 children)

Outraged feelings aren't the problem. Nobody is complaining about defederating Nazis. Defending and lying about Stalinist atrocities is morally no different from defending and lying about Nazi atrocities. If you let Nazis and tankies overrun your communities they won't be a "real alternative." Just like with Nazis, tolerating intolerance is intolerant.

[–] Gull@kbin.social 3 points 1 year ago (1 children)

You're right - having multiple copies of everything is a drawback of housing each application in its own container or VM. The standard rejoinder is that disk space is cheap. The validity of that rejoinder depends on what you're doing and what hardware or budget you are working with.

Another problem is that old versions of these dependencies will be baked into an image that is then used for many years without updates. This ensures the application keeps working without being disrupted by an update to a shared library, but it also means things like security flaws persist. Arguably, this is mitigated by only that image having the problem, but one insecure app can be a real problem - especially when it accesses shared resources - and when the same problem applies to many applications.

Compiled code optimized for a specific system's hardware is less relevant than it used to be - even Gentoo users do not focus on this anymore. Rolling your own container isn't much harder than compiling with your own options.

[–] Gull@kbin.social 1 points 1 year ago* (last edited 1 year ago)

You don't have to be perfect or make zero mistakes. You just have to be careful with a couple things like sudo rm -rf and overriding warnings when you try to uninstall system packages. This is not rocket science and has not been for decades. The average user is not the worst-case user. More frequently something specific is broken, like ssh, so that it would be more useful to have file versioning.

[–] Gull@kbin.social 1 points 1 year ago

You're doing the right thing. They're just trying to juice their own numbers by pressuring you to say something effusive.

view more: ‹ prev next ›