Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support AP-style mentions of centralized social media accounts #319

Open
wants to merge 1 commit into
base: develop
from

Conversation

@thebaer
Copy link
Member

thebaer commented Jun 8, 2020

This allows users to easily link to users on the following non-ActivityPub platforms:

  • twitter.com
  • medium.com

Of course, since these platforms don't speak ActivityPub, mentioned users won't be notified. But for example, adding @ilikebeans@twitter.com in a post will send users to the correct Twitter profile when clicked.

This also adds missing error handling in federatePost().

What does everyone think about adding this? Would love to hear your feedback.

This allows users to mention users on the following non-ActivityPub
social media sites:

- twitter.com
- medium.com

It also adds missing error handling in federatePost().
@thebaer thebaer added the experimental label Jun 8, 2020
@shinenelson
Copy link

shinenelson commented Jun 8, 2020

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 and 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 or other social media decide to embrace ActivityPub, this would still work backward compatible too.

@rgx1
Copy link

rgx1 commented Jun 8, 2020

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, does a beautiful job of bridging the platforms.

I have mentioned them both in a recent post.


Renato's output will look like this :

image

The link to the source post is live and working. Another crossposter I use does less well, creating less attractive output.

image

...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 :

#xp

RT [@TheMedicaIVideo](https://twitter.com/TheMedicaIVideo/status/1266604854358814722)

the beauty of brown eyes 👁`

And outputs :

image

That post is Here.


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.

@thebaer
Copy link
Member Author

thebaer commented Jun 11, 2020

Thanks for the ideas! This is definitely a larger discussion that's out of scope for this PR, so let's move it to this thread on our forum -- the right place for these kinds of discussions.

@shinenelson
Copy link

shinenelson commented Jun 11, 2020

agreed. I wasn't aware of the forum; or I didn't look enough. I should've just assumed that it existed though and looked for it because every community has a discourse these days 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.