ChaiaEran

The INCORRIGIBLE Chaia, BSc

Esoteric goth-y femme. Occasionally speedy. Liker of randomizers. Queer Jewish gremlin. I make Youtube videos and stream on Twitch! Also the developer of @PushBlockPitDevlog.

My Twitch going live posts are over at @ChaiaGoingLive.

 

מיר וועלן בעסער זיין אין די גלות, מיר וועלן זיך באפריין

דעלך סני לחברך לא תעביד. שחררו את פלסטין

Chaia Eran: Cute as hell, Queer AFTRANS RIGHTS NOW!TRANS YOUR GENDER
יידFree Palestine Now!!!This is an Anti-NFT Site
KEEP THE WEB Free; SAY NO TO WEB3<HTML> Learn it today!Firefox NOW!
RWBYGAMEBOY ADVANCEPRO AO3 FREAK
FIGHT FOR OPEN WEB STANDARDS; FIGHT FOR ONLINE PRIVACY; FIGHT AGAINST MONOPOLISTIC PRACTICES; STAND UP TO GOOGLE!Questions or Comments? E-Mail


bluetinge
@bluetinge

Can we recreate Cohost in a decentralized environment?

It's been great to see so many people planning to keep the Cohost community alive by sharing links to their own blogs following one another through RSS. In theory, something like Cohost should be entirely possible to recreate through decentralized networks — even as we move to different blogging platforms or create our own websites, we can use RSS to follow one another and stay in touch. The barrier of entry is incredibly low: platforms like WordPress and Tumblr already offer RSS feeds, and tools like the excellent RuSSHDown even let you create an RSS feed all on their own!

But there's still something missing... Or, well, there's plenty missing, but one thing in particular stuck out to me: reblogging. Sharing and reblogging content is a huge part of any Cohost-like system... is it possible to recreate it without relying on a centralized server?

Gif of scrolling and hitting reblog button

Note: the default styling is a bit basic but it's all easily customizable!

The above is a reblog button that I've created that's intended to work on as many different systems and platforms as possible. I have a widget for creating one on the main page at rssr.bluetinge.dev, which doubles as a tool to reblog any RSS feed on the internet, and a sample page of what the results could look like here, but if you don't mind, I'd like to explain a bit about how it works first and make a case for why people should give it a try! And if you
don't have an RSS feed or blog yet, scroll to the bottom where I have a tutorial on how to get started! 



You must log in to comment.

in reply to @bluetinge's post:

That's a cute idea!
I could perhaps stylize it as ReSShaRe, so that it works with the existing RSSR namespace I've registered (for RSS-Reblog); or alternatively, perhaps it's early enough in the project that changing the namespace wouldn't be too bad... Hmm
Whatever I go with it's a cute name, ty!

it is neat! thank you! we still are not sure whether reshares are a good thing or a bad thing.

one of the most interesting dynamics about cohost is that, because there's no technical mechanism that keeps us from overwhelming people's feeds, we had to learn to be parsimonious with the resharing... there are still definitely times when we have reshared stuff, just, we had to learn to actively reflect on it.

compare and contrast other social media sites, which are intentionally designed to make that an impulsive decision.

we wonder what will wind up happening with rss reshares, long-term.

Thanks for the comment!

I think it's possible that with something like what I have now, the barrier of inconvenience for sharing (necessitating the upload a whole new feed manually) will have a similar effect of restricting how much users will share things, esp. since the worry about overwhelming others' feeds is still a real concern. I could absolutely still see that being misused, though.

I am now thinking a bit more about possible negative side effects of reshares, though. Were there other concerns about reshares that y'all had? I'm wondering if there are things I could do to mitigate potential negative aspects of this.

yeah - we weren't up for a long explanation last night but we had the same thought, that the fact your thing requires so much manual work will mean it doesn't lead to people being impulsive. we think it's a good direction for experiment.

it's also the case that the worst abuse-cases of RSS are not things we have to guess at, they're things like attempting to steal a feed (and put ads on it...) by misrepresenting the authoritative source of it, or misquoting people for character assassination purposes. these are things that can already be done without your tool, and in fact the first one was part of the decline of RSS the first time around. I don't think your tool needs to actively worry about these types of threats, at least not in its present state.

so, leaving aside the active-malice stuff mentioned above, there are two negative psychological elements to reshares on social media in general.

one of them is the gambling-psychology element of it, essentially trying to tempt people into seeking fame by optimizing their writing into something that others will want to reshare a lot. (our personal view is that fame is a trap; that's not specific to social media. sometimes it may be a tool as well, but it's a dangerous one.) this gambling-psychology concern mostly applies to the authors of posts, though it's helped along by heavy UI optimization and experiments, making it as easy and good-feeling as possible for readers to reshare.

the other is that reshares, especially of short posts that weren't meant to stand alone, decontextualize the source material. on some platforms they also make it very easy for the resharer to prime readers with their own, fake context, which can be a very powerful tool of harassment. this approach has been very effective at getting people who should be allies to fight each other, and since it's such a simple pattern to imitate, we're certain that lots of people doing it don't even recognize what they're doing as harmful.

the bottom line is that sometimes people are writing stuff that they want reshared, such as a plea for a certain sort of social change, or for help with their finances, or showing off their art.... and sometimes they're not. probably most people, most of the time, are better off when their words aren't reshared. however, when you do hit one of those scenarios where you want it, you really want it!

we don't know what this means for your tool, we're just sharing our general thoughts on this topic in case they're useful to you or others. we've said all this before, but perhaps not in one place.

we're still super excited about your tool because it does feel like a piece that will make it easier to build community on an rss-centric tech stack, rather than just individualist pontificating. we are probably going to end up using it :)

Thank you very much for your detailed replies, I really appreciate it!

The most overt examples of abuse that y'all described (i.e. outright plagiarism or deception) had occurred to me, though in its present state I agree that the effort required to do so is probably largely equivalent to the effort to do so manually. I'm now considering that maybe I should make it opt-in -- i.e. only posts where the button has explicitly been added could be shared -- and that is probably something I will do if the tool becomes widely used, though at this state that would likely just be another barrier to usability.

With regards to misrepresentation of posts out of context, though, that is perhaps something that could more explicitly address:

  • Currently, the link to the original post is already included, but it's unlikely someone will click on it if it has already been reproduced in full. Perhaps the reshare should by default only include some portion of the original post, with a "read more" link that goes back to the original?
  • In the same manner, I could make it so that the item's element always explicitly links back to the original post -- currently it does so by default, but it will link back to the resharer's link if provided. This has some benefits (i.e. if the resharer added additional comments) but also could fall into the same problem of reducing context.

The best way to approach these issues is probably giving more control to the original author over how their post looks when reshared... Definitely something I'll need to spend some time looking into. Thanks for giving your perspectives!