Guthrie McAfee Armstrong

33 Followers
119 Following
23 Posts

#Quaker Friend in #Atlanta 🕊️

Mostly on Bluesky currently: https://bsky.app/profile/gmarmstrong.dev

New to Mastadon and excited to be here. Long time FLOSS advocate, decades career in analog and digital media (audio / video / graphics / editing / art).
Shout out to my friend @gmarmstrong

I love all of you and I want nothing but the best for each of you, particularly those on infosec.exchange. I understand that Mastodon isn't Twitter, that DMs aren’t end-to-end encrypted, that we are spread across different instances and it can be hard to find your friends, and that an instance can go away at any time, and that translating posts doesn't work correctly, and there is no native giphy support, and that some instances are overwhelmed and super slow, and that you don't think the federated model can scale to a billion users, or that it doesn't support full text search of every post and account, or that we can't comply with the GDPR, or that we don't support quote tweet style functionality, or that we shouldn't collect IP addresses, and many other things.

The fediverse is a work in progress. I've been here for going on 6 years. In that time, it's come a long, long way. That said, Mastodon is not going to appeal to everyone. The decisions I make are not going to appeal to everyone. No one is forcing you to be here. No one is forcing you to disclose your personal secrets into a network of federated servers running by volunteers and hobbyists. NB: this is not Twitter. It has some similar functionality, but it is not Twitter. Parts of it are better, IMO, and parts are not. The security community is generally among the most skilled and competent IT people the world has to offer. Mastodon is open source. Do you see where I'm going?

I set this instance up a long time ago for reasons I don't even remember. I have poured my soul into this thing because I believe in the importance of this community. I have effectively peaked in my career as a CISO and I and my family live well. I am not running this instance for fame, money, a better job, or anything other than wanting to foster a community of people that can learn from each other and make the world a better place. That's it.

As I've said in several recent interviews, I felt particularly obligated to ensure the security community had a good landing spot in the fediverse as everyone was running for the doors in Twitter. We've grown from 180 active users to about 30000 in the span of 3 weeks. I do not expect everyone to stay. Some will set up their own instances. Some will move to one of the other excellent security focused instances. Some will give up and move to on to some other social media. And that is OK. While I am super excited to see the buzz here, I don't have subscriber targets, engagement targets, retention targets, or anything else. The only metric I hold myself to is whether I think this is serving a useful purpose to the community.

I appreciate all of you, regardless of where you land. Infosec.exchange has been here for a long time and will continue to be here for you.

@shengokai … it’s really astounding how many of your repliers have basically been repeating “whatever, go make your own instance/software for Black people,” as if this isn’t a feature that we can easily implement on Mastodon for everyone to share.
@shengokai Yes, not to mention the increased vulnerability to mass harassment or even defederation that such instances would have to face. I have the freedom to choose to exist on whichever of the many Mastodon instances that exist, and that freedom should be available to everyone, without having to worry about whether a simple mode of communication like QTs would be properly displayed on the rest of the network.
@erkattak It also makes it easier for users to alert their admins—and each other—when a vulnerability still needs to be patched on their instance.
@shengokai This is a great point. The QT design we’re familiar with was one in which a QT was (almost) hidden from view (and thus shielded from feedback by other repliers), relative to direct replies. Would something functionally equivalent to replying and then boosting your own reply (but with a single UI action) be preferable to the old design?

So, to conclude. I think that implementing QTs needs to be done with an eye towards the specific affordances of mastodon and an eye towards the history of their use. Further, I think there are a lot of creative technical solutions to the QT problem that don't involve mirroring its use on twitter. Finally, I think that people are just refusing to learn from over a decade of lessons about QTs in their arguments against them.

That's my take.

LB: I think the time before lawyers descend on brands.town is getting short, but they are going out with a bang, and I'm fucking here for it. Plus there's now new weird mastodon-specific shit-posting (all the instances in the comic are Problematic) that will be understood absolutely nowhere else, which I also love.
@arktronic @gcluley Very cool! That is a good sign, and the same happens for me on your profile. Still, you've raised a good point about how another instance (or even just a website that looks like a Mastodon interface) can be deceptive.
@arktronic @gcluley Interesting! I suppose the home instance could have been caching its own verification from earlier. I've never dove into the codebase. Any #MastoDev folks out there able to provide some insight?