It is, of course, #selfhosted and supports #rss.
Any and all feedback is welcome!
#indieweb
✨ Blog Post ✨
🐘 Welcome to Mastodon — Forget Twitter, Mastodon has 10x the engagement.
I've been comparing Twitter and Mastodon. I have 1/10 the followers on Mastodon but TEN TIMES the engagement. From real humans!!
https://www.caseywatts.com/blog/welcome-to-mastodon/?utm_medium=social&utm_source=mastodon
#mastodon #twitter #socialmedia #indieweb
A great collection of recent, updated resources about some of the most confusing #IndieWeb concepts. I’ve definitely stumbled upon all these during my journey as well. Nice to see them so well curated. Thanks for putting this together!
From: @stevenwoodson
https://mastodon.online/@stevenwoodson/109893967669779575
Web 1.0 was like the debut album from a promising new band: rough around the edges, sometimes uncontrolled, compelling, and full of the passionate energy that later albums lack due to the greed of a big label deal. #oldweb #indieweb #yesterweb #retroweb
That should work. The microformats1 hReview property details specified "fixed decimal point (one decimal point of precision)," which should carry over for backward compatibility: https://microformats.org/wiki/hreview#Property_details
Looking forward to hearing from both @cassiecodes@front-end.social and @philhawksworth@indieweb.social at Monday’s geeky gathering here in Brighton:
https://www.storyblok.com/ev/stories-on-the-road-uk-23#brighton-%C2%B7-february-27th
@fediversereport @brembs I like the immediate engagement on Mastodon, but the recency bias is strong & the current lack of full text search a limitation. I'm searching for the best way to post text-&-image threads, or text-&-referenced-ideas (QT), with visibility to search engines, assurance of long-term presence, & Twitter-like ease-of-use. Could we encourage scholarly institutions to consider useful additions to the #fediverse?
#feedback #FediTips #IndieWeb
@torresburriel The integration potential of #indieweb sounds exciting! Meanwhile I'd like to post simple searchable versions of threads on my own website & have been hunting for simple html templates that I can understand & manage myself. Hoping to find templates with good modern design? for text interspersed with standard 16x9 images (or sets of 2/3/4 images). Should be simple but I've been hunting... #FediTips help welcome please!
#Mozilla's choice to remove their built-in web feed support without providing an official extension to carry on the legacy is another strike to the #openWeb and #indieWeb on their side.
I often wonder what has been going on inside #Mozilla. #Firefox reached its largest market share (around 30%) some 10 years ago. Since then, it has been inexorably losing market share. There is little doubt that this has been largely due to the growth of mobile and Google's unfair marketing advantage, BUT:
Operating for less than four years, it standardized several foundations of the #fediverse & #IndieWeb:
#Webmention
#Micropub
#ActivityStreams2
#ActivityPub
Each of these has numerous interoperable implementations which are in active use by anywhere from thousands to millions of users.
Two additional specifications also had several implementations as of the time of their publication as a W3C Recommendations (which you can find from the Implementation Report linked near the top of each spec). However today they’re both fairly invisible "plumbing" (as most specs should be) or they haven’t picked up widespread use like the others:
#LinkedDataNotifications (LDN)
#WebSub
To be fair, LDN was only one building block in what eventually became SoLiD², the basis of Tim Berners–Lee’s startup Inrupt.
However, in the post Elon-acquisition of Twitter and subsequent Twexodus, as Anil Dash noted³, “nobody ran to the ’web3’ platforms”, and nobody ran to SoLiD either.
The other spec, WebSub, was roughly interoperably implemented as PubSubHubbub before it was brought to the Social Web Working Group. Yet despite that implementation experience, a more rigorous specification that fixed a lot of bugs, and a test suite⁴, WebSub’s adoption hasn’t really noticeably grown since. Existing implementations & services are still functioning though. My own blog supports WebSub notifications for example, for anyone that wants to receive/read my posts in real time.
One of the biggest challenges the Social Web Working Group faced was with so many approaches being brought to the group, which approach should we choose?
As one of the co-chairs of the group, with the other co-chairs, and our staff contacts over time, we realized that if we as chairs & facilitators tried to pick any one approach, we would almost certainly alienate and lose more than half of the working group who had already built or were actively interested in developing other approaches.
We (as chairs) decided to do something which very few standards groups do, and for that matter, have ever done successfully.
From 15+ different approaches, or projects, or efforts that were brought⁵ to the working group, we narrowed them down to about 2.5 which I can summarize as:
1. #IndieWeb building blocks, many of which were already implemented, deployed, and showing rough interoperability across numerous independent websites
2. ActivityStreams based approaches, which also demonstrated implementability, interoperability, and real user value as part of the OStatus suite, implemented in StatusNet, Identica, etc.
2.5 "something with Linked Data (LD)" — expressed as a 0.5 because there wasn’t anything user-visible “social web” with LD working at the start of the Working Group, however there was a very passionate set of participants insisting that everything be done with RDF/LD, despite the fact that it was less of a proven social web approach than the other two.
As chairs we figured out that if we were able to help facilitate the development of these 2.5 approaches in parallel, nearly everyone who was active in the Working Group would have something they would feel like they could direct their positive energy into, instead of spending time fighting or tearing down someone else’s approach.
It was a very difficult social-technical balance to maintain, and we hit more than a few bumps along the way. However we also had many moments of alignment, where two (or all) of the various approaches found common problems, and either identical or at least compatible solutions.
I saw many examples where the discoveries of one approach helped inform and improve another approach. Developing more than one approach in the same working group was not only possible, it actually worked.
I also saw examples of different problems being solved by different approaches, and I found that aspect particularly fascinating and hopeful. Multiple approaches were able to choose & priortize different subsets of social web use-cases and problems to solve from the larger space of decentralized social web challenges. By doing so, different approaches often explored and mapped out different areas of the larger social web space.
I’m still a bit amazed we were able to complete all of those Recommendations in less than four years, and everyone who participated in the working group should be proud of that accomplishment, beyond any one specification they may have worked on.
With hindsight, we can see the positive practical benefits from allowing & facilitating multiple approaches to move forward. Today there is both a very healthy & growing set of folks who want simple personal sites to do with as they please (#IndieWeb), and we also have a growing network of Mastodon instances and other software & services that interoperate with them, like Bridgy Fed⁶.
Millions of users are posting & interacting with each other daily, without depending on any large central corporate site or service, whether on their own personal domain & site they fully control, or with an account on a trusted community server, using different software & services.
Choosing to go from 15+ down to 2.5, but not down to 1 approach turned out to be the right answer, to both allow a wide variety⁷ of decentralized social web efforts to grow, interoperate via bridges, and frankly, socially to provide something positive for everyone to contribute to, instead of wasting weeks, possibly months in heated debates about which one approach was the one true way.
There’s lots more to be written about the history of the Social Web Working Group, which perhaps I will do some day.
For now, if you’re curious for more, I strongly recommend diving into the group’s wiki https://www.w3.org/wiki/Socialwg and its subpages for more historical details. All the minutes of our meetings are there. All the research we conducted is there.
If you’re interested in contributing to the specifications we developed, find the place where that work is being done, the people actively implementing those specs, and even better, actively using their own implementations⁸.
You can find the various IndieWeb building blocks living specifications here:
* https://spec.indieweb.org/
And discussions thereof in the development chat channel:
* https://chat.indieweb.org/dev
If you’re not sure, pop by the indieweb-dev chat and ask anyway!
The IndieWeb community has grown only larger and more diverse in approaches & implementations in the past five years, and we regularly have discussions about most of the specifications that were developed in the Social Web Working Group.
This is day 33 of #100DaysOfIndieWeb #100Days
← Day 32: https://tantek.com/2023/047/t1/nineteen-years-microformats
→ 🔮
Post Glossary:
ActivityPub
https://www.w3.org/TR/activitypub/
ActivityStreams2
https://www.w3.org/TR/activitystreams-core/
https://www.w3.org/TR/activitystreams-vocabulary/
Linked Data Notifications
https://www.w3.org/TR/ldn/
Micropub
https://micropub.spec.indieweb.org/
Webmention
https://webmention.net/draft/
WebSub
https://www.w3.org/TR/websub/
References:
¹ https://www.w3.org/wiki/Socialwg
² https://www.w3.org/wiki/Socialwg/2015-03-18-minutes#solid
³ https://mastodon.cloud/@anildash/109299991009836007
⁴ https://websub.rocks/
⁵ https://indieweb.org/Social_Web_Working_Group#History
⁶ https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed
⁷ https://indieweb.org/plurality
⁸ https://indieweb.org/use_what_you_make
Link: Re; Reading social streams in feed reader 🔗 It’s absolutely fair enough not following social media in your RSS reader. I also like being referred to as Mr Leon Paternoster.
🏷 #Indieweb #RSS
https://thenewleafjournal.com/leafbud/re-reading-social-streams-in-feed-reader/
@Samir @atomicpoet @davew @TechCrunch @fediversenews Opera/Presto used to tell you that without looking at the source. Vivaldi inherited that feature. I think other browsers have extensions to do it too. Hopefully with the comeback of the #indieWeb and #openWeb these features will have a comeback.
very nice app https://www.wickeditor.com/
kinda if HyperCard and Framer had a really cute kid.
Static sites are great in lots of ways, but #webmentions are kind of a pain in the ass. I wrote a Netlify build plugin which uses my atom feed to determine mentions to dispatch. #IndieWeb https://qubyte.codes/blog/dispatching-webmentions-with-a-netlify-build-plugin
Finally released version 3.3.7 of the jekyll-webmention_io plugin, which updates some key dependencies, and staged a couple of major new features for the planned version 3.4.0! Progress!
It’s amazing to realise that the more we put names to things the more we can help others to understand it. In fact, the more I read today about #indieweb, the more I have two feelings. One side I feel I’ve been wasting my time for more than 10 years in #digital. On the other side, I want to learn and practice more and more about indieweb. https://tantek.com/2023/029/t1/indieweb-beyond-blogging