Phát triển ứng dụng biến video thành tài liệu định dạng văn bản. Ứng dụng này phân tích frame video và kết hợp thông tin thành tài liệu cuối cùng.
#video2docs #tài liệu #phần_mềm #ứng_dụng #định_dạng_văn_bản #VideoToDocs #Documentation #Software #App #TextFormatting
#TextFormatting
This is the overview article I needed on Typst. It concisely explains how the document preparation system works, in what it differs from LaTeX, and why it may be a suitable replacement for LaTeX.
@silverpill Who are the longformers anyway?
They're those who either are commercial or looking for professional/commercial users or both. Flipboard. Automattic (WordPress). Ghost. These kinds.
They know themselves. They know each other. And they know Mastodon. And that's it.
None of them has ever heard of Pleroma or Akkoma.
None of them has ever heard of Misskey or the Forkeys.
None of them has ever heard of Mitra.
None of them has ever heard of GoToSocial.
None of them has ever heard of Hollo.
None of them has ever heard of Friendica, Hubzilla, (streams) or Forte, even though Friendica and Hubzilla are both older than Mastodon. And apparently, neither has @Helge. But then again, Friendica and its nomadic, security-enhanced descendants are being overlooked by almost everyone. That's why there's always on-going work for features to be "introduced to the Fediverse" which Friendica has had for a decade and a half.
Granted, the HTML support on Friendica, Hubzilla, (streams) and Forte can be summarised with "yes". But elaborate tables that show what either of them supports how would be very useful.
Also, granted, everything I've mentioned above (normally) uses something else than HTML for formatting in the frontend. For example, Misskey and all Forkeys use MFM ("Misskey-Flavoured Markdown"). Friendica uses extended BBcode with the option to use Markdown instead. Hubzilla uses even more extended BBcode. (streams) and Forte can use the same even more extended BBcode and Markdown and HTML at the same time within the same post, although not all markup languages support all features.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Mitra #GoToSocial #Hollo #Friendica #Hubzilla #Streams #(streams) #Forte #LongFormContent #BBcode #Markdown #HTML #TextFormatting
They're those who either are commercial or looking for professional/commercial users or both. Flipboard. Automattic (WordPress). Ghost. These kinds.
They know themselves. They know each other. And they know Mastodon. And that's it.
None of them has ever heard of Pleroma or Akkoma.
None of them has ever heard of Misskey or the Forkeys.
None of them has ever heard of Mitra.
None of them has ever heard of GoToSocial.
None of them has ever heard of Hollo.
None of them has ever heard of Friendica, Hubzilla, (streams) or Forte, even though Friendica and Hubzilla are both older than Mastodon. And apparently, neither has @Helge. But then again, Friendica and its nomadic, security-enhanced descendants are being overlooked by almost everyone. That's why there's always on-going work for features to be "introduced to the Fediverse" which Friendica has had for a decade and a half.
Granted, the HTML support on Friendica, Hubzilla, (streams) and Forte can be summarised with "yes". But elaborate tables that show what either of them supports how would be very useful.
Also, granted, everything I've mentioned above (normally) uses something else than HTML for formatting in the frontend. For example, Misskey and all Forkeys use MFM ("Misskey-Flavoured Markdown"). Friendica uses extended BBcode with the option to use Markdown instead. Hubzilla uses even more extended BBcode. (streams) and Forte can use the same even more extended BBcode and Markdown and HTML at the same time within the same post, although not all markup languages support all features.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Mitra #GoToSocial #Hollo #Friendica #Hubzilla #Streams #(streams) #Forte #LongFormContent #BBcode #Markdown #HTML #TextFormatting
Markdown and the Slow Fade of the Formatting Fetish
https://ia.net/topics/markdown-and-the-slow-fade-of-the-formatting-fetish
🎉 BREAKING NEWS: Apple Notes users can finally rejoice as they wait for the thrilling iOS 26 update to bring Markdown support—because who needs #innovation when you can have text formatting? 📱💤 Welcome to the future of note-taking, where Apple is sprinting valiantly to catch up with the 2010s. ⏳🙄
https://www.macrumors.com/2025/06/04/apple-notes-rumored-markdown-support-ios-26/ #AppleNotes #iOS26 #MarkdownSupport #textFormatting #catchUp #HackerNews #ngated
@Martin Holland Vanilla Mastodon cannot generate any text formatting in any shape or form AFAIK. You can be lucky that it can display a small subset of it, and even that has only been possible since October, 2022, when Mastodon 4 was released.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #TextFormatting
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #TextFormatting
@hexaheximal There's no syntax for it on mastodon.social. You simply can't do it there.
Some users have already mentioned Markdown which is supported by a few Mastodon forks, Pleroma, Akkoma, Misskey and its several forks (including but not limited to Firefish, Iceshrimp, Sharkey and Catodon), Mitra, (streams), Forte and optionally also by Friendica, probably also by others.
For completion's sake, Friendica, Hubzilla, (streams) and Forte mainly use BBcode.
The syntax for quotes is either [quote]Here goes the quote[/quote] or [quote="Whoever is quoted"]Here goes the quote[/quote].
Both in-line code and code blocks are delimited with
Lastly, (streams) and Forte even support HTML.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Firefish #Iceshrimp #Sharkey #Catodon #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #Markdown #BBcode #HTML #TextFormatting
Some users have already mentioned Markdown which is supported by a few Mastodon forks, Pleroma, Akkoma, Misskey and its several forks (including but not limited to Firefish, Iceshrimp, Sharkey and Catodon), Mitra, (streams), Forte and optionally also by Friendica, probably also by others.
For completion's sake, Friendica, Hubzilla, (streams) and Forte mainly use BBcode.
The syntax for quotes is either [quote]Here goes the quote[/quote] or [quote="Whoever is quoted"]Here goes the quote[/quote].
Both in-line code and code blocks are delimited with
Lastly, (streams) and Forte even support HTML.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Firefish #Iceshrimp #Sharkey #Catodon #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #Markdown #BBcode #HTML #TextFormatting
@Larry Garfield @Renaud Chaput In this case, the handling of long-form content should be configurable per account.
The settings could be:
Maybe there could be an additional setting for formatted content in general:
#Long #LongPost #LongPosts #LongPostMeta #CWLong #CWLongPost #CWLongPostMeta #500Characters #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica #Hubzilla #TextFormatting #RichText
The settings could be:
- Render fully (default; what the devs of Hubzilla and (streams) want)
- Always link (what Mastodon does with Article-type objects)
- Link if title or subject is available, otherwise render fully
- Link if title or subject is available, otherwise block
- Block everything over 500 characters
Maybe there could be an additional setting for formatted content in general:
- Render fully (default)
- Render partially (the Mastodon 4 way right now)
- Remove all formatting (what Mastodon up until 3 did)
- Block
#Long #LongPost #LongPosts #LongPostMeta #CWLong #CWLongPost #CWLongPostMeta #500Characters #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica #Hubzilla #TextFormatting #RichText
This blog post covers two methods for implementing selected text formatting for QML TextEdit: a QML/JS hacky solution as well as a more comprehensive C++ solution, including a Qt 6.7 backport: https://www.kdab.com/formatting-selected-text-in-qml/ #QML #QtDev #Cpp #TextFormatting
@ᴚ uɐᗡ It's called a quote. Standard feature on Friendica, Hubzilla (where I am), (streams), the now-deceased rest of the family, Misskey and all its forks etc., basically everywhere that isn't Mastodon.
Within Friendica, Hubzilla and (streams), it's handled basically the same way as on good old bulletin-board forums: in BBcode.
(streams) also has ways of doing that with Markdown or HTML.
There are various different ways of getting that code, also depending on whether one replies to a post or a comment.
ActivityPub uses Rich Text for formatting. So Friendica converts this into the corresponding formatting in Rich Text, and on Hubzilla and (streams), the optional ActivityPub bridge PubCrawl does that.
Mastodon, in turn, has introduced some Rich Text displaying capabilities with version 4.0.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams) #TextFormatting #BBcode #RichText
Within Friendica, Hubzilla and (streams), it's handled basically the same way as on good old bulletin-board forums: in BBcode.
[quote]if the process is really that involved and if they can fix it[/quote](streams) also has ways of doing that with Markdown or HTML.
There are various different ways of getting that code, also depending on whether one replies to a post or a comment.
ActivityPub uses Rich Text for formatting. So Friendica converts this into the corresponding formatting in Rich Text, and on Hubzilla and (streams), the optional ActivityPub bridge PubCrawl does that.
Mastodon, in turn, has introduced some Rich Text displaying capabilities with version 4.0.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams) #TextFormatting #BBcode #RichText
WhatsApp is testing additional text formatting options for Android and iOS users enrolled in the beta program. Now, you can use '>' to highlight a part of your message and create bulleted lists with '-' or '*'. Add a number before your message for numbered lists! Check out the screenshot to see these new features in action. 📝🌟
@Daniel de Kay The biggest cultural difference based on server software has to be between Mastodon on the one hand and the Mike Macgirvin creations Friendica, Hubzilla and (streams) on the other hand.
Not only do they have vastly different user bases, but they developed independently from one another. When the Mastodon culture developed, those who shaped it didn't even know the other side, so they couldn't adopt any of its culture.
Said other side's culture dates back to 2010 when Friendica was launched as Mistpark, and since that was almost six years before Mastodon, it couldn't be inspired by Mastodon's culture either.
Add to that that these respective cultures are greatly shaped by technical features and limitations or the lack thereof.
Mastodon's culture is largely built around its 500-character limit which is ample for your typical phone-wielding Mastodon user. Friendica, Hubzilla and (streams) don't have any defined character limit whatsoever, and its target audience is largely on desktop or laptop computers, often running Linux, with large screens and full-size hardware keyboards.
So it's the most normal thing in the world for them to write in one post as much as they want while Mastodon users debate whether threads are good, or you should always limit yourself to 500 characters or less.
Also, alt-text. Mastodon has many disabled users, including blind or visually-impaired users. And it has a dedicated alt-text field for each image. On top of that, it offers 1,500 characters for each alt-text which, in connection with the 500-character limit for toots, has people write detailed image descriptions and explanations and put them into the alt-text. That's often information that doesn't even belong in alt-text, but there's no room for it elsewhere.
Friendica, Hubzilla and (streams) have unlimited room, so putting stuff into alt-text because the post text is too limited seems ridiculous. But they don't have a vocal disabled community, so there's little interest in accessibility. And neither of them has a dedicated alt-text field. Alt-text is supported, but it has to be manually grafted into the image-embedding code in the post. And there's no official documentation for that, I think not even for Friendica which is the only one out of the three with actually useful end-user documentation.
It's similar with content warnings. On Mastodon, they're put into the repurposed summary field, and next to nobody knows that it's a repurposed summary field rather than invented for content warnings from scratch. So since Mastodon has a content warning field, writer-side content warnings are huge, but also cause for drama.
Mastodon 4.0 has introduced filters that can create reader-side content warnings, but hardly anyone uses them, even fewer people support them with keywords or hashtags, many don't even know this feature exists, and it's generally ignored because it's un-Mastodon.
The Friendica/Hubzilla/(streams) complex doesn't have a content warning field. Hubzilla and (streams) have a summary field labelled as such. Friendica doesn't even have that; it uses a pair of BBcode tags for that.
And within their own ecosystem, they don't even need it. They've got the "NSFW app" instead, an over-one-decade-old, optional, simple-as-anything substring filter that automatically hides entire posts with all media and everything behind content warnings if it finds one of the entered keywords or hashtags.
So they can't understand Mastodon's commotion about content warnings, and Mastodon users can't understand why they don't add Mastodon-style content warnings.
And then there are all the things that were or are being debated on Mastodon and whether or not it should introduce them. Especially the second-wave Twitter refugees are often staunchly against them.
Full-text search and quote-tweets are being actively used on Twitter to track down and harass members of minorities who have fled to Mastodon. Of course, they don't want Mastodon to introduce either. That is, in the case of full-text search, Mastodon has found a solution, but one that doesn't really federate to the rest of the Fediverse.
Quotes and text formatting are seen as bad, too. Many don't know quotes because Twitter doesn't have them, and so they think quotes could be used as tools of harassment. And both are seen as making Mastodon feel less like Mastodon and more complicated.
Friendica and Hubzilla had all this before there was Mastodon, and (streams) inherited it from its long line of ancestors. Their users have gotten so used to having all this that they don't understand what the problems should be, also because they're so detached from Mastodon's culture. So they keep on using these features unashamedly, even around Mastodon users.
Some differences are rather simple. Take mentions, for example. Friendica has always used long names for mentions, as does its offspring. Mastodon users may find that freaky. Meanwhile, Friendica, Hubzilla or (streams) users may find Mastodon's mentions cryptic because they use the short name. But even they matter.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #FediverseCulture #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #CharacterLimit #CharacterLimits #500Characters #CW #CWs #ContentWarning #ContentWarnings #ContentWarningMeta #AltText #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Quotes #QuotePost #QuotePosts #QuoteBoost #QuoteBoost #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuotedShares #TextFormatting #FullTextSearch
Not only do they have vastly different user bases, but they developed independently from one another. When the Mastodon culture developed, those who shaped it didn't even know the other side, so they couldn't adopt any of its culture.
Said other side's culture dates back to 2010 when Friendica was launched as Mistpark, and since that was almost six years before Mastodon, it couldn't be inspired by Mastodon's culture either.
Add to that that these respective cultures are greatly shaped by technical features and limitations or the lack thereof.
Mastodon's culture is largely built around its 500-character limit which is ample for your typical phone-wielding Mastodon user. Friendica, Hubzilla and (streams) don't have any defined character limit whatsoever, and its target audience is largely on desktop or laptop computers, often running Linux, with large screens and full-size hardware keyboards.
So it's the most normal thing in the world for them to write in one post as much as they want while Mastodon users debate whether threads are good, or you should always limit yourself to 500 characters or less.
Also, alt-text. Mastodon has many disabled users, including blind or visually-impaired users. And it has a dedicated alt-text field for each image. On top of that, it offers 1,500 characters for each alt-text which, in connection with the 500-character limit for toots, has people write detailed image descriptions and explanations and put them into the alt-text. That's often information that doesn't even belong in alt-text, but there's no room for it elsewhere.
Friendica, Hubzilla and (streams) have unlimited room, so putting stuff into alt-text because the post text is too limited seems ridiculous. But they don't have a vocal disabled community, so there's little interest in accessibility. And neither of them has a dedicated alt-text field. Alt-text is supported, but it has to be manually grafted into the image-embedding code in the post. And there's no official documentation for that, I think not even for Friendica which is the only one out of the three with actually useful end-user documentation.
It's similar with content warnings. On Mastodon, they're put into the repurposed summary field, and next to nobody knows that it's a repurposed summary field rather than invented for content warnings from scratch. So since Mastodon has a content warning field, writer-side content warnings are huge, but also cause for drama.
Mastodon 4.0 has introduced filters that can create reader-side content warnings, but hardly anyone uses them, even fewer people support them with keywords or hashtags, many don't even know this feature exists, and it's generally ignored because it's un-Mastodon.
The Friendica/Hubzilla/(streams) complex doesn't have a content warning field. Hubzilla and (streams) have a summary field labelled as such. Friendica doesn't even have that; it uses a pair of BBcode tags for that.
And within their own ecosystem, they don't even need it. They've got the "NSFW app" instead, an over-one-decade-old, optional, simple-as-anything substring filter that automatically hides entire posts with all media and everything behind content warnings if it finds one of the entered keywords or hashtags.
So they can't understand Mastodon's commotion about content warnings, and Mastodon users can't understand why they don't add Mastodon-style content warnings.
And then there are all the things that were or are being debated on Mastodon and whether or not it should introduce them. Especially the second-wave Twitter refugees are often staunchly against them.
Full-text search and quote-tweets are being actively used on Twitter to track down and harass members of minorities who have fled to Mastodon. Of course, they don't want Mastodon to introduce either. That is, in the case of full-text search, Mastodon has found a solution, but one that doesn't really federate to the rest of the Fediverse.
Quotes and text formatting are seen as bad, too. Many don't know quotes because Twitter doesn't have them, and so they think quotes could be used as tools of harassment. And both are seen as making Mastodon feel less like Mastodon and more complicated.
Friendica and Hubzilla had all this before there was Mastodon, and (streams) inherited it from its long line of ancestors. Their users have gotten so used to having all this that they don't understand what the problems should be, also because they're so detached from Mastodon's culture. So they keep on using these features unashamedly, even around Mastodon users.
Some differences are rather simple. Take mentions, for example. Friendica has always used long names for mentions, as does its offspring. Mastodon users may find that freaky. Meanwhile, Friendica, Hubzilla or (streams) users may find Mastodon's mentions cryptic because they use the short name. But even they matter.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #FediverseCulture #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #CharacterLimit #CharacterLimits #500Characters #CW #CWs #ContentWarning #ContentWarnings #ContentWarningMeta #AltText #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Quotes #QuotePost #QuotePosts #QuoteBoost #QuoteBoost #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuotedShares #TextFormatting #FullTextSearch
🔍 Ever wondered how to make your document visually appealing? It's all about the details—Text, Paragraph, and Page Formatting! 🖌️✨
Uncover the secrets: https://basicscomp.com/document-formatting
#DocumentFormatting #MicrosoftWordTips #TextFormatting #ParagraphDesign #PageLayout #DocumentDesign #FormattingSkills #WordProcessing #OfficeHacks #ProfessionalDocs #TechTuesday #LearnWithBasicsComp #OfficeProductivity #DesignTips #VisualAppeal #TechSkills #WordMastery #FormatLikeAPro #CreateWithWord
I'm tempted to add the following preamble to all my posts and comments. This would answer a lot of questions right away and maybe leave nothing unclear.
Unfortunately, the target audience of this, Mastodon users, won't read it because it's too long. Not to mention that it'd require a boatload of content warnings and filter-triggering hashtags; see below.
#Fediverse #Mastodon #Friendica #Hubzilla #MastodonIsNotTheFediverse #NotOnlyMastodon #CharacterLimit #CharacterLimits #500Characters #TextFormatting #Quotes #QuoteTweets #QuoteToots #Long #LongPost #LongPosts #CWLong #CWLongPost #Meta #CWMeta #FediMeta #FediverseMeta #Fedisplaining #CWFedisplaining
Preamble
IMPORTANT: I am not on Mastodon. I am on Hubzilla. Hubzilla is not a Mastodon instance. Hubzilla is a wholly different project in the Fediverse. The Fediverse is not only Mastodon. The Fediverse has never been only Mastodon. And Hubzilla is not a fork of Mastodon either.
Mastodon was not even here first. The first was StatusNet from 2008 which later became GNU social. Then came Friendica in 2010. And Hubzilla is from 2015 and based on a project from 2012. Mastodon was launched in 2016. It was immediately federated with all three because it spoke a language that these three spoke, too. Except for GNU social, all are still federated with one another to this day. And this is normal, legal and fully intentional.
We aren't the intruders. Technically speaking, Mastodon is the intruder.
Hubzilla has features that Mastodon doesn't have. Hubzilla has an unlimited character count where Mastodon has a limit of 500 characters. Hubzilla can create various ways of text formatting such as bold type, italics, code blocks, lists or headlines; Mastodon can display them now, but it can't create them. Hubzilla can embed hyperlinks; Mastodon toots only support URLs in plain sight. Hubzilla can do both quotes and "quote-tweets", and it doesn't have to resort to screenshots for either. And Hubzilla always mentions users by their full name, not by their short name like Mastodon.
When Mastodon was launched with its self-imposed restrictions, Hubzilla had had all these features for almost four years already. Friendica had had the same features for almost six years already. And many of these features, including longer posts and text formatting, have been available on all other Fediverse projects since they were created.
Thus, I will use features that are not available on Mastodon even though Mastodon users could read this. I will not refrain from writing over 500 characters in one post, and I will not refrain from using text formatting just because Mastodon users aren't used to that.
We were here first. And we won't limit ourselves just because you're limited by the software you're using. We will continue to make use of features that you don't have. Deal with it.
Unfortunately, the target audience of this, Mastodon users, won't read it because it's too long. Not to mention that it'd require a boatload of content warnings and filter-triggering hashtags; see below.
#Fediverse #Mastodon #Friendica #Hubzilla #MastodonIsNotTheFediverse #NotOnlyMastodon #CharacterLimit #CharacterLimits #500Characters #TextFormatting #Quotes #QuoteTweets #QuoteToots #Long #LongPost #LongPosts #CWLong #CWLongPost #Meta #CWMeta #FediMeta #FediverseMeta #Fedisplaining #CWFedisplaining
@We Distribute First of all: I wouldn't make it only about #Mastodon. I wouldn't make it mainly about Mastodon either. #MastodonIsNotTheFediverse.
I wouldn't even make it look like it's only or mainly about Mastodon. I wouldn't give the impression that the #Fediverse is "Mastodon and some other stuff that was bolted onto Mastodon that nobody really gives a damn about, but someone told me I'd better mention that but, like, idfc..."
Also, I'd split it up, at least into various sub-topics.
First of alll, I'd present Fediverse projects, one by one, in chronological order instead of in order of size, importance or popularity. I'd with #StatusNet (2008). Or if I were to only include projects that at least understand #ActivityPub, I'd start with #Friendica (2010). I might skip projects that have been discontinued (Red Matrix, Osada, Zap...) or abandoned (Anfora, reel2bits...).
Also, I'd ask devs, creators who aren't necessarily the devs (#Diaspora*, Friendica and Hubzilla aren't maintained by their respective creators, for example) and experienced users. That's better than trying to only do my own research.
That is, I might include a mini-series with important dead projects, for example to show how #Hubzilla and #Streams came to exist. Okay, this example could be covered with one or two episodes.
Depending on the target audience, there could be a tech sub-topic which could cover protocols or other technology.
Another sub-topic would cover culture. Again, not with a focus solely on one specific project. For example, #ContentWarnings and the necessity therefor aren't only a Mastodon thing, especially since other projects cover them in different ways, unbeknownst to almost everyone on ActivityPub-based projects.
#FullTextSearch is a hot topic only on Mastodon which didn't even have it until a few days ago. On most other projects, it's absolutely normal to have it. #Quotes are similar: On Mastodon, they're still being debated. Almost everywhere else, they've been available forever, and even quoting Mastodon toots has been possible forever.
I'd also look at #AltText and #ImageDescriptions from a not-only-Mastodon point of view to break with the general perception that an #ImageDescription always goes into alt-text, full stop, because there's no room anywhere else.
A few episodes would be Mastodon-centric. One would be about the various stages of #TwitterMigration which pretty much exclusively led to Mastodon. Also, I might do an episode on how Mastodon newbies discover the Fediverse around #MastodonSocial by and by. And I'd certainly do one about how Mastodon users perceive and react upon the Fediverse outside of Mastodon and what comes in from there. Particularly those who either want the Fediverse to be Mastodon and only Mastodon or want everyone else out there to only do what can be done on Mastodon, i.e. forgo #TextFormatting and limit their posts to #500Characters, regardless of how many they could actually post.
The #Threadiverse in general and the #RedditMigration definitely deserve their own episode.
Another episode, later into the podcast, could cover cultural differences caused by how the various communities came into the Fediverse. There are the millions who have come over from #Twitter since late October 2022, and who have adapted parts of the old pre-Musk Twitter culture to Mastodon with little regard for anything else because they weren't even aware of there being anything else. There are the fresh arrivals who can't stop acting like they're still on #X, many of whom are pining for a #Bluesky invitation because it promises to be even closer to "literally Twitter without Musk". There is the "old guard" from Friendica and Hubzilla. There is the Threadiverse which basically continues to live the #Reddit culture in decentralised, non-corporate places now and tries to put up with hardly working moderation.
Last but not least, maybe a look at media coverage could be worth some episodes.
I wouldn't even make it look like it's only or mainly about Mastodon. I wouldn't give the impression that the #Fediverse is "Mastodon and some other stuff that was bolted onto Mastodon that nobody really gives a damn about, but someone told me I'd better mention that but, like, idfc..."
Also, I'd split it up, at least into various sub-topics.
First of alll, I'd present Fediverse projects, one by one, in chronological order instead of in order of size, importance or popularity. I'd with #StatusNet (2008). Or if I were to only include projects that at least understand #ActivityPub, I'd start with #Friendica (2010). I might skip projects that have been discontinued (Red Matrix, Osada, Zap...) or abandoned (Anfora, reel2bits...).
Also, I'd ask devs, creators who aren't necessarily the devs (#Diaspora*, Friendica and Hubzilla aren't maintained by their respective creators, for example) and experienced users. That's better than trying to only do my own research.
That is, I might include a mini-series with important dead projects, for example to show how #Hubzilla and #Streams came to exist. Okay, this example could be covered with one or two episodes.
Depending on the target audience, there could be a tech sub-topic which could cover protocols or other technology.
Another sub-topic would cover culture. Again, not with a focus solely on one specific project. For example, #ContentWarnings and the necessity therefor aren't only a Mastodon thing, especially since other projects cover them in different ways, unbeknownst to almost everyone on ActivityPub-based projects.
#FullTextSearch is a hot topic only on Mastodon which didn't even have it until a few days ago. On most other projects, it's absolutely normal to have it. #Quotes are similar: On Mastodon, they're still being debated. Almost everywhere else, they've been available forever, and even quoting Mastodon toots has been possible forever.
I'd also look at #AltText and #ImageDescriptions from a not-only-Mastodon point of view to break with the general perception that an #ImageDescription always goes into alt-text, full stop, because there's no room anywhere else.
A few episodes would be Mastodon-centric. One would be about the various stages of #TwitterMigration which pretty much exclusively led to Mastodon. Also, I might do an episode on how Mastodon newbies discover the Fediverse around #MastodonSocial by and by. And I'd certainly do one about how Mastodon users perceive and react upon the Fediverse outside of Mastodon and what comes in from there. Particularly those who either want the Fediverse to be Mastodon and only Mastodon or want everyone else out there to only do what can be done on Mastodon, i.e. forgo #TextFormatting and limit their posts to #500Characters, regardless of how many they could actually post.
The #Threadiverse in general and the #RedditMigration definitely deserve their own episode.
Another episode, later into the podcast, could cover cultural differences caused by how the various communities came into the Fediverse. There are the millions who have come over from #Twitter since late October 2022, and who have adapted parts of the old pre-Musk Twitter culture to Mastodon with little regard for anything else because they weren't even aware of there being anything else. There are the fresh arrivals who can't stop acting like they're still on #X, many of whom are pining for a #Bluesky invitation because it promises to be even closer to "literally Twitter without Musk". There is the "old guard" from Friendica and Hubzilla. There is the Threadiverse which basically continues to live the #Reddit culture in decentralised, non-corporate places now and tries to put up with hardly working moderation.
Last but not least, maybe a look at media coverage could be worth some episodes.
@marqle People can't find instances with over #500Characters because they don't know that #Firefish
And that's because everyone and their dog keeps talking about the #Fediverse as being only Mastodon.
Or maybe it was hard enough already to learn Mastodon's UI coming from Twitter, so they aren't ready to learn yet another UI.
Or they can't find an app named "Firefish" in their app store.
- exists
- is fully federated with #Mastodon
- gives you 3,000 characters by default or even more
- has had #FullTextSearch, #Quotes and #TextFormatting since its inception when it was still #CalcKey
- is easier to move to from Mastodon than another Mastodon instance
And that's because everyone and their dog keeps talking about the #Fediverse as being only Mastodon.
Or maybe it was hard enough already to learn Mastodon's UI coming from Twitter, so they aren't ready to learn yet another UI.
Or they can't find an app named "Firefish" in their app store.
@Mark Kraft Obviously, staying on #MastodonSocial won't let you write #LongPosts. Not unless the devs raise the default character count.
One option would be to ask around which #Mastodon instances allow for more than #500Characters and then move there.
An even better option would be to ditch Mastodon altogether and move elsewhere in the #Fediverse. Then you won't have to ask around for instances with a high character count, and you can stay connected with the same people. Remember that #MastodonIsNotTheFediverse.
#Firefish, for example, offers 3,000 characters by default. Some instances offer even more. And it offers #TextFormatting through #Markdown including formatting that Mastodon still can't display.
There are Fediverse projects with even higher character counts. But another advantage of Firefish is that it can import Mastodon accounts AFAIK which makes moving easier.
One option would be to ask around which #Mastodon instances allow for more than #500Characters and then move there.
An even better option would be to ditch Mastodon altogether and move elsewhere in the #Fediverse. Then you won't have to ask around for instances with a high character count, and you can stay connected with the same people. Remember that #MastodonIsNotTheFediverse.
#Firefish, for example, offers 3,000 characters by default. Some instances offer even more. And it offers #TextFormatting through #Markdown including formatting that Mastodon still can't display.
There are Fediverse projects with even higher character counts. But another advantage of Firefish is that it can import Mastodon accounts AFAIK which makes moving easier.
I'm halfway expecting #Mastodon users to demand a #ContentWarning for #TextFormatting.
Like, everyone outside of Mastodon must issue a #CW if they use
Like, everyone outside of Mastodon must issue a #CW if they use
- bold type
- italics
- a
code block - a bullet-point list
I'm wondering...
What if someone on #Mastodon started a campaign for defederating everything in the #Fediverse that isn't Mastodon?
Reasons:
If you actually find this a good idea, keep in mind that defederating an entire decentralised project is a game of Whack-a-Mole.
What if someone on #Mastodon started a campaign for defederating everything in the #Fediverse that isn't Mastodon?
Reasons:
- users of these projects keep shoving them into the faces of Mastodon users
- they think their projects are better than Mastodon
- they keep bragging about what their projects can do that Mastodon can't
- they spam Mastodon timelines with #LongPosts with over #500Characters
- they pester Mastodon users with their #RichText #TextFormatting
- they even use text formatting that Mastodon doesn't support, that must be intentional
- their mentions look weird because they're different from Mastodon mentions
- or they don't mention anyone at all when replying
- they can #FullTextSearch Mastodon already now
- they can make #QuoteToots of Mastodon toots, and nothing can stop them
- they rarely add alt-text
- they don't add content warnings because they don't have instance rules that demand so
- or they don't add content warnings because they claim that they'd allegedly got a better way of handling them, and the content warning field was actually for something else
- they never mark their images sensitive
- not a single one of their instances has signed the Mastodon Covenant
- you can't reach the admins of their instances
- or if you can, and you report a user for some of the stuff above, the admin claims the user hadn't done anything wrong
- it confuses and disturbs newbies when they find out that the Fediverse is not only Mastodon
- it makes the Fediverse too complicated if not everything is Mastodon
If you actually find this a good idea, keep in mind that defederating an entire decentralised project is a game of Whack-a-Mole.
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst