@darius hey I have a question you may be able to a good person to ask that I was thinking about today. Whats the feasibility look like to get rel="me" working with dat:// links in mastodon profile fields? whould that require a mastodon insstance running a dat base node in order for it to verify?


@liaizon Mastodon would need to be able to speak over the dat protocol and make the query to confirm. so we'd have to add a dependency to Mastodons server of a library that can essentially do "curl dat://" and then use that to confirm the link

@darius cool thanks for the answer! I will file this in my head for "open an issue in 2021" #MastodonIdeas

@bamfic @darius do they even have verified links using rel="me" at all?

There's #spritely and other fediverse projects likely to support p2p storage this year, so leverage is coming 😉
@bamfic @darius

@AceNovo @bamfic @darius oh thats a good idea for a place to bring this up early. thanks.



Having a client that supports Dat isn't too crazy if you're already using JS

@RangerMauve @liaizon right but this should be serverside for security reasons; the Mastodon server is in Ruby



Dang... I guess the only reliable method would be to use the node.js dat-cli. I think Karissa was mentioning that there should be an installer that people can use without going through node and npm

Sign in to participate in the conversation
Friend Camp

The decentralized web is about trust. You should only join Friend Camp if you personally trust Darius Kazemi with your social media data. You probably only have that level of trust if we are IRL friends or have been internet friends for a long time. Generally speaking this is a small, closed community. In the end, Darius is the arbiter of what is allowed here. If you don't have a good idea of the kind of behavior that flies with Darius, again, you probably shouldn't join this instance. In the interest of specificity, we do have a code of conduct and privacy policy which you should read. Friend Camp features several modifications that were requested by our users. * you can log in via any subdomain, which means you can log in to multiple accounts in the same browser session (for example, log in once on friend.camp and then as another user on alt.friend.camp) * they are no longer called "toots", they are now "posts" * if you have a locked account and you get a follow request, a reminder appears under your "post" button (on normal Mastodon mobile it is otherwise buried in a sub-menu and you might not see it for a long time) * the emoji dropdown is a neutral smiley face instead of the cry-laughing smiley @mentions are rendered as "@user" for a Friend Camp user and "@user@domain" for remote users. This helps clear up when you follow two people who have the same username on different servers. * there is a "never ask me again" checkbox on the confirmation for clearing your notifications -- more info here * When an mp3 link is in a post, we also embed an inline mp3 player. git commit here * 500 characters of profile text git commit here, requested by @deerful Important Bit from the Privacy Docs: If you want decent privacy (the info doesn't leave this server), the only way to do that is to set your account to private, only accept friend requests from other friend.camp users, and only ever @ mention other friend.camp users. Once you start talking to people on other servers, all bets are off. Any private message you send to someone on another server could be looked at by the admin of a different server. This is kind of like email: if you are on a private email server, and you send an unencrypted email to a gmail account, congrats, Google now has the content of that email. But also, you do this every day, so, hey. The internet! Our beautiful icon is based on photo3idea_studio from www.flaticon.com, licensed CC 3.0 BY. It has been modified by @casey@friend.camp!