To my understanding it's contradictory to the Mastodon concept to hard-code a server URL.

Given: urlPrefix = "https://fintoot.space/" in
https://git.drupalcode.org/project/social_media_links/-/blob/8.x-2.x/src...

Should be changed to urlPrefix = "https://"

Of course that interfers with existing usage. I'm not a developer, thinking about a solution along the lines of adding an update script to detect whether active modules

  • have an active Mastodon plugin
  • given database entries in the respective tables
  • using an (unpatched!) fintoot prefix

... and append the deprecated prefix to the entries.

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

hexabinaer created an issue. See original summary.

Eugene Dubois’s picture

I absolutely agree. Where is fintoot.space even coming from?

Janner’s picture

It would also be really useful if we could find a way to incorporate the rel="me"attribute so that it serves to verify the account.


You can verify yourself as the owner of the links in your profile metadata. For that, the linked website must contain a link back to your Mastodon profile. The link back must have a rel="me"attribute. The text content of the link does not matter. Here is an example: <a rel="me" href="https://mastodon.social/@Account">Mastodon</a>

crafter made their first commit to this issue’s fork.

saidatom’s picture

Status: Active » Reviewed & tested by the community

MR looks good to go, moving into RTBC.

hexabinaer’s picture

Where is fintoot.space even coming from?

I wouldn't want to blame anyone ;-)

Thanks for forwarding this issue!

Edit: I see the changed urlPrefix but nothing to preserve legacy data. IMHO we should at least add an update hint. Where would that be placed?

Neslee Canil Pinto made their first commit to this issue’s fork.

Neslee Canil Pinto’s picture

Version: 8.x-2.9 » 8.x-2.x-dev
Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.