It is caching guarantees for a day. It shouldn’t do it for first time authentications I guess.
I’ll try to fix this today. At most, you will need to wait for a day. Sorry for the inconvenience.
Really? I’m glad to hear that. I prefer default UI but many people prefer Teserract because of its features. Thank you for continuing.
v1 excites me! As someone who has been using Lemmy since v0.17.0, I must say that Lemmy has improved tremendously.
You’re welcome. You have probably checked it by mistake. It is a bit confusing as there are about 10 checkboxes in the settings :)
You have checked “bot account” in your account settings.
Ok I should fix this one.
Hello! I just added manually. Now it should not check for Fediseer in theory. Can you try?
Happy if I gave an idea.
I just do query DNS records and fetch nodeinfo. Shouldn’t that be enough?
After verifying that the user is admin, will you continue to send PM code when logging in? If so, then software without a message receiving mechanism will still not be able to use Fediseer.
I suggest you consider the way I did it in Lemmy Federate. I create a private/public key pair and ask admins to add the public key as a TXT record. If the private key entered while logging in matches the public key in DNS, admin can log in.
This way it is not necessary to query the user with webfinger and send a message. You also avoid the hassle of distinguishing between different messaging structures in the Fediverse.
Of course not. I made this change to make the whole fediverse compatible with Lemmy Federate, not just Piefed.
Please see this because that’s not the case: https://lemy.lol/comment/20647547
Actually, Lemmy Federate is not tied to lemy.lol since this update: https://lemy.lol/post/46419115
Piefed.social should decide if they want to add their instance to the Lemmy Federate. I’m not blocking anyone. In fact, there are already two Piefed instances registered to Lemmy Federate. But these instances are using generic ActivityPub client instead of specialized clients unlike Lemmy and Mbin instances.
I’m not against Piefed but I’m not gonna work for a Piefed specific code either for reasons you can imagine.
It’s good to see an auth library with built-in OIDC server. Thanks for the post I’ll check.
It’s cool but without legacy support, there’s no way mainstream attention. Do what Tutanota does, encrypt whenever possible.
This depends on the instance of the video being used. Some instances clone a copy of the video, some use proxies, and some send the link directly to the user. I don’t recommend it if you have limited bandwidth.
Sorry for the wait, fixed.