• 1 Post
  • 13 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle
  • For user/password/jwt, it’s needed to find the post id and the comment id in your instance’s database. No instance will offer you free post/comment id search unless you happen to be a user.

    Yes kbin is still not supported, I actually tried implementing it today but it doesn’t have a proper sesrch API like lemmy (finding a federated post id in my local instance’s databse). Kbin is still in beta so.




  • All you said is true if you are browsing through your instance, but if you were browsing another instance’s website and saw a post or if someone sent you a link to a post in an instance you don’t use, then you should figure out a way to see that post through your instance. In Mastodon, you go to search and paste the post link. In Lemmy, you do something similar. Those can be done but are quite tedious. This problem is what FediRedirect aims to make solving it more convenient.




  • Some redirections aren’t supported (bc Mastodon isn’t fully compatible with Lemmy), and sometimes it doesn’t work bc of a server problem (your instance doesn’t federate with that link’s instance). However, FediRedirect is still in beta, open any issue here: https://github.com/ManeraKai/fediredirect.

    Also, why does it require my login credentials.

    For lemmy:
    (Username and Password) or (jwt) are required for resolving /post and /comment. If Username and Password didn’t work, go to your instance’s cookies and copy your jwt.

    Same for mastodon, but it only has the read:search permission (scopes aren’t implemented in Lemmy yet)



    • Say a friend sent you a lemmy.world link, you want to reply to it but you only have a programming.dev account, so you redirect the link to programming.dev that has your account.
    • Say a friend sent you a lemmy link, but you only have an account in kbin, so you redirect to kbin (kbin is not implemented yet).
    • You want to see a post in your own instance’s UI and Theme.
    • You want to use Pleroma’s UI not Mastodon’s UI and vise versa.