[BUG] Telegram doesn't show the extract of my article... #938
Labels
No labels
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#938
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When I copy the URL of my article to telegram, the extract of the articole doens't show. The links to the articles are
https://amreolog.duckdns.org/~/SoftwareLiberoEticaDigitale/esame-a-distanza-con-zoom-e-seb-no-grazie
https://fediverse.blog/~/SoftwareLiberoEticaDigitale@amreolog.duckdns.org/Esame%20a%20distanza%20con%20zoom%20e%20SEB%3F%20No%20grazie!
I expected that under the message telegram shows the domain name, title, subtitle and the image of the article.
I have tried to use the @WebpageBot
I have tried to change the article image with a lower resolution(1024x560) and a different image format (JPEG) but the issue.
The issue doesn't happen with another fediverse.blog article like this
https://fediverse.blog/~/%D0%A0%D0%B0%D1%81%D1%81%D0%BA%D0%B0%D0%B7%D1%8B%D0%90%D0%B2%D1%82%D0%BE%D1%81%D1%82%D0%BE%D0%BF%D0%B5%D1%80%D0%B0/%D0%92%20%D0%B5%D0%B1%D0%B5%D0%BD%D1%8F%D1%85%20%D0%B2%D1%8B%D0%B5%D0%B1%D1%83%D1%82%20(Final)
Append the last character "!" to the address bar in your browser, and then you should see your article.
In some environment (like this Gitea issue board!), "!" desn't seem to be recognized as a part of URI. This is not a problem of Plume, but environment you paste the URI.
Trailing exclamation mark isn't encoded because of Rocket's bug. Upgrading to Rocket 0.5 solves this problem.