Natanael

To be pedantic, transparency mod bots exists on reddit and server admins can redact the log here.

Server admins can set up moderation filters to deal with stuff like that, and should be coordinating with each other on detected spam patterns, etc.

Lemmy has language tags. Clients could offer integration with translation tools.

Lemmy is built around forums, which is very distinct from microblogging when it comes to moderation and management.

You don’t get the same kind of context collapse as on Twitter. You don’t get the same kind of dependency on server wide shared culture like on many niche Mastodon servers. Although context collapse still happens to some degree on reddit and may happen here when threads gets popular, it’s possible for forums to be moderated to minimize it and enforce quality. You don’t get nearly as many people trying to enforce their rules in others’ spaces, because forum makes it clear that it’s not “your feed” (like how some try to control what they see not with filters but instead by harassing people who post stuff they don’t like), here it’s somebody’s forum and somebody else is the moderator. You can stop seeing specific content by blocking those forums instead of blocking the users. Forums which you don’t interact with doesn’t affect you!

Because of how the federation works here, volume alone is never the main problem. Forums can be hosted on small instances just fine. Users on small instances can use big forums just fine. If a particular forum is poorly moderated it can be blocked regardless of where it’s hosted. Admins for small servers can filter content from problematic servers, regardless how big they are, and can do it on a per-forum basis too in order to avoid collateral.

Spurious defederation between servers where one has a lot of users is where the problems gets complicated.

It’s losing cost advantages as time goes. Long term storage is still on tape (and that’s actively developed too!), and flash is getting cheaper, and spinning disks have inherent bandwidth and latency limits. It’s probably not going away entirely, but it’s main usecases are being squeezed on both ends

It’s also what Google Maps live view is using. Street view imagery plus rough location plus on-phone camera sensor calibration data allows it to compute highly accurate positions relative to surroundings.

Taxing liquid capital is fairly straightforward, especially if it’s tied to income (like company founders owning shares).

Taxing non-liquid assets is complicated because it’s hard to make it fair in cases of family home inheritance and similar situations.

But taxing use of assets as collateral for loans (to create liquidity from a non-liquid asset) should be reasonably fair, it can be treated as an advance on capital gains taxes on the collateralized asset.

The scaling attack specifically can make a photo sent to you look innocent to you and malicious to the reviewer, see the link above

There’s basically ideologues versus hateful people versus indifferent sociopaths (overlap is common)

I consider political ideologues and “technocrats” and extremely pedantic rule-following bureaucrats to be different flavors of ideologues (has a specific worldview they try to enforce / uphold)

Yeah so here’s the next problem - downscaling attacks exists against those algorithms too.

https://scaling-attacks.net/

Also, even if those attacks were prevented they’re still going to look through basically your whole album if you trigger the alert

Apple had it report suspected matches, rather than warning locally

It got canceled because the fuzzy hashing algorithms turned out to be so insecure it’s unfixable (easy to plant false positives)

Nestlé

https://github.com/bluesky-social/atproto/tree/main/packages/bsky

The old design was built to scale to a few million users. The new backend is revised to handle ~hundreds of millions. They’ll releasing bits and pieces at a time.

Sure, but the openness of the protocols, especially the portability of accounts, makes it hard for them to push negative changes on users.

https://bsky.app/profile/jay.bsky.team/post/3krxdfy6koc22

He never had ownership. Not all investments provide ownership.

Bluesky is a public benefit corporation. That’s very different from for profit

3rd party moderation tools already exists, using the same API as the official moderation system, available to subscribe to even directly in the official app. If you don’t want bluesky’s moderation decisions enforced, you can run a different client which don’t apply the bluesky labels (or if the bluesky appview blocks something entirely, you can circumvent that and retrieve it directly from that user’s PDS)

is specifically not clarified to leave open the possibility for monetization such as forcing as on users

What

The network is specifically designed around portability and content addressing so they can’t lock you in

it would never be a useful alternative to the Official Bubble maintained by the Bluesky corporation that you must submit to or be left out in the cold interacting with users only on alternate, small personal networks.

There are already plenty of people running their own self hosted PDS servers to host their account, talking to the rest of the bluesky users, using 3rd party moderation filters and 3rd party clients, with 3rd party feed generators to view stuff like topic specific feeds

Also there’s bridgy so you can talk across Mastodon / bluesky by letting bridgy mirror posts and replies between the two networks

If you’ve already noticed incoming traffic is weird, you try to look for what distinguishes the sources you don’t want. You write rules looking at the behaviors like user agent, order of requests, IP ranges, etc, and put it in your web server and tells it to check if the incoming request matches the rules as a session starts.

Unless you’re a high value target for them, they won’t put endless resources into making their systems mimic regular clients. They might keep changing IP ranges, but that usually happens ~weekly and you can just check the logs and ban new ranges within minutes. Changing client behavior to blend in is harder at scale - bots simply won’t look for the same things as humans in the same ways, they’re too consistent, even when they try to be random they’re too consistently random.

When enough rules match, you throw in either a redirect or an internal URL rewrite rule for that session to point them to something different.

The trick is distinguishing them by behavior and switching what you serve them

Yeah seriously use a gaming laptop at that point. The point of the Steam Deck is that it’s compact and quick to put away