Add Lemmy

kepic

Name: Lemmy
Homepage: https://join-lemmy.org
Short description: A federated link-sharing platform similar to Reddit.
Optional API documentation URL: https://join-lemmy.org/docs/en/

Profile page would be a good place for a string.

yarmo

Since Lemmy is ActivityPub-compatible, hopefully this one will just work when we get the unified ActivityPub claim verification [1] working.

[1] https://community.keyoxide.org/d/35-unify-verification-for-activitypub-compatible-platforms/2

MgaicLike

yarmo It just works 👍️

aronza

MgaicLike yarmo I cannot seem to get kbin.social to work.

These instances do not appear to show a "profile page" like mastodon does.

So for kbin.social, i added a separate post at https://kbin.social/m/u_aronza/t/81501/Alberto-Ronzani-Keyoxide-Proof
however, as you can see on https://keyoxide.org/DD438872F3CCC3D6919B59A9E46ED6748A54AC68 that url gets totally mangled, for some reason...

What should be done? The docs are quite vague about how to add a post, to be honest...

MgaicLike

MgaicLike But the profile does not get displayed in the typical user@instance.tld format, but in form of a link to the profile...

vladimyr

MgaicLike

MgaicLike But the profile does not get displayed in the typical [user@instance.tld](mailto:user@instance.tld) format, but in form of a link to the profile...

Is this still the case? Cause according to https://codeberg.org/keyoxide/doipjs/src/commit/edc3f401bc88055339e59c7ad644a015f16c4c23/src/serviceProviders/activitypub.js#L80-L99 it should be formatted in standard @username@instance.tld form? 🤔

EDIT: I somehow missed yarmo 's response. Because this is now fixed and the linked Kbin post by @aronza does not contain a valid claim I'm marking it as solved.

MgaicLike

aronza kbin is not Lemmy, therefore it probably is worth open another thread for it...

yarmo

I have added specific instructions for kbin and lemmy:
https://docs.keyoxide.org/service-providers/kbin/
https://docs.keyoxide.org/service-providers/lemmy/

aronza that url gets totally mangled, for some reason...

That was indeed an issue but should now be fixed. If you add the fingerprint to the post you link to, it should display fine now