this post was submitted on 27 Jul 2023
66 points (98.5% liked)
Fediverse
28395 readers
253 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
ok sounds like it's not a feature - the link format i suggested includes both the instance ID and the instance url, so it would be possible for your home server to use that to preprocess to a useable link. I wonder if there's a suggestions box π
I just got a PR merged today that might help with this. I'll start experimenting with it more over the next week or so.
Basic theory is that I can detect at least lemmy posts in the comment bodies and then rewrite those to your local instance. Primarily question is going to be performance, as remote network calls will be necessary.
oh that's awesome! yeah i can see it being an issue especially if that post isn't already federated. would be a great quality of life improvement though.
Ya if it's not federated already, I'm thinking the link will just remain as-is? Then comes the question of what happens after federation is complete? Ideally I'm thinking to do these rewrites as the comment containing the link gets federated so it only happens once, but that prevents updates... If I do it during someone looking at the post, then that becomes a lot of network traffic...
Still a lot to plan out initially and then propose to the devs for feedback... So it'll be awhile still.
yeah that seems entirely reasonable. it'll still be a big improvement in most cases. also even if it only happens as it federates initially it'll probably still catch many cases. is it possible to do a follow-up check only for links that weren't updated the first time? if you could store a cool-off and maximum number of tries that would probably keep it light and as functional as possible.
when serving posts with un-processed links that haven't been updated, and it hasn't been checked in the last 3 hours, re-check for a federated article and update. do this for up to 24 hours after the comment is posted, after that just give up? that gives it a few opportunities but doesn't continue to waste resources if it's unlikely the link will be resolved.
I'm not sure if it's easy to add columns to track those attempts though.
Yeah, I was disappointed that federation didnβt automatically log you in everywhere like Google across its services, or that you cannot just βlog in with [your home instance]β like OAuth.
(See my other comment for pondering how this could work)
I even tried using my feddit.de credentials (with @feddit.de appended, of course) on another instance, assuming the website code would notice the @ and pass them on to feddit.de instead. @ChaoticNeutralCzech@beehaw.org
I got very confused and tried clicking all kinds of stuff, ending up with a dozen accounts across the Fediverse. I am not the only one who did, apparently.
You two can stop now. It's not funny.
I think full federated auth across servers is a much more difficult problem - it'd be nice but outside the scope of this request!