101010.pl

FlatPressSo you like <a href="https://fosstodon.org/tags/FlatPress" class="mention hashtag" rel="nofollow noopener" target="_blank">#FlatPress</a> as a blogging engine, but don't really warm up to <a href="https://fosstodon.org/tags/BBCode" class="mention hashtag" rel="nofollow noopener" target="_blank">#BBCode</a>? <a href="https://mastodon.social/@Fraenkiman" class="u-url mention" rel="nofollow noopener" target="_blank">@Fraenkiman</a> has got you covered! Check out his Parsedown plugin that brings <a href="https://fosstodon.org/tags/Markdown" class="mention hashtag" rel="nofollow noopener" target="_blank">#Markdown</a> to FlatPress: <a href="https://wiki.flatpress.org/res:plugins:parsedown" rel="nofollow noopener" translate="no" target="_blank">https://wiki.flatpress.org/res:plugins:parsedown</a> M⬇️ <a href="https://fosstodon.org/tags/foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#foss</a> <a href="https://fosstodon.org/tags/blogging" class="mention hashtag" rel="nofollow noopener" target="_blank">#blogging</a>

Cătă<a href="https://mastodon.social/users/taylorlorenz" class="u-url mention" rel="nofollow noopener" target="_blank">@taylorlorenz</a> don't be shy on testing waters on other ActivityPub based platforms as well. You get the same audience and the same people, while enjoying these platforms' particular features. Friendica, for example, has a DM inbox already, as well as Quote Posts.You can also add titles to your posts, as well as format your text using <a href="https://libranet.de/search?tag=markdown" class="mention hashtag" rel="nofollow noopener" target="_blank">#markdown</a> or <a href="https://libranet.de/search?tag=BBCode" class="mention hashtag" rel="nofollow noopener" target="_blank">#BBCode</a>, and many other features that haven't made their way into Mastodon just yet (or were already for years when Mastodon added them). Not to mention you can write texts as long as your heart desires, as there's no limit on them (and they appear just as long on Mastodon).A good and fairly popular Friendica server is venera.social

Jupiter Rowland@<a href="https://calckey.social/@maegul" rel="nofollow noopener" target="_blank">maegul</a> @<a href="https://calckey.social/@box464" rel="nofollow noopener" target="_blank">Jeff Sikes</a> @<a href="https://calckey.social/@kainoa" rel="nofollow noopener" target="_blank">Kainoa</a> @<a href="https://calckey.social/@atomicpoet" rel="nofollow noopener" target="_blank">Chris Trottier</a> This would have to happen on the server side. And this, in turn, would work the best if it happened directly on the instance servers, and if it was part of the #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener" target="_blank">Fediverse</a> projects themselves. We've seen what happens when you rely on a third party. It tends to lean towards something centralised, either because someone deliberately only designs a centralised service for it, e.g. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener" target="_blank">Mastodon</a> full-text search, or because nobody but the devs can be bothered to run an instance, e.g. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Guppe" rel="nofollow noopener" target="_blank">Guppe</a>. Also, decentralised third-party services will have to be connected to Fediverse instances by the admins manually because the admins will have to decide which instance to connect. Many admins won't take that step at all because they've stopped reading the manual the very moment their instance started working reasonably well, and so they don't even know that they have to connect to such a service. That said, the Fediverse already speaks one common formatting language, and that's #<a class="" href="https://hub.netzgemeinde.eu/search?tag=RichText" rel="nofollow noopener" target="_blank">RichText</a>. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CalcKey" rel="nofollow noopener" target="_blank">CalcKey</a> translates the #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Markdown" rel="nofollow noopener" target="_blank">Markdown</a> in out-going messages to Rich Text. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener" target="_blank">Hubzilla</a> translates the #<a class="" href="https://hub.netzgemeinde.eu/search?tag=BBcode" rel="nofollow noopener" target="_blank">BBcode</a> in out-going messages to Rich Text. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener" target="_blank">Streams</a> translates Markdown, BBcode and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=HTML" rel="nofollow noopener" target="_blank">HTML</a> to Rich Text. And so forth. Also, translation between message formats will remain half-useless as long as certain projects show a severe lack of capabilities of displaying messages, and this won't change anytime soon, if ever. Like it or not, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener" target="_blank">Mastodon</a> fans, but Mastodon is the worst offender. It can't have more than four images in one post, and it can't embed images within the text. All stuff that has been possible on projects older than Mastodon even before there was Mastodon. On #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener" target="_blank">Hubzilla</a> (and not only there, but just to take one example), I can design any regular message like a blog post: <pre><code>Text block 1 Image 1 Text block 2 Image 2 Text block 3 Image 3 Text block 4 Image 4 Text block 5 Image 5 Text block 6 Image 6 Text block 7 Image 7 Text block 8 Image 8 Text block 9</code></pre> This is perfectly normal. And this is perfectly legit. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener" target="_blank">Friendica</a>, Hubzilla and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener" target="_blank">Streams</a> were deliberately designed to make this possible. And while Hubzilla has an optional extra functionality for long-form articles, Friendica and (streams) only have this one way of long-form posting. So, again, this is normal and legit and intentional. On Mastodon, however, the very same post looks like this: <pre><code>Text block 1 Text block 2 Text block 3 Text block 4 Text block 5 Text block 6 Text block 7 Text block 8 Text block 9 Image 8 | Image 7 Image 6 | Image 5</code></pre> The images are ripped out of their context, reversed in their order, and only four even make it into what Mastodon displays. The only thing a "translator" could possibly do here is put the images in the correct order. Still, only four would make it onto Mastodon timelines due to Mastodon's limitations, only that it'll be the first four instead of the last four. And also due to Mastodon's limitations, they will still end up after the end of the post instead of embedded between text blocks where they belong. In the opposite direction, from Mastodon to Hubzilla, a "translator" could be a bit more useful. Currently, when a Mastodon toot with multiple images appears on Hubzilla, the images are put ahead of the text and in reverse order. What the "translator" could do (unless Hubzilla introduces that first) is embed the images at the end of the post in "reverse reverse" order. I'd suggest to also resize them (non-destructively; Hubzilla does that by default with its own images) so that four of them can be shown in a 2x2 arrangement just like on Mastodon, but on Hubzilla, that would cost them the alt-text.

Jupiter Rowland@<a class="" href="https://c.im/@LucyWildboots" rel="nofollow noopener" target="_blank">LucyWildboots 🏳️‍🌈</a> @<a class="" href="https://libranet.de/profile/clacke" rel="nofollow noopener" target="_blank">clacke post fosdem 🇸🇪🇭🇰💙💛</a> @<a class="" href="https://mastodon.social/@atomicpoet" rel="nofollow noopener" target="_blank">Chris Trottier</a> @<a class="" href="https://mas.to/@MetalSamurai" rel="nofollow noopener" target="_blank">Kevin Davidson</a> @<a class="" href="https://thegoatery.dyndns.org/profile/goatsarah" rel="nofollow noopener" target="_blank">Sarah Brown</a> @<a class="" href="https://mastodon.online/@IceCubesApp" rel="nofollow noopener" target="_blank">IceCubesApp</a> @<a class="" href="https://mastodon.social/@MonaApp" rel="nofollow noopener" target="_blank">Mona app</a> I'm not sure if it's wise to give mobile apps for the #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener" target="_blank">Fediverse</a> direct access to all features of all Fediverse projects. At first glance, it sounds convenient. You install one app, and you can do everything with it on every project. But imagine some poor sap who has just migrated from Twitter to Mastodon, who loads a Fediverse app from the app store, and who ends up with an outright monster of an app with a UI cluttered with greyed-out options and menu items. Why is it so cluttered? Because the devs also included full #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener" target="_blank">Hubzilla</a> support. And I mean full support for all features of Hubzilla channels with all apps activated, including full access to all account and channel options and settings, including a post editor with buttons for the whole extent of Hubzilla's bored-up #<a class="" href="https://hub.netzgemeinde.eu/search?tag=BBcode" rel="nofollow noopener" target="_blank">BBcode</a> implementation, including article, webpage and wiki page editors (which partly support #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Markdown" rel="nofollow noopener" target="_blank">Markdown</a> and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=HTML" rel="nofollow noopener" target="_blank">HTML</a> on top of BBcode), including connecting your phone to the #<a class="" href="https://hub.netzgemeinde.eu/search?tag=WebDAV" rel="nofollow noopener" target="_blank">WebDAV</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CalDAV" rel="nofollow noopener" target="_blank">CalDAV</a> and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CardDAV" rel="nofollow noopener" target="_blank">CardDAV</a> servers included in your channel, including even support for creating and managing nomadic clones. And Hubzilla is something that's even cumbersome to handle in a desktop browser. Now imagine all this packed into a mobile app. Such an all-in-one app would also confuse people to have access to multiple separate calendar systems through the app. One is a public calendar as available on #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener" target="_blank">Friendica</a>, Hubzilla and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener" target="_blank">Streams</a>. The second one is a CalDAV-equipped engine for private calendars which Hubzilla has in addition to the public calendar, and which in itself supports multiple calendars, not to mention calendars on other channels which gave you write access. The third one is a collaborative calendar as offered by #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mobilizon" rel="nofollow noopener" target="_blank">Mobilizon</a>. Oh, and it'd of course support #<a class="" href="https://hub.netzgemeinde.eu/search?tag=OwnCast" rel="nofollow noopener" target="_blank">OwnCast</a> as well as the live stream feature included in #<a class="" href="https://hub.netzgemeinde.eu/search?tag=PeerTube" rel="nofollow noopener" target="_blank">PeerTube</a> to the point of enabling you to live-stream through one of these projects how you use the self-same app to handle another Fediverse project. Last but not least, every update on every Fediverse project that comes with new or changed features will require an upgrade for the app.

tallship<a class="u-url mention" href="https://nerdculture.de/@gordoooo_z" rel="nofollow noopener" target="_blank">@gordoooo_z</a> <a class="u-url mention" href="https://fedi.pawlicker.com/users/PhenomX6" rel="nofollow noopener" target="_blank">@PhenomX6</a> <a class="u-url mention" href="https://sauropods.win/@futurebird" rel="nofollow noopener" target="_blank">@futurebird</a> <a class="u-url mention" href="https://the9thcircle.club/@ink8" rel="nofollow noopener" target="_blank">@ink8</a> Whatever Eugen decides at this point it’s irrelevant. He’s pretty much lost his grip over holding the Fediverse brand as secondary to the notion of a fantasy “mastodon network” when he gave that Time Magazine interview two months ago in which the word “Fediverse” appeared not one single time - that caused enormous, untold damages including confusion that remains in the news media and disenfranchisement of large swaths of developers and users alike on not just other platforms, but mastodon instances themselves.There’s really no such thing as toots anymore, Eugen himself refers to “Posts” and “Quote Posts”, and the submit button in mastodon now says “publish”. The reason <a class="hashtag" href="https://gleasonator.com/tag/misskey" rel="nofollow noopener" target="_blank">#Misskey</a> calls them “notes” is because that’s what they are actually called in <a class="hashtag" href="https://gleasonator.com/tag/activitypub" rel="nofollow noopener" target="_blank">#ActivityPub</a> - there are also other types, that other platforms use as well, including “article”, although, instances like <a class="hashtag" href="https://gleasonator.com/tag/qoto" rel="nofollow noopener" target="_blank">#qoto</a> have set the character count for notes at 65535 🙂It’s been covered in this thread already that Quote Posts are simply beyond the control of mastodon devs, Eugen’s edicts, or local mastodon users or admins, because most other platforms support it and there isn’t anything <a class="hashtag" href="https://gleasonator.com/tag/mastopub" rel="nofollow noopener" target="_blank">#mastopub</a> can do about it. In Misskey, users can disallow it, but that only affects other local users, so it’s s moot point (except for silo instances).There are very few Fediverse platforms that aren’t taking advantage of most things that are possible, for example, <a class="hashtag" href="https://gleasonator.com/tag/soapbox" rel="nofollow noopener" target="_blank">#Soapbox</a> now has federated events, and introduced custom emoji reactions like Misskey has, and live chat - Misskey’s traditionally led the way with these federating features with <a class="hashtag" href="https://gleasonator.com/tag/calckey" rel="nofollow noopener" target="_blank">#Calckey</a> going even further.Some platforms however, intentionally incorporate a leaner set of features; <a class="hashtag" href="https://gleasonator.com/tag/smithereen" rel="nofollow noopener" target="_blank">#Smithereen</a> is one example, it doesn’t even sccomodate boosts, which harkens back to <a class="hashtag" href="https://gleasonator.com/tag/myspace" rel="nofollow noopener" target="_blank">#Myspace</a>, <a class="hashtag" href="https://gleasonator.com/tag/vkontakte" rel="nofollow noopener" target="_blank">#VKontakte</a> (aka, “VK” - not sure I spelled that right), and very early <a class="hashtag" href="https://gleasonator.com/tag/faceplant" rel="nofollow noopener" target="_blank">#Faceplant</a> days. <a class="hashtag" href="https://gleasonator.com/tag/epicyon" rel="nofollow noopener" target="_blank">#Epicyon</a> has anti-silo capabilities baked in.<a class="hashtag" href="https://gleasonator.com/tag/mitra" rel="nofollow noopener" target="_blank">#Mitra</a> has <a class="hashtag" href="https://gleasonator.com/tag/substack" rel="nofollow noopener" target="_blank">#Substack</a> style subscriptions at it’s core. Anyone can subscribe remotely from any Fediverse server instance where the user can receive DMs - and in congruence with privacy concerns that are typically expected for Fediverse implementations, it’s based on <a class="hashtag" href="https://gleasonator.com/tag/monero" rel="nofollow noopener" target="_blank">#Monero</a> (XMR).Most platforms also support <a class="hashtag" href="https://gleasonator.com/tag/markdown" rel="nofollow noopener" target="_blank">#Markdown</a>, with Cakckey being perhaps supporting the greatest superset IIRC, including <a class="hashtag" href="https://gleasonator.com/tag/latex" rel="nofollow noopener" target="_blank">#LaTEX</a>, and <a class="hashtag" href="https://gleasonator.com/tag/friendica" rel="nofollow noopener" target="_blank">#Friendica</a>, being much older than msstodon, has continued to evolve over the past decade and still has support for <a class="hashtag" href="https://gleasonator.com/tag/bbcode" rel="nofollow noopener" target="_blank">#BBCode</a> too, and direct links for uploading images for those who prefer to.I didn’t see any mention of Markdown support when I bothered to look at the mastopub roadmap, yet even on that platform, Quote Posts are all throughout the stream and people boost and reply to them as the time - and, as mentioned earlier, anyone can create a post, simply pasting the link from someone else’s post, and then boost that… Voila! Local <a class="hashtag" href="https://gleasonator.com/tag/quote_post" rel="nofollow noopener" target="_blank">#Quote_Post</a>.mastodon was successful in its arrogance of leveraging some pretty graphics and welcoming verbiage into a brand that Eugen weaponized against virtually all other Fediverse platforms, and now, with all of the fine forks like <a class="hashtag" href="https://gleasonator.com/tag/hometown" rel="nofollow noopener" target="_blank">#Hometown</a> and several newcomers, we’ll soon be seeing hardforking as a result of that hostility.But not just forks, funding and ambitious development as evidenced by existing and emerging platforms like <a class="hashtag" href="https://gleasonator.com/tag/cloudflare" rel="nofollow noopener" target="_blank">#Cloudflare</a>’s <a class="hashtag" href="https://gleasonator.com/tag/wildebeest" rel="nofollow noopener" target="_blank">#Wildebeest</a>, Tumbler, and the very unique, <a class="hashtag" href="https://gleasonator.com/tag/django" rel="nofollow noopener" target="_blank">#Django</a> based Takahē Fediverse server that I wrote about here:<a href="https://tallship.writeas.com/takahe-a-new-fediverse-paradigm" rel="nofollow noopener" target="_blank">https://tallship.writeas.com/takahe-a-new-fediverse-paradigm</a>Average people are already migrating in larger numbers everyday away from the archaic mastodonian resource hog to other, more capable and promising (and friendlier) platforms elsewhere in the Fediverse that have integrated and fully support <a class="hashtag" href="https://gleasonator.com/tag/masto_migration" rel="nofollow noopener" target="_blank">#masto_migration</a>, and even ones that don’t (yet) haver that feature.Unlike other dinosaurs and the eponymous mammal for which Eugen chose the namesake of his <a class="hashtag" href="https://gleasonator.com/tag/tootsuite" rel="nofollow noopener" target="_blank">#TootSuite</a> product, we shouldn’t expect extinction for his platform, but the apathy and indifference levels are rising, as is the enmity in many sectors of the community for what others perceive as a betrayal (or sellout), and that kind of self-inflicted damage is often difficult to mitigate, with waves of disenchantment reverberating get into the future… Just look at what happened to <a class="hashtag" href="https://gleasonator.com/tag/sourceforge" rel="nofollow noopener" target="_blank">#SourceForge</a> - it still technically exists, but never recovered after the community betrayal it committed years ago.And finally, there’s a irony so obvious that’s it’s not even plausible to deny… Eugen subverted the very rudimentary principal that the Fediverse network is ideologically predicated upon - <a class="hashtag" href="https://gleasonator.com/tag/desoc" rel="nofollow noopener" target="_blank">#DeSoc</a>… There’s no question that his goals shifted to that if building a silo for himself, at least to some great degree. Very sad.An interesting thing about condescending others, you find yourself alone and isolated in an otherwise vibrant, busy world.<a class="hashtag" href="https://gleasonator.com/tag/tallship" rel="nofollow noopener" target="_blank">#tallship</a> <a class="hashtag" href="https://gleasonator.com/tag/takahe" rel="nofollow noopener" target="_blank">#Takahe</a> <a class="hashtag" href="https://gleasonator.com/tag/activitypub" rel="nofollow noopener" target="_blank">#ActivityPub</a> <a class="hashtag" href="https://gleasonator.com/tag/privacy" rel="nofollow noopener" target="_blank">#privacy</a> <a class="hashtag" href="https://gleasonator.com/tag/community_values" rel="nofollow noopener" target="_blank">#community_values</a> <a class="hashtag" href="https://gleasonator.com/tag/foss" rel="nofollow noopener" target="_blank">#FOSS</a>⛵.

Jupiter Rowland@<a class="" href="https://embers.social/profile/ada" rel="nofollow noopener" target="_blank">Ada</a> @<a class="" href="https://social.defcon42.net/@mirko" rel="nofollow noopener" target="_blank">defcon42/Mirko</a> @<a class="" href="https://thias.hellqui.st/users/m" rel="nofollow noopener" target="_blank">m@thias.hellqui.st</a> To me, it sounds more like some #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener" target="_blank">Mastodon</a> users, especially those who came in through the #<a class="" href="https://hub.netzgemeinde.eu/search?tag=TwitterMigration" rel="nofollow noopener" target="_blank">TwitterMigration</a>, actually can't stand there being something else in the #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener" target="_blank">Fediverse</a> than their beloved Mastodon. When they caught their first glimpse of the Fediverse beyond Mastodon, they reacted much like the people of Krikkit when they caught their first glimpse of the universe beyond Krikkit: "It has to go!" They make themselves and each other believe that Mastodon is superior to any other Fediverse project in just about any regard imaginable while apparently completely refusing to learn about those other projects. They're supported in their belief by mass media only ever writing about Mastodon and the number of Mastodon users. However, mass media only write about Mastodon because they simply don't know a thing about the rest of the Fediverse, and they didn't know a thing about Mastodon until the #<a class="" href="https://hub.netzgemeinde.eu/search?tag=TwitterTakeover" rel="nofollow noopener" target="_blank">TwitterTakeover</a> had actually happened, and the second wave of former #<a class="" href="https://hub.netzgemeinde.eu/search?tag=birbsite" rel="nofollow noopener" target="_blank">birbsite</a> users had come flooding into Mastodon in such numbers that it was impossible to ignore even for those who act as if #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FLOSS" rel="nofollow noopener" target="_blank">FLOSS</a> doesn't exist. As for the numbers of Mastodon users, they're so high because I guess more than 90% of all Mastodon users still don't know that the Fediverse is not only Mastodon, because they have never heard of anything else in the Fediverse. Mastodon was pretty much the only Fediverse project advertised on #<a class="" href="https://hub.netzgemeinde.eu/search?tag=BirbSocial" rel="nofollow noopener" target="_blank">BirbSocial</a> when this was still possible. There are various reasons why Mastodon users don't spread across the Fediverse in masses. None of it is because Mastodon is superior to everything else because, truth be told, it isn't. I'll come to this later. One reason is, again, that the vast majority of them still don't know anything else. Another one is because it was hard enough to get used to Mastodon after years of using #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Twitter" rel="nofollow noopener" target="_blank">Twitter</a>, and they don't want to get used to yet another platform. And another one is that it's hard to move from Mastodon to something else and take your account or at least your connections with you. Another reason may be because people don't need anything beyond microblogging, and that's what Mastodon does. Now, sorry for all those of you who fight tooth and claw to defend Mastodon against the competition, but #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Akkoma" rel="nofollow noopener" target="_blank">Akkoma</a> does microblogging, too. With extra features beyond Mastodon, some of which Mastodon users have been pestering Eugen Rochko to include in Mastodon for ages (e.g. "quote retweet"). All while being more lightweight and requiring fewer server resources than Mastodon. Oh, and it federates with Mastodon. Other Fediverse projects aren't even competition for Mastodon because they specialise in something else. @<a class="" href="https://pixelfed.social/pixelfed" rel="nofollow noopener" target="_blank">Pixelfed</a> specialises in posting pictures, much like #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Instagram" rel="nofollow noopener" target="_blank">Instagram</a>. @<a class="" href="https://framapiaf.org/users/peertube" rel="nofollow noopener" target="_blank">PeerTube</a> specialises in video upload and streaming, not too dissimilarly from #<a class="" href="https://hub.netzgemeinde.eu/search?tag=YouTube" rel="nofollow noopener" target="_blank">YouTube</a>. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Plume" rel="nofollow noopener" target="_blank">Plume</a> and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=WriteFreely" rel="nofollow noopener" target="_blank">WriteFreely</a> specialise in distraction-free traditional blogging, much like #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Medium" rel="nofollow noopener" target="_blank">Medium</a>. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Lemmy" rel="nofollow noopener" target="_blank">Lemmy</a> specialises in groups and posting and discussing news, much like #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Reddit" rel="nofollow noopener" target="_blank">Reddit</a> or #<a class="" href="https://hub.netzgemeinde.eu/search?tag=HackerNews" rel="nofollow noopener" target="_blank">HackerNews</a>. You can't claim that Mastodon is better at each of these things than these platforms. And then there are the jacks-of-all-trades which are usually filed under either "macroblogging" or "like #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Facebook" rel="nofollow noopener" target="_blank">Facebook</a> ". They weren't launched to have something that goes beyond Mastodon because their history reaches far back before Mastodon. Mastodon was launched in 2016 (and not 2022 like many believe). #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener" target="_blank">Friendica</a> was launched in early 2010, even before the crowdfunding campaign for the development of #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Diaspora" rel="nofollow noopener" target="_blank">Diaspora</a> started. And in that early stage, Friendica, then still named #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mistpark" rel="nofollow noopener" target="_blank">Mistpark</a>, was vastly more powerful than Diaspora* ever got and also vastly more powerful than Mastodon 13 years later. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener" target="_blank">Hubzilla</a>, created by the same man as Friendica, is the most extreme one of them all. For starters, it eliminates the need for multiple accounts by having multiple independent channels with separate identities on the same account. Each channel can have multiple profiles like on Friendica so you can present your channel differently to individual contacts or groups of them and differently again to the general public. It can do micro- and macroblogging with 50,000 or more characters and just about everything that can be done with #<a class="" href="https://hub.netzgemeinde.eu/search?tag=BBcode" rel="nofollow noopener" target="_blank">BBcode</a> (italics, bold type, underline, lists with bullet points or numbers, quotes, <code>code blocks</code>), and you can embed as many pictures as you want in your posts where you want them instead of them automatically being attached to the end of the post. Group handling in Hubzilla is much easier than list handling in Mastodon. You never have to type the name of a contact to find them. You can edit contacts and add them to groups or remove them, and you can edit groups and add or remove contacts, all with a few mouse clicks. And while Mastodon shows a maximum of four lists on the main page, Hubzilla will give you easy access to all your groups. On top of that, you can have <ul><li>very fine-grained access rights control with pre-definable contact roles </li><li>forums (just like Friendica, Hubzilla has #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Guppe" rel="nofollow noopener" target="_blank">Guppe</a> built in) </li><li>more elegant macroblogging with articles which, in addition to BBcode, support #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Markdown" rel="nofollow noopener" target="_blank">Markdown</a> </li><li>simple webpages (or not so simple if you're the admin of a hub, and you can expand it further) </li><li>wikis (I'm not even kidding) </li><li>a public calendar </li><li>a virtually unlimited number of private calendars with #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CalDAV" rel="nofollow noopener" target="_blank">CalDAV</a> connection </li><li>a virtually unlimited number of address books with #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CardDAV" rel="nofollow noopener" target="_blank">CardDAV</a> connection </li><li>a file server with #<a class="" href="https://hub.netzgemeinde.eu/search?tag=WebDAV" rel="nofollow noopener" target="_blank">WebDAV</a> connection with its own access rights management which also ties in with the Photos and optional Gallery app (Mastodon drops your pictures somewhere, Hubzilla lets you upload them to your personal cloud space where you can access them whenever you want)</li></ul> All with one run-of-the-mill Hubzilla account. And once per channel, separately. And as if that wasn't enough, Hubzilla introduced the #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Zot" rel="nofollow noopener" target="_blank">Zot</a> protocol and with it a concept named #<a class="" href="https://hub.netzgemeinde.eu/search?tag=NomadicIdentity" rel="nofollow noopener" target="_blank">NomadicIdentity</a>. Mastodon and Friendica let you have multiple accounts, even on separate instances. They also support migration from one account to another, and unlike Mastodon, Friendica lets you take all your content with you. Hubzilla (and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener" target="_blank">Streams</a>, the successor of its slimmed-down successor, still created by the same guy) goes even further: Not only can you easily move from one hub to another, you can have channels on multiple hubs and automatically keep them fully in sync! If one hub goes down, it doesn't matter because you've got everything on all your other accounts. Last but not least, both Friendica and Hubzilla federate with almost everything that moves, even far beyond the #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ActivityPub" rel="nofollow noopener" target="_blank">ActivityPub</a> Fediverse. This could be Diaspora*, this could be #<a class="" href="https://hub.netzgemeinde.eu/search?tag=GNUsocial" rel="nofollow noopener" target="_blank">GNUsocial</a>, this could be #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Wordpress" rel="nofollow noopener" target="_blank">Wordpress</a> blogs with or without the ActivityPub add-on, this could be RSS feeds (and they both generate feeds themselves, so this is bidirectional, too), this could even be Twitter until the API is shuttered. Friendica even used to federate with Facebook until Facebook put rocks in the way; this is the only connector that Hubzilla didn't take over. The obvious downside is that for someone who just came in from the #<a class="" href="https://hub.netzgemeinde.eu/search?tag=birdcage" rel="nofollow noopener" target="_blank">birdcage</a>, all this is utter overkill. In fact, people who are used to Mastodon may find Friendica borderline unusuable due to its many features. And Hubzilla is so infamous for its own clumsy UI capitulating before its sheer power that even Friendica users find it hard to use, fresh converts from Twitter to Mastodon even more so. Some design decisions may be hard to understand for outsiders. Converts from other Fediverse projects to Hubzilla regularly fail at something as seemingly similar as connecting to users on other ActivityPub-based projects until you tell them that ActivityPub is an optional app on Hubzilla that has to be activated first because Hubzilla concentrates on Zot with its Nomadic Identity. Also, just because these projects offer so much power, that doesn't mean that everyone needs it. If you do, it can be convenient to have it all under one login. But if all you're looking for is a bit of microblogging and online socialising, you don't need to drag a CMS and a full-blown cloud server with all bells and whistles along with you that just clutter up the UI. In that case, projects like Mastodon and Akkoma win because they're more approachable. And while Friendica, Hubzilla & Co. can do threaded discussions and even have something like forums, Lemmy can do this more elegantly because it specialises in it. While you can use Hubzilla's private calendar feature for event planning, it's easier to do the same with #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mobilizon" rel="nofollow noopener" target="_blank">Mobilizon</a> which, again, specialises in it. Or you can host podcasts on Friendica, Hubzilla & Co, but you can host them better on #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Funkwhale" rel="nofollow noopener" target="_blank">Funkwhale</a> and even better on #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Castopod" rel="nofollow noopener" target="_blank">Castopod</a>. Wanting the Fediverse to be only Mastodon hinders development, namely the development of new projects within the Fediverse that may be able to do all-new things that we haven't seen in the Fediverse yet. Things that, sorry to say again, you'll never be able to do with Mastodon. P.S.: For extra kicks, don't just read this on Mastodon. Open my original post; there you can see what Hubzilla is capable of, and what Mastodon strips away.

*banned 4 MarkDown love*<a href="https://kafuka.me/@emuz" class="u-url mention" rel="nofollow noopener" target="_blank">@emuz</a> I was really curious about the name. It seemed similar to some funny English words. <a href="https://gameliberty.club/@realcaseyrollins" class="u-url mention" rel="nofollow noopener" target="_blank">@realcaseyrollins</a> , think about another RealCaseyRollins @ KamFukWi.me ? LOL. 😜 Sorry for the little joke, it's good to know the origin of the name, and that is not a collapsed funny one like this above.I like your choice of GlitchSocial, it's a nice platform, I enjoy it in a couple other instances where I have accounts. I would suggest you could promote the awesome support of Rich Text options in GS -- <a href="https://qoto.org/tags/MarkDown" class="mention hashtag" rel="nofollow noopener" target="_blank">#MarkDown</a> and <a href="https://qoto.org/tags/BBcode" class="mention hashtag" rel="nofollow noopener" target="_blank">#BBcode</a> right off the box, fully supported. For someone in <a href="https://qoto.org/tags/Publishing" class="mention hashtag" rel="nofollow noopener" target="_blank">#Publishing</a>, that is Great -- and I do use it to prepare my Blog Release posts with some of the possible touches MD enables. Header size, bold and italic; quote blocks, code tag with pretty contrasting text.Succes with your instance, Tom! Thanks for offering an awesome service that takes effort, dedication and expense; many people don't even realize how much.

Nobody [LinuxWalt (@lnxw48a1)]@<a href="https://nulled.red/users/amic" class="h-card mention" rel="nofollow noopener" target="_blank">amic</a> No. GS has plugins that add support for #<a href="https://nu.federati.net/tag/textile" rel="nofollow noopener" target="_blank">Textile</a> and #<a href="https://nu.federati.net/tag/markdown" rel="nofollow noopener" target="_blank">Markdown</a>, but not #<a href="https://nu.federati.net/tag/bbcode" rel="nofollow noopener" target="_blank">BBCode</a> (yet).

(wakest's old account)so now that features are really starting to diverge between different <a href="https://mastodon.social/tags/activitypub" class="mention hashtag" rel="nofollow noopener" target="_blank">#activitypub</a> sites we really need a way to come together and decide how these little bits can fit together. for instance <a href="https://mastodon.social/tags/misskey" class="mention hashtag" rel="nofollow noopener" target="_blank">#misskey</a> has a ton of features they have implemented recently like polls and reactions other then 'star',the masto fork now.kibousoft.co.jp has implemented <a href="https://mastodon.social/tags/bbcode" class="mention hashtag" rel="nofollow noopener" target="_blank">#bbcode</a> in their instance and it looked like misskey is doing something similar with <a href="https://misskey.xyz/notes/5b7c8643894f8100445b1f28" rel="nofollow noopener" target="_blank">https://misskey.xyz/notes/5b7c8643894f8100445b1f28</a>

(wakest's old account)<a href="https://now.kibousoft.co.jp/@fb10155987946582408" class="u-url mention" rel="nofollow noopener" target="_blank">@fb10155987946582408</a> it supports this <a href="https://mastodon.social/tags/bbcode" class="mention hashtag" rel="nofollow noopener" target="_blank">#bbcode</a> [spin]FEDIVERSE[/spin] [pulse]FEDIVERSE[/pulse] [large=2x]FEDIVERSE[/large] [flip=vertical]FEDIVERSE[/flip] [flip=horizontal]FEDIVERSE[/flip] [b]FEDIVERSE[/b] [i]FEDIVERSE[/i] [u]FEDIVERSE[/u] [s]FEDIVERSE[/s] [size=5]FEDIVERSE[/size] [color=red]FEDIVERSE[/color] [colorhex=A55A4A]FEDIVERSE[/colorhex] [code]FEDIVERSE[/code] [quote]FEDIVERSE[/quote]

Recent searches

Search options

Administered by:

Server stats:

#bbcode