I'm adding new profile fields to #Smithereen, so I would like to ask the fediverse about what kinds of contact info one would expect to be able to add to their profile. So far I've seen:
Personal website/blog
Matrix
XMPP
Telegram
Signal
Phone number
Twitter
Email
I've not yet seen these in fediverse profiles but they are mainstream enough that won't hurt to add:
@grishka
I'm not sure Iif I've got the gist of what you are planning to do, but my understanding is that you want to add dedicated fields in the user's profile for their social contact info. If that's the case, then I wonder why jot letting the user to define the field names? Something similar to what mastodon does. The benefits are:
So, #Smithereen no longer requires a username when signing up. You instead get assigned one automatically, of the form "idXXX" where XXX is the ID for your user record. You can change it later in settings if you wish. Current Mastodon versions handle this change no problem.
The username is only visible in two places:
The URL of your profile
When someone mentions you
So it's not very important. Definitely not important enough to be a required field when you register.
In case someone wants possibly the longest thread on the fediverse for testing purposes, here you go: https://mastodon.social/@brownpau/112322747861701800
With the way I store replies in #Smithereen, this will soon exceed my limit of 256 levels ¯_(ツ)_/¯
Reposts are now done in #Smithereen. You can only make "quote-posts", not Announce reposts because Announce is too confusing and doesn't fit my vision. However, Announce reposts are no longer this half-assed thing like they were before. They now show up in people's profiles and use a different icon from my native reposts.
Since reposts/boosts are now stored as actual posts, albeit with a bunch of special-case handling in many places, they now appear in profiles too.
Smithereen's native type of repost will be the "quote-post", the one that creates its own separate comment thread. All this is specifically for compatibility with the rest of the fediverse predominantly using the Announce activity for reposting.
I want an opinion. If you have a rule to not allow signups with some email domain, would you expect it to also apply to signup requests, when your server is in manual-approval mode?
Safest might be to launch a server in manual-approval mode for a bit, and then see approval request with a clear red box or something saying "Blocked by email rule, do you want to override and approve the account?"
Mark that domain as suspicious so I take more time with this signup request.
And a third option: make signups open, except for the domain.
The second and third option require different UI and are technically specialized lists for different purposes than simple blocking. So I would answer with the first option.
Is there an #ActivityPub server where I need to parse HTML for <link type="application/activity+json" href="..."/> to get to the JSON representation of an object? I want to add support for this in #Smithereen but I need something to test against.
I like my approach with deactivation period better than what others do. For example, @pixelfed deletes accounts immediately and it turns out people change their minds on this stuff sometimes.