home.social

Bailey Townsend

@[email protected]
View on hachyderm.io →
  1. Bailey Townsend @baileytownsend ·

    Have y’all heard the gospel yet about the xteink devices yet?

    #esp32 #eink
  2. Bailey Townsend @baileytownsend ·

    RE: hachyderm.io/@baileytownsend/1

    I want to follow this up with an AMAA (ask me anything !)
    I've done a few of these on and thought it might be fun to do one here! I don't believe in dumb questions, so please ask me any you may have! Happy to answer anything, or at least hopefully point you in the right direction! Feel free to reply your questions to this post.

    Also feel free to even ask me stuff like "Is atproto really ", "Aren't relays/PDS expensive?", "What do migrations look like there?", etc. Nothing is off the table, and I'd be glad to answer anything! Good chance I will have questions in the future about and that I will be asking!

    #atproto #bluesky #decentralized #activitypub #mastodon
  3. Bailey Townsend @baileytownsend ·

    @katzenmann Hey! Been checking out today, but I come from land. Relays have gotten pretty cheap to run now, thankfully. They used to keep a mirror of the whole network, but now only keep a couple of days. Can squeeze by with less than $40 on them nowadays, or even cheaper.
    whtwnd.com/bnewbold.net/3lo7a2.

    We also have a bunch of community ran ones, a few listed at this beautiful URL lol compare.hose.cam.

    Relay's also don't directly do feed aggregation, but they do feed the feed with the posts. But that can also be swapped out between relay's or even something called JetStream, which is a diet relay. Feeds listen to this firehose and filter out posts on how it wants, like which content it wants to show. For instance, here's a feed URL for posts about cornbread lol
    api.graze.social/xrpc/app.bsky

    The feed just returns the at-uri's which can be used to hydrate the feed from getting posts from an AppView or connecting directly to the user's PDSs

    #activitypub #atproto
  4. Bailey Townsend @baileytownsend ·

    In atproto land, the PDS (my handle is pds.dad) is a bit of my specialty. Thought I'd talk about some stuff I really like over here that I think the Mastodon instance did better.

    - Having a nice rendered about page is super nice. Shows some quick stats as well. For a PDS you have to code your own if you want that and that's what I did with selfhosted.social. But it's very nice to have a place to create an account on the server, show rules, and just kind of make it welcoming.

    - Pending acceptance to the server. Was very cool that when I created an account on hachyderm.io that it put me in a bit of a pending area till moderators accepted me. The PDS has 2 ways to gatekeep creating an account. 1 you can only create an account if you have an invite code, 2 it's open but is protected from a captcha to stop bots. This was a custom thing I added with my PDS Gatekeeper project (tangled.org/pds.dad/pds-gateke). I kind of want to add pending invites to PDS Gatekeeper now after seeing how y'all do that here!

    - Multi factor and 2 factor authentication. Bluesky's PDSs have email 2FA because they have something similar to my PDS Gatekeeper called the entryway that sits in front of their PDSs. It handles that. But since that's not part of the PDS, they do not have 2FA built it. That is changing very soon with a PR to the repo. But it will be email 2FA. Was really nice to do the 2FA app or a security key, in addition, it looks like everything is default OAuth here. OAuth on atproto is still pretty new, but it's quickly becoming the standard.

    I think the PDS will catch up in a few of these areas, and they are pain points PDS admins have run into in the past. So it has been nice to see how something similar is also tackling them. I'm seeing some other pro/cons between each, but I mostly like to focus on the positive that I think each brings to the table. Teamwork makes the dream work.

    #atproto #protocols #mastodon #activitypub