Bluesky’s original “invite only but each person can invite” makes way more sense for bot management than “requiring photo identification” that can’t be verified and can be generated by ai.
Interestingly they’re basing it off the Bluesky atproto architecture. Seems like they’re keeping controlled sign-ups and setting the appview to only index (and only display) their own users.
And if they don’t break protocol compatibility, others could have a “read-only view” of their network from servers / clients that federate (comparable to a lemmy server which would reject incoming messages but still let you browse)
Bluesky’s original “invite only but each person can invite” makes way more sense for bot management than “requiring photo identification” that can’t be verified and can be generated by ai.
Interestingly they’re basing it off the Bluesky atproto architecture. Seems like they’re keeping controlled sign-ups and setting the appview to only index (and only display) their own users.
And if they don’t break protocol compatibility, others could have a “read-only view” of their network from servers / clients that federate (comparable to a lemmy server which would reject incoming messages but still let you browse)