#sharkey — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #sharkey, aggregated by home.social.
-
Da soll mal noch jemand sagen, das #Fediverse hätte keine Reichweite.
Ich mit meinen eher kleinen und ziemlich überschaubaren Follower-Zahlen habe auf einen einzigen Beitrag insgesamt 265 Reaktionen bekommen. Likes, Sterne, Boosts, Emojis, Antworten. Und das alles in gerade mal ungefähr acht Stunden.
Vielleicht fühlt sich das Fediverse manchmal leiser an als andere Netzwerke. Aber wenn ein Thema Menschen wirklich anspricht, dann entstehen dort immer echte Gespräche und echter Diskurs. Genau deshalb bin ich gerne hier.#Fediverse #Friendica #Mastodon #Sharkey #Pleroma #Misskey #Akkoma #Pixelfed #Lemmy
RE: f.utzer.de/objects/f5430ab4-13… -
Da soll mal noch jemand sagen, das #Fediverse hätte keine Reichweite.
Ich mit meinen eher kleinen und ziemlich überschaubaren Follower-Zahlen habe auf einen einzigen Beitrag insgesamt 265 Reaktionen bekommen. Likes, Sterne, Boosts, Emojis, Antworten. Und das alles in gerade mal ungefähr acht Stunden.
Vielleicht fühlt sich das Fediverse manchmal leiser an als andere Netzwerke. Aber wenn ein Thema Menschen wirklich anspricht, dann entstehen dort immer echte Gespräche und echter Diskurs. Genau deshalb bin ich gerne hier.#Fediverse #Friendica #Mastodon #Sharkey #Pleroma #Misskey #Akkoma #Pixelfed #Lemmy
RE: f.utzer.de/objects/f5430ab4-13… -
Da soll mal noch jemand sagen, das #Fediverse hätte keine Reichweite.
Ich mit meinen eher kleinen und ziemlich überschaubaren Follower-Zahlen habe auf einen einzigen Beitrag insgesamt 265 Reaktionen bekommen. Likes, Sterne, Boosts, Emojis, Antworten. Und das alles in gerade mal ungefähr acht Stunden.
Vielleicht fühlt sich das Fediverse manchmal leiser an als andere Netzwerke. Aber wenn ein Thema Menschen wirklich anspricht, dann entstehen dort immer echte Gespräche und echter Diskurs. Genau deshalb bin ich gerne hier.#Fediverse #Friendica #Mastodon #Sharkey #Pleroma #Misskey #Akkoma #Pixelfed #Lemmy
RE: f.utzer.de/objects/f5430ab4-13… -
Da soll mal noch jemand sagen, das #Fediverse hätte keine Reichweite.
Ich mit meinen eher kleinen und ziemlich überschaubaren Follower-Zahlen habe auf einen einzigen Beitrag insgesamt 265 Reaktionen bekommen. Likes, Sterne, Boosts, Emojis, Antworten. Und das alles in gerade mal ungefähr acht Stunden.
Vielleicht fühlt sich das Fediverse manchmal leiser an als andere Netzwerke. Aber wenn ein Thema Menschen wirklich anspricht, dann entstehen dort immer echte Gespräche und echter Diskurs. Genau deshalb bin ich gerne hier.#Fediverse #Friendica #Mastodon #Sharkey #Pleroma #Misskey #Akkoma #Pixelfed #Lemmy
RE: f.utzer.de/objects/f5430ab4-13… -
Da soll mal noch jemand sagen, das #Fediverse hätte keine Reichweite.
Ich mit meinen eher kleinen und ziemlich überschaubaren Follower-Zahlen habe auf einen einzigen Beitrag insgesamt 265 Reaktionen bekommen. Likes, Sterne, Boosts, Emojis, Antworten. Und das alles in gerade mal ungefähr acht Stunden.
Vielleicht fühlt sich das Fediverse manchmal leiser an als andere Netzwerke. Aber wenn ein Thema Menschen wirklich anspricht, dann entstehen dort immer echte Gespräche und echter Diskurs. Genau deshalb bin ich gerne hier.#Fediverse #Friendica #Mastodon #Sharkey #Pleroma #Misskey #Akkoma #Pixelfed #Lemmy
RE: f.utzer.de/objects/f5430ab4-13… -
@[email protected] Jep, die sind toll 🤭 Nur schade, werden die bei Mastodon nicht einmal als Stern wiedergegeben 🤔 #neuhier #fediverse #sharkey
-
So, ich starte nun doch mein neues Fediverse-Abenteuer 👀
Ich habe mir einen Account auf Sharkey eingerichtet und werde dort erstmal ein bisschen herumprobieren.
Vorerst bleiben beide Accounts bestehen, bis ich herausgefunden habe, welche Plattform besser zu mir passt. Mehrere Accounts dauerhaft parallel zu bespielen, kostet nämlich ehrlich gesagt deutlich mehr Energie, als ich an Löffeln zur Verfügung habe 🥄 😅Ihr findet mich unter:
@[email protected]Folgt mir gerne auch dort, solange ich mich noch nicht entschieden habe, kann ich euch leider nicht "mitnehmen" 😉
Ich würde mich freuen, dort viele bekannte Gesichter wiederzusehen 😊
-
Hallihallo 👋
Nachdem ich letztes Jahr mit Mastodon ins Fediverse eingestiegen bin, probiere ich nun eine weitere Fedi-Plattform aus und bin auf Empfehlung hier gelandet 😊
Ich bin gespannt, wie sich Sharkey im Alltag anfühlt, welche grossartigen Features es hier gibt und welche Menschen ich hier kennenlernen werde ✨
Bis auf Weiteres behalte ich meinen Mastodon-Account noch, daher übertrage ich erstmal nichts. Sollte ich mich hier langfristig wohler fühlen, wird dieser Account mein Hauptaccount werden.
Mehrere Accounts parallel zu bespielen, verlangt nämlich deutlich mehr Löffel, als ich aktuell übrig habe 🥄 😅
Infos zu mir findet ihr in der Bio, und alles andere darf sehr gerne ungeniert gefragt werden 😊
Ich nehme übrigens sehr gerne Sharkey-Anfänger*innen-Tipps entgegen, sei es zu Features, Gepflogenheiten oder auch einfach dazu, wie eins hier eigentlich die Followys nennt 🤭 #neuhier #fediverse #sharkey -
Ich spiele mit dem Gedanken, Sharkey mal auszuprobieren.
Einige hier "schwärmen" ja immer wieder davon ... 👀
Wenn ihr euch angesprochen fühlt: vermutlich nicht ohne Grund 🤭 -
More Stickers are needing to be designed.
The Fediverse Stickers are now on https://vex.blue/shop/ so you can order them. But what is the next stickers you'd love to see?
Any artists wanna work together to create something unique for the Fediverse together?
#Stickers #Fediverse #FediverseMerch #FediverseMarketing #Marketing #SmallBusiness #Fedi #Mastodon #Sharkey #ActivityPub #Misskey #PixelFed #Loops #PeerTube -
-
@[email protected] bitte, sehr gerne doch.
Ich hätte noch weitere, falls Bedarf besteht.
Ich bin mit #Calckey im Fediverse unterwegs, das ist ähnlich wie #Sharkey. Weils nicht so einschränkt 😉
https://tube.tchncs.de/w/w8bVvpfaZLsSbQQkPUPjy9 -
@[email protected] wenn du zu #Sharkey umziehen würdest 😉 kannst du auch alle Beiträge mitnehmen. Egal ob 300, 3000 oder 30.000
Mal von den ganzen anderen Features nicht gesprochen....
https://tube.tchncs.de/w/w8bVvpfaZLsSbQQkPUPjy9
#FediTipp #Fediverse
@[email protected] -
12 Sticker Large Fediverse Pack has now been released.
Get 12 Fediverse Stickers ~50mm each for £9. Showing off various Fediverse Software for you to enjoy and share on your laptops, Notebooks, Vehicle and more.
They all have a water resistant laminate protecting your design from rain water.
Check them out now: https://ko-fi.com/s/0caa46706b
#Fediverse #FediverseStickers #Stickers #SmallBusiness #Mastodon #Sharkey #Lemmy #PieFed #Misskey #PeerTube #Loops #PixelFed #Decentralized -
12 Sticker Large Fediverse Pack has now been released.
Get 12 Fediverse Stickers ~50mm each for £9. Showing off various Fediverse Software for you to enjoy and share on your laptops, Notebooks, Vehicle and more.
They all have a water resistant laminate protecting your design from rain water.
Check them out now: https://ko-fi.com/s/0caa46706b
#Fediverse #FediverseStickers #Stickers #SmallBusiness #Mastodon #Sharkey #Lemmy #PieFed #Misskey #PeerTube #Loops #PixelFed #Decentralized -
12 Sticker Large Fediverse Pack has now been released.
Get 12 Fediverse Stickers ~50mm each for £9. Showing off various Fediverse Software for you to enjoy and share on your laptops, Notebooks, Vehicle and more.
They all have a water resistant laminate protecting your design from rain water.
Check them out now: https://ko-fi.com/s/0caa46706b
#Fediverse #FediverseStickers #Stickers #SmallBusiness #Mastodon #Sharkey #Lemmy #PieFed #Misskey #PeerTube #Loops #PixelFed #Decentralized -
12 Sticker Large Fediverse Pack has now been released.
Get 12 Fediverse Stickers ~50mm each for £9. Showing off various Fediverse Software for you to enjoy and share on your laptops, Notebooks, Vehicle and more.
They all have a water resistant laminate protecting your design from rain water.
Check them out now: https://ko-fi.com/s/0caa46706b
#Fediverse #FediverseStickers #Stickers #SmallBusiness #Mastodon #Sharkey #Lemmy #PieFed #Misskey #PeerTube #Loops #PixelFed #Decentralized -
Bigger Versions of these Fediverse Stickers will be coming to our store in the near future. Each being updated to a 50mm Height format instead of the current 25mm of these small ones.
What do you think of these stickers? Would you purchase something like this?
@[email protected]
#Fediverse #FediverseStickers #Stickers #SmallBusiness #Mastodon #Sharkey #Lemmy #PieFed #Misskey #PeerTube #Loops #PixelFed #Advert #Decentralized #SupportSmallCreators -
Bigger Versions of these Fediverse Stickers will be coming to our store in the near future. Each being updated to a 50mm Height format instead of the current 25mm of these small ones.
What do you think of these stickers? Would you purchase something like this?
@[email protected]
#Fediverse #FediverseStickers #Stickers #SmallBusiness #Mastodon #Sharkey #Lemmy #PieFed #Misskey #PeerTube #Loops #PixelFed #Advert #Decentralized #SupportSmallCreators -
Bigger Versions of these Fediverse Stickers will be coming to our store in the near future. Each being updated to a 50mm Height format instead of the current 25mm of these small ones.
What do you think of these stickers? Would you purchase something like this?
@[email protected]
#Fediverse #FediverseStickers #Stickers #SmallBusiness #Mastodon #Sharkey #Lemmy #PieFed #Misskey #PeerTube #Loops #PixelFed #Advert #Decentralized #SupportSmallCreators -
Bigger Versions of these Fediverse Stickers will be coming to our store in the near future. Each being updated to a 50mm Height format instead of the current 25mm of these small ones.
What do you think of these stickers? Would you purchase something like this?
@[email protected]
#Fediverse #FediverseStickers #Stickers #SmallBusiness #Mastodon #Sharkey #Lemmy #PieFed #Misskey #PeerTube #Loops #PixelFed #Advert #Decentralized #SupportSmallCreators -
Bigger Versions of these Fediverse Stickers will be coming to our store in the near future. Each being updated to a 50mm Height format instead of the current 25mm of these small ones.
What do you think of these stickers? Would you purchase something like this?
@[email protected]
#Fediverse #FediverseStickers #Stickers #SmallBusiness #Mastodon #Sharkey #Lemmy #PieFed #Misskey #PeerTube #Loops #PixelFed #Advert #Decentralized #SupportSmallCreators -
🚀 Mini Fediverse Sticker Pack is here!
Show your love for the decentralized web with 22 stickers (11 designs, 2 of each) featuring your favourite platforms like Mastodon, Misskey, PixelFed, Lemmy & more.
✨ ~25mm die-cut stickers
✨ Easy-peel backing (accessible & hassle-free)
✨ Laminated for extra durability & water resistance
Perfect for laptops, notebooks, cases, and anywhere you want to rep the Fediverse 🌐
👉 https://ko-fi.com/s/f3a2f9c606
#Fediverse #Stickers #Mastodon #Misskey #Sharkey #PixelFed #Lemmy #ActivityPub #Decentralized #IndieMaker #SmallBusiness #Creative #StickerPack #SupportSmallCreators #FediArt #OpenWeb #TechCommunity -
I'm super excited - I just deployed the forums feature in catodon.rocks and it seems to work, I made my first post in a Lemmy community!
I definitely have a lot of work to do, but you can -cautiously!- test the feature on our server, it is live. If something serious shows up, I will revert it and try again tomorrow. But this feels awesome - the first (proper) threadiverse post from a Misskey/Sharkey fork! Let's go 🥳
#catodon #sharkey #misskey #fediverse #threadiverse
RE: https://catodon.rocks/notes/akv4dziup8bz00hy -
Heads up for anyone who might be thinking of migrating to Catodon from Sharkey with the option to migrate back: It seems like you will currently lose any Pages if you migrate back to Sharkey (because of the AiScript removal). I will fix this in a few days. Until then, perhaps postpone migrations, unless you don't have any significant Pages, or if you don't mind recreating the lost Pages.
#catodon #sharkey -
kleine Service Info, ich hab jetzt meine #Sharkey Server umgestellt umgestellt von #Meilisearch auf #PGroonga
#fedimins
Mit Meilisearch hatte ich ein kleines Hitze ble aufgrund der kontinuierlichen Indexierung. Mit pgroonga Habe ich das kurioserweise nicht. -
kleine Service Info, ich hab jetzt meine #Sharkey Server umgestellt umgestellt von #Meilisearch auf #PGroonga
#fedimins
Mit Meilisearch hatte ich ein kleines Hitze ble aufgrund der kontinuierlichen Indexierung. Mit pgroonga Habe ich das kurioserweise nicht. -
kleine Service Info, ich hab jetzt meine #Sharkey Server umgestellt umgestellt von #Meilisearch auf #PGroonga
#fedimins
Mit Meilisearch hatte ich ein kleines Hitze ble aufgrund der kontinuierlichen Indexierung. Mit pgroonga Habe ich das kurioserweise nicht. -
kleine Service Info, ich hab jetzt meine #Sharkey Server umgestellt umgestellt von #Meilisearch auf #PGroonga
#fedimins
Mit Meilisearch hatte ich ein kleines Hitze ble aufgrund der kontinuierlichen Indexierung. Mit pgroonga Habe ich das kurioserweise nicht. -
Mittlerweile gibt es so viele Journalisten im #Fediverse, dass ich mich echt frage, weshalb nicht viel mehr darüber geschrieben wird in den grossen Medien. Nein, alles was gross publiziert wird sind #fckTrump, #fckBigTech, #fckAI etc.
Wenn sich die Journis hier mal zusammentun würden und mal organisiert über längere Zeit über das Fediverse schreiben würden, sähe es bzgl. Anzahl Nutzer:innen hier vermutlich ganz anders aus.
#journalism #Journalismus #Mastodon #Friendica #Pleroma #Sharkey
-
@That Old Guy with the Beard @libertyoftheforest @Melissa BearTrix Actually, you must never do either.
You must never put any exclusive information such as explanations only into the alt-text.
That's because there are people who cannot access alt-text, be it due to physical disabilities (you can't access alt-text if you don't have at least one working hand, at least not easily), be it due to their choice of software.
If there's any information not in the image, not in the post text, only in the alt-text, then these people will not be able to get this information. It's lost to them.
So do not use alt-text to expand your 500-character limit!
If you need more than 500 characters once, write a thread.
If you need more than 500 characters regularly, move to where you have more characters, e.g.:- a Mastodon server with a higher character count
- a Mastodon fork with a higher character count
- Misskey (3,000 characters)
- Sharkey (at least 3,000 characters, often even more)
- Akkoma (at least 5,000 characters)
- Friendica (16,777,215 characters)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Misskey #Sharkey #Akkoma #Friendica #Hubzilla #AltText #AltTextMeta #CWAltTextMeta -
Fedistar v1.12.6
=> https://fedistar.netMulti-column Fediverse client application for desktop
- Supporting SNS
- - Mastodon
- - Pleroma
- - Friendica
- - Firefish
- - Gotosocial
- - Pixelfed
- - Akkoma (Unofficial)
- - Sharkey (Unofficial)
- - Hometown (Unofficial)
- - Iceshrimp (Unofficial)
- Multiple accounts management
- Multiple columns
- You can see timelines without sign in
- Desktop notification
- Streaming update
- Send reactions from another accounts
- Change column widthChangelog:
=> https://github.com/h3poteto/fedistar/releases/tag/v1.12.6#Fediverse #Mastodon #Pleroma #Friendica #Firefish #Gotosocial #Pixelfed #Akkoma #Sharkey #Hometown #Iceshrimp
-
Does anyone have any pointers for getting Meilisearch working with Sharkey/Misskey?
Both are installed and start up correctly. When I search I can see in Meilisearch's journald log that I am getting a query, but nothing returns.
One lead I have is that teh query parameters are blank in the journald logs - but that could just be for privacy reasons.
I don't see anything (after successfully connecting to Meilisearch) in the Sharkey logs.
#sharkey #misskey #meilisearch #help #debug -
wrote a blog post about why i moved from GoToSocial to Sharkey, the state of ActivityPub mobile apps (not great if you're western and use a Misskey/Misskey fork server, sorry), and why i find myself hoping Bluesky adds something like MFM one day. :wlfChuckle:
also contains an uncharitable word about Nostr. you're welcome. :wlfAghast:
#Fediverse #Sharkey #ActivityPub #SelfHosting #NixOS #GoToSocial #Bluesky #MFM -
Is there any reason to always see the "Mark all notifications as read" button, even when there are no unread notifications, besides cluttering the UI? Just made it appear only when unread notifications are over zero. Will deploy later today on catodon.rocks, along with the dedicated Direct messages page.
#Catodon #Sharkey #Firefish -
@[email protected] Use a different service in the Fediverse.
For example, the Misskey family, which includes IceShrimp, Misskey, Foundkey, Sharkey and so on; there, you can organise your bookmarks into folders
You can create as many of these folders as you need.
The same applies to the built-in cloud: files can be sorted into folders and are always ready for reuse.
#Fediverse #Sharkey #Calckey #Bookmark -
The time has come and I'm beyond excited 😁
We just opened registrations on catodon.rocks.
I know that Catodon created a lot of expectations when Firefish fell apart, and I'm sure many of you were disappointed to see it not going anywhere for a long time. This time I am doing it on my own, so things will happen the way they should have. And, although you can now check it out for youselves, I will say this: I firmly believe that it's better, on every level, than Firefish ever was. I was in both projects, I love them both, but Catodon combines the best features of Firefish and Sharkey, while also being very debloated, being much more comprehensible, and adding actually useful stuff - and I have more plans for the future.
I'd love to hear your feedback on the UX of Catodon, and see how we can improve it further! Let's create the fedi experience we deserve =)
:catodon:
#Catodon #Fediverse #Firefish #Sharkey
RE: https://catodon.rocks/notes/ajo1s763f05z0002 -
Sharkey/Misskey users: Would it make a real difference to you if you could only upload media files instead of any file to your Drive? I'm thinking of restricting it to media files (and only from https) for Catodon, for security reasons. I doubt any of the users in our 3+ years old Firefish server uploaded any other type of file.
#Sharkey #Misskey #Firefish #Catodon -
-
CW: Misskey only allows for 512 characters of alt-text which is bad for my image posts; CW: long (over 8,600 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, alt-text meta, character limit meta, content warning meta
Just the other day, I found something out. Something very inconvenient about Misskey and maybe also the Forkeys.
It should be commonly known that Misskey has a local limit of 3,000 characters for posts (which it refers to as "notes"). What is not so well-known is that Misskey has a limit of about 8,000 characters, probably 8,192 or so, for inbound messages, ironically fewer than this post is long. Also, it has a limit of 512 characters for alt-text, both locally and in-bound.
Mastodon has a character limit for in-bound content, too, at least for Note-type objects (not for Article-type objects because it refuses to render them fully and links to the original instead). To my best knowledge, it rejects messages with over 100,000 characters. As for its 1,500-charater limit for alt-text, it enforces that by truncating alt-text that's longer.
Misskey, in contrast, truncates everything that exceeds its limits while still letting it in. If your post is longer than the inbound limit of ca. 8,000, all excess characters are chopped off and thrown away. If your alt-text is longer than 512 characters, all excess characters are chopped off and thrown away.
I don't know which Forkey behaves how in this regard, seeing as all Forkeys I know about have a configurable local post character limit that can be adjusted to well over 8,000. But even if the inbound limit is configurable, too, I don't think any *key admin cranks it over 60,000 or over 70,000 or over 100,000. It's simply unimaginable that someone, anyone, could ever post that much at once if your idea of the Fediverse is pure microblogging.
Also, I don't know what *key users do when they come across a truncated post or what blind or visually-impaired *key users do when they come across a truncated alt-text. Do they even suspect that it's a truncated copy of something that's longer at its source and then go check the source? Either way, it's very inconvenient.
It's especially inconvenient for me. My longest posts by a gigantic margin are image posts with original images. They always have a long image description block in the post itself that tends to be tens of thousands of characters long. It contains highly detailed visual descriptions of all images in the post. It contains all explanations necessary to understand the post, the images and the descriptions. It contains verbatim transcripts of all bits of text within the borders of the image that I can read, no matter whether or not my audience can.
In addition, each image has a shorter description in the alt-text, along with a bit that announces the long description, including where to find it. I even used to explain how to get to that description for Mastodon users for whom the summary and content warning hides the post text, but not the images, depending on which Mastodon version and frontend they use. This alone took up several hundred characters in the alt-text. All in all, I got to a point in which my alt-texts always ended up either at precisely 1,500 characters or just a few characters short.
I myself am not really bound to character limits. I used to post images here on Hubzilla where I have over 16.7 million characters for the post, including all alt-texts. Now I post them on (streams) where I have over 24 million characters. I could theoretically write alt-texts as long as I want to, seeing as, unlike on Mastodon, they aren't separate text fields; instead, they're being woven into the image-embedding markup code in the post text.
Still, I stick to a maximum of 1,500 characters for alt-text to keep Mastodon from truncating it. If you post images into the Fediverse, the main audience for your alt-text is on Mastodon, and most of them don't understand that there's something, anything, out there in the Fediverse that does not work exactly like Mastodon. And 1,500 characters can be tight already.
But if I have to stay within Misskey's limits, I can hardly post images anymore. At least not with appropriate descriptions and explanations.
Since late 2024, I have been working on-and-off on a series of fairly simple avatar portraits or rather their image descriptions. The idea is for the long description to consist of a preamble that starts with a general summary, followed by explanations, then followed by visual descriptions of what all images in the post have in common. Next come the individual descriptions of each image. Each post shall have three or four images with three or four portraits each, all in the same pose, all with only minor differences in outfits, all with a neutral, bright white background.
In addition, of course, each image shall have an alt-text, and none of the alt-texts shall depend on each other.
Now, the problem is that I have to describe three or four individual portraits in each alt-text. I'm actually struggling to squeeze such a description plus the note that announces the long description into 1,500 characters, especially if I want to fulfill Veronica Lewis a.k.a. Veronica With Four Eyes' requirements for outfit descriptions to a tee in the alt-text as well (https://veroniiiica.com/how-to-write-alt-text-for-casual-outfits/, https://veroniiiica.com/writing-image-descriptions-for-red-carpet-outfits/; see also https://veroniiiica.com/how-to-write-alt-text-image-descriptions-visually-impaired/ and https://veroniiiica.com/how-to-create-visual-descriptions/).
But in 512 characters so that even Misskey users won't get a severely truncated version? This is absolutely impossible. Even if I limit the long description announcement to some 100 characters, even if I didn't walk people through how to get to the long description, I'd have fewer than 140 characters on average to describe each individual outfit.
The long description won't fare any better. Currently, the preamble starts with some 14,000 characters of explanations, most of which are necessary to understand the visual descriptions. But when Misskey goes and truncates the post at the 8,000-something mark, Misskey users won't even get to any visual description because all visual descriptions would be chopped off.
What makes matters worse is that the preamble grows the longer, the easier to understand I make it and the less I leave people with unexplained technical or jargon terms which you shouldn't use in image descriptions at all anyway. So the next time I go through it and rewrite it to make it easier to understand, I'll also make it even longer than it already is.
But what if I simply cut all the explanations? For one, I'd leave people to their own devices to understand extremely obscure niche content. They won't. My explanations aren't 14,000 characters long because I've artificially inflated them, but because there is so much to know before you understand the post and the images and the descriptions.
Besides, the visual descriptions alone won't fit into 8,192 characters either. What I currently have is over 5,000 characters of common visual description for all portraits in all images plus about 2,500 characters of individual visual description for the three portraits in the first image. That's over 7,500 characters altogether already. And I still have to describe nine portraits in another three images. The post will end up with some 15,000 characters of visual descriptions unless they grow longer when I simplify them again.
I guess users of Misskey or any Forkey will still have to put up with truncated alt-texts and truncated long descriptions in the future. But my future image posts will contain a paragraph at the beginning that explains that the post and/or the alt-text may be truncated on Misskey and the Forkeys, and that both are uncut at the source. Still, this means that *key users will have to put up with the extra hassle of opening my original post at a source with a quite cumbersome UI. And I've got my doubts that this UI is really accessible.
Unfortunately, this also means that *key users won't get any hashtags along with these posts. But then again, the handling of Identi.ca-style/Friendica-style hashtags with the number sign outside the link is broken on all *keys and will remain so for the foreseeable future.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Calckey #Firefish #Sharkey #CherryPick #Iceshrimp #Iceshrimp-JS #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #A11y #Accessibility -
CW: Misskey only allows for 512 characters of alt-text which is bad for my image posts; CW: long (over 8,600 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, alt-text meta, character limit meta, content warning meta
Just the other day, I found something out. Something very inconvenient about Misskey and maybe also the Forkeys.
It should be commonly known that Misskey has a local limit of 3,000 characters for posts (which it refers to as "notes"). What is not so well-known is that Misskey has a limit of about 8,000 characters, probably 8,192 or so, for inbound messages, ironically fewer than this post is long. Also, it has a limit of 512 characters for alt-text, both locally and in-bound.
Mastodon has a character limit for in-bound content, too, at least for Note-type objects (not for Article-type objects because it refuses to render them fully and links to the original instead). To my best knowledge, it rejects messages with over 100,000 characters. As for its 1,500-charater limit for alt-text, it enforces that by truncating alt-text that's longer.
Misskey, in contrast, truncates everything that exceeds its limits while still letting it in. If your post is longer than the inbound limit of ca. 8,000, all excess characters are chopped off and thrown away. If your alt-text is longer than 512 characters, all excess characters are chopped off and thrown away.
I don't know which Forkey behaves how in this regard, seeing as all Forkeys I know about have a configurable local post character limit that can be adjusted to well over 8,000. But even if the inbound limit is configurable, too, I don't think any *key admin cranks it over 60,000 or over 70,000 or over 100,000. It's simply unimaginable that someone, anyone, could ever post that much at once if your idea of the Fediverse is pure microblogging.
Also, I don't know what *key users do when they come across a truncated post or what blind or visually-impaired *key users do when they come across a truncated alt-text. Do they even suspect that it's a truncated copy of something that's longer at its source and then go check the source? Either way, it's very inconvenient.
It's especially inconvenient for me. My longest posts by a gigantic margin are image posts with original images. They always have a long image description block in the post itself that tends to be tens of thousands of characters long. It contains highly detailed visual descriptions of all images in the post. It contains all explanations necessary to understand the post, the images and the descriptions. It contains verbatim transcripts of all bits of text within the borders of the image that I can read, no matter whether or not my audience can.
In addition, each image has a shorter description in the alt-text, along with a bit that announces the long description, including where to find it. I even used to explain how to get to that description for Mastodon users for whom the summary and content warning hides the post text, but not the images, depending on which Mastodon version and frontend they use. This alone took up several hundred characters in the alt-text. All in all, I got to a point in which my alt-texts always ended up either at precisely 1,500 characters or just a few characters short.
I myself am not really bound to character limits. I used to post images here on Hubzilla where I have over 16.7 million characters for the post, including all alt-texts. Now I post them on (streams) where I have over 24 million characters. I could theoretically write alt-texts as long as I want to, seeing as, unlike on Mastodon, they aren't separate text fields; instead, they're being woven into the image-embedding markup code in the post text.
Still, I stick to a maximum of 1,500 characters for alt-text to keep Mastodon from truncating it. If you post images into the Fediverse, the main audience for your alt-text is on Mastodon, and most of them don't understand that there's something, anything, out there in the Fediverse that does not work exactly like Mastodon. And 1,500 characters can be tight already.
But if I have to stay within Misskey's limits, I can hardly post images anymore. At least not with appropriate descriptions and explanations.
Since late 2024, I have been working on-and-off on a series of fairly simple avatar portraits or rather their image descriptions. The idea is for the long description to consist of a preamble that starts with a general summary, followed by explanations, then followed by visual descriptions of what all images in the post have in common. Next come the individual descriptions of each image. Each post shall have three or four images with three or four portraits each, all in the same pose, all with only minor differences in outfits, all with a neutral, bright white background.
In addition, of course, each image shall have an alt-text, and none of the alt-texts shall depend on each other.
Now, the problem is that I have to describe three or four individual portraits in each alt-text. I'm actually struggling to squeeze such a description plus the note that announces the long description into 1,500 characters, especially if I want to fulfill Veronica Lewis a.k.a. Veronica With Four Eyes' requirements for outfit descriptions to a tee in the alt-text as well (https://veroniiiica.com/how-to-write-alt-text-for-casual-outfits/, https://veroniiiica.com/writing-image-descriptions-for-red-carpet-outfits/; see also https://veroniiiica.com/how-to-write-alt-text-image-descriptions-visually-impaired/ and https://veroniiiica.com/how-to-create-visual-descriptions/).
But in 512 characters so that even Misskey users won't get a severely truncated version? This is absolutely impossible. Even if I limit the long description announcement to some 100 characters, even if I didn't walk people through how to get to the long description, I'd have fewer than 140 characters on average to describe each individual outfit.
The long description won't fare any better. Currently, the preamble starts with some 14,000 characters of explanations, most of which are necessary to understand the visual descriptions. But when Misskey goes and truncates the post at the 8,000-something mark, Misskey users won't even get to any visual description because all visual descriptions would be chopped off.
What makes matters worse is that the preamble grows the longer, the easier to understand I make it and the less I leave people with unexplained technical or jargon terms which you shouldn't use in image descriptions at all anyway. So the next time I go through it and rewrite it to make it easier to understand, I'll also make it even longer than it already is.
But what if I simply cut all the explanations? For one, I'd leave people to their own devices to understand extremely obscure niche content. They won't. My explanations aren't 14,000 characters long because I've artificially inflated them, but because there is so much to know before you understand the post and the images and the descriptions.
Besides, the visual descriptions alone won't fit into 8,192 characters either. What I currently have is over 5,000 characters of common visual description for all portraits in all images plus about 2,500 characters of individual visual description for the three portraits in the first image. That's over 7,500 characters altogether already. And I still have to describe nine portraits in another three images. The post will end up with some 15,000 characters of visual descriptions unless they grow longer when I simplify them again.
I guess users of Misskey or any Forkey will still have to put up with truncated alt-texts and truncated long descriptions in the future. But my future image posts will contain a paragraph at the beginning that explains that the post and/or the alt-text may be truncated on Misskey and the Forkeys, and that both are uncut at the source. Still, this means that *key users will have to put up with the extra hassle of opening my original post at a source with a quite cumbersome UI. And I've got my doubts that this UI is really accessible.
Unfortunately, this also means that *key users won't get any hashtags along with these posts. But then again, the handling of Identi.ca-style/Friendica-style hashtags with the number sign outside the link is broken on all *keys and will remain so for the foreseeable future.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Calckey #Firefish #Sharkey #CherryPick #Iceshrimp #Iceshrimp-JS #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #A11y #Accessibility -
CW: Misskey only allows for 512 characters of alt-text which is bad for my image posts; CW: long (over 8,600 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, alt-text meta, character limit meta, content warning meta
Just the other day, I found something out. Something very inconvenient about Misskey and maybe also the Forkeys.
It should be commonly known that Misskey has a local limit of 3,000 characters for posts (which it refers to as "notes"). What is not so well-known is that Misskey has a limit of about 8,000 characters, probably 8,192 or so, for inbound messages, ironically fewer than this post is long. Also, it has a limit of 512 characters for alt-text, both locally and in-bound.
Mastodon has a character limit for in-bound content, too, at least for Note-type objects (not for Article-type objects because it refuses to render them fully and links to the original instead). To my best knowledge, it rejects messages with over 100,000 characters. As for its 1,500-charater limit for alt-text, it enforces that by truncating alt-text that's longer.
Misskey, in contrast, truncates everything that exceeds its limits while still letting it in. If your post is longer than the inbound limit of ca. 8,000, all excess characters are chopped off and thrown away. If your alt-text is longer than 512 characters, all excess characters are chopped off and thrown away.
I don't know which Forkey behaves how in this regard, seeing as all Forkeys I know about have a configurable local post character limit that can be adjusted to well over 8,000. But even if the inbound limit is configurable, too, I don't think any *key admin cranks it over 60,000 or over 70,000 or over 100,000. It's simply unimaginable that someone, anyone, could ever post that much at once if your idea of the Fediverse is pure microblogging.
Also, I don't know what *key users do when they come across a truncated post or what blind or visually-impaired *key users do when they come across a truncated alt-text. Do they even suspect that it's a truncated copy of something that's longer at its source and then go check the source? Either way, it's very inconvenient.
It's especially inconvenient for me. My longest posts by a gigantic margin are image posts with original images. They always have a long image description block in the post itself that tends to be tens of thousands of characters long. It contains highly detailed visual descriptions of all images in the post. It contains all explanations necessary to understand the post, the images and the descriptions. It contains verbatim transcripts of all bits of text within the borders of the image that I can read, no matter whether or not my audience can.
In addition, each image has a shorter description in the alt-text, along with a bit that announces the long description, including where to find it. I even used to explain how to get to that description for Mastodon users for whom the summary and content warning hides the post text, but not the images, depending on which Mastodon version and frontend they use. This alone took up several hundred characters in the alt-text. All in all, I got to a point in which my alt-texts always ended up either at precisely 1,500 characters or just a few characters short.
I myself am not really bound to character limits. I used to post images here on Hubzilla where I have over 16.7 million characters for the post, including all alt-texts. Now I post them on (streams) where I have over 24 million characters. I could theoretically write alt-texts as long as I want to, seeing as, unlike on Mastodon, they aren't separate text fields; instead, they're being woven into the image-embedding markup code in the post text.
Still, I stick to a maximum of 1,500 characters for alt-text to keep Mastodon from truncating it. If you post images into the Fediverse, the main audience for your alt-text is on Mastodon, and most of them don't understand that there's something, anything, out there in the Fediverse that does not work exactly like Mastodon. And 1,500 characters can be tight already.
But if I have to stay within Misskey's limits, I can hardly post images anymore. At least not with appropriate descriptions and explanations.
Since late 2024, I have been working on-and-off on a series of fairly simple avatar portraits or rather their image descriptions. The idea is for the long description to consist of a preamble that starts with a general summary, followed by explanations, then followed by visual descriptions of what all images in the post have in common. Next come the individual descriptions of each image. Each post shall have three or four images with three or four portraits each, all in the same pose, all with only minor differences in outfits, all with a neutral, bright white background.
In addition, of course, each image shall have an alt-text, and none of the alt-texts shall depend on each other.
Now, the problem is that I have to describe three or four individual portraits in each alt-text. I'm actually struggling to squeeze such a description plus the note that announces the long description into 1,500 characters, especially if I want to fulfill Veronica Lewis a.k.a. Veronica With Four Eyes' requirements for outfit descriptions to a tee in the alt-text as well (https://veroniiiica.com/how-to-write-alt-text-for-casual-outfits/, https://veroniiiica.com/writing-image-descriptions-for-red-carpet-outfits/; see also https://veroniiiica.com/how-to-write-alt-text-image-descriptions-visually-impaired/ and https://veroniiiica.com/how-to-create-visual-descriptions/).
But in 512 characters so that even Misskey users won't get a severely truncated version? This is absolutely impossible. Even if I limit the long description announcement to some 100 characters, even if I didn't walk people through how to get to the long description, I'd have fewer than 140 characters on average to describe each individual outfit.
The long description won't fare any better. Currently, the preamble starts with some 14,000 characters of explanations, most of which are necessary to understand the visual descriptions. But when Misskey goes and truncates the post at the 8,000-something mark, Misskey users won't even get to any visual description because all visual descriptions would be chopped off.
What makes matters worse is that the preamble grows the longer, the easier to understand I make it and the less I leave people with unexplained technical or jargon terms which you shouldn't use in image descriptions at all anyway. So the next time I go through it and rewrite it to make it easier to understand, I'll also make it even longer than it already is.
But what if I simply cut all the explanations? For one, I'd leave people to their own devices to understand extremely obscure niche content. They won't. My explanations aren't 14,000 characters long because I've artificially inflated them, but because there is so much to know before you understand the post and the images and the descriptions.
Besides, the visual descriptions alone won't fit into 8,192 characters either. What I currently have is over 5,000 characters of common visual description for all portraits in all images plus about 2,500 characters of individual visual description for the three portraits in the first image. That's over 7,500 characters altogether already. And I still have to describe nine portraits in another three images. The post will end up with some 15,000 characters of visual descriptions unless they grow longer when I simplify them again.
I guess users of Misskey or any Forkey will still have to put up with truncated alt-texts and truncated long descriptions in the future. But my future image posts will contain a paragraph at the beginning that explains that the post and/or the alt-text may be truncated on Misskey and the Forkeys, and that both are uncut at the source. Still, this means that *key users will have to put up with the extra hassle of opening my original post at a source with a quite cumbersome UI. And I've got my doubts that this UI is really accessible.
Unfortunately, this also means that *key users won't get any hashtags along with these posts. But then again, the handling of Identi.ca-style/Friendica-style hashtags with the number sign outside the link is broken on all *keys and will remain so for the foreseeable future.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Calckey #Firefish #Sharkey #CherryPick #Iceshrimp #Iceshrimp-JS #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #A11y #Accessibility
