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.

Sign up for GitHub

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

Jump to bottom

Posting a status linking to $LOCAL_DOMAIN/.* results in empty content, but only for Markdown and HTML posts #40

Open
aescling opened this issue Apr 8, 2022 · 0 comments
Open

Posting a status linking to $LOCAL_DOMAIN/.* results in empty content, but only for Markdown and HTML posts #40

aescling opened this issue Apr 8, 2022 · 0 comments
Labels
LV.1: Application Backend @ installing and running the application LV.5: Features Frontend @ Featureset STATUS: bug Improper behaviour STATUS: need info Further information is requested STATUS: upstream This issue should be solved upstream if possible

Comments

@aescling
Copy link
Contributor

aescling commented Apr 8, 2022 •
edited
Loading

On GlitchCat, posting a link to, for example, https://glitch.cat.family/about/more is only possible in plaintext statuses.

I have yet to confirm if this is a problem with Glitch Edition generally (and thus if it’s really a LOCAL_DOMAIN thing); I have also not confirmed that other instances can link to us, but I would be very surprised if they can’t (since a local development instance Kibicat Mastodon was able to link to the GlitchCat /about/more).

Mastodon seems to dislike linking to localhost (very reasonable) so testing if LOCAL_DOMAIN links nuke their statuses is fruitless on a local development instance.

Mentions do get processed and attached to the contentless statuses.
@aescling aescling added STATUS: bug Improper behaviour STATUS: need info Further information is requested LV.1: Application Backend @ installing and running the application STATUS: upstream This issue should be solved upstream if possible labels Apr 8, 2022
@aescling aescling changed the title Posting a status containing a link to anything on $LOCAL_DOMAIN results in a status with empty content, but only with the Markdown and HTML content types Posting a status linking to $LOCAL_DOMAIN results in empty content, but only for Markdown and HTML posts Apr 8, 2022
@aescling aescling changed the title Posting a status linking to $LOCAL_DOMAIN results in empty content, but only for Markdown and HTML posts Posting a status linking to $LOCAL_DOMAIN/* results in empty content, but only for Markdown and HTML posts Apr 9, 2022
@aescling aescling changed the title Posting a status linking to $LOCAL_DOMAIN/* results in empty content, but only for Markdown and HTML posts Posting a status linking to $LOCAL_DOMAIN/.* results in empty content, but only for Markdown and HTML posts Apr 9, 2022
@aescling aescling added the LV.5: Features Frontend @ Featureset label Apr 10, 2022
@aescling aescling mentioned this issue Apr 11, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
LV.1: Application Backend @ installing and running the application LV.5: Features Frontend @ Featureset STATUS: bug Improper behaviour STATUS: need info Further information is requested STATUS: upstream This issue should be solved upstream if possible
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aescling