No matter where you look on #Mastodon, you will never escape one of the following:
- #Linux power users
- #Weebs
- #Transgirls
- #Furry gooners
- #Liberal journalist/lawyer
- Disillusioned #sysadmin
- Bright-eyed #IT student
- Memelords with expert level #shitposts
- Niche #indieweb sites
- #bots with mildly-entertaining-to-insanely-annoying automated feeds
and last but not least:
- Wine moms with blogs just having fun 😊
@OohDirectory I just found you folks from @jimniels
Sooo coooooollllll!!!!
#SmallWeb #indieweb
Trombei com o novo sítio da desenvolvedora e artista chinesa Nic Chan, e agora quero deixar o meu sistema operacional com essa cara 8-bit/ Macintosh/ #pixelart.
É uma ótima pedida para quem quer se inspirar em configurar um sítio pessoal. Funciona sem Javascript, mas habilitá-lo vale a pena.
Um #SurfandoWeb via The Jolly Teapot.
Has anyone created a Buy Music Club page for #music from the #Fediverse?
#BandcampFriday #Bandcamp #FediArt #FediMusic #Mastodon #MastoMusic #IndieWeb
In een van de hoekjes van het internet wordt maandelijks het Indieweb Carnaval gevierd. De organisator noemt een thema, (onafhankelijke) bloggers schrijven er op los.
Deze maand is meertaligheid het onderwerp. Het internet spreekt Engels en dit weblog Nederlands (op een enkele post na waarvan ik denk dat het zinvol is een vertaalde versie te schrijven). Het gevolg is dat het aantal […]
As Manton points out, there are many of us now, many implementers and publishers that are implementing and supporting multiple protocols, and thus it matters to us that we at least maintain the level of compatibility and interoperability that we achieved in the initial Recommendations of these specifications.
I think we can continue to do that, especially if we scope the Working Group to being a maintenance WG for the existing specs. This is something that Evan has convinced me of, while previously I saw a renewed Social Web WG to work on new features. Given the progress with use of extensions, and the Fed ID CG/WG stages process (or something like it), that seems like a better way to pursue new features, in parallel in the Social CG.
Another benefit of one Social Web working group is that its scope is easier to determine and explain, both to prior participants, and to W3C Members who will be voting on its creation.
A renewal of a working group to do maintenance on all of its prior specs, both editorial and bug fixes, makes a lot of sense to W3C and to Members, who like seeing working groups that take up the responsibility of maintaining specs. This especially makes more sense when all those specifications have far more implementations now than when they were shipped by the prior working group!
As I saw in another blog post about the social web, we are all here on “team open”, and I think we suffer, collectively, by attempting to draw lines with any “ActivityPub-only” approach. Both because it unnecessarily divides a very diverse, mixed, and broader “ActivtyPub supporting” community, and because it’s much fuzzier, to the point of overlapping with adjacent and aligned efforts.
The rel=me specification is a good example of this overlap. Would that be included in an “ActivityPub-only” approach? Because it’s certainly used by communities beyond that.
We have a whole task force on HTML Discovery in the CG where some of us (myself included) is working on improving rel=author support when interacting between HTML representations of profiles, yes, often with microformats, and retrieving the JSON(-LD) Activity Streams 2 versions of those profiles. That sort of interoperability benefits from a more inclusive approach.
We have bridges (https://fed.brid.gy/) that have helped the “ActvityPub-verse” grow that we could only dream about during the prior Social Web WG, because that group put in the hard work of figuring out interoperability across protocols and formats. We already did that hard work so why squander it? A maintenance group for all our specs provides a venue for any marginal bits of small work we may (or may not) need to maintain the positive outcomes of all that prior hard work.
Lastly, @github.com/gobengo brings up important concerns that I think merit explicitly addressing, regarding “experience in the SocialWG from 2013-2017” (actually 2014-2018 per https://www.w3.org/wiki/Socialwg)
First, in summary I will say as the saying goes “Don't fight the last war”, or I prefer a non-violent expression instead: “Don’t argue the prior debates”.
We were in a very different situation at the start of the first Social Web Working Group, having emerged from an incredibly diverse “W3C Workshop on Social Standards: The Future of Business” (AKA osfw3c) in 2013.
The first Social Web WG had to evaluate numerous prior group efforts (17+) and different approaches (~15) that were proposed by members of the group for consideration before narrowing down to ~3 approaches. Lots of time was spent doing this, which we would obviously avoid by sticking to maintenance of existing specs.
We also found so much in common that we were able to leverage as building blocks and points of compatibility. HTTP & link rel discovery. URLs for profiles. Etc. the list goes on.
All of that is pointing out how the first Social Web WG was very different than what a similarly scoped Social Web WG could be like today.
Second, the other strong point of more recent evidence that we should use instead of fearing “the last war”, is how the Social CG has been conducted for the past 5-6 years, especially the past few years mostly chaired by Dmitri.
Every Social CG meeting I have been to has been incredibly positive & productive. Even when we disagree, we do so in very civil, polite, informed ways that consider each other’s use-cases, perspectives, opinions, with folks working on different projects and protocols! It has been an incredible experience and I am grateful to be a part of it, and especially grateful for Dmitri’s stewardship. I mentioned this briefly in a post after a recent meeting https://tantek.com/2024/216/t1/socialcg-telcon.
With the Social CG, under Dmitri’s chairing, we have found a new more harmonious rhythm, and frankly, broader inclusiveness of different efforts and communities than we ever had previously. We have proven we can have regular meetings that “continue[s] the work of the W3C Social Web Working Group” where agenda items are curated and prioritized in a manner that respects the time and interests of the participants.
I would expect the harmony of the Social Web CG to continue in a similar renewed Social Web WG, and would support Dmitri as a co-chair of that working group to keep our momentum going. In addition, I would ask anyone else wanting to co-chair to learn from and adopt Dmitri’s chairing workmode accordingly. I believe that is our best path to success for this community, and for all our collective goals.
References:
* https://www.w3.org/wiki/SocialCG
* https://www.w3.org/wiki/SocialWG
* https://indieweb.org/2013/osfw3c
✍️ Mentions United ... 3, 2, 1, Go
At some point, you write something yourself. In this case, a JavaScript solution to unite blog posts with their interactions on the #socialweb and beyond...
Reminder that I write about a lot of stuff, blindness, life stuff, my author news. I never stick to 1 topic so if you wanna follow, my RSS feed is https://robertkingett.com/feed/ #RSS #Blog #IndieWeb
Looks like Libre.fm, an open-software version of Last.fm by the GNU Project, is being reworked to support ActivityPub!
#LibreFM #LastFM #Fediverse #SocialWeb #IndieWeb #ActivityPub #GNU #GNUProject #Music #FediMusic
IndieWeb Carnival: multilingualism in a global Web
For some reason this month has a plethora of daily blogging or other creativity prompts. Here’s a list of the ones I found so far:
* #Blogtober (consider this post my first for this, retroactively day 1)
* Inktober — https://inktober.com/
* LOLtober - https://weblog.anniegreens.lol/2024/10/loltober-2024
* Looptober — https://looptober.com/
* Mathober - https://mathober.com/
* Viztober — https://www.instagram.com/evalottchen/p/DAiNm3ZtuTj/
Having found so many for the month I created an “October” page on the #IndieWeb wiki to document them all (and in case folks find others to add):
* https://indieweb.org/October
October is also a very popular month for seasonal blog styling:
* https://indieweb.org/Halloween
Do you have a custom Halloween theme for your personal site? Add it to the wiki!
This is post 23 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/247/t4/w3c-link-checker-before-federating
→ 🔮
Happy October!
For some reason this month has a plethora of daily blogging or other creativity prompts. Here’s a list of the ones I found so far:
* #Blogtober (consider this post my first for this, retroactively day 1)
* Inktober — https://inktober.com/
* LOLtober - https://weblog.anniegreens.lol/2024/10/loltober-2024
* Looptober — https://looptober.com/
* Mathober - https://mathober.com/
* Viztober — https://www.instagram.com/evalottchen/p/DAiNm3ZtuTj/
Having found so many for the month I created an “October” page on the #IndieWeb wiki to document them all (and in case folks find others to add):
* https://indieweb.org/October
October is also a very popular month for seasonal blog styling:
* https://indieweb.org/Halloween
Do you have a custom Halloween theme for your personal site? Add it to the wiki!
This is post 23 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/247/t4/w3c-link-checker-before-federating
→ 🔮
I wrote a short note about Meta's toaster problem— toaster are impossible to make, digital platforms are easier. So Zuck needs a bigger more expensive moat.
#IndieWeb #Fediverse #OpenSocialWeb
https://www.fromjason.xyz/p/notebook/meta-s-toaster-problem/
I really like personal homepages and have quite a list of them bookmarked. I'll post one every week unless I fall behind this schedule. 😉 So here's Cool Personal Homepages #CPH Vol. 25: zkbro https://html-chunder.neocities.org/
I'm looking for folks to take over maintenance of two IndieWeb-technology Perl libraries:
* https://metacpan.org/pod/Web::Mention
* https://metacpan.org/pod/Web::Microformats2
I still use these regularly—if passively—but I'm told that they've become difficult to install on new systems due to failing tests.
I'd love to see someone with active interest in #Perl or #IndieWeb take this software under their wing and help keep it up to date. Please DM me if you're interested!
🤖 I posted to my #AmateurRadio blog.
#Radiosport #IndieWeb #HamRadio
https://w8mhb.com/radiosport-pota-awards
🔖 Read The IndieWeb is for developers.
This is a great set of points.
In The Margins #newsletter no. 4:
Talking creative ruts, woodland diaries and #smallweb links.