I’m new to Mastodon code and find it hard to understand exactly how some components are drawing and getting their data - If anyone could lend a hand or just answer a few questions, it would be amazing!
I’m also looking for admins who can install/test a branch or patch that extends the verify system in some nifty ways.
Please if you are familiar or just run your own instance, reach out because your help is greatly appreciated and could make the world a safer place.
This post is an automated archive from a submission made on /r/mastodon, powered by Fediverser software running on alien.top. Responses to this submission will not be seen by the original author until they claim ownership of their alien.top account. Please consider reaching out to them let them know about this post and help them migrate to Lemmy.
Lemmy users: you are still very much encouraged to participate in the discussion. There are still many other subscribers on !mastodon@communick.news that can benefit from your contribution and join in the conversation.
Reddit users: you can also join the fediverse right away by getting by visiting https://portal.alien.top. If you are looking for a Reddit alternative made for and by an independent community, check out Fediverser.
Nostr NIP-05 and Bluesky use .well-known or DNS TXT fields if youre looking for alternative implementations.
Privacy / ease-of-use: https://mastodon.social/@the_angel is founder of eBig Design here in NYC and an artist group working on a Mastodon instance. People love the Mastodon way of verify, but would like to make it easier. They’d like the confidence of confirming Twitter+LinkedIn+Medium but without always having to display these accounts. My job here is to insert links that seem to be rendered from the header.jsx component — any help, advice or suggestions appreciated!
Could you give more information about what you’re referring to? Extending the verify system? What’s the end goal?
