Thinking of adding a sort of #microblog element to my personal site (bcavello.com) because I am finding it intimidating to add new posts because I want to keep my posts section with a level of deep premeditation and polish. But I also have ideas that I often sit on FOR YEARS and it’s frustrating to not have written them down or shared them.
Ok! You can now follow OldInsuranceMaps.net here on the Fediverse: @oldinsurancemaps
This is a happy bonus of migrating the old blog and newsletter into #microblog .
Also woah this is complicated but I think I have things set up how I want them now 🤞 The main blog url is still https://blog.oldinsurancemaps.net, but now the newsletter is hosted there as well, and all content gets cross-posted to BlueSky and here.
@michael @haraldkliems @organicmaps @openstreetmap @mangroveReviews @sudoer777 @CoMaps @Dorothea
These are great #ideas, and also typical candidates to file an #ideation issue for at the #fediverse ideas repository, at..
https://codeberg.org/fediverse/fediverse-ideas/issues
As long-time #fedi advocate and #FOSS passionado I've seen countless times #people #come #together on nifty #ActivityPub ideas, only for it to fade out, and be forgotten again, until the next person throws it into ephemeral #microblog timeline voids.
Das FediVerse:
Da gibt es diejenigen, die "Fäden" aus drei, vier, fünf, zehn Beiträgen auf einmal veröffentlichen (ja, hallo mastodons 500 -Zeichen-MICROblogging-Limit, "Notizzettel", @crossgolf_rebel@moppels.bar sie liebevoll nennt),
und dann gibt es welche, die einfach Fedizens blockieren, weil diese halt MACROblogging-Plattformen, wie zB iceshrimp, misskey, friendica, hubzilla, WordPress, Ghost, uvm nutzen und darüber 3000, 5000, 10000 und mehr Zeichen schreiben.
Ich hätte ja gern eine Instanz, die sich 140.social nennt und - ihr erkennt es vielleicht am Namen - maximal 140 Zeichen erlaubt, ganz wie Twitter in dessen frühen Tagen 😉
#FediVerse #Microblog #Macroblog #WordPress #Ghost
Micro.blog launches new 'Studio' tier with video hosting
#HackerNews #Microblog #Studio #Video #Hosting #Indie #Alternative #YouTube
Our fediverse conversations are gonna have the context they have been missing!
This past June, I put together a write-up about two major approaches to backfilling conversations. The ability to properly backfill conversations means we will be able to make major inroads toward solving the feeling that the fediverse is quiet.
I, alongside several other members of the SWICG Forums and Threaded Discussions Task Force (ForumWG) have been working toward building implementor support for Conversational Contexts — the ability to explicitly classify a set of objects as belonging to a conversation, whether that be a topic, reply tree, or similar.
I am happy to report that we have made some wonderful inroads this past few months!
- jesseplusplus@mastodon.social has been working closely with the Mastodon team to allow software to backfill from Mastodon — this pull request has now been approved!
- I have been working with both nutomic@lemmy.ml and rimu@piefed.social to allow software to backfill from Lemmy and Piefed, respectively. (Lemmy PR, Piefed issue)
This marks a major milestone in the adoption of conversational contexts. With Mastodon on board backfill will be possible with the majority of the microblogiverse. With Lemmy and Piefed on board, backfill will be possible with the majority of the threadiverse.
Remember that pfefferle@mastodon.social was an early adopter of conversational contexts, and we have been able to backfill from WordPress blogs for quite awhile now (so that's the blogiverse too)
I for one, am eagerly awaiting the next version of all of these softwares!!
Our fediverse conversations are gonna have the context they have been missing!
This past June, I put together a write-up about two major approaches to backfilling conversations. The ability to properly backfill conversations means we will be able to make major inroads toward solving the feeling that the fediverse is quiet.
I, alongside several other members of the SWICG Forums and Threaded Discussions Task Force (ForumWG) have been working toward building implementor support for Conversational Contexts — the ability to explicitly classify a set of objects as belonging to a conversation, whether that be a topic, reply tree, or similar.
I am happy to report that we have made some wonderful inroads this past few months!
- jesseplusplus@mastodon.social has been working closely with the Mastodon team to allow software to backfill from Mastodon — this pull request has now been approved!
- I have been working with both nutomic@lemmy.ml and rimu@piefed.social to allow software to backfill from Lemmy and Piefed, respectively. (Lemmy PR, Piefed issue)
This marks a major milestone in the adoption of conversational contexts. With Mastodon on board backfill will be possible with the majority of the microblogiverse. With Lemmy and Piefed on board, backfill will be possible with the majority of the threadiverse.
Remember that pfefferle@mastodon.social was an early adopter of conversational contexts, and we have been able to backfill from WordPress blogs for quite awhile now (so that's the blogiverse too)
I for one, am eagerly awaiting the next version of all of these softwares!!