robryk @robryk@qoto.org

@rysiek

Istnieje stary odpowiednik takich działań: poszukiwanie "dźwiękowego sobowtóra", który umie naśladować głos naszego "celu". Czy wiesz może o przypadkach, kiedy ktoś w jakimś podobnym kontekście takowego w przeszłości używał?

@ftdl

Serwujecie na pol.social media z niewłaściwym Content-Type. Np takie https://pol.social/system/media_attachments/files/110/935/884/311/554/703/original/be66df9224d6be69.webp ma `Content-Type: text/plain`, a jest obrazkiem. To powoduje, że linki do nich (np. te w klientach innych instancji) otwierają stronę robaczków miast obrazek.

@kravietz

Thanks for making me realize that there were two attacks (that the S-400 AD system was attacked earlier).

@lutzky @delroth

If you want to understand the mechanics of this in Fedi, there is no single description I know of, but reading https://www.w3.org/TR/activitypub/#inbox-forwarding helped me understand how the heck all of this is not magic.

@delroth @lutzky

One set of relevant situations is what delroth described above. Another situation is posting something and using your effective moderation power over responses to create an impression of a wide agreement (note that the more egregious variant of this, where you call someone out whom you've blocked, was impossible on Twitter, because you couldn't mention people you've blocked).

There are multiple approaches to dealing with those issues. One of them is what Twitter has (used to have?). Another very similar one is the G+ approach of making top-level posts very different from comments, and explicitly giving moderation power over comments to post's author (this differs insofar comment authors do not get to moderate responses to their comments). Another one is what Fedi would approximately have if all servers were single-user: you see responses that the post's author approves of (passively), and responses of everyone you follow. (Multi-user-serverful Fedi expands this to responses of everyone anyone on your server follows.)

I think that the distinction between post and comment is something that's badly missing in Fedi, and is probably the source of most of the nonmisguided[1] requests to defederate from a server A due to that server not defederating from B, whom we consider bad.

[1] Quite often they come from some misunderstanding on how silencing and defederation work, which is not surprising given that most of this appears to be emergent properties of a system.

@madargon I wonder whether the extensions that allow one to somewhat limit agent forwarding can be helpful here. (After all, if one limits agent forwarding to only be used to authenticate to host foo, then something somewhere has to be able to evaluate this predicate.)

@lutzky

I'm not sure if we're talking about the same situation.

Let's say Alice blocks Bob and posts something. Now it's impossible for Charlie to see Bob's replies to Alice. Note that Charlie's client is not aware of Alice having blocked Bob, so even if Charlie was willing to cooperate, they wouldn't be able to reproduce the same effect client-side.

@rysiek

flightradar24 claims that there's ~1 plane/hour within ~30km of Ozyorny (I didn't try to figure out more precisely where the crash was) during daylight hours. That coupled with differences in size, speed, and altitude between drones and private jet aircraft make it IMO very unlikely that it was accidental.

@delroth Did you happen to try measuring its resonance(s)?

@lutzky

I thought that people you blocked couldn't reply on your posts (or, expressed in observable terms, that neither you nor unrelated 3rd parties would see their posts in your replies).

@janl @grrrr_shark

In my experience they heat up just as slowly. Is it also yours?

@autoerot1ca @mairin Yes, it does have such a rule: https://hub.fosstodon.org/why-fosstodon-is-english-only/

@msuriar

A contrary opinion: it's terrible. You can do whatever you can do with it with subqueries, any reasonable optimizer will treat both identically, and HAVING makes things appear less composable than they are (tbf group by by itself already has that property, but knowing about HAVING but not about subqueries makes one assume that SQL is noncomposable).

@neilk

What's the typical sequence of steps if (a) no one volunteers why (presumably because no one knows) (b) when ~half the people think it's obviously self-explanatory and the other ~half think there's no good reason?

@niconiconi Or maybe a problem with authority.

@rq @starshine unless your serial connection is fast enough to support e.g. vi and everything knows which escape sequences to use.