Yes, they started the restriction a year ago. For a future reference, here's the announcement about the restriction (written in Japanese): https://support.misskey.io/hc/ja/articles/7604557294607
nmtake
I think it doesn't work. I skimmed Lemmy source code (search scrape_text_for_mentions
if you're interested)
and found this issue so I'm almost sure the mention in the post body
doesn't work, but haven't tested, so I used the word may. Sorry for your confusion.
FYI username mention in a post body (not in a comment) may not work.
Thanks for writing the summary for the current image-proxying related issues. I prefer the "proxying images route" for better privacy, but its drawbacks sounds worse.
If Lemmy has a user-customizable setting like "Don't load external media automatically" (including images, videos, etc.), I'm happy with the "passing through external images" route.
Yes, fenced code block with specifying langauge may work as a workaround.
```text
systemctl --user cat emacs
```
but I said "inline" explicitly.
lemmy-ui: Highlighting some words blindly in inline code is really annoying. For example,
systemctl --user cat emacs
pactl load-module module-switch-on-connect
Since it's a MediaWiki page you can get Markdown source of the page with appending action=raw
query to the URL.
Strong focus on privacy and security (all authentication with the Lemmy API is done through secure httpOnly cookies, user IP addresses are not leaked to external image hosts, etc)
Awesome. The current lemmy-ui sends a lot of traffic to other Lemmy instances to get pictrs-cached images, so this is huge improvement. On the other hand, on next.lemm.ee those requests seems to be gone. As feedback, I noticed this page still seems to send a request to imgur, ~~and the text is difficult to read because of the low-contrast theme.~~ (edit: fixed and now completely readable. thank you @[email protected] )
Glad it worked. I didn't know the endpoint before reading your post.
As you said, GET /resolove_object
(https://join-lemmy.org/api/interfaces/ResolveObject.html) may work:
$ post_id=9589178
$ curl 'https://lemm.ee/api/v3/resolve_object?q=https%3A%2F%2Fprogramming.dev%2Fpost%2F${post_id}' | jq .post.post.id
22873872
$ curl 'https://lemm.ee/api/v3/post?id=22873872' | jq '.post_view.post | [.id, .name]'
[
22873872,
"How do you get the url or id of the same post on a different instance?"
]
Firefox has "permissions.default.image" (link) option that disables image loading, but this Wikipage is very old so I'm not sure whether it works properly in current FIrefox.