!hannah 🦄(@infosec.exchange) is a user on infosec.exchange. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

Could you make my first steps in mastodon easier and give me some accounts writing about #itsec, #infosec, or #datascience?

!hannah 🦄(@infosec.exchange) @superruserr

@jester Welcome to infosec.exchange and .

Here are some accounts where I've had recent conversations with about and so on:

@gilscottfitzgerald @TheGibson @finux @galaxis @frootware @gozes @varx @tinker @dewb @nathanpruitt @rysiek @uranther @mastor @lattera @crowd42 @jeff @Nitron @garrett and of course @jerry too.

(sorry for the lack of newlines)

· Web · 10 · 23

@nathanpruitt @superruserr @jester @gilscottfitzgerald @finux @galaxis @frootware @gozes @varx @tinker @rysiek @uranther @mastor @lattera @crowd42 @jeff @Nitron @garrett @jerry

Plenty of nerds here. Thanks for the shout-out. Enjoy your time here. Lots of fun projects to work on on this fairly new platform.

Also if you're into Ruby devel, strongly recommend the mastodon-api from the official tootsuite repo.

Welcome again

@superruserr @jerry @garrett @Nitron @jeff @crowd42 @lattera @mastor @uranther @rysiek @nathanpruitt @dewb @tinker @varx @gozes @frootware @galaxis @finux @gilscottfitzgerald @jester

There's the bug again...

I was wondering why the follows were coming in, and I found this...

My handle is @thegibson all lower case, but Mastodon seems to often capitalize my name due to a cached account out in the fediverse somewhere.

Anyhow, Welcome aboard.

Beside you in time.

@thegibson @jester @gilscottfitzgerald @finux @galaxis @frootware @gozes @varx @tinker @nathanpruitt @rysiek @uranther @mastor @lattera @crowd42 @jeff @Nitron @garrett @jerry @superruserr

That's on mastodon.social btw, not sure why.. Id totally bug report it buddy, definately looks like you may potentially exist twice in the accounts table over there with multiple unique identifiers assigned to you.

@dewb @TheGibson
The two accounts from this instance have different avatars. One has the current one, the other one has 'I tried'

@samis @dewb and the problem now is that to rectify it, that change has to be made on every instance It's living on... this is complicated...

We really need a way to input a proxy address to rectify this.

@dewb @thegibson

I got this in my DB (see screenshot).

Was hackers.town reinstalled at some point?

@galaxis @thegibson yeah I checked my account stable as well but I only have him in there once thankfully so he probably doesn't have an issue with me. Those IDs earlier were his IDs from Mastodon.Social though so he exists in their system twice

@dewb @galaxis

Yeah... but It's been going on for a very long time... well before 2.32

@dewb @galaxis pretty sure the old one is cached on some servers, and autofill pops it up first...

Doesn't happen on in-line replies.

@thegibson @galaxis
I'd hate to be the one who writes the migration for that issue. lol

Once someone works on migration for it and people upgrade. It should fix permanently.. on the instances that chose to upgrade that is....

The release with that fix is going to suck depending how it's done.

@dewb @galaxis yeah, if you look at the dates on that account, It's from the original Hackers.town.

That account should be purged.

@dewb @galaxis

Too bad there isn't a way to assign a proxy address to my account on my server.

@dewb @thegibson Maybe with some clever rewriting in the webserver instead of application logic?

@galaxis @dewb maybe.

The application will not allow the assignment of another account with the capitalization in place.

Is it urine the name or the account ID? I would assume the account ID, but that appears to be sequential so unsure...

@TheGibson @dewb @galaxis Update to 2.3.2, then you'll be able to create the account. Then update to 2.3.3, because that fixed that bug.

@bhtooefr @galaxis @dewb

Pretty sure this is a different bug, but I planned on running the upgrades today anyhow.

@TheGibson @dewb @galaxis Oh, I'm sure it is, but if you actually WANT the differently-capitalized account to somehow experiment with, 2.3.2 has a bug that will let you make it.

@bhtooefr @galaxis @dewb @thegibson

Pretty sure part of the fix should be a query like

select distinct on (upper(username), upper(domain)) * from accounts

For listing accounts. That way irregardless of case sensitivity it will always assume that the latest sequence generated for each account is the account that is actually in use

looks like @Krita
@Krita has this issue too.. I tagged both so they'll get this.

Krita the capital one i assume is the one you're using over there right Kri?

@dewb @krita @TheGibson @dewb @galaxis Except always using the latest is incorrect behavior in the case of accounts created in the 2.3.2 bug - the *OLDEST* is the correct one in that case.

There may simply need to be a way for the instance to specify which is the correct one, or for the instance to proxy as @TheGibson suggested?

@bhtooefr @galaxis @dewb @Krita @dewb

I am an old school smtp/Directory services guy...

I think that having somethng that works like a proxy mail address would be the correct solution.

I feel like this could be used by a rogue admin in a malicious manner, but an admin is an admin...

@bhtooefr @galaxis @dewb @Krita @dewb
@Krita

This has been going on for me since early December... this is why I am sure this is not so much a bug as a weak spot in how the account names are handled when a new instance is spun up in the same namespace as the old instance.

the issue is two-fold.

1. The username is alphabetically the same, and therefore a new account using proper capitalization is not possible.

2. The old name cached in remote instances. can't flush cache other locations.

@thegibson @dewb @krita @galaxis @bhtooefr

@Gargron already fixed the issue going further with new account signups with *later builds*. However the issue now lies in the existing data that still needs to be cleaned on other instances that arent your that have your account information. (data needs to be cleaned up which is why you have your issue)

@thegibson @dewb @krita @galaxis @bhtooefr @Gargron

That query would be a good starting point as you would know the latest account that was ever created by a user on a server (since identites are created sequentially) when federated presence introduces a new account on a server from a different domain from a server where the accounts data is being shared from.

@thegibson @dewb @krita @galaxis @bhtooefr @Gargron

*Not being a postgres guy*.. and due to the collation of the database being en_US.UTF-8.. i'm curious how psql handles collations within expressions / sort order / groupings / predicate lookups etc.. etc.

What I mean by that is..

en_US.UTF-8 is treating
a=A = false
a=a = true

when there may be a collation that treats

a=A = true
a=a = true

@thegibson @dewb @krita @galaxis @bhtooefr @Gargron

Fucky wucky!! A widdle fucko boingo! -- lol

I get to read some psql docs now and brush up on some things. (I dont generally work on this platform)

@thegibson @dewb @krita @galaxis @bhtooefr @Gargron

Also gargron likely doesnt read these messages from this account. So feel free to scream at him. (im not sure why, i think i may have upset him in the past some how or another :awesome_rotate: )

@dewb @Krita @dewb @galaxis @bhtooefr

So the fix is complex...

There can be a process that syncs the removal (or non-existence of cached account info on every instance.

There can be a way for admins to set a proxy address.

Remove caps sensitivity,(I think that the user number is likely more important though.

@dewb @bhtooefr @galaxis @dewb @TheGibson *Wanted* to use the lowercase one but getting the capitalised one every time, so yes.

@dewb @galaxis @TheGibson

Thanks for letting us know.

I knew that thegibson is at hackers.town but I did not realize this issue.

This is good to know.

(had to repost this...three time..because I did it again).

@galaxis @dewb

At some point...

That's humorous...

We are on our 3rd db... 😂

That's OK... since the beginning I have notified the fediverse that we were designed to fail... It's a hacker's server... we test in prod.

@superruserr @jerry @garrett @Nitron @jeff @crowd42 @lattera @mastor @rysiek @nathanpruitt @dewb @tinker @varx @gozes @frootware @galaxis @finux @TheGibson @gilscottfitzgerald @jester

Thanks for the #introductions! I lurk and try to learn #infosec where I can. I went to #DEFCON last year so now I am like ... Level 2 Ranger-Hacker [chaotic-good] :detective_g1:

Trying to become more security and privacy-minded in this wacky world. :cybre_glitch: Especially interested in applied #cryptography :crt_w_noise:

@gozes @dewb @lattera @TheGibson @gilscottfitzgerald @jester @finux @galaxis @frootware @varx @tinker @nathanpruitt @rysiek @uranther @mastor @crowd42 @jeff @garrett @superruserr well, I think you’re all great and I’m honored to be here with you. You all are worthy. Don’t think otherwise.

@jerry @gozes @dewb @lattera @TheGibson @gilscottfitzgerald @jester @finux @galaxis @frootware @varx @nathanpruitt @rysiek @uranther @mastor @crowd42 @jeff @garrett @superruserr - Also. There’s always one asshole in the group. I’m looking around and everyone looks nice. That can mean only one thing...