Show Navigation
Notices tagged with federated
-
I felt the #earthquake here in #SanFrancisco. A single quick sharp jolt with rapid decay, duration less than 2s, meaning it was relatively nearby and small in magnitude
I was about to say, perhaps #earthquakes are the last use-case for #Twitter because yes I reflexively checked it and did see posts about it from folks, including a few friends.
Then I checked https://indieweb.social/tags/earthquake and it has plenty of recent #fediverse posts about the earthquake, several @sfba.social.
Feels like something big has shifted.
The #federated #IndieWeb has replaced another #socialMedia silo use-case.
This is post 7 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/027/t1/indieweb-ideals-systems-swappable
→ 🔮
Post glossary:
silo
https://indieweb.org/silo
social media
https://indieweb.org/social_media
use-case
https://indieweb.org/use_case
-
Great article on #POSSE by David Pierce (@davidpierce@mastodon.social @pierce) @Verge:
https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon
Several key points of POSSE explained in the article:
First, post on your own site:
“In a POSSE world, everybody owns a domain name, and everybody has a blog. (… a place on the internet where you post your stuff and others consume it.)”
Second, syndicate elsewhere, appropriately for each destination:
“Then, your long blog post might be broken into chunks and posted as a thread on X and Mastodon and Threads. The whole thing might go to your Medium page and your Tumblr and your LinkedIn profile, too. If you post a photo, it might go straight to Instagram, and a vertical video would whoosh straight to TikTok, Reels, and Shorts. Your post appears natively on all of those platforms,”
You can use Bridgy Publish (https://brid.gy/) to POSSE to many destinations, and Bridgy Fed (https://fed.brid.gy/) to #federate to #Mastodon and other #fediverse destinations, directly from your site instead of posting a copy on yet another account on yet another server.
Third, and this is a key piece that distinguishes proper POSSE setups, with original post perma(short)links back to your posts on your domain:
“typically with some kind of link back to your blog.”
All copies link to (your) home.
"And your blog becomes the hub for everything, your main home on the internet."
You have power over your domain (name), not outside silos.
David embedded a screenshot of one of my posts, a reply post:
in which I posted a reply *on my own site*¹ to @Zeldman.com’s tweet (itself a reply to a POSSE copy of one of my posts), and POSSEd my reply to Twitter so it would thread with his reply.
This illustrates another important detail of a proper POSSE setup:
Fourth, post *replies* and other responses from your own site, whether to other #IndieWeb sites, or to others’s silo posts (tweets etc.).
Own your data means owning your replies as well.
David also noted several challenges and good questions about POSSE. Some of these have answers & established practices, others are areas of exploration. E.g.
"The first is the social side of social media: what do you do with all the likes, replies, comments, and everything else that comes with your posts?"
The short answer is #backfeed: https://indieweb.org/backfeed
Backfeed is a concept I first wrote about as “reverse syndication”².
As you syndicate your posts out to #socialMedia silos, you reverse syndicate any responses there back to your original post.
Your site can do this with a service like #Bridgy, which uses the #Webmention standard to forward such silo responses back to your site, and #BridgyFed which does same for responses from Mastodon to your #federated posts.
David asked many other questions, which are deserving of their own posts to help answer, so I’ll leave you with just one more:
"The most immediate question, though, is simply how to build a POSSE system that works."
The short answer is: just start³.
Even if you have to do it manually (until it hurts), even if you have to edit your posts on a static GitHub site (behind your domain name of course), and then copy & paste to your silo(s) of choice, just start.
By practicing POSSE, even manually, you will learn what aspects of POSSE & backfeed matter the most to you, what aspects actually involve reaching & responding to friends and others you care about.
By doing so you will naturally focus on setting up & making what you need, and you too can join the future of web publishing, today.
Questions? Join us in the chat: https://chat.indieweb.org/ (also on Discord, IRC, and Slack⁴)
This is day 46 of #100DaysOfIndieWeb. #100Days
← Day 45: https://tantek.com/2023/289/t1/bridgyfed-webmention-like-fediverse
→ 🔮
Post glossary:
backfeed / reverse syndication
https://indieweb.org/backfeed
Bridgy
https://brid.gy/
make what you need
https://indieweb.org/make_what_you_need
manual (until it hurts)
https://indieweb.org/manual_until_it_hurts
original post link
https://indieweb.org/original_post_link
own your data
https://indieweb.org/own_your_data
own your replies
https://indieweb.org/own_your_replies
permalink
https://indieweb.org/permalink
permashortlink
https://indieweb.org/permashortlink
POSSE
https://indieweb.org/POSSE
silo
https://indieweb.org/silo
social media
https://indieweb.org/social_media
static site
https://indieweb.org/static_site
start
https://indieweb.org/start
Webmention
https://indieweb.org/Webmention
¹ https://tantek.com/2023/253/t2/
² https://tantek.com/2010/034/t2/diso-2-personal-domains-shortener-hatom-push-relmeauth
³ https://tantek.com/2023/001/t1/own-your-notes
⁴ https://indieweb.org/discuss
-
Implemented liking/favoriting of #Mastodon posts via Bridgy Fed on my site! (Actually of any post on any site that #BridgyFed can discover an #ActivityPub endpoint to send likes to.)
Tested it by liking @evanp.me (@evan@cosocial.ca @evanpro)’s reply¹ confirming that he received a notification from my prior post². I sent a #Webmention from my like post³ to Bridgy Fed, and it #federated the like to Evan’s server, which subsequently showed up in the "favourites" list of Evan’s post:
https://cosocial.ca/@evan/111237962392745000/favourites
Every step that connects heterogenous #socialWeb systems & protocols feels like progress.
This is day 45 of #100DaysOfIndieWeb. #100Days #IndieWeb #like #likes #fediverse #favorite #favourite #favourites
← Day 44: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me
→ 🔮
¹ https://cosocial.ca/@evan/111237962392745000
² https://tantek.com/2023/287/t1/federating-mentions
³ https://tantek.com/2023/289/f1
-
10 years ago today the first #federated #IndieWeb comment thread was published and collected peer-to-peer IndieWeb replies across websites without any intermediary, silo or otherwise¹.
2013-04-19 @eschnou.com posted a brief note on his personal site with #atMentions of a few domains (putting an '@' sign immediately before a domain name to indicate an explicit cross-web @-mention), which itself was also a first²
"Testing #indieweb federation with @waterpigs.co.uk, @aaronparecki.com and @indiewebcamp.com !"
When @aaronpk.com was notified and replied from his site within minutes³, it became the first peer-to-peer federated IndieWeb comment thread, at the time using h-entry and Pingback. I blogged about it a few days later⁴.
Earlier this year I blogged more observations of all the user interactions that happened on that day and shortly thereafter to make this all work: https://tantek.com/2023/014/t4/domain-first-federated-atmention
Unfortunately Laurent Eschnou’s original post is no longer up, and we only have the Internet Archive copy. However most of the IndieWeb reply posts are still up including Barnaby’s: https://waterpigs.co.uk/notes/1334/
The oldest still working federated post and comment thread was second overall, unsurprisingly from @aaronparecki.com⁵, a whole 40 days after Laurent’s first.
This is day 37 of #100DaysOfIndieWeb. #100Days #OpenWeb #federation #fediverse
← Day 36: https://tantek.com/2023/100/t1/auto-linked-hashtags-federated
→ 🔮
Glossary
federation
https://indieweb.org/federation
h-entry
https://microformats.org/wiki/h-entry
Pingback
https://indieweb.org/Pingback
reply post
https://indieweb.org/reply
References
¹ https://web.archive.org/web/20130427010301/http://eschnou.com/entry/testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html
² https://tantek.com/2023/014/t4/domain-first-federated-atmention
³ https://aaronparecki.com/2013/04/19/3/indieweb
⁴ https://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread
⁵ https://aaronparecki.com/2013/05/21/4/xkcd
-
Previously^1 I asked "How should we @ someone [on the #IndieWeb]?" & suggested we use @-domain. With some web spelunking, the earliest such use I found was 2013-03-26 (~10y ago!) by @eschnou.com, maybe^2 the first #siteToSite #federated #atMention!
"And my first ever #indieweb pingback goes to @tantek.com, @aaronparecki.com and @waterpigs.co.uk ! Yes, I can now federate... well.. if I can manage to get it to interop :-)"
Though the original post disappeared in a site update (and was unarchived), you can see it on the Internet Archive of @eschnou.com’s #IndieWeb tag page: https://web.archive.org/web/20130609045145/http://eschnou.com/tag/indieweb#2013Mar26
At the time, Barnaby (@waterpigs.co.uk) did confirm receiving that @-mention on his site via Pingback (this was before Webmention was a thing^3): https://waterpigs.co.uk/notes/1199/ (https://twitter.com/BarnabyWalters/status/316664943820812289)
@eschnou.com also asked in the IndieWeb chat if @aaronparecki.com had gotten his @-domain mention: https://chat.indieweb.org/2013-03-26#t1364333721000000
You can see at the bottom of that chat log that he did.
I myself started using @-domain in my posts ~4 years later in a 2017 reply: https://tantek.com/2017/345/t1/aaronpk-paid-thanks (https://twitter.com/t/status/940382393097228288) though only when the same person controlled the domain and the Twitter @-name of the first part of the domain name before the "." (which was/is not many people. Workaround: use other @-domain mentions in posts after the POSSE tweet cut-off).
I think that was my earliest use because two days after that post I added @-domain auto-linking to the https://tantek.com/github/cassis (@cassisjs) "auto_link" function https://github.com/tantek/cassis/commit/0e8e6270c0a3b600423c283f59b5d22c3648d59a (https://twitter.com/cassisjs/status/941107922318381057), likely having already tested it in production on my own site with that post.
I’m still #testingInProduction the updates noted in ^3, notably "https:" for all @-mentions (@-name @-domain @-@) and hope to merge them into the repo soon. Aside: both that and the #testInProduction hashtag have hilarious Twitter results^4.
Does anyone know of any other auto-linkers that support linking @-domain in plain text to an https URL of that domain? Extra internet points if they also support @-@ auto-linking.
This is day 14 of #100DaysOfIndieWeb #100Days.
← Day 13: https://tantek.com/2023/013/t1/indieweb-home-internet
→ 🔮
^1 Day 11: https://tantek.com/2023/011/t1/indieweb-evolving-at-mention
^2 I’m curious if StatusNet, OStatus, or OpenMicroBlogging had an explicit syntax for site-to-site @-mentions, whether any of them resembled @-domain, and is there evidence of their earliest @-mention usage (if any) still visible on the web (or Internet Archive) cc: @evanp.me (@evan@prodromou.pub)
^3 https://tantek.com/2023/012/t1/six-years-webmention-w3c
^4 Navigating to Twitter hashtag results left as an exercise to the reader, to provide a deliberate soft barrier to a potential doomscrolling trap.
-
https://500ish.com/mastodon-brought-a-protocol-to-a-product-fight-ba9fda767c6a
#Medium link; don't be surprised if it does weird things before showing you the article.
"Mastodon brought a protocol to a product fight"
> Yes, yes, the network is under immense strain as people flee the Elon strain infecting Twitter. But come on, there are folks who really believe this is going to replace, or even stand alongside Twitter, as a massively scaled social network? I call bullshit. While it’s impressive that millions of users have apparently given Mastodon a try, the product is far too slapdash and clunky to keep folks engaged. A lump of coal.
No, it isn't meant to be a #Twitter replacement. Keep your Twitter account until you no longer want it--or the company closes and the site shuts down--you can use Mastodon alongside Twitter.
And the #Fediverse networks are much more than just #Mastodon. Don't think you have experienced the network and all it has to offer if all you've done is briefly tried to use Mastodon, because you haven't experienced it.
> I’ve somehow avoided signing up for the service up until now. Largely because signing up was and is so comically obtuse — pick your server everyone, hope you choose wisely!
Have you not used e-mail? It works the same way. You pick a server, such as Gmail or Outlook dot com, and sign up. Please tell me you realize that the people you communicate with are not all on the same e-mail service that you use.
> But, but, it’s not a product, it’s a protocol. Yeah, that’s a nice thing to say. And to believe in. But I truly believe the ship has sadly sailed for such idealism in this space. Jack Dorsey can talk about how this should have been what Twitter was from the get go until he’s bluesky in the face. It’s just not going to happen. And he’s more to blame for that than most everyone else. As is he for the Elon element of this current equation. But that’s a different story.
Okay, so how about this story: Twitter has only been profitable two or three years of its entire history. Since it started, it has existed by burning through investors' funds. Eventually, with or without Elon Musk's ownership, that runs out. Without such funding, their corporate-centralized ( #corpocentric ) model cannot exist very long. And same for their centralized competitors, such as Post.news, Gab, Parler, and so on. What is left is either #federated or #peer-to-peer approaches, where no single entity is responsible for funding and managing the entire network. So whether it is the #Fediverse ( with #ActivityPub and #OStatus and their successors ) & the Federation ( with #Diaspora ) or #Bluesky, or #Twister, or #NOSTR, the eventual future of #socnets is #decentralized, if not entirely peer-to-peer unless a national government takes over Facebook and Twitter in order to provide effectively unlimited resources. It is the protocol that makes it possible for thousands or millions of instances to displace and replace one big centralized instance.
1/2
-
I've never played #Minecraft - Is this #Federated software? Is it #FreeSoftware? If so, how can Microsoft control what's happening on someone's private server? Even if such code existed in a #FreeSoftware application, I would have thought there'd be a fork that eliminates that external control. It's time for that now.
But if #Minecraft isn't #FreeSoftware aka Free/Libre Open Source Software, then I really have no sympathies for people running or using it...
-
The HN discussion perpetuates the usual misunderstanding of a #Federated network. People claim they must have accounts on multiple instances in order to follow conversations there. But a person really needs only one account on one instance because they can follow accounts on other instances *because Federation*! https://news.ycombinator.com/item?id=14157801
-
@jaideneverett Welcome :) !GNUsocial is like Twitter, but #non-commercial and #federated. The servers are run by hobbyists and #activists
-
Welcome @geniusmusing to the !fediverse. GM is an active user of another #federated network and is now joining !gnusocial as well.
-
Another #Federated #secure messaging tool: https://ring.cx/ Anyone tried this yet?
-
@deavmi afaik the #deleted posts are a new !gnusocial feature for #federated deleting
-
Of course, I dread the day that someone takes jonkman.ca Can't !selfhost Domain Name Services -- we need…
-
@moshpirit !gnusocial has a small team of volunteers doing the development, much like !friendica, …
-
@moshpirit What do you think about the #newhere tag, as used on !Diaspora? If it helps people inte…
-
@mcscx @aroque @roelofpieter #federated deletion can be troublesome because someone else may contr…
-
I love this !sn / !gnusocial network. Nowhere else have I seen such heated disagreements as we've …
-
I copy that. :-) :-) :-) A #social, #federated code #repository platform ... I wonder if we can m…
-
@roland Yes, and also to any other #federated network. I hate seeing all the JS that Evan's #PumpI…
-
@marcus Other than promoting the use of the #newhere tag (and encouraging people to monitor the ta…
Tantek
LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
Bob Jonkman
Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca
McScx
lnxw48 (Linux Walt)
Roland Haeder
All stadeus content and data are available under the