when the event goes live, it’ll be a website you can login to and place pixels

the login system sends a DM to your account with a code to verify your identity, no passwords are used

oh shit i didn’t see this notification 😅

keep an eye out 👀

Oh hey it’s also toast’s 1 year as well 🎉

https://toast.ooo/post/3679257

@user works on all fediverse platforms, but !community does not

i was proposing for this to be a possible solution to make it work across all existing platforms w/o requiring all the other platforms to support lemmy’s system

if using lemmy, it could automatically make this change

this would primarily be used by other fedi platforms to easily differentiate community & users

eg if i followed @sc07@group.toast.ooo on mastodon it would for sure follow [email protected] and not @[email protected] (an account with the same identifier)

but if you search a community up on another fedi platform, it won’t always pick the community or the user (if they have the same name)

as far as the other platforms know, there’s one actor but points to two different accounts

afaik the webfinger spec doesn’t allow for multiple actors having the same identifier, like how lemmy does it (here’s what gets returned when a username matches a community and user)

how I was thinking about it the instance owners would pick the subdomain the communities would be placed on, everything would still route through the main host but external interactions (like following a community) would be routed through the subdomain

eg for blahaj.zone’s lemmy instance it could be setup as users sending in @lemmy.blahaj.zone and communities ending in @group.lemmy.blahaj.zone or something like that

not every community would have it’s own subdomain, no

community actors would just have the hostname part be a different domain eg

users:

• @UserA@toast.ooo
• @UserB@toast.ooo

communities:

• @CommunityA@group.toast.ooo
• @CommunityB@group.toast.ooo

It appears that proton’s is only for them and they don’t offer it to other websites unfortunately

https://proton.me/blog/proton-captcha

The instances page at join-lemmy is completely automated

This definitely needs to get pushed to the two main devs for lemmy as they control that website