@fediverse What type of social media do you feel is lacking most in the fediverse?
To elaborate, there are a lot of different types of social media already on the fediverse such as microblogs, regular blogs, image sharing, link sharing and video sharing.
Personally, I’d love to see a gaming-focused social media platform on the fediverse.
@carl @ch0ccyra1n @fediverse
Even better if Fediverse servers could treat any RSS/Atom feed as a “degraded” ActivityPub actor and let users subscribe, boosts and comment posts. We would have de facto a comment platform for everything that has a RSS/Atom feed.
You can’t boost, comment and vote on a RSS post, since AP sends those activities to the origin server.
But subscribing could work, Lemmy would implement a RSS reader basically.
@sexy_peach
isn’t the origin server messaged just to provide counters and notifications to OP?
I don’t exactly know. Sorry
@post @carl @ch0ccyra1n @fediverse
Think we should call it “entry-level” actor or something like that tho. 😁
Degraded sounds it once where top-level but now its wearing off or something.
@me @ch0ccyra1n @carl @fediverse
Yes, mine was a reference to the concept of graceful degradation:
https://www.w3.org/wiki/Graceful_degradation_versus_progressive_enhancement
@me @carl @fediverse
A good metaphor to be used for UI/UX could be Fediverse users as friends in a room commenting TV shows/news that are RSS/Atom feeds: friends can hear each others’ comments but TV is just a one-way communication medium.
@post @me @fediverse That was indeed a good metaphor. I think that kind of interaction in the Fediverse would be very interesting to see. Cultural institutions, civic environments, public actors and so forth being able to use their ordinary web to tell of their activities, but where the choice to engage is on the receiving end.
@carl @me @fediverse
And we wouldn’t have comments split across multiple unofficial RSS->Fediverse bots as it is now.
Bots connecting different platforms are a waste of energy (and therefore have an environmental impact) when we can instead have open protocols.
@post @me @fediverse Good point too!
@post @ch0ccyra1n @carl @fediverse
Ah thanks didn’t know “gracefull degradation” but reminds me of other IT alignment processes in which a customer (me) asked for a “slim/thin” service level instead of a full blown SLA.
But going to use this one instead 👌👌
@post
You are looking for #Friendica
@ch0ccyra1n @carl
@post @ch0ccyra1n @fediverse That would be quite a thing!
@Post @Carl Heath @ch0ccyra1n :ins: :she_her: :vim: :trans: :lesb: :polyam: @Fediverse RSS and Atom only work in one direction. You cannot subscribe to a blog or a news site via RSS and Atom and then send comments. There is no back channel, full stop.
If this was possible, you could be absolutely certain that at least #Friendica and #Hubzilla would have had this very feature implemented since long before Mastodon was even launched. But they don’t, although they federate with just about everything that moves otherwise.
@jupiter_rowland @fediverse I see, and realize the complexity. Given this, it would be awesome with that kind of connection, some kind of tool that could take any web page and make a two way connection in the style of RSS. Something easy to install or connect to a web, and provide interaction.
@Carl Heath @Fediverse That’d require changes to both sides, both whichever Fediverse project you’re using and whichever site with an RSS feed you want to interact with.
You will never be able to use Mastodon to comment on a post on a blog with a backend that has last change at some point in the 2010s or the 2000s. The blog doesn’t even have a back channel in any shape or form. It’d have to pull a WordPress and install a proper ActivityPub connector.
Even Friendica or Hubzilla devs would have to take ONE blog and hackney themselves directly into the backend of that one particular blog, directly into the SQL database. Much like Friendica established federation with Diaspora* back in the day when Diaspora* had nothing even resembling an API. They had to reverse-engineer the Diaspora* protocol and crack the encryption. It took literal months. And when they were done, the connection was established by latching directly onto Diaspora*'s database with no actual interface at all. It was akin to connecting a piece of out-board hardware to a computer using a drill and a soldering iron.
At least, Diaspora* was a whole network. Here I’m talking about ONE (1) website. And when they’re done, they’ll have to move on to the next one. And so forth.