mastodon.me.uk

Jupiter RowlandIf Mastodon's various user interfaces won't constantly advertise groups after Mastodon has introduced them, nobody will use them; CW: long (almost 1,800 characters), Fediverse meta, Fediverse-beyond-Mastodon meta

Yellow FlagI 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.<a href="https://infosec.exchange/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a> <a href="https://infosec.exchange/tags/CWS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CWS</a> <a href="https://infosec.exchange/tags/ChromeWebStore" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChromeWebStore</a>

Yellow FlagI meant to publish a rant about Google and Chrome Web Store for a while now, and now it is out: <a href="https://palant.info/2025/01/13/chrome-web-store-is-a-mess/" rel="nofollow noopener" translate="no" target="_blank">https://palant.info/2025/01/13/chrome-web-store-is-a-mess/</a>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: <a href="https://palant.info/2025/01/13/biscience-collecting-browsing-history-under-false-pretenses/" rel="nofollow noopener" translate="no" target="_blank">https://palant.info/2025/01/13/biscience-collecting-browsing-history-under-false-pretenses/</a>This post provides more details on BIScience Ltd., another company selling browsing data of extension users. <a href="https://infosec.exchange/@tuckner" class="u-url mention" rel="nofollow noopener" target="_blank">@tuckner</a> 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.<a href="https://infosec.exchange/tags/google" class="mention hashtag" rel="nofollow noopener" target="_blank">#google</a> <a href="https://infosec.exchange/tags/cws" class="mention hashtag" rel="nofollow noopener" target="_blank">#cws</a> <a href="https://infosec.exchange/tags/ChromeExtensions" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChromeExtensions</a> <a href="https://infosec.exchange/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> <a href="https://infosec.exchange/tags/ChromeWebStore" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChromeWebStore</a>

Yellow FlagMy research on how Chrome extensions spam Chrome Web Store search with irrelevant keywords has been picked up by <a href="https://infosec.exchange/@dangoodin" class="u-url mention" rel="nofollow noopener" target="_blank">@dangoodin</a>: <a href="https://arstechnica.com/security/2025/01/googles-chrome-web-store-has-a-serious-spam-problem-promoting-shady-extensions/" rel="nofollow noopener" translate="no" target="_blank">https://arstechnica.com/security/2025/01/googles-chrome-web-store-has-a-serious-spam-problem-promoting-shady-extensions/</a>The article quotes me towards the end, something that is worth repeating:<blockquote>“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.”</blockquote><a href="https://infosec.exchange/tags/cws" class="mention hashtag" rel="nofollow noopener" target="_blank">#cws</a> <a href="https://infosec.exchange/tags/ChromeWebStore" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChromeWebStore</a> <a href="https://infosec.exchange/tags/google" class="mention hashtag" rel="nofollow noopener" target="_blank">#google</a> <a href="https://infosec.exchange/tags/ChromeExtensions" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChromeExtensions</a> <a href="https://infosec.exchange/tags/spam" class="mention hashtag" rel="nofollow noopener" target="_blank">#spam</a>

Yellow FlagBack 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. <a href="https://palant.info/2025/01/08/how-extensions-trick-cws-search/" rel="nofollow noopener" translate="no" target="_blank">https://palant.info/2025/01/08/how-extensions-trick-cws-search/</a>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?<a href="https://infosec.exchange/tags/google" class="mention hashtag" rel="nofollow noopener" target="_blank">#google</a> <a href="https://infosec.exchange/tags/cws" class="mention hashtag" rel="nofollow noopener" target="_blank">#cws</a> <a href="https://infosec.exchange/tags/ChromeExtensions" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChromeExtensions</a> <a href="https://infosec.exchange/tags/chrome" class="mention hashtag" rel="nofollow noopener" target="_blank">#chrome</a> <a href="https://infosec.exchange/tags/ChromeWebStore" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChromeWebStore</a> <a href="https://infosec.exchange/tags/spam" class="mention hashtag" rel="nofollow noopener" target="_blank">#spam</a>

Jupiter Rowland@<a href="https://social.dhelonious.de/@daniel" rel="nofollow noopener" target="_blank">Dr. Daniel Dizdarevic</a> 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 <a href="https://hub.netzgemeinde.eu/item/136f021c-06cb-4e38-abe6-2bf37fd521d8" rel="nofollow noopener" target="_blank">this post</a>. 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 <a href="https://hub.netzgemeinde.eu/item/f8ac991d-b64b-4290-be69-28feb51ba2a7" rel="nofollow noopener" target="_blank">what will probably remain my last image post on this channel</a>. 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. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Metaverse" rel="nofollow noopener" target="_blank">Metaverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=VirtualWorlds" rel="nofollow noopener" target="_blank">VirtualWorlds</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener" target="_blank">CW</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWs" rel="nofollow noopener" target="_blank">CWs</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWMeta" rel="nofollow noopener" target="_blank">CWMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarning" rel="nofollow noopener" target="_blank">ContentWarning</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarnings" rel="nofollow noopener" target="_blank">ContentWarnings</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarningMeta" rel="nofollow noopener" target="_blank">ContentWarningMeta</a>

Stefan BohacekWould it make sense to classify demanding others to use Content Warnings and alt text as harassment?Looking at the mastodon.social server rules at <a href="https://mastodon.social/about" rel="nofollow noopener" translate="no" target="_blank">https://mastodon.social/about</a>, 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.<a href="https://stefanbohacek.online/tags/FediAdmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#FediAdmin</a> <a href="https://stefanbohacek.online/tags/MastoAdmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#MastoAdmin</a> <a href="https://stefanbohacek.online/tags/CWs" class="mention hashtag" rel="nofollow noopener" target="_blank">#CWs</a> <a href="https://stefanbohacek.online/tags/netiquette" class="mention hashtag" rel="nofollow noopener" target="_blank">#netiquette</a> <a href="https://stefanbohacek.online/tags/fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#fediverse</a>

Jupiter Rowland@<a href="https://disabled.social/@raphaelmorgan" rel="nofollow noopener" target="_blank">Morgan ⚧️</a> 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) <a href="https://streams.elsmussols.net/item/8829de04-af65-4fa5-a6fa-438103c7d6c8" rel="nofollow noopener" target="_blank">My first attempt at a new meme-posting format on a new, specialised channel</a> 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 <a href="https://hub.netzgemeinde.eu/item/aeb3fcf9-48d4-44c8-88e0-b70c2336a512" rel="nofollow noopener" target="_blank">I ran a poll</a> 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) <a href="https://streams.elsmussols.net/item/400df1f5-1d25-45cd-bfa3-3b4093b9de8a" rel="nofollow noopener" target="_blank">sometimes it needs no explanation</a>. Sometimes ](content warning: eye contact, food) <a href="https://streams.elsmussols.net/item/1e9fa857-db59-4e22-bdaf-f05ff6b0c268" rel="nofollow noopener" target="_blank">it can entirely be covered by links</a>. Sometimes (content warning: eye contact) <a href="https://streams.elsmussols.net/item/572473d7-8087-4eb0-8dff-f44519a1c13e" rel="nofollow noopener" target="_blank">I only need a short explanation</a>. But in cases like (content warning: eye contact, swearing) <a href="https://streams.elsmussols.net/item/641bf10c-a56f-453e-a600-f1ae57a26a53" rel="nofollow noopener" target="_blank">this</a> or (content warning: eye contact, anger, crying, Japanese swearing) <a href="https://streams.elsmussols.net/item/ad44e605-618d-48ee-90ae-4bc15c6fa526" rel="nofollow noopener" target="_blank">this</a>, 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) <a href="https://streams.elsmussols.net/item/b6ae326a-c207-46dd-836b-6bc2b6a3509c" rel="nofollow noopener" target="_blank">this</a>. 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. <a href="https://streams.elsmussols.net/item/d67e641f-b1c2-46dd-9843-d1b88d362bb7" rel="nofollow noopener" target="_blank">Here</a> 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) <a href="https://hub.netzgemeinde.eu/item/8c2b4728-dda5-498b-9f84-2f11e163a4a5" rel="nofollow noopener" target="_blank">this</a>, (content warning: eye contact) <a href="https://hub.netzgemeinde.eu/item/c8a14063-b4e2-48fa-baf9-cb4faef7225b" rel="nofollow noopener" target="_blank">this</a> and (content warning: eye contact) <a href="https://hub.netzgemeinde.eu/item/f8ac991d-b64b-4290-be69-28feb51ba2a7" rel="nofollow noopener" target="_blank">this</a>. 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, <a href="https://hub.netzgemeinde.eu/item/2cc2a459-97ce-4fbe-8aa2-86e367b5554e" rel="nofollow noopener" target="_blank">I've been to a New Orleans-themed place</a> 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, <a href="https://hub.netzgemeinde.eu/item/95b6e36d-7fcd-4791-8cc1-c93e8b9975a3" rel="nofollow noopener" target="_blank">I've written an article about that</a>. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener" target="_blank">CW</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWs" rel="nofollow noopener" target="_blank">CWs</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWMeta" rel="nofollow noopener" target="_blank">CWMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarning" rel="nofollow noopener" target="_blank">ContentWarning</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarnings" rel="nofollow noopener" target="_blank">ContentWarnings</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarningMeta" rel="nofollow noopener" target="_blank">ContentWarningMeta</a>

Jupiter Rowland@<a href="https://mastodon.social/users/Mrfunkedude" rel="nofollow noopener" target="_blank">Mr. Funk E. Dude</a> The hashtag would be #<a class="" href="https://hub.netzgemeinde.eu/search?tag=EyeContact" rel="nofollow noopener" target="_blank">EyeContact</a> 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: #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWEyeContact" rel="nofollow noopener" target="_blank">CWEyeContact</a> I don't think there's any consensus on whether #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener" target="_blank">CW</a> and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarning" rel="nofollow noopener" target="_blank">ContentWarning</a> should be used as actual content warning hashtags or for content warning discussions, which should be tagged #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWs" rel="nofollow noopener" target="_blank">CWs</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarnings" rel="nofollow noopener" target="_blank">ContentWarnings</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWMeta" rel="nofollow noopener" target="_blank">CWMeta</a> and/or #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarningMeta%E2%81%A0" rel="nofollow noopener" target="_blank">ContentWarningMeta⁠</a>, or for both. I mean, apart from #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener" target="_blank">CW</a> being constantly used for either "continuous wave" in amateur radiotelegraphy or the CW Television network. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener" target="_blank">Mastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener" target="_blank">Forte</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Filters" rel="nofollow noopener" target="_blank">Filters</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediTips" rel="nofollow noopener" target="_blank">FediTips</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hashtag" rel="nofollow noopener" target="_blank">Hashtag</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hashtags" rel="nofollow noopener" target="_blank">Hashtags</a>

Touaregtweet'De CWS rondt vier à vijf dossiers per week af, zo blijkt uit het rapport. Bij 35 duizend dossiers en een productiegemiddelde van vijf dossiers per week zou dat 135 jaar duren. Toen de aanmeldingstermijn voor gedupeerden van het toeslagenschandaal eind december 2023 sloot, waren er 69.049 aanmeldingen.'<a href="https://www.ftm.nl/artikelen/commissie-werkelijke-schade-toeslagen?share=8k5wXTF9HZ27NP%2BwsFrzM3Uf4RSc7PWQJn5pY%2F7Dk6IZUBAy23KnHjw5HurP" rel="nofollow noopener" translate="no" target="_blank">https://www.ftm.nl/artikelen/commissie-werkelijke-schade-toeslagen?share=8k5wXTF9HZ27NP%2BwsFrzM3Uf4RSc7PWQJn5pY%2F7Dk6IZUBAy23KnHjw5HurP</a> <a href="https://mastodon.social/tags/toeslagenschandaal" class="mention hashtag" rel="nofollow noopener" target="_blank">#toeslagenschandaal</a> <a href="https://mastodon.social/tags/CWS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CWS</a> <a href="https://mastodon.social/tags/ftm" class="mention hashtag" rel="nofollow noopener" target="_blank">#ftm</a>

Yellow FlagInteresting. 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?<a href="https://infosec.exchange/tags/google" class="mention hashtag" rel="nofollow noopener" target="_blank">#google</a> <a href="https://infosec.exchange/tags/cws" class="mention hashtag" rel="nofollow noopener" target="_blank">#cws</a>

Maxi 11x 💉Uff, das neue Webdesign von Mastodon 4.3. Hab mal einen Screenshot von 4.2 halbtransparent darüber gelegt. Regt mich jetzt schon hart auf, wie viel Platz durch die Einrückung im Benachrichtigungsreiter verloren geht.Das 'Absperrband' für <a href="https://chaos.social/tags/CWs" class="mention hashtag" rel="nofollow noopener" target="_blank">#CWs</a> macht sie auch sehr unattraktiv und verengt ihre Funktion visuell auf Triggerwarnungen, die aber nur ein Teilaspekt ihrer sozialen Rolle hier sind. Versteh ich nicht, wie man das so an der Community vorbei designen kann. <a href="https://chaos.social/tags/Mastodon43" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mastodon43</a>

Jupiter Rowland@<a href="https://social.wedistribute.org/users/damon" rel="nofollow noopener" target="_blank">damon</a> It doesn't help that Mastodon itself is largely a bubble. Some 70% of all Fediverse users are on Mastodon. But it seems like that within Mastodon itself, at least 95% of all posts originate from Mastodon. Maybe even more. There are several reasons for this. First of all, other projects don't federate with Mastodon that much. Misskey is huge in East Asia, especially Japan. And Japanese Misskey users who hardly know English or not at all won't be interested in connecting with Western Mastodon users, so a large chunk of the second-biggest free project in the Fediverse is out of the equation. Lemmy is the third-biggest, but Lemmy federates with Mastodon only barely so, also because Lemmy is all about discussion groups and enclosed conversations, both of which Mastodon simply doesn't support. Lemmy users can't follow Mastodon users because Lemmy users can't follow users, full stop. And Mastodon users have to wrap their minds around how to federate with Lemmy. It isn't as straight-forward as communication within Mastodon. And so they simply don't. Other examples include Hubzilla and (streams) channels having ActivityPub off on purpose to keep ignorant and obnoxious Mastodon users out. But this goes the other way as well. Mastodon can be outright hostile to non-Mastodon users. Why? Because they don't behave like what Mastodon users are used to from Mastodon and, by extent, partly also Twitter. And they have joined the Fediverse in expectation of something that's one big distributed but homogenous Twitter clone. Anything that deviates from that may be disturbing. There are Mastodon users who, upon seeing a post with over 500 characters, and be it in the federated timeline, block the poster. This alone cuts into the reach of everything that isn't Mastodon. Not few wish for a switch with which they can permanently filter out all posts with over 500 characters. Others may block everyone who uses text formatting. Either it simply goes on their nerves. Or they can't imagine that it's even possible to format text in the Fediverse because they can't do that on Mastodon, so they think it's all some Unicode trickery. And as this Unicode trickery is not accessible and inclusive because it irritates screen readers, they deem whoever uses text formatting ableist and therefore blockworthy. Then there's the issue of content warnings. They must be provided the Mastodon way, or you risk being blocked. However, not everything out there provides a) the right text field with b) the right label on it. Non-Mastodon projects may still label the summary field a summary field instead of a CW field like Mastodon does. Friendica, for example, has done away with that text field entirely and users BBcode tags instead. Hubzilla doesn't provide any means of adding a summary/a Mastodon CW to a reply. And both have had their own way of adding CWs since long before there was Mastodon which their own users consider vastly superior to Mastodon's way. In general, boosts are very important on Mastodon. I'd say that most activity on Mastodon is boosts because they're so easy to do on a phone without a hardware keyboard. Your reach on Mastodon depends on boosts. But if you don't play exactly along Mastodon's written and unwritten rules, and if you don't adhere to the "Fediquette" which is entirely defined by only Mastodon users and geared towards only Mastodon's features (or lack thereof), you're boosted far less. If you post more than 500 characters at once, it takes a lot for your post to get boosted. If you post an image without alt-text, the post will be boosted dramatically less because not exactly few Mastodon users refuse to boost image posts without alt-text. You may even be muted or blocked for not providing alt-text. But alt-text only is a thing on Mastodon, and hardly anyone provides it outside Mastodon. In general, anything that deviates from the standards defined by vanilla Mastodon will cut into your visibility on Mastodon deeply. CC: @<a href="https://social.fedcast.ch/users/Hiker" rel="nofollow noopener" target="_blank">Hiker</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener" target="_blank">Mastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=NotOnlyMastodon" rel="nofollow noopener" target="_blank">NotOnlyMastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener" target="_blank">CW</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWs" rel="nofollow noopener" target="_blank">CWs</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWMeta" rel="nofollow noopener" target="_blank">CWMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarning" rel="nofollow noopener" target="_blank">ContentWarning</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarnings" rel="nofollow noopener" target="_blank">ContentWarnings</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarningMeta" rel="nofollow noopener" target="_blank">ContentWarningMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediquette" rel="nofollow noopener" target="_blank">Fediquette</a>

Jupiter Rowland@<a href="https://chaos.social/@f4grx" rel="nofollow noopener" target="_blank">F4GRX SÃ©bastien</a> If I had any way to add another click-to-open level that works on Mastodon as well without mobile users having to deal with their Web browser popping open, I would. Things would be way easier if sensitive Mastodon users got used to the concept of filters, though, and learned how to set them up. That's one reason for my many hashtags. But it's strange to see someone from chaos.social irritated by too many CWs. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener" target="_blank">Mastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener" target="_blank">CW</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWs" rel="nofollow noopener" target="_blank">CWs</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWMeta" rel="nofollow noopener" target="_blank">CWMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarning" rel="nofollow noopener" target="_blank">ContentWarning</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarnings" rel="nofollow noopener" target="_blank">ContentWarnings</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarningMeta" rel="nofollow noopener" target="_blank">ContentWarningMeta</a>

Jupiter RowlandHat Friendica aber wieder ein dediziertes Zusammenfassungs-Textfeld? Die alte Dreifaltigkeit Titel, Zusammenfassung, Post? Ich schrieb ja über Mastodon-Apps und Friendica, daß eine Mastodon-App irgendwas braucht, was genauso funktioniert wie Mastodons CW-Feld. Etwas, wo sie verläßlich immer eine CW reindrücken kann, so daß die dann genauso verläßlich wie auf Mastodon als CW funktioniert. Und zwar, ohne auf irgendwelche projektspezifischen Spezialitäten eingehen zu können. Die App muß Friendica immer 100% verläßlich blind wie Mastodon "bedienen" können. Natürlich kann man auf Friendica den Titel als Zusammenfassung/CW nehmen. Aber zum einen muß das eingestellt werden. Zum anderen muß die App dann die CW ins Titelfeld eintragen. Eine Mastodon-App wird aber stur versuchen, die CW ins Zusammenfassungsfeld zu drücken, ob da jetzt eins ist oder nicht. Wenn sie jetzt die CW ins Titelfeld eintragen soll, dann ist das ein Friendica-Spezialfeature. Wenn sie selbsttätig aus den Einstellungen erkennen soll, ob die CW in den Titel eingetragen oder z. B. als BBcode realisiert werden soll, ist das erst recht ein Friendica-Spezialfeature. Ich weiß nicht, vielleicht kann Fedilab das. Aber die ganzen praktisch reinen Mastodon-Apps, die von Leuten entwickelt werden, die ihren Lebtag von Friendica noch nie auch nur gehört haben, die können das nicht. Eine rein gegen Mastodon entwickelte App wird wiederum für Alt-Text ein Textfeld anbieten, das den Alt-Text in ein Bild einträgt, das an einen Post als Datei angehängt ist. So läuft das nämlich auf Mastodon und nur so. Mein letzter Informationsstand ist, daß genau das aber auf Friendica nicht geht. Wenn man da Alt-Text haben will, muß man das Bild erst hochladen, dann in-line in den Post einbetten und dann den Alt-Text in den BBcode eintragen. Theoretisch ginge das auch mit einer App. Aber das wäre wieder ein Friendica-Special-Feature. Und eine reine Mastodon-App von einem Entwickler, der Friendica überhaupt nicht kennt, unterstützt keine Friendica-Special-Features, sondern wirklich nur und ausschließlich Sachen, die Mastodon kann und die Mastodon genau so macht. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LangerPost" rel="nofollow noopener" target="_blank">LangerPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLangerPost" rel="nofollow noopener" target="_blank">CWLangerPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener" target="_blank">CW</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWs" rel="nofollow noopener" target="_blank">CWs</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWMeta" rel="nofollow noopener" target="_blank">CWMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarning" rel="nofollow noopener" target="_blank">ContentWarning</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarnings" rel="nofollow noopener" target="_blank">ContentWarnings</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarningMeta" rel="nofollow noopener" target="_blank">ContentWarningMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MastodonApp" rel="nofollow noopener" target="_blank">MastodonApp</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MastodonApps" rel="nofollow noopener" target="_blank">MastodonApps</a>

Jupiter RowlandMy most recent introduction post as per August 7th, 2024; CW: long (xx,xxx characters), Fediverse meta, Fediverse beyond Mastodon meta, alt-text meta, image description meta, content warning meta, hashtag meta

Kevin Karhan :verified:<a href="https://awawa.club/users/byte" class="u-url mention" rel="nofollow noopener" target="_blank">@byte</a> +9001%<a href="https://infosec.space/tags/AltText" class="mention hashtag" rel="nofollow noopener" target="_blank">#AltText</a> and <a href="https://infosec.space/tags/CWs" class="mention hashtag" rel="nofollow noopener" target="_blank">#CWs</a> should be absolutely mandatory...

Jupiter Rowland@<a href="https://graz.social/@publicvoit" rel="nofollow noopener" target="_blank">Karl Voit :emacs: :orgmode:</a> Der Abschnitt "Update: Friendica posts in Mastodon" ist nicht nur sachlich falsch, sondern auch noch stark unvollständig. Ich als langjähriger Hubzilla-Nutzer mit Friendica-Vergangenheit würde das eher so formulieren: Update: Posts and comments from Friendica, Hubzilla and (streams) in Mastodon Posts and comments coming into Mastodon from Friendica, Hubzilla and (streams) are special cases. That's because neither of them have Mastodon's dedicated CW field. Instead, they have reader-side content warnings that can optionally be created automatically. By default, a post is automatically hidden behind a content warning button if it contains "nsfw" and/or "sensitive". Automatic reader-side content warnings have been part of the culture of both Friendica and Hubzilla since before Mastodon was even made as well as of fairly new (streams). Poster-side content warnings in a dedicated field have never been part of their culture, both because they've got a much better solution for content warnings and because they don't provide dedicated means for poster-side content warnings. Technically speaking, Hubzilla and (streams) do have Mastodon's CW field. But unlike Mastodon, it isn't labelled "CW". It's labelled "summary". It has been a summary field originally, but since a hard-coded maximum of 500 characters doesn't require summaries, Mastodon repurposed that field for content warnings. Hubzilla and (streams) have no character limits at all, so using that field for summaries is still justified. Hence, Hubzilla and (streams) users use this field for short summaries for very long posts, if at all, but not for content warnings. Also, just like Friendica, both Hubzilla and (streams) have a conversation model like Facebook or Tumblr or blogs with only one post and many comments. All replies are comments, and there is a separate, dedicated entry form for comments under each post. This entry form does not, however, have a summary field because what sense does it make to give a summary for a blog comment? Hence, Hubzilla and (streams) users can't put Mastodon-style content warnings on replies at all. Also, neither Hubzilla nor (streams) can re-use content warnings from posts or comments they reply to. Friendica, the oldest one of the three, doesn't even have a dedicated summary field. The only way to add a summary, i.e. a Mastodon-style CW, is between the Friendica-specific BBcode tag pair <code>[abstract][/abstract]</code>. This works in both posts and comments, but the availability of this tag pair is neither advertised in the post editor nor in the comment editor. Since Friendica doesn't have a dedicated UI element for Mastodon-style CWs, neither for posts nor for comments, most Friendica users don't give Mastodon-style CWs at all because they simply don't know that this is possible in the first place, much less how. Also, users of Friendica, Hubzilla and (streams) tend to find the idea of writing a content warning between a pair of obscure BBcode tags (Friendica) or into the summary field (Hubzilla, (streams)) ridiculous. Trying to convince them otherwise would be like trying to convince Mastodon users to double their CWs with keywords or hashtags to trigger the NSFW content-warning generation on non-Mastodon projects. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener" target="_blank">CW</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWs" rel="nofollow noopener" target="_blank">CWs</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarning" rel="nofollow noopener" target="_blank">ContentWarning</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarnings" rel="nofollow noopener" target="_blank">ContentWarnings</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarningMeta" rel="nofollow noopener" target="_blank">ContentWarningMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener" target="_blank">(streams)</a>

Jupiter Rowland@<a href="https://mstdn.party/@CatHat" rel="nofollow noopener" target="_blank">Hat.  Cat in an N95😷</a> If I actually wanted to make my pictures themselves accessible, I'd stop taking pictures in #<a class="" href="https://hub.netzgemeinde.eu/search?tag=VirtualWorlds" rel="nofollow noopener" target="_blank">VirtualWorlds</a> with scenery in them. Portraits of avatars with a plain white background, images of single objects with a plain white background, that'd be it. It'd save me a lot of time describing and explaining and transcribing things that don't really matter within the context of the post, but that people might want to know about. Maybe then I could fit a full image description into Mastodon-size #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener" target="_blank">AltText</a>. Maybe. And it'd also save me a lot of hassle with #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWs" rel="nofollow noopener" target="_blank">CWs</a> that don't even work properly from Hubzilla to Mastodon because there might be something in detailed background scenery that could insult or disturb or trigger someone. I mean, one of the several buildings on a medieval or urban sim, maybe tucked away in the background, could be a church that'd require a #<a class="" href="https://hub.netzgemeinde.eu/search?tag=religion" rel="nofollow noopener" target="_blank">religion</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarning" rel="nofollow noopener" target="_blank">ContentWarning</a>. There could be some human figure somewhere in that busy scenery that just happens to be oriented towards the general direction of the point-of-view, that'd therefore require an #<a class="" href="https://hub.netzgemeinde.eu/search?tag=EyeContact" rel="nofollow noopener" target="_blank">EyeContact</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener" target="_blank">CW</a>. There could be a mostly white speck of two and a half pixels on an 800x533-pixel image that looks somewhat like an ambulance because it actually is an ambulance in-world, and therefore it'd require #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarnings" rel="nofollow noopener" target="_blank">ContentWarnings</a> for #<a class="" href="https://hub.netzgemeinde.eu/search?tag=health" rel="nofollow noopener" target="_blank">health</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=PhysicalHealth" rel="nofollow noopener" target="_blank">PhysicalHealth</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=medicine" rel="nofollow noopener" target="_blank">medicine</a> and maybe even #<a class="" href="https://hub.netzgemeinde.eu/search?tag=work" rel="nofollow noopener" target="_blank">work</a>. But if I do want to post about an entire sim rather than an object or an avatar, I've got a problem. Also, I've just realised that I've yet to solve the problem of where to put image descriptions for illustrated long-form articles <a href="https://hub.netzgemeinde.eu/articles/jupiter_rowland" rel="nofollow noopener" target="_blank">which Hubzilla can do as well</a>. I think it's obvious that I can't put them into the article itself.

Warmth Highest<a href="https://mastodon.online/tags/cws" class="mention hashtag" rel="nofollow noopener" target="_blank">#cws</a> <a href="https://mastodon.online/tags/baseball" class="mention hashtag" rel="nofollow noopener" target="_blank">#baseball</a> <a href="https://apnews.com/article/college-world-series-2023-lsu-a0b66765c437af99e4641e177780a100" rel="nofollow noopener" translate="no" target="_blank">https://apnews.com/article/college-world-series-2023-lsu-a0b66765c437af99e4641e177780a100</a>

Recent searches

Search options

Administered by:

Server stats:

#cws