zirk.us is one of the many independent Mastodon servers you can use to participate in the fediverse.
Literature, philosophy, film, music, culture, politics, history, architecture: join the circus of the arts and humanities! For readers, writers, academics or anyone wanting to follow the conversation.

Administered by:

Server stats:

723
active users

#cws

0 posts0 participants0 posts today

About #ContentWarnings aka #CWs
About #AutisticPeople
About #Depression #Anxiety #Autism #Suicide

Did you know that Austistic People are 3 times more likely to die to suicide?
Did you know that many Austistic People also suffer at a much higher rate than neurotypicals from countless mental and physical comorbidities including depression, anxiety, heart disease?
Did you know that many Austistic People are much more easily overwhelmed than their neurotypical peers?
Did you know that many Austistic People are extremelyl troubled and overwhelmed by political news especially these days?
DId you know that putting #News items (especially #PoliticalNews) behind a Content Warning (CW) possibly #SavesLives?

I might have sent a less than polite reply to this mail by Google’s Chrome Web Store developer support. I know what I can, but I’m definitely not going to report 62 malicious extensions individually. Moderating that place is their job, not mine. If they need 62 tickets, they can surely create those themselves.

I meant to publish a rant about Google and Chrome Web Store for a while now, and now it is out: palant.info/2025/01/13/chrome-

This details many of Google’s shortcoming at keeping Chrome Web Store safe, with the conclusion: “for the end users the result is a huge (and rather dangerous) mess.”

I am explaining how Google handled (or rather didn’t handle for most part) my recent reports. How they make reporting problematic extensions extremely hard and then keep reporters in the dark about the state of these reports. How Google repeatedly chose to ignore their own policies and allowed shady, spammy and sometimes outright malicious extensions to prevail.

There is some text here on the completely meaningless “Featured” badge that is more likely to be awarded to malicious extensions than to legitimate ones. And how user reviews aren’t allowing informed decisions either because Google will allow even the most obvious fakes to remain.

I’ve also decided to publish a guest post by a researcher who wanted to remain anonymous: palant.info/2025/01/13/biscien

This post provides more details on BIScience Ltd., another company selling browsing data of extension users. @tuckner and I wrote a bit about that one recently, but this has been going on since at least 2019 apparently. Google allows it as long as extension authors claim (not very convincingly) that this data collection is necessary for the extension’s functionality. It’s not that Google doesn’t have policies that would prohibit it, yet Google chooses not to enforce those.

Almost Secure · Chrome Web Store is a mess
More from Yellow Flag

My research on how Chrome extensions spam Chrome Web Store search with irrelevant keywords has been picked up by @dangoodin: arstechnica.com/security/2025/

The article quotes me towards the end, something that is worth repeating:

“It wasn’t that hard to notice, and they have better access to the data than me. So either Google isn’t looking or they don’t care.”

Ars Technica · Google’s Chrome Web Store has a serious spam problem promoting shady extensionsBy Dan Goodin

Back in October I asked here why searching for “Norton Password Manager” on Chrome Web Store brings up five completely unrelated extensions which all show up before the actual Norton Password Manager. Now I know the answer: some extension authors figured out how to use translations in order to mess with the search results. palant.info/2025/01/08/how-ext

I found 920 extensions using this approach. Most of them fall into a few large extension clusters that are spamming Chrome Web Store. For example, I could attribute 122 extensions to the Kodice / Karbon Project / BroCode cluster that I covered in June 2023 originally. Another 100 extensions belong to the PDF Toolbox cluster that originally appeared on my blog in May 2023. The ZingFront / ZingDeck / BigMData cluster is one I also researched back in 2023 but didn’t publish – 223 extensions.

There is also a cluster that was new to me and which I couldn’t really tie to a company name (apart from finding two red herrings). There seems to be a Ukrainian/Russian language part and a Farsi (?) language part here, and it’s hundreds of extensions despite only 55 of them qualifying for the list in this article.

Now that this is out, are you as excited as me to see what Google will do about this?

Almost Secure · How extensions trick CWS search
More from Yellow Flag

More than half the posts on my home feed have #CW wrappers. I have a sparse but calm feed with interesting pics interspersed.

Correction: That should read 'have filters on them', not #CWs. Apologies - first day back at work and brain is not yet functioning on all four cylinders.

Replied in thread
@Dr. Daniel Dizdarevic It isn't just because of compression, nor is it because I scale my images down from my original 2100x1400 renderings to 800x533.

As I've said: I don't describe the image with the things in it. I describe the things. Not as they appear in the image, but as they are in-world where I can walk closer to them or move the camera closer to them. It's like an image with a near-infinite resolution.

For example, if there's a light grey blob in the image, four pixels wide, three pixels high, I describe it as what it is in-world, a white sign with three lines of black writing on it. I transcribe the text on the sign 100% verbatim including all spelling mistakes, I translate it afterwards if it isn't in English, I may even explain the text if someone out there needs an explanation, and I may go as far as naming and describing the typeface.

Or if there are two by two pixels on different levels between red and white, I describe them as what they are in-world, a strawberry cocktail in a conical glass, somewhat like a Martini glass. And I slap an "alcohol" content warning on the whole post. Nowadays, I'd even flag the image sensitive just because of these four pixels.

I used to go as far as describing images within my image and even images within images within my image at higher levels of detail than anyone else would describe their own images. I used to describe things that weren't even visible in-world in the place shown in the image. Pictures of places that I would have to walk or even teleport to to be able to describe them. Textures that I would have to make visible otherwise to be able to see all details.

The last time I've described an image in an image with details not visible in the place shown in my image was in this post. I used almost 5,000 characters to describe a poster on the info board. I had to walk to the place displayed in the image on the poster to be able to describe it. The description of the image within the image got so lengthy that, when I was done, I had to remind the reader that I'm returning to describing "my" image. And I actually "cheated" by adjusting the camera in such a way that one of the three posters on the info board is entirely concealed behind a tree trunk because it would have been painfully difficult to describe.

I stopped going that deep when I wrote the image description for what will probably remain my last image post on this channel. The long description was already growing absolutely humongous, and it's my longest one to date with over 60,000 characters. I had actually thought this scene would be easy to describe.

The problem I encountered was that there were simply too many images within images within my image. There's one teleporter near the left-hand edge with a preview image that made me reconsider. In-world, no matter how close I move the camera to the preview image, it mostly shows a square area that appear to be tan all over except for something dark and unidentifiable in the middle.

Actually, however, the place shown in the preview image has hundreds of single-destination teleporters. Several dozen of them are activated and have one preview image each of their destination. I teleported there to take closer looks at everything. I was actually about to write a description of that "teleport station" when I realised that I also had to describe every single one of these preview images, at least those that face the camera in the preview image on the teleporter in the place that I was originally describing. And some of these preview images had images in them in turn.

I would have had to describe probably over a hundred images. In dozens of images. On teleporters which are shown in yet another image on a sub-pixel level. In an image description which was already going out of hand length-wise. On the second day that I was working on that image description. I would have had to teleport at least three times from the place shown in my image to be able to describe these sub-sub-subimages.

That was when I decided to sacrifice details for convenience and only describe what's visible in-world within the borders of the image, excluding both objects that are entirely obstructed by something else and surfaces that entirely face away from the point of view. I do fully transcribe any text that's partially obstructed, though, although I'm considering two transcripts of such texts, namely one transcript of what's visible and one full transcript for better understanding.

#Long #LongPost #CWLong #CWLongPost #Metaverse #VirtualWorlds #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta
hub.netzgemeinde.euInspector Jupiter Rowland, Scotland Yard...Taking a fully monochrome avatar to a fully monochrome place in OpenSim; CW: long (26,312 characters, including 889 characters of actual post and 25,271 characters in the image description)

Would it make sense to classify demanding others to use Content Warnings and alt text as harassment?

Looking at the mastodon.social server rules at mastodon.social/about, which, of course, don't mention this.

It just seems like this should be up to moderators to enforce, if CWs and alt text are even required, not vigilante users.

Would love to hear other people's/admins' thoughts.

Mastodon hosted on mastodon.socialMastodonThe original server operated by the Mastodon gGmbH non-profit
Replied in thread
@Morgan ⚧️ Well, what I meant with "do what I do anyway" is not what everyone else does.

My Fediverse meme posts have fairly standard image descriptions. What may make them long and complex are the explanations. They matter in this context because everyone else would explain meme images in the alt-text, but explanations don't belong into alt-text. And meme posts about Fediverse things do need a lot of explanation if they go beyond Mastodon, and mine tend to go way beyond Mastodon.

(Content warning: eye contact) My first attempt at a new meme-posting format on a new, specialised channel was made under the assumption that Mastodon users prefer explanations given to them on a silver platter, right in the post itself which also contains the image. I was told a while ago that external links are bad and inconvenient and probably not accessible, and it's better to explain everything myself.

I always have to explain the meme template, and especially in this case, I also had to explain the topic. So I ended up with nine explanations on four or five levels with some 25,000 characters altogether, more than half of which went into the two explanations for the topic.

I couldn't imagine that this was actually what people wanted, seeing as it was generally Mastodon users who seemed to want me to explain everything, but at the same time, it's Mastodon users who complain the most loudly about long posts. And so I ran a poll on how people actually wanted meme posts to be explained. At least of the few who voted, nobody wanted explanations in the post if they end up tens of thousands of characters long.

Ever since, I've delegated the meme template explanations to KnowYourMeme which I link to.

As for the topic, (content warning: eye contact, guns) sometimes it needs no explanation. Sometimes ](content warning: eye contact, food) it can entirely be covered by links. Sometimes (content warning: eye contact) I only need a short explanation.

But in cases like (content warning: eye contact, swearing) this or (content warning: eye contact, anger, crying, Japanese swearing) this, I have to write extensive explanations, even if I can link to a whole lot of external information sources.

For my original images, renderings from very obscure 3-D virtual worlds, I do much more. I always write two image descriptions for each image.

One goes into the alt-text, and it's as long as I can make it within the 1500-character limit imposed by Mastodon, Misskey and their forks. And that's the short description that's mostly only there to satisfy the "every image must have alt-text, no matter what" fundamentalists.

There's also a long description in the post itself which is much, much more detailed. It also contains all necessary explanations which I have to write myself because I can't really rely on external links. And if there's any text anywhere within the borders of the image, legible or not, verbatim transcripts of all these bits of text go into the long description.

My most recent example, already on my new image-posting channel, but from four months ago, is (content warning: eye contact) this. I've taken care to have as little scenery or surrounding or anything else in the pictures as possible, and still, I ended up with over 20,000 characters of image description. Here I explain why portraits are easier to describe.

A few examples with scenery, in chronological order, and much longer descriptions, and I consider them all outdated regardless: (content warning: eye contact, food) this, (content warning: eye contact) this and (content warning: eye contact) this.

The first two links also demonstrate how I used to describe pictures within a picture, even on three levels in the case of the second link. But if I had carried on doing this the same way for the image behind the third link, I would have had to describe over a hundred images in various locations on at least four levels. Besides, I would have described details that not only aren't visible in the image, but that aren't visible either in the place shown in the image. Also, this might have revealed eye contact or another trigger of sorts.

So I decided against describing things that cannot be seen in the shown place. This was the first time that I actually imposed a limitation on myself.

I could post many, many, many more scenery pictures, maybe even with actual scenery and with many more details. But it would always take me days to describe one of them. The last two image posts I've linked to required two days to write descriptions.

For example, I've been to a New Orleans-themed place a month ago. It would have made for a gorgeous picture report. But it would have taken me at least a week and a half to only describe the four images that Mastodon would let through. In fact, Mastodon would have rejected the post anyway because, with the massive image descriptions, it would have exceeded 100,000 characters by far.

If you're wondering why my descriptions of virtual world images have to be so long and so detailed, I've written an article about that.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta
Replied in thread
@Mr. Funk E. Dude The hashtag would be

#EyeContact

And, in addition to the one above, if you really want to drive the point home that the hashtag is there with a content-warning function to a) trigger post-removing/post-rejecting filters, b) trigger post-hiding filters on Mastodon and c) trigger the "NSFW" post-hiding feature on Friendica, Hubzilla, (streams) and Forte:

#CWEyeContact

I don't think there's any consensus on whether #CW and #ContentWarning should be used as actual content warning hashtags or for content warning discussions, which should be tagged #CWs, #ContentWarnings, #CWMeta and/or #ContentWarningMeta⁠, or for both. I mean, apart from #CW being constantly used for either "continuous wave" in amateur radiotelegraphy or the CW Television network.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #Filters #FediTips #Hashtag #Hashtags
MastodonMr. Funk E. Dude (@Mrfunkedude@mastodon.social)50.1K Posts, 107 Following, 4.29K Followers · Candidate for mayor of Mastodon. Rational man with an absurdist kink. Toot curator. Cynical Optimist. Grounded Psychonaut. Livestreamer. Maker of bread. Writer. Zombie killer. Secular Buddhist. Amateur photographer. Will create mischief for food. #fedi22 #MastoHelper #video #peertube #gaming #reviews #entertainment #baking #advice #live #livestreaming #kindness #mentalhealth #cannabis #adhd #dogs #cats Enjoy the content? Want to buy me a "bowl" ? https://ko-fi.com/mrfunkedude
@nellie-m @Shaula Evans I myself have put a food content warning on this post because there are Christmas-themed candy canes in what amounts to an image in an image in my image, and because there are berries on branches on another image in another image in my image. I've added an eye contact content warning for a similar reason: There are animals in several images in images in my image. And they've got eyes.

For starters, they may be microscopically tiny, but they're there. And I've been told that some autists can be triggered by microscopically tiny eyes in images. And besides, since they're there, the long image description in the post mentions them, even though you have to read at least some 20 minutes or so into it. And so they're in the post which justifies the content warnings, too.

I've stopped describing images in images in images when I got to an image that would have contained hundreds of them. But I still take all measures I can to keep people from being triggered by sensitive content in images within my images.

#Long #LongPost #CWLong #CWLongPost #ContentWarning #ContentWarnings #ContentWarningMeta #CW #CWs #CWMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
hub.netzgemeinde.euThe upcycling and upgrading of Clutterfly furniture continues14 more boxes of upgraded Clutterfly items released; CW: long post (almost 49,000 characters due to extremely long image descriptions, but the main post text itself is 770 characters long), eye contact (technically invisible, but present), food (berries and candy canes, technically invisible, but...

Interesting. When I search for “Norton Password Manager” on Chrome Web Store, it first lists five completely unrelated extensions, and only the last search result is the actual Norton Password Manager. Somebody told me that website is run by a company specializing in search, so this shouldn’t be due to incompetence, right? What is it then?