# POSSE and backfeed

**URL:** <https://discuss.write.as/t/posse-and-backfeed/1510>\
**Category:** Development\
**Tags:** writefreely\
**Created:** [June 11, 2020, 12:54pm UTC](https://discuss.write.as/t/posse-and-backfeed/1510 "2020-06-11T12:54:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![matt](https://discuss.write.as/user_avatar/discuss.write.as/matt/32/2760_2.png) [@matt](https://discuss.write.as/u/matt)\
**Post date:** [June 11, 2020, 12:54pm UTC](https://discuss.write.as/t/posse-and-backfeed/1510/1 "2020-06-11T12:54:24Z")

</div>

Moving a [discussion](https://github.com/writeas/writefreely/pull/319#issuecomment-640877550) from writefreely#319.

* * *

[@shinenelson](https://github.com/shinenelson) posted:

> I’m not sure whether this would categorize as a whole separate feature in itself, but I’m going to put it out there anyway.
> 
> How about implementing IndieWeb [POSSE](https://indieweb.org/POSSE) and [backfeed](https://indieweb.org/backfeed)?
> 
> I’m aware that this is way beyond the scope of what this pull request is trying to do. I’m probably coming out of nowhere and stepping on your toes, but I thought it’d be a good idea that could also pave the way for a bigger discussion.
> 
> And to start the discussion, I’d say the advantage of implementing POSSE would be that the syndication of posts would be uniform everywhere and they’ll all point back to one canonical URL.
> 
> And _IF_, at some point in the future, [Twitter](https://www.theverge.com/2019/12/12/21012553/twitter-bluesky-decentralized-social-network-developers-reaction-mastodon-activitypub) or other social media decide to embrace ActivityPub, this would still work backward compatible too.

* * *

[@rgx1](https://github.com/rgx1) posted:

> I think this is a great idea.
> 
> I do use a couple of different Crossposters, and one of them, [the one made by Renato Lond](https://crossposter.masto.donte.com.br/), does a beautiful job of bridging the platforms.
> 
> I have mentioned [them both in a recent post](https://write.tedomum.net/rgx/crossposting-and-surprises-happened).
> 
> * * *
> 
> Renato’s output will look like this :
> 
> ![image](https://user-images.githubusercontent.com/66519794/84085970-c60a6980-a9b4-11ea-9864-60ad3e284042.png)
> 
> The link to the source post is live and working. Another crossposter I use does less well, creating less attractive output.
> 
> ![image](https://user-images.githubusercontent.com/66519794/84083993-a40ee800-a9b0-11ea-8dab-d5e3f2fb0405.png)
> 
> …although the link to source is present and working.
> 
> * * *
> 
> We could do better yet – I could created a better looking post, with the full source URL hidden (and it will display so, even in the normal Mastodon instances), using the MarkDown support provided at my Glitch.Social instance.
> 
> Source looks like :
> 
> ```auto
> #xp
> 
> RT [@TheMedicaIVideo](https://twitter.com/TheMedicaIVideo/status/1266604854358814722)
> 
> the beauty of brown eyes 👁`
> 
> ```
> 
> And outputs :
> 
> ![image](https://user-images.githubusercontent.com/66519794/84084883-585d3e00-a9b2-11ea-95e1-bd9f50c69f24.png)
> 
> [That post is Here.](https://muensterland.social/@rgx/104310624318785578)
> 
> * * *
> 
> As I noted earlier this week upon experimentation, this looks wonderful on Glitch-Social, and will display hidden URL even on normal Mastodon 3.x.x instances.
> 
> There seems to be an allowance for these hidden URLs in posts originating from other platforms in Fediverse – and while plain vanilla Mastodon **WILL strip off Bold, Italics,** etc, it _will preserve the URLs as intended_.
> 
> I love this – and have made posts now that have up to 5 URLs included and not a single ‘https’ to be seen. Clean, elegant, functional.