Allow for posting attachements with remote media uri #318
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#318
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?
Basically: don't require people to upload media to post it.
this is more for api stuff then front end stuff, but if i want to make a post i can't have the attachment be "beefox.xyz/warblehole.webp", instead if have to upload it to the instance. this may not be ideal in some situaitons.
(yes i know this is a really neiche thing, feel free to shoot it down i will work out some other way c:)
this probably isn't possible - the way the API works is that you upload media and are given an ID, which you then pass to on the status creation call
there's no link between URL and status, just media ID and status
Maybe there could be an extension API route that receives an URL, downloads it server-side, and gives out the media ID which is then used on status creation?
darn :/
though i will say in activity pub, attachments are just links to the file, so it is technically possible, however it might mean a bigger rewrite then i hoped it would be
Write your post in HTML and hotlink the image?
that's my current plan, however then we encounter the issue of mastodon not supporting any formating including images in posts
If it's just to have an API endpoint to do this; I wonder if it's already possible using the AP c2s API 🤔
I have a simple example here for AP c2s that you can maybe play with to see if you can get something working https://git.pleroma.social/pleroma/pleroma/-/issues/2937
oh yes this is useful!
I will have to think about how to implement it on my end but this is helpful c: