Self Proclaimed Internet user and Administrator of Reddthat

  • 55 Posts
  • 34 Comments
Joined 1 year ago
cake
Cake day: June 6th, 2023

help-circle


  • This is sso support as the client. So you could use any backend that supports the oauth backend (I assume, didn’t look at it yet).

    So you could use a forgejo instance, immediately making your git hosting instance a social platform, if you wanted.
    Or use something as self hostable like hydra.

    Or you can use the social platforms that already exist such as Google or Microsoft. Allowing faster onboarding to joining the fediverse. While allowing the issues that come with user creation to be passed onto a bigger player who already does verification. All of these features are up for your instance to decide on.
    The best part, if you don’t agree with what your instance decides on, you can migrate to one that has a policy that coincides with your values.

    Hope that gives you an idea behind why this feature is warranted.




















  • The downvotes you can see (on this post) are from accounts on your instance then. As this post is semi inflammatory it is highly likely to have garnered some downvotes.

    Edit: I guess I was wrong regarding the logic of how downvotes work when we block them. As the http request (used too?) return an error when responding to a downvote. I’ll have to look at it again. As the only way it was/is 15, is if:

    • we kept track of downvotes and sent out the activities notification
    • your instance got the notifications from other instances about our post, (which is not how Lemmy works unless I’m seriously misunderstanding it.)