#fedimeta — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #fedimeta, aggregated by home.social.
-
I'm watching Mampuku on Netflix (15 minute episodes, so much better than the description makes it out to be).
The main character's husband is an inventor. What drives him is the desire to create things that make people happy and make their lives better. They are lovely people to hang out with as I watch the series.
This is a mindset I want to see more of in the world. (And explains yet another reason why I love the company here on Fedi.)
-
I'm watching Mampuku on Netflix (15 minute episodes, so much better than the description makes it out to be).
The main character's husband is an inventor. What drives him is the desire to create things that make people happy and make their lives better. They are lovely people to hang out with as I watch the series.
This is a mindset I want to see more of in the world. (And explains yet another reason why I love the company here on Fedi.)
-
I'm watching Mampuku on Netflix (15 minute episodes, so much better than the description makes it out to be).
The main character's husband is an inventor. What drives him is the desire to create things that make people happy and make their lives better. They are lovely people to hang out with as I watch the series.
This is a mindset I want to see more of in the world. (And explains yet another reason why I love the company here on Fedi.)
-
I'm watching Mampuku on Netflix (15 minute episodes, so much better than the description makes it out to be).
The main character's husband is an inventor. What drives him is the desire to create things that make people happy and make their lives better. They are lovely people to hang out with as I watch the series.
This is a mindset I want to see more of in the world. (And explains yet another reason why I love the company here on Fedi.)
-
I'm watching Mampuku on Netflix (15 minute episodes, so much better than the description makes it out to be).
The main character's husband is an inventor. What drives him is the desire to create things that make people happy and make their lives better. They are lovely people to hang out with as I watch the series.
This is a mindset I want to see more of in the world. (And explains yet another reason why I love the company here on Fedi.)
-
@libewa Hashtags im Fließtext sind grauenhaft!
-
@libewa Hashtags im Fließtext sind grauenhaft!
-
@libewa Hashtags im Fließtext sind grauenhaft!
-
@libewa Hashtags im Fließtext sind grauenhaft!
-
@libewa Hashtags im Fließtext sind grauenhaft!
-
Ich habe mit tatsächlich gestern Gedanken darüber gemacht. Man muss #Hashtags auch gemäßigt benutzen. Nutzt man zu viele, wirkt es attention-seeking, nutzt man zu wenige, wird man nicht gefunden. Außerdem erreicht man auf manchen Instanzen schnell die Längenbegrenzung. Dann gibt es oft noch für ein Thema mehrere Hashtags (schreibt man jetzt 26 oder 2026?), und so füllt sich der Post.
#Mastodon (WebUI) zeigt Hashtags am Ende des Posts wenigstens kleiner an, damit sie weniger stören.
#fedimeta -
Ich habe mit tatsächlich gestern Gedanken darüber gemacht. Man muss #Hashtags auch gemäßigt benutzen. Nutzt man zu viele, wirkt es attention-seeking, nutzt man zu wenige, wird man nicht gefunden. Außerdem erreicht man auf manchen Instanzen schnell die Längenbegrenzung. Dann gibt es oft noch für ein Thema mehrere Hashtags (schreibt man jetzt 26 oder 2026?), und so füllt sich der Post.
#Mastodon (WebUI) zeigt Hashtags am Ende des Posts wenigstens kleiner an, damit sie weniger stören.
#fedimeta -
Ich habe mit tatsächlich gestern Gedanken darüber gemacht. Man muss #Hashtags auch gemäßigt benutzen. Nutzt man zu viele, wirkt es attention-seeking, nutzt man zu wenige, wird man nicht gefunden. Außerdem erreicht man auf manchen Instanzen schnell die Längenbegrenzung. Dann gibt es oft noch für ein Thema mehrere Hashtags (schreibt man jetzt 26 oder 2026?), und so füllt sich der Post.
#Mastodon (WebUI) zeigt Hashtags am Ende des Posts wenigstens kleiner an, damit sie weniger stören.
#fedimeta -
Ich habe mit tatsächlich gestern Gedanken darüber gemacht. Man muss #Hashtags auch gemäßigt benutzen. Nutzt man zu viele, wirkt es attention-seeking, nutzt man zu wenige, wird man nicht gefunden. Außerdem erreicht man auf manchen Instanzen schnell die Längenbegrenzung. Dann gibt es oft noch für ein Thema mehrere Hashtags (schreibt man jetzt 26 oder 2026?), und so füllt sich der Post.
#Mastodon (WebUI) zeigt Hashtags am Ende des Posts wenigstens kleiner an, damit sie weniger stören.
#fedimeta -
Ich habe mit tatsächlich gestern Gedanken darüber gemacht. Man muss #Hashtags auch gemäßigt benutzen. Nutzt man zu viele, wirkt es attention-seeking, nutzt man zu wenige, wird man nicht gefunden. Außerdem erreicht man auf manchen Instanzen schnell die Längenbegrenzung. Dann gibt es oft noch für ein Thema mehrere Hashtags (schreibt man jetzt 26 oder 2026?), und so füllt sich der Post.
#Mastodon (WebUI) zeigt Hashtags am Ende des Posts wenigstens kleiner an, damit sie weniger stören.
#fedimeta -
@frumble
#hashtag immer eine gute option
#fedimeta #fediverse (guck an, 154 Personen reden darüber) -
@frumble
#hashtag immer eine gute option
#fedimeta #fediverse (guck an, 154 Personen reden darüber) -
@frumble
#hashtag immer eine gute option
#fedimeta #fediverse (guck an, 154 Personen reden darüber) -
@frumble
#hashtag immer eine gute option
#fedimeta #fediverse (guck an, 154 Personen reden darüber) -
@frumble
#hashtag immer eine gute option
#fedimeta #fediverse (guck an, 154 Personen reden darüber) -
CW: Fedi meta
mastodon.social, a commonly used instance that many people use, may have portions of unmoderated content. If you are still there, please migrate immediately to a smaller instance to stay connected with people from smaller instances.
#fedimeta
#fedimigration -
CW: Fedi meta
mastodon.social, a commonly used instance that many people use, may have portions of unmoderated content. If you are still there, please migrate immediately to a smaller instance to stay connected with people from smaller instances.
#fedimeta
#fedimigration -
CW: Fedi meta
mastodon.social, a commonly used instance that many people use, may have portions of unmoderated content. If you are still there, please migrate immediately to a smaller instance to stay connected with people from smaller instances.
#fedimeta
#fedimigration -
CW: Fedi meta
mastodon.social, a commonly used instance that many people use, may have portions of unmoderated content. If you are still there, please migrate immediately to a smaller instance to stay connected with people from smaller instances.
#fedimeta
#fedimigration -
CW: Fedi meta
mastodon.social, a commonly used instance that many people use, may have portions of unmoderated content. If you are still there, please migrate immediately to a smaller instance to stay connected with people from smaller instances.
#fedimeta
#fedimigration -
@Mark Wyner Won’t Comply :vm: First of all, you completely forgot the social media posters. The TOC link leads nowhere.
Also, maybe it's fair to mention that I'm working on an entire wiki about alt-texts and image descriptions, especially for the Fediverse. 46 pages are planned as of now, 24 of them are already written. These will include over 30 pages on how to do things, how not to do things and what never to do at all.
I won't add step-by-step guides for certain frontends. But I've already started adding rules and guidelines for how to describe images appropriately and write alt-texts in a way that won't break stuff anywhere.
Even if it's a very incomplete WIP, it's unique in several ways:- It's the only wiki about alt-texts and image descriptions. Few writers have even only written multiple pages or articles on this subject.
- It's the only guide that takes the existence of the Fediverse outside of Mastodon into consideration. This means that it's also the only guide that doesn't assume that Fediverse equals always having only 500 characters for the message text. It actually recommends an additional, longer image description in the message text in certain situations, regardless of whether or not vanilla Mastodon users can do that.
- It's the only guide that, instead of regurgitating the alt-text rules for webpages and blogs and assuming that they apply to the Fediverse just the same, talks about the peculiarities of posting images into the Fediverse, how Mastodon's alt-text quality criteria are different from the W3C WAI and WCAG alt-text quality criteria, and why it's critically important to know and fulfill Mastodon's requirements for good alt-texts.
- It's probably the only guide that doesn't assume that you can always precisely target a certain audience for your content and make sure that only those receive it who understand it right off the bat.
- It is the only guide that lists over 60 references, including your blog post, but also including university webpages as well as over two dozen guides from Veronica Lewis a.k.a. Veronica with Four Eyes.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
@Mark Wyner Won’t Comply :vm: First of all, you completely forgot the social media posters. The TOC link leads nowhere.
Also, maybe it's fair to mention that I'm working on an entire wiki about alt-texts and image descriptions, especially for the Fediverse. 46 pages are planned as of now, 24 of them are already written. These will include over 30 pages on how to do things, how not to do things and what never to do at all.
I won't add step-by-step guides for certain frontends. But I've already started adding rules and guidelines for how to describe images appropriately and write alt-texts in a way that won't break stuff anywhere.
Even if it's a very incomplete WIP, it's unique in several ways:- It's the only wiki about alt-texts and image descriptions. Few writers have even only written multiple pages or articles on this subject.
- It's the only guide that takes the existence of the Fediverse outside of Mastodon into consideration. This means that it's also the only guide that doesn't assume that Fediverse equals always having only 500 characters for the message text. It actually recommends an additional, longer image description in the message text in certain situations, regardless of whether or not vanilla Mastodon users can do that.
- It's the only guide that, instead of regurgitating the alt-text rules for webpages and blogs and assuming that they apply to the Fediverse just the same, talks about the peculiarities of posting images into the Fediverse, how Mastodon's alt-text quality criteria are different from the W3C WAI and WCAG alt-text quality criteria, and why it's critically important to know and fulfill Mastodon's requirements for good alt-texts.
- It's probably the only guide that doesn't assume that you can always precisely target a certain audience for your content and make sure that only those receive it who understand it right off the bat.
- It is the only guide that lists over 60 references, including your blog post, but also including university webpages as well as over two dozen guides from Veronica Lewis a.k.a. Veronica with Four Eyes.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
@Mark Wyner Won’t Comply :vm: First of all, you completely forgot the social media posters. The TOC link leads nowhere.
Also, maybe it's fair to mention that I'm working on an entire wiki about alt-texts and image descriptions, especially for the Fediverse. 46 pages are planned as of now, 24 of them are already written. These will include over 30 pages on how to do things, how not to do things and what never to do at all.
I won't add step-by-step guides for certain frontends. But I've already started adding rules and guidelines for how to describe images appropriately and write alt-texts in a way that won't break stuff anywhere.
Even if it's a very incomplete WIP, it's unique in several ways:- It's the only wiki about alt-texts and image descriptions. Few writers have even only written multiple pages or articles on this subject.
- It's the only guide that takes the existence of the Fediverse outside of Mastodon into consideration. This means that it's also the only guide that doesn't assume that Fediverse equals always having only 500 characters for the message text. It actually recommends an additional, longer image description in the message text in certain situations, regardless of whether or not vanilla Mastodon users can do that.
- It's the only guide that, instead of regurgitating the alt-text rules for webpages and blogs and assuming that they apply to the Fediverse just the same, talks about the peculiarities of posting images into the Fediverse, how Mastodon's alt-text quality criteria are different from the W3C WAI and WCAG alt-text quality criteria, and why it's critically important to know and fulfill Mastodon's requirements for good alt-texts.
- It's probably the only guide that doesn't assume that you can always precisely target a certain audience for your content and make sure that only those receive it who understand it right off the bat.
- It is the only guide that lists over 60 references, including your blog post, but also including university webpages as well as over two dozen guides from Veronica Lewis a.k.a. Veronica with Four Eyes.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
@Hirad @Mehrad :kde: :emacs: :rstats: Which is curious, seeing as the GNU FM developer also started GNU social and scooped up StatusNet's abandoned code to merge it into GNU social. The idea was to use GNU social in some way to make GNU FM federate.
GNU social even implemented ActivityPub at some point, but GNU FM never did. Now GNU social is dead anyway.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #GNUFM #GNUsocial -
@🌴 Seph 💭 👾 That's one nice thing about Hubzilla: You can customise the UI apart from theming. You can completely change the layout. (Not sure if you can do that with Saiwal's themes, but you can with Redbasic.)
By default, a new channel has barely got any icons in the navbar and not even that many in the app menu. The right-hand end of the navbar of a new channel only contains icons for search, HQ, help and the app menu. You can configure under Apps which icons shall appear where. Star them, and they're in the menu. Pin them, and they're on the navbar.
In fact, whereas (I think) Friendica has all its features on all the time, Hubzilla is very modular. Many of its features are optional and off by default; they're called "apps". If you don't need it, don't activate it, and you won't have UI elements for it.
Even the various pages can be rearranged in the PDL editor. You don't need something, throw it out. You only need one sidebar, choose a layout with only one sidebar instead of both. You can do without any sidebars, pick a layout without sidebars.
Saiwal's theme previews have to show what can be done with them. Hence, a lot of UI elements are in place that either can be configured away or have to be configured into place in the first place.
For example, if you look at the AdminLTE preview: You only have to pin the apps that you need all the time. If you want to, you can unpin them all, and they're gone. But then you'll have to go via the Featured Apps menu to get to them. You can slim that down as well, but then you have to open the Apps page to get to them.
The entire wide dark navigation bar on the left can be folded in if you don't need it. Fold it out when you need it.
Main Navigation looks like a homebrew element that doesn't necessarily have to be default. The Archives field can be configured away or has to be configured into place.
The buttons below the posts can't be reduced that much. The speech bubble unfolds the comments. Then come thumb up and (optional, off-by-default) thumb down. Next comes repeat (= share on Friendica). The smiley is for replying with nothing but one emoticon; I think this is actually an optional feature, too.
Now, when I look at the Solidified preview: Almost every other button on the left-hand bar is for an app that isn't even activated by default. Most of the rest are for features that are available right away, but their buttons usually aren't.
Most of what's on the right was probably configured in for the showcase. Even if it's there by default, it can be removed.
The centre only seems cluttered because the posts are arranged across three columns instead of all in one. Even there you can choose how to arrange the posts.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #UtsuktaThemes #AdminLTE #Solidified #Hubzilla -
@🌴 Seph 💭 👾 That's one nice thing about Hubzilla: You can customise the UI apart from theming. You can completely change the layout. (Not sure if you can do that with Saiwal's themes, but you can with Redbasic.)
By default, a new channel has barely got any icons in the navbar and not even that many in the app menu. The right-hand end of the navbar of a new channel only contains icons for search, HQ, help and the app menu. You can configure under Apps which icons shall appear where. Star them, and they're in the menu. Pin them, and they're on the navbar.
In fact, whereas (I think) Friendica has all its features on all the time, Hubzilla is very modular. Many of its features are optional and off by default; they're called "apps". If you don't need it, don't activate it, and you won't have UI elements for it.
Even the various pages can be rearranged in the PDL editor. You don't need something, throw it out. You only need one sidebar, choose a layout with only one sidebar instead of both. You can do without any sidebars, pick a layout without sidebars.
Saiwal's theme previews have to show what can be done with them. Hence, a lot of UI elements are in place that either can be configured away or have to be configured into place in the first place.
For example, if you look at the AdminLTE preview: You only have to pin the apps that you need all the time. If you want to, you can unpin them all, and they're gone. But then you'll have to go via the Featured Apps menu to get to them. You can slim that down as well, but then you have to open the Apps page to get to them.
The entire wide dark navigation bar on the left can be folded in if you don't need it. Fold it out when you need it.
Main Navigation looks like a homebrew element that doesn't necessarily have to be default. The Archives field can be configured away or has to be configured into place.
The buttons below the posts can't be reduced that much. The speech bubble unfolds the comments. Then come thumb up and (optional, off-by-default) thumb down. Next comes repeat (= share on Friendica). The smiley is for replying with nothing but one emoticon; I think this is actually an optional feature, too.
Now, when I look at the Solidified preview: Almost every other button on the left-hand bar is for an app that isn't even activated by default. Most of the rest are for features that are available right away, but their buttons usually aren't.
Most of what's on the right was probably configured in for the showcase. Even if it's there by default, it can be removed.
The centre only seems cluttered because the posts are arranged across three columns instead of all in one. Even there you can choose how to arrange the posts.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #UtsuktaThemes #AdminLTE #Solidified #Hubzilla -
@🌴 Seph 💭 👾 That's one nice thing about Hubzilla: You can customise the UI apart from theming. You can completely change the layout. (Not sure if you can do that with Saiwal's themes, but you can with Redbasic.)
By default, a new channel has barely got any icons in the navbar and not even that many in the app menu. The right-hand end of the navbar of a new channel only contains icons for search, HQ, help and the app menu. You can configure under Apps which icons shall appear where. Star them, and they're in the menu. Pin them, and they're on the navbar.
In fact, whereas (I think) Friendica has all its features on all the time, Hubzilla is very modular. Many of its features are optional and off by default; they're called "apps". If you don't need it, don't activate it, and you won't have UI elements for it.
Even the various pages can be rearranged in the PDL editor. You don't need something, throw it out. You only need one sidebar, choose a layout with only one sidebar instead of both. You can do without any sidebars, pick a layout without sidebars.
Saiwal's theme previews have to show what can be done with them. Hence, a lot of UI elements are in place that either can be configured away or have to be configured into place in the first place.
For example, if you look at the AdminLTE preview: You only have to pin the apps that you need all the time. If you want to, you can unpin them all, and they're gone. But then you'll have to go via the Featured Apps menu to get to them. You can slim that down as well, but then you have to open the Apps page to get to them.
The entire wide dark navigation bar on the left can be folded in if you don't need it. Fold it out when you need it.
Main Navigation looks like a homebrew element that doesn't necessarily have to be default. The Archives field can be configured away or has to be configured into place.
The buttons below the posts can't be reduced that much. The speech bubble unfolds the comments. Then come thumb up and (optional, off-by-default) thumb down. Next comes repeat (= share on Friendica). The smiley is for replying with nothing but one emoticon; I think this is actually an optional feature, too.
Now, when I look at the Solidified preview: Almost every other button on the left-hand bar is for an app that isn't even activated by default. Most of the rest are for features that are available right away, but their buttons usually aren't.
Most of what's on the right was probably configured in for the showcase. Even if it's there by default, it can be removed.
The centre only seems cluttered because the posts are arranged across three columns instead of all in one. Even there you can choose how to arrange the posts.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #UtsuktaThemes #AdminLTE #Solidified #Hubzilla -
@🌴 Seph 💭 👾 That's one nice thing about Hubzilla: You can customise the UI apart from theming. You can completely change the layout. (Not sure if you can do that with Saiwal's themes, but you can with Redbasic.)
By default, a new channel has barely got any icons in the navbar and not even that many in the app menu. The right-hand end of the navbar of a new channel only contains icons for search, HQ, help and the app menu. You can configure under Apps which icons shall appear where. Star them, and they're in the menu. Pin them, and they're on the navbar.
In fact, whereas (I think) Friendica has all its features on all the time, Hubzilla is very modular. Many of its features are optional and off by default; they're called "apps". If you don't need it, don't activate it, and you won't have UI elements for it.
Even the various pages can be rearranged in the PDL editor. You don't need something, throw it out. You only need one sidebar, choose a layout with only one sidebar instead of both. You can do without any sidebars, pick a layout without sidebars.
Saiwal's theme previews have to show what can be done with them. Hence, a lot of UI elements are in place that either can be configured away or have to be configured into place in the first place.
For example, if you look at the AdminLTE preview: You only have to pin the apps that you need all the time. If you want to, you can unpin them all, and they're gone. But then you'll have to go via the Featured Apps menu to get to them. You can slim that down as well, but then you have to open the Apps page to get to them.
The entire wide dark navigation bar on the left can be folded in if you don't need it. Fold it out when you need it.
Main Navigation looks like a homebrew element that doesn't necessarily have to be default. The Archives field can be configured away or has to be configured into place.
The buttons below the posts can't be reduced that much. The speech bubble unfolds the comments. Then come thumb up and (optional, off-by-default) thumb down. Next comes repeat (= share on Friendica). The smiley is for replying with nothing but one emoticon; I think this is actually an optional feature, too.
Now, when I look at the Solidified preview: Almost every other button on the left-hand bar is for an app that isn't even activated by default. Most of the rest are for features that are available right away, but their buttons usually aren't.
Most of what's on the right was probably configured in for the showcase. Even if it's there by default, it can be removed.
The centre only seems cluttered because the posts are arranged across three columns instead of all in one. Even there you can choose how to arrange the posts.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #UtsuktaThemes #AdminLTE #Solidified #Hubzilla -
@🌴 Seph 💭 👾 Have you taken a look at Hubzilla yet?
It was created by the same guy as Friendica, and it's a descendent of Friendica. (Forked to Free-Friendika, then forked to Red, both in 2011, then largely rewritten against a brand-new protocol in 2012, then renamed Red Matrix, then greatly expanded in features and renamed Hubzilla in 2015.)
One could say it's Friendica- entirely running on its own protocol, Zot6
- with nomadic identity that makes it possible to clone your channel across multiple servers and making it resilient against server outage
- with multiple channel (identities, like complete Friendica accounts, but without separate logins) on one account/login, and you can switch between them without logging out and back in again (all with multiple profiles like on Friendica)
- without Bluesky integration
- with less pandering to Mastodon
- with an even better permissions system
- with full (client-side and server-side) OpenWebAuth support
- with polls
- with WebDAV access to your file space
- with a built-in CalDAV calendar server
- with an optional built-in CardDAV addressbook server
- with optional articles, planning cards, wikis and webpages
- with a very extensive, detailed and well-written built-in help system
- with the ability to integrate git repositories with 3rd-party add-ons and themes that can even be upgraded with shell scripts as easily as the whole hub
- with 3rd-party themes available that change the entire UI and UX instead of reskinning the existing UI, especially the Utsukta themes by @Saiwal
It does not provide any previews for links, though I'm sure something like this can be developed as a third-party addon.
If you want to try it, it's quite tricky to find a good hub with 3rd-party themes installed to start on. There aren't any in North America; don't go looking for them.
You may want to get in touch with @pepe about joining his Whoville hub. It's well-equipped, it's well-maintained, but keep in mind it's in Europe.
If you find Hubzilla to your liking, and you want to have your own hub hosted, there appear to be quite a few Hubzilla hosting services. Pick one you like, set up your own hub, activate the add-ons you need, install the third-party themes and add-ons you need, get it to run properly, and then clone your daily-driver production channel over from Whoville. Make the instance on your own hub the main one, and keep the one at Whoville as a clone in case your hoster is offline, or something else is wrong with your hub.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla -
@🌴 Seph 💭 👾 Have you taken a look at Hubzilla yet?
It was created by the same guy as Friendica, and it's a descendent of Friendica. (Forked to Free-Friendika, then forked to Red, both in 2011, then largely rewritten against a brand-new protocol in 2012, then renamed Red Matrix, then greatly expanded in features and renamed Hubzilla in 2015.)
One could say it's Friendica- entirely running on its own protocol, Zot6
- with nomadic identity that makes it possible to clone your channel across multiple servers and making it resilient against server outage
- with multiple channel (identities, like complete Friendica accounts, but without separate logins) on one account/login, and you can switch between them without logging out and back in again (all with multiple profiles like on Friendica)
- without Bluesky integration
- with less pandering to Mastodon
- with an even better permissions system
- with full (client-side and server-side) OpenWebAuth support
- with polls
- with WebDAV access to your file space
- with a built-in CalDAV calendar server
- with an optional built-in CardDAV addressbook server
- with optional articles, planning cards, wikis and webpages
- with a very extensive, detailed and well-written built-in help system
- with the ability to integrate git repositories with 3rd-party add-ons and themes that can even be upgraded with shell scripts as easily as the whole hub
- with 3rd-party themes available that change the entire UI and UX instead of reskinning the existing UI, especially the Utsukta themes by @Saiwal
It does not provide any previews for links, though I'm sure something like this can be developed as a third-party addon.
If you want to try it, it's quite tricky to find a good hub with 3rd-party themes installed to start on. There aren't any in North America; don't go looking for them.
You may want to get in touch with @pepe about joining his Whoville hub. It's well-equipped, it's well-maintained, but keep in mind it's in Europe.
If you find Hubzilla to your liking, and you want to have your own hub hosted, there appear to be quite a few Hubzilla hosting services. Pick one you like, set up your own hub, activate the add-ons you need, install the third-party themes and add-ons you need, get it to run properly, and then clone your daily-driver production channel over from Whoville. Make the instance on your own hub the main one, and keep the one at Whoville as a clone in case your hoster is offline, or something else is wrong with your hub.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla -
@🌴 Seph 💭 👾 Have you taken a look at Hubzilla yet?
It was created by the same guy as Friendica, and it's a descendent of Friendica. (Forked to Free-Friendika, then forked to Red, both in 2011, then largely rewritten against a brand-new protocol in 2012, then renamed Red Matrix, then greatly expanded in features and renamed Hubzilla in 2015.)
One could say it's Friendica- entirely running on its own protocol, Zot6
- with nomadic identity that makes it possible to clone your channel across multiple servers and making it resilient against server outage
- with multiple channel (identities, like complete Friendica accounts, but without separate logins) on one account/login, and you can switch between them without logging out and back in again (all with multiple profiles like on Friendica)
- without Bluesky integration
- with less pandering to Mastodon
- with an even better permissions system
- with full (client-side and server-side) OpenWebAuth support
- with polls
- with WebDAV access to your file space
- with a built-in CalDAV calendar server
- with an optional built-in CardDAV addressbook server
- with optional articles, planning cards, wikis and webpages
- with a very extensive, detailed and well-written built-in help system
- with the ability to integrate git repositories with 3rd-party add-ons and themes that can even be upgraded with shell scripts as easily as the whole hub
- with 3rd-party themes available that change the entire UI and UX instead of reskinning the existing UI, especially the Utsukta themes by @Saiwal
It does not provide any previews for links, though I'm sure something like this can be developed as a third-party addon.
If you want to try it, it's quite tricky to find a good hub with 3rd-party themes installed to start on. There aren't any in North America; don't go looking for them.
You may want to get in touch with @pepe about joining his Whoville hub. It's well-equipped, it's well-maintained, but keep in mind it's in Europe.
If you find Hubzilla to your liking, and you want to have your own hub hosted, there appear to be quite a few Hubzilla hosting services. Pick one you like, set up your own hub, activate the add-ons you need, install the third-party themes and add-ons you need, get it to run properly, and then clone your daily-driver production channel over from Whoville. Make the instance on your own hub the main one, and keep the one at Whoville as a clone in case your hoster is offline, or something else is wrong with your hub.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla -
@🌴 Seph 💭 👾 Have you taken a look at Hubzilla yet?
It was created by the same guy as Friendica, and it's a descendent of Friendica. (Forked to Free-Friendika, then forked to Red, both in 2011, then largely rewritten against a brand-new protocol in 2012, then renamed Red Matrix, then greatly expanded in features and renamed Hubzilla in 2015.)
One could say it's Friendica- entirely running on its own protocol, Zot6
- with nomadic identity that makes it possible to clone your channel across multiple servers and making it resilient against server outage
- with multiple channel (identities, like complete Friendica accounts, but without separate logins) on one account/login, and you can switch between them without logging out and back in again (all with multiple profiles like on Friendica)
- without Bluesky integration
- with less pandering to Mastodon
- with an even better permissions system
- with full (client-side and server-side) OpenWebAuth support
- with polls
- with WebDAV access to your file space
- with a built-in CalDAV calendar server
- with an optional built-in CardDAV addressbook server
- with optional articles, planning cards, wikis and webpages
- with a very extensive, detailed and well-written built-in help system
- with the ability to integrate git repositories with 3rd-party add-ons and themes that can even be upgraded with shell scripts as easily as the whole hub
- with 3rd-party themes available that change the entire UI and UX instead of reskinning the existing UI, especially the Utsukta themes by @Saiwal
It does not provide any previews for links, though I'm sure something like this can be developed as a third-party addon.
If you want to try it, it's quite tricky to find a good hub with 3rd-party themes installed to start on. There aren't any in North America; don't go looking for them.
You may want to get in touch with @pepe about joining his Whoville hub. It's well-equipped, it's well-maintained, but keep in mind it's in Europe.
If you find Hubzilla to your liking, and you want to have your own hub hosted, there appear to be quite a few Hubzilla hosting services. Pick one you like, set up your own hub, activate the add-ons you need, install the third-party themes and add-ons you need, get it to run properly, and then clone your daily-driver production channel over from Whoville. Make the instance on your own hub the main one, and keep the one at Whoville as a clone in case your hoster is offline, or something else is wrong with your hub.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla -
@🌴 Seph 💭 👾 Have you taken a look at Hubzilla yet?
It was created by the same guy as Friendica, and it's a descendent of Friendica. (Forked to Free-Friendika, then forked to Red, both in 2011, then largely rewritten against a brand-new protocol in 2012, then renamed Red Matrix, then greatly expanded in features and renamed Hubzilla in 2015.)
One could say it's Friendica- entirely running on its own protocol, Zot6
- with nomadic identity that makes it possible to clone your channel across multiple servers and making it resilient against server outage
- with multiple channel (identities, like complete Friendica accounts, but without separate logins) on one account/login, and you can switch between them without logging out and back in again (all with multiple profiles like on Friendica)
- without Bluesky integration
- with less pandering to Mastodon
- with an even better permissions system
- with full (client-side and server-side) OpenWebAuth support
- with polls
- with WebDAV access to your file space
- with a built-in CalDAV calendar server
- with an optional built-in CardDAV addressbook server
- with optional articles, planning cards, wikis and webpages
- with a very extensive, detailed and well-written built-in help system
- with the ability to integrate git repositories with 3rd-party add-ons and themes that can even be upgraded with shell scripts as easily as the whole hub
- with 3rd-party themes available that change the entire UI and UX instead of reskinning the existing UI, especially the Utsukta themes by @Saiwal
It does not provide any previews for links, though I'm sure something like this can be developed as a third-party addon.
If you want to try it, it's quite tricky to find a good hub with 3rd-party themes installed to start on. There aren't any in North America; don't go looking for them.
You may want to get in touch with @pepe about joining his Whoville hub. It's well-equipped, it's well-maintained, but keep in mind it's in Europe.
If you find Hubzilla to your liking, and you want to have your own hub hosted, there appear to be quite a few Hubzilla hosting services. Pick one you like, set up your own hub, activate the add-ons you need, install the third-party themes and add-ons you need, get it to run properly, and then clone your daily-driver production channel over from Whoville. Make the instance on your own hub the main one, and keep the one at Whoville as a clone in case your hoster is offline, or something else is wrong with your hub.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla -
@silverpill @Rimu @elle I could come up with a bunch of conspiracy theories for this behaviour.
Enforcement of Mastodon dominance.
A front against Mike Macgirvin, inventor of the most "disruptive" Fediverse software from a Mastodon point of view, as well as all his creations and inventions.
Forcing a grass-roots development under corporate control and eradicating the grass-roots part. Essentially "embrace-extend-extinguish", but trying desperately to speed-run the "embrace" and "extend" parts to cut to the "extinguish" part as quickly as possible.
The only way this could possibly fail is if Mastodon decided not to play along because more people consider Mastodon the ActivityPub reference implementation and Fediverse gold standard than not.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ActivityPub -
@silverpill @Rimu @elle I could come up with a bunch of conspiracy theories for this behaviour.
Enforcement of Mastodon dominance.
A front against Mike Macgirvin, inventor of the most "disruptive" Fediverse software from a Mastodon point of view, as well as all his creations and inventions.
Forcing a grass-roots development under corporate control and eradicating the grass-roots part. Essentially "embrace-extend-extinguish", but trying desperately to speed-run the "embrace" and "extend" parts to cut to the "extinguish" part as quickly as possible.
The only way this could possibly fail is if Mastodon decided not to play along because more people consider Mastodon the ActivityPub reference implementation and Fediverse gold standard than not.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ActivityPub -
@silverpill @Rimu @elle I could come up with a bunch of conspiracy theories for this behaviour.
Enforcement of Mastodon dominance.
A front against Mike Macgirvin, inventor of the most "disruptive" Fediverse software from a Mastodon point of view, as well as all his creations and inventions.
Forcing a grass-roots development under corporate control and eradicating the grass-roots part. Essentially "embrace-extend-extinguish", but trying desperately to speed-run the "embrace" and "extend" parts to cut to the "extinguish" part as quickly as possible.
The only way this could possibly fail is if Mastodon decided not to play along because more people consider Mastodon the ActivityPub reference implementation and Fediverse gold standard than not.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ActivityPub -
@silverpill @Rimu @elle I could come up with a bunch of conspiracy theories for this behaviour.
Enforcement of Mastodon dominance.
A front against Mike Macgirvin, inventor of the most "disruptive" Fediverse software from a Mastodon point of view, as well as all his creations and inventions.
Forcing a grass-roots development under corporate control and eradicating the grass-roots part. Essentially "embrace-extend-extinguish", but trying desperately to speed-run the "embrace" and "extend" parts to cut to the "extinguish" part as quickly as possible.
The only way this could possibly fail is if Mastodon decided not to play along because more people consider Mastodon the ActivityPub reference implementation and Fediverse gold standard than not.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ActivityPub -
@silverpill @Rimu @elle I could come up with a bunch of conspiracy theories for this behaviour.
Enforcement of Mastodon dominance.
A front against Mike Macgirvin, inventor of the most "disruptive" Fediverse software from a Mastodon point of view, as well as all his creations and inventions.
Forcing a grass-roots development under corporate control and eradicating the grass-roots part. Essentially "embrace-extend-extinguish", but trying desperately to speed-run the "embrace" and "extend" parts to cut to the "extinguish" part as quickly as possible.
The only way this could possibly fail is if Mastodon decided not to play along because more people consider Mastodon the ActivityPub reference implementation and Fediverse gold standard than not.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ActivityPub -
@Mika When I read the Bonfire suggestion, I was about to suggest Hubzilla, the most powerful Fediverse server application.
In case you don't know it: It basically evolved in 2015 from a fork of a Friendica fork, and it was created by Friendica's inventor. It probably has one of the best user documentations in the Fediverse, but it also has quite a steep learning curve, and newly created channels require quite a bit of configuration before you can really use them.
The same guy still maintains two more recent members of the same software family, (streams) from 2021 and Forte from 2024. They aren't quite as blistering with features as Hubzilla (they lack all the CMS stuff: articles, cards, wikis, webpages), and they don't offer nearly as many connection options as Friendica and Hubzilla.
Although they're still somehow complex, and although they don't have much of a user documentation, I dare say they're easier to get into because they don't require quite as much undocumented initial configuration after creating a channel.
All three offer groups (Hubzilla calls them "forums"), but no subforums. Whereas Friendica groups can only be co-administered by someone on the same server, groups/forums on Hubzilla, (streams) and Forte can be co-administered by anyone on Friendica, Hubzilla, (streams) or Forte.
However, there aren't any phone apps for them. They can be installed as progressive Web apps, though, and their Web UIs transform into mobile mode quite well AFAIK.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #Forte -
@Mika When I read the Bonfire suggestion, I was about to suggest Hubzilla, the most powerful Fediverse server application.
In case you don't know it: It basically evolved in 2015 from a fork of a Friendica fork, and it was created by Friendica's inventor. It probably has one of the best user documentations in the Fediverse, but it also has quite a steep learning curve, and newly created channels require quite a bit of configuration before you can really use them.
The same guy still maintains two more recent members of the same software family, (streams) from 2021 and Forte from 2024. They aren't quite as blistering with features as Hubzilla (they lack all the CMS stuff: articles, cards, wikis, webpages), and they don't offer nearly as many connection options as Friendica and Hubzilla.
Although they're still somehow complex, and although they don't have much of a user documentation, I dare say they're easier to get into because they don't require quite as much undocumented initial configuration after creating a channel.
All three offer groups (Hubzilla calls them "forums"), but no subforums. Whereas Friendica groups can only be co-administered by someone on the same server, groups/forums on Hubzilla, (streams) and Forte can be co-administered by anyone on Friendica, Hubzilla, (streams) or Forte.
However, there aren't any phone apps for them. They can be installed as progressive Web apps, though, and their Web UIs transform into mobile mode quite well AFAIK.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #Forte -
@Mika When I read the Bonfire suggestion, I was about to suggest Hubzilla, the most powerful Fediverse server application.
In case you don't know it: It basically evolved in 2015 from a fork of a Friendica fork, and it was created by Friendica's inventor. It probably has one of the best user documentations in the Fediverse, but it also has quite a steep learning curve, and newly created channels require quite a bit of configuration before you can really use them.
The same guy still maintains two more recent members of the same software family, (streams) from 2021 and Forte from 2024. They aren't quite as blistering with features as Hubzilla (they lack all the CMS stuff: articles, cards, wikis, webpages), and they don't offer nearly as many connection options as Friendica and Hubzilla.
Although they're still somehow complex, and although they don't have much of a user documentation, I dare say they're easier to get into because they don't require quite as much undocumented initial configuration after creating a channel.
All three offer groups (Hubzilla calls them "forums"), but no subforums. Whereas Friendica groups can only be co-administered by someone on the same server, groups/forums on Hubzilla, (streams) and Forte can be co-administered by anyone on Friendica, Hubzilla, (streams) or Forte.
However, there aren't any phone apps for them. They can be installed as progressive Web apps, though, and their Web UIs transform into mobile mode quite well AFAIK.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #Forte -
CW: How must foreign-language text be transcribed in an image description? CW: long (over 2,200 characters), alt-text meta, image description meta
I'm pretty sure that posting this will turn out completely futile. But I'll try anyway.
I'm especially asking the Mastodon alt-text enforcers: How must foreign-language text be transcribed, both by Web accessibility standards and by Mastodon's alt-text standards?
Let's assume I have some text in an image that's in a different language than the post and therefore in a different language than the image description. But I still have to transcribe it.
Now, according to image-describing rules, text must always be transcribed 100% verbatim. Word by word, character by character, exactly identical to the original in the image.
Here's the catch: Screen reader software may not be able to reliably switch the language in which they read out text in the middle of a description. They definitely cannot switch the language in the middle of an alt-text, I know that, just like they cannot navigate within alt-text.
This means that if I describe an image in English, but there's French text somewhere, a screen reader may read it out as gobbledygook instead of proper French. It may read the French text like it's English.
But even if the screen reader did read out the French text in proper French, someone who doesn't understand French won't understand the text.
This leaves me with two options:- Transcribe the foreign-language text verbatim, add a translation afterwards.
This would make the foreign-language text understandable, but it would also produce gobbledygook. - Give a translated transcript of the foreign-language text that's as close to the original as possible.
No gobbledygook, but I'd break the rule of always transcribing text verbatim.
The latter option would produce weird results if applied to a sign with essentially the same text in French, English and German where the French and German texts translate into something that slightly differs from both each other and the English text. I've happened upon this before.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Transcript #Transcripts #ScreenReader #ScreenReaders #ForeignLanguage #Inclusion #A11y #Accessibility - Transcribe the foreign-language text verbatim, add a translation afterwards.
-
CW: How must foreign-language text be transcribed in an image description? CW: long (over 2,200 characters), alt-text meta, image description meta
I'm pretty sure that posting this will turn out completely futile. But I'll try anyway.
I'm especially asking the Mastodon alt-text enforcers: How must foreign-language text be transcribed, both by Web accessibility standards and by Mastodon's alt-text standards?
Let's assume I have some text in an image that's in a different language than the post and therefore in a different language than the image description. But I still have to transcribe it.
Now, according to image-describing rules, text must always be transcribed 100% verbatim. Word by word, character by character, exactly identical to the original in the image.
Here's the catch: Screen reader software may not be able to reliably switch the language in which they read out text in the middle of a description. They definitely cannot switch the language in the middle of an alt-text, I know that, just like they cannot navigate within alt-text.
This means that if I describe an image in English, but there's French text somewhere, a screen reader may read it out as gobbledygook instead of proper French. It may read the French text like it's English.
But even if the screen reader did read out the French text in proper French, someone who doesn't understand French won't understand the text.
This leaves me with two options:- Transcribe the foreign-language text verbatim, add a translation afterwards.
This would make the foreign-language text understandable, but it would also produce gobbledygook. - Give a translated transcript of the foreign-language text that's as close to the original as possible.
No gobbledygook, but I'd break the rule of always transcribing text verbatim.
The latter option would produce weird results if applied to a sign with essentially the same text in French, English and German where the French and German texts translate into something that slightly differs from both each other and the English text. I've happened upon this before.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Transcript #Transcripts #ScreenReader #ScreenReaders #ForeignLanguage #Inclusion #A11y #Accessibility - Transcribe the foreign-language text verbatim, add a translation afterwards.
-
CW: How must foreign-language text be transcribed in an image description? CW: long (over 2,200 characters), alt-text meta, image description meta
I'm pretty sure that posting this will turn out completely futile. But I'll try anyway.
I'm especially asking the Mastodon alt-text enforcers: How must foreign-language text be transcribed, both by Web accessibility standards and by Mastodon's alt-text standards?
Let's assume I have some text in an image that's in a different language than the post and therefore in a different language than the image description. But I still have to transcribe it.
Now, according to image-describing rules, text must always be transcribed 100% verbatim. Word by word, character by character, exactly identical to the original in the image.
Here's the catch: Screen reader software may not be able to reliably switch the language in which they read out text in the middle of a description. They definitely cannot switch the language in the middle of an alt-text, I know that, just like they cannot navigate within alt-text.
This means that if I describe an image in English, but there's French text somewhere, a screen reader may read it out as gobbledygook instead of proper French. It may read the French text like it's English.
But even if the screen reader did read out the French text in proper French, someone who doesn't understand French won't understand the text.
This leaves me with two options:- Transcribe the foreign-language text verbatim, add a translation afterwards.
This would make the foreign-language text understandable, but it would also produce gobbledygook. - Give a translated transcript of the foreign-language text that's as close to the original as possible.
No gobbledygook, but I'd break the rule of always transcribing text verbatim.
The latter option would produce weird results if applied to a sign with essentially the same text in French, English and German where the French and German texts translate into something that slightly differs from both each other and the English text. I've happened upon this before.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Transcript #Transcripts #ScreenReader #ScreenReaders #ForeignLanguage #Inclusion #A11y #Accessibility - Transcribe the foreign-language text verbatim, add a translation afterwards.
-
CW: How must foreign-language text be transcribed in an image description? CW: long (over 2,200 characters), alt-text meta, image description meta
I'm pretty sure that posting this will turn out completely futile. But I'll try anyway.
I'm especially asking the Mastodon alt-text enforcers: How must foreign-language text be transcribed, both by Web accessibility standards and by Mastodon's alt-text standards?
Let's assume I have some text in an image that's in a different language than the post and therefore in a different language than the image description. But I still have to transcribe it.
Now, according to image-describing rules, text must always be transcribed 100% verbatim. Word by word, character by character, exactly identical to the original in the image.
Here's the catch: Screen reader software may not be able to reliably switch the language in which they read out text in the middle of a description. They definitely cannot switch the language in the middle of an alt-text, I know that, just like they cannot navigate within alt-text.
This means that if I describe an image in English, but there's French text somewhere, a screen reader may read it out as gobbledygook instead of proper French. It may read the French text like it's English.
But even if the screen reader did read out the French text in proper French, someone who doesn't understand French won't understand the text.
This leaves me with two options:- Transcribe the foreign-language text verbatim, add a translation afterwards.
This would make the foreign-language text understandable, but it would also produce gobbledygook. - Give a translated transcript of the foreign-language text that's as close to the original as possible.
No gobbledygook, but I'd break the rule of always transcribing text verbatim.
The latter option would produce weird results if applied to a sign with essentially the same text in French, English and German where the French and German texts translate into something that slightly differs from both each other and the English text. I've happened upon this before.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Transcript #Transcripts #ScreenReader #ScreenReaders #ForeignLanguage #Inclusion #A11y #Accessibility - Transcribe the foreign-language text verbatim, add a translation afterwards.
-
CW: How must foreign-language text be transcribed in an image description? CW: long (over 2,200 characters), alt-text meta, image description meta
I'm pretty sure that posting this will turn out completely futile. But I'll try anyway.
I'm especially asking the Mastodon alt-text enforcers: How must foreign-language text be transcribed, both by Web accessibility standards and by Mastodon's alt-text standards?
Let's assume I have some text in an image that's in a different language than the post and therefore in a different language than the image description. But I still have to transcribe it.
Now, according to image-describing rules, text must always be transcribed 100% verbatim. Word by word, character by character, exactly identical to the original in the image.
Here's the catch: Screen reader software may not be able to reliably switch the language in which they read out text in the middle of a description. They definitely cannot switch the language in the middle of an alt-text, I know that, just like they cannot navigate within alt-text.
This means that if I describe an image in English, but there's French text somewhere, a screen reader may read it out as gobbledygook instead of proper French. It may read the French text like it's English.
But even if the screen reader did read out the French text in proper French, someone who doesn't understand French won't understand the text.
This leaves me with two options:- Transcribe the foreign-language text verbatim, add a translation afterwards.
This would make the foreign-language text understandable, but it would also produce gobbledygook. - Give a translated transcript of the foreign-language text that's as close to the original as possible.
No gobbledygook, but I'd break the rule of always transcribing text verbatim.
The latter option would produce weird results if applied to a sign with essentially the same text in French, English and German where the French and German texts translate into something that slightly differs from both each other and the English text. I've happened upon this before.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Transcript #Transcripts #ScreenReader #ScreenReaders #ForeignLanguage #Inclusion #A11y #Accessibility - Transcribe the foreign-language text verbatim, add a translation afterwards.
-
@Prof. Rachel Thorn 🍉🇺🇦🏳️⚧️🏳️ Just out of curiosity: Are there any good excuses for not having added an alt-text that you'd accept?
For example, when someone new to Hubzilla tells you that they neither know what alt-text is nor how to add it? Hubzilla doesn't have dedicated UI elements for adding alt-texts. Images are embedded into posts like in blog posts rather than attached as files like on Mastodon. Alt-texts have to be manually woven into the image-embedding phpBB code, and the newbie might not know that this is explained in Hubzilla's built-in help, or it's simply too tedious to "program" an alt-text in.
Or when a Hubzilla veteran of over ten years tells you that Hubzilla has no way whatsoever to add an alt-text to a video? Like images, videos are embedded into posts. But the video-embedding code has no option for an alt-text. Granted, if it's a video, I'd rather expect or supply a full, time-coded transcript in the message text. But maybe what's expected is both a full, time-coded transcript and an alt-text that's sufficiently detailed by Mastodon's standards.
If neither of these are acceptable to you, there's something else you should know: Hubzilla does not support Mastodon's report feature either because that's a non-standard, homegrown Mastodon feature, and Hubzilla is not built against Mastodon. So if you report someone to their Hubzilla admin, the admin simply will never receive your report.
This is likely to lead Mastodon users into believing that either the server on the other end is unmoderated (which, in Hubzilla's case and by Mastodon's standards, is technically true because Hubzilla is all about self-moderation), or the admin doesn't care, both of which, by Mastodon's standards, is reason enough to have the server Fediblocked.
Again, I'm just being curious and cautious. You should not believe that I'm trying to weasel myself out of having to describe images.
After all, I'm working on an extensive wiki about image descriptions and alt-texts in the Fediverse with 50+ pages with dozens of webpages and blog posts on how to describe images. I'm using the same knowledge that I'm pouring into the wiki, the same rules and guidelines that already have or will have wiki pages, to describe my own images, even though some of them collide with each other and with Mastodon's image description preferences and quality standards. I don't think anyone else in the Fediverse is taking describing images more seriously.
I rarely post images anymore due to the effort involved. But whenever I do, I take all the effort that's needed to both describe and explain them, taking into consideration the context, Mastodon's culture and preferences regarding alt-texts and image descriptions, the potential target audience and what knowledge they may or may not have about what's in the image. I've declared all my existing image descriptions outdated, also because it'd be too tedious to go and upgrade them all whenever I learn something new about describing images. (Don't go looking for my most recent images on this channel; I post my images elsewhere now because Hubzilla can't make Mastodon blur sensitive images.)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
@Prof. Rachel Thorn 🍉🇺🇦🏳️⚧️🏳️ Just out of curiosity: Are there any good excuses for not having added an alt-text that you'd accept?
For example, when someone new to Hubzilla tells you that they neither know what alt-text is nor how to add it? Hubzilla doesn't have dedicated UI elements for adding alt-texts. Images are embedded into posts like in blog posts rather than attached as files like on Mastodon. Alt-texts have to be manually woven into the image-embedding phpBB code, and the newbie might not know that this is explained in Hubzilla's built-in help, or it's simply too tedious to "program" an alt-text in.
Or when a Hubzilla veteran of over ten years tells you that Hubzilla has no way whatsoever to add an alt-text to a video? Like images, videos are embedded into posts. But the video-embedding code has no option for an alt-text. Granted, if it's a video, I'd rather expect or supply a full, time-coded transcript in the message text. But maybe what's expected is both a full, time-coded transcript and an alt-text that's sufficiently detailed by Mastodon's standards.
If neither of these are acceptable to you, there's something else you should know: Hubzilla does not support Mastodon's report feature either because that's a non-standard, homegrown Mastodon feature, and Hubzilla is not built against Mastodon. So if you report someone to their Hubzilla admin, the admin simply will never receive your report.
This is likely to lead Mastodon users into believing that either the server on the other end is unmoderated (which, in Hubzilla's case and by Mastodon's standards, is technically true because Hubzilla is all about self-moderation), or the admin doesn't care, both of which, by Mastodon's standards, is reason enough to have the server Fediblocked.
Again, I'm just being curious and cautious. You should not believe that I'm trying to weasel myself out of having to describe images.
After all, I'm working on an extensive wiki about image descriptions and alt-texts in the Fediverse with 50+ pages with dozens of webpages and blog posts on how to describe images. I'm using the same knowledge that I'm pouring into the wiki, the same rules and guidelines that already have or will have wiki pages, to describe my own images, even though some of them collide with each other and with Mastodon's image description preferences and quality standards. I don't think anyone else in the Fediverse is taking describing images more seriously.
I rarely post images anymore due to the effort involved. But whenever I do, I take all the effort that's needed to both describe and explain them, taking into consideration the context, Mastodon's culture and preferences regarding alt-texts and image descriptions, the potential target audience and what knowledge they may or may not have about what's in the image. I've declared all my existing image descriptions outdated, also because it'd be too tedious to go and upgrade them all whenever I learn something new about describing images. (Don't go looking for my most recent images on this channel; I post my images elsewhere now because Hubzilla can't make Mastodon blur sensitive images.)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
@Prof. Rachel Thorn 🍉🇺🇦🏳️⚧️🏳️ Just out of curiosity: Are there any good excuses for not having added an alt-text that you'd accept?
For example, when someone new to Hubzilla tells you that they neither know what alt-text is nor how to add it? Hubzilla doesn't have dedicated UI elements for adding alt-texts. Images are embedded into posts like in blog posts rather than attached as files like on Mastodon. Alt-texts have to be manually woven into the image-embedding phpBB code, and the newbie might not know that this is explained in Hubzilla's built-in help, or it's simply too tedious to "program" an alt-text in.
Or when a Hubzilla veteran of over ten years tells you that Hubzilla has no way whatsoever to add an alt-text to a video? Like images, videos are embedded into posts. But the video-embedding code has no option for an alt-text. Granted, if it's a video, I'd rather expect or supply a full, time-coded transcript in the message text. But maybe what's expected is both a full, time-coded transcript and an alt-text that's sufficiently detailed by Mastodon's standards.
If neither of these are acceptable to you, there's something else you should know: Hubzilla does not support Mastodon's report feature either because that's a non-standard, homegrown Mastodon feature, and Hubzilla is not built against Mastodon. So if you report someone to their Hubzilla admin, the admin simply will never receive your report.
This is likely to lead Mastodon users into believing that either the server on the other end is unmoderated (which, in Hubzilla's case and by Mastodon's standards, is technically true because Hubzilla is all about self-moderation), or the admin doesn't care, both of which, by Mastodon's standards, is reason enough to have the server Fediblocked.
Again, I'm just being curious and cautious. You should not believe that I'm trying to weasel myself out of having to describe images.
After all, I'm working on an extensive wiki about image descriptions and alt-texts in the Fediverse with 50+ pages with dozens of webpages and blog posts on how to describe images. I'm using the same knowledge that I'm pouring into the wiki, the same rules and guidelines that already have or will have wiki pages, to describe my own images, even though some of them collide with each other and with Mastodon's image description preferences and quality standards. I don't think anyone else in the Fediverse is taking describing images more seriously.
I rarely post images anymore due to the effort involved. But whenever I do, I take all the effort that's needed to both describe and explain them, taking into consideration the context, Mastodon's culture and preferences regarding alt-texts and image descriptions, the potential target audience and what knowledge they may or may not have about what's in the image. I've declared all my existing image descriptions outdated, also because it'd be too tedious to go and upgrade them all whenever I learn something new about describing images. (Don't go looking for my most recent images on this channel; I post my images elsewhere now because Hubzilla can't make Mastodon blur sensitive images.)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
@Prof. Rachel Thorn 🍉🇺🇦🏳️⚧️🏳️ Just out of curiosity: Are there any good excuses for not having added an alt-text that you'd accept?
For example, when someone new to Hubzilla tells you that they neither know what alt-text is nor how to add it? Hubzilla doesn't have dedicated UI elements for adding alt-texts. Images are embedded into posts like in blog posts rather than attached as files like on Mastodon. Alt-texts have to be manually woven into the image-embedding phpBB code, and the newbie might not know that this is explained in Hubzilla's built-in help, or it's simply too tedious to "program" an alt-text in.
Or when a Hubzilla veteran of over ten years tells you that Hubzilla has no way whatsoever to add an alt-text to a video? Like images, videos are embedded into posts. But the video-embedding code has no option for an alt-text. Granted, if it's a video, I'd rather expect or supply a full, time-coded transcript in the message text. But maybe what's expected is both a full, time-coded transcript and an alt-text that's sufficiently detailed by Mastodon's standards.
If neither of these are acceptable to you, there's something else you should know: Hubzilla does not support Mastodon's report feature either because that's a non-standard, homegrown Mastodon feature, and Hubzilla is not built against Mastodon. So if you report someone to their Hubzilla admin, the admin simply will never receive your report.
This is likely to lead Mastodon users into believing that either the server on the other end is unmoderated (which, in Hubzilla's case and by Mastodon's standards, is technically true because Hubzilla is all about self-moderation), or the admin doesn't care, both of which, by Mastodon's standards, is reason enough to have the server Fediblocked.
Again, I'm just being curious and cautious. You should not believe that I'm trying to weasel myself out of having to describe images.
After all, I'm working on an extensive wiki about image descriptions and alt-texts in the Fediverse with 50+ pages with dozens of webpages and blog posts on how to describe images. I'm using the same knowledge that I'm pouring into the wiki, the same rules and guidelines that already have or will have wiki pages, to describe my own images, even though some of them collide with each other and with Mastodon's image description preferences and quality standards. I don't think anyone else in the Fediverse is taking describing images more seriously.
I rarely post images anymore due to the effort involved. But whenever I do, I take all the effort that's needed to both describe and explain them, taking into consideration the context, Mastodon's culture and preferences regarding alt-texts and image descriptions, the potential target audience and what knowledge they may or may not have about what's in the image. I've declared all my existing image descriptions outdated, also because it'd be too tedious to go and upgrade them all whenever I learn something new about describing images. (Don't go looking for my most recent images on this channel; I post my images elsewhere now because Hubzilla can't make Mastodon blur sensitive images.)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
CW: Appreciating lgbtqia.space and the difficulty of moderating an instance on Fedi
Hey, running a Fedi instance is not easy. Since the last time I posted here, I've seen plenty of instances shut down. It can be easy to take these spaces for granted. They're not.
Having to handle an online community that's going to be federated with a whole bunch of others is hard and ungrateful work. You always have to handle conflict, knowing that you may leave people unhappy, and most of your users will never know about half of the shit you've protected them from.
Many try with the best of intentions and leave completely burnt out. It shouldn't be that way, but alas, it often is. lgbtqia.space is still standing. Let's all enjoy this space while it lasts, for all things must one day end. I can only hope that it won't end the way so many other instances did.
And if you're a former moderator of an instance that shutdown... this might be a painful post to read. I'm sorry. For what it's worth, you did your best. Your regrets, your mistakes, they don't take away from that. It's not easy.
