wake.st is one of the many independent Mastodon servers you can use to participate in the fediverse.
the personal instance of Liaizon Wakest

Administered by:

Server stats:

1
active users

ActivityPub federation of Gitlab underway!

"I have finished preparing my design documents for this feature. See here for the reasoning behind adding ActivityPub to Gitlab and an overview of the implementation path, and here more specifically for this current issue, with more detailed specifications.

I now feel confident enough to get starting implementing this into Gitlab. I'm going to add the activities iteratively, there is quite some distance to cover up." -Kik

via gitlab.com/gitlab-org/gitlab/-

GitLabShare events externally via ActivityPub (#21582) · Issues · GitLab.org / GitLab · GitLab Description While working in Gitlab developers and projects create a lot of interesting events, commits, comments, releases, etc. Each of these...

@liaizon @jeffmcneill huh why not though? Is there some context to this i'm missing

@natriumchloride @jeffmcneill oh just the context that there have been endless articles with titles like "rss is dead"

I would hope we can do a better job then rss but I guess the task is even more complex

@liaizon
> there have been endless articles with titles like "rss is dead"

Reports of RSS' demise have been greatly exaggerated. As with XMPP, and many other open standards that still have communities actively using them, with a range of Free Code (and sometimes proprietary) implementations. Many websites still publish RSS feeds. Eg RSS can be used to follow Titter accounts via a Nitter instance, and similar stuff is possible in Invidious using RSS.

@natriumchloride @jeffmcneill

@strypey @liaizon @natriumchloride @jeffmcneill rss declined for numerous reasons but here's the big ones:

1. general developer antipathy toward xml
2. unlike permissive html, rss was strict and developers constantly fucked up implementing it correctly, a single minor error made the entire feed unusable (tying back to 1, maybe the xml hate was justified)
3. end users wanted to be fed the entire document through rss and read it on their reader of choice rather than ujst get a link through syndication, but this stripped tracking and ad embeds so content producers weren't enthusiastic
4. clients tended to be poor, everybody remembers the couple good paid ones that were essentially aggregator services in reality
5 . mozilla of course, ignoring their mission statement massively contributed to the death spiral by removing direct rss support from the browser

so now we live in a world where regular webpages that are literally just status feeds don't even have rss on them so you have to scrape and dom interpret the fucking things; and people beg them to post updates "via mastodon" which they inevitably do by joining a massive server that silently blocks half the fediverse from being able to subscribe to it. what a fucking mess

@Moon
> mozilla of course, ignoring their mission statement massively contributed to the death spiral by

... pretty much every decision their upper management have made for about a decade.

@jeffmcneill @natriumchloride @liaizon

@Moon @jeffmcneill @strypey @natriumchloride @liaizon lmao literally the same happened to XMPP (except #2). Many tried using XMPP for literally everything, I remember some even prophecised it replacing E-Mail. Yet here we are.
@strypey @liaizon @natriumchloride @jeffmcneill
I have to question the motivations of people who write articles with
headlines like "RSS is dead". Is the motivation
"we can't monetize this, so let's try and kill it by convincing a critical mass of people that it's dead"?

RSS has been wildly successful because:

* On a very broad conceptual level, it is dead simple. Some of the details might be complicated, but those details have been abstracted away by authors of code libraries for decades.
* It is effective at doing its job.
* It is boring in a good way, in the way that roads and bridges are boring, so the tech people who are running around looking for the next thing to salivate over never notice it.
* It is widely implemented, with very little fanfare. I think this follows naturally from effective, simple, and boring.

A lot of those points apply to email too. And hasn't
"email is dead" been a meme in tech circles for a bit now, too?

If you want your open protocol to succeed, being simple, effective, and boring is probably not a bad strategy.