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.

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.

It's dangerous to tell people to _always_ rely on Mastodon profile green URL checkmarks as an equivalent of Twitter's old  thing: this advice is only valid on mainstream instances that have not modified (maliciously or otherwise) the URL verification code.

If someone wants to impersonate a celebrity/organization/etc., they can easily create a new Mastodon instance with modified green checkmark code.

#feditips #infosec cc: @gcluley

@djsundog ha! So could maybe start with a fork, put up a poll, let everyone shout for a bit, and that’s the next feature — shitpost driven development 
what even is zero trust, really? is NO factor authentication next? Is all we are dust in the wind? #infosec #afterhours
@gmarmstrong I get it. I also check the Twit drama as well. But what I find here is that this server managed by @jerry is interesting in that we all have a vested interest in its success. I've seen a number of conversations about volunteering, supporting the community, etc. That feeling of community did not exist on the Twit. Potentially something special here.
Friendly reminder that when you capitalize the first letter of each word in a Hashtag people who use screen readers can participate fully in conversations instead of having strings of gibberish read out to them. #MastodonTips #Accessibility #Hashtags

Today was “log day”, a thing me and the team like to do every couple of months. We take a look at our logs and check:

- log volumes are what we’d expect
- log “shape” and structure is as expected, because if not, something changed
- if we’re getting the most out of our logs in terms of the alerts they generate, this includes adding new alerts or removing old ones that don’t offer much value
- we’re not accidentally logging anything we shouldn’t be (secrets etc)

It’s a tradition I’ve had for a few years and it’s one I really believe in. Not to be confused with “leg day” of course, which is altogether different, but many consider to be just as important.