@sec_yote_agenda Personally, I think that instead of #Escrow making actual #Reputation as key decision part is a more viable option.

After all the #Furry community should be able to use #Keyoxide (or even #Keybase) to verify producers and reviews to make scamming harder and more expensive.

Sadly this would kinda raise the bar for new suitmakers, but it would reward those doing their craft longterm and having good customer relations.

Escrow exist for juristictions w/o consumer protections...

@Suzimiya vielleicht nen Beleg um zu beweisen dass wer Zugang zum Account hat?

So das #Keybase-Prinzip...

@slyborg @Garwboy Oh yeah...

I forgot #linktree!

Anyone else remember #Keybase?

https://mstdn.social/@kkarhan/110656287268155132

@atomicpoet everyone who trusts any of the #PRISM collaborators, espechally #NSAbook, disqualifies themselves for any #security-based discussion - period!

Fact is: #AllGafamsAreEvil and every #SingleVendor / #SingleProvider solution is either #backdoored by governments (i.e. #ANØM) or literally illegal and will be attacked (i.e. #EncroChat).

So no, don't trust #WhatsApp nor #Threema nor #Telegram nor #Keybase nor #Signal.

@wintermute @spockthebest @TomLarrow

ALL OF THESE!

Not to mention:

- #Discord's ToS are unacceptable.

- Discord is slow af.

- I'm not gonna sign up for a shitty account just to read something that should be in the manpages if not git of a project.

- Again: Projects are then shackled to a shitty provider on a whim with no contractual obligations whatsoever...

- There's a reason #DeterrenceDispensed quit #Keybase...

https://mstdn.social/@kkarhan/110519612338936271

For everyone who liked https://keybase.io but is rightfully mad at their #sellout and subsequent self-destruction and #bloat, there's a new and better option in town: https://keyoxide.org

Basically #KeyOxide does the same as the original #Keybase:
Public proofs with #GnuPG / #OpenPGP signatures.

I intent to check it out soon...
Maybe even do some step-by-step tutorial?

:boost_ok: as always...

@kusuriya @mail *nodds in agreement*

#Keybase in it's original form as a means to sync and host #Pubkeys and #verify accounts is good, but them selling out and snitching on users [i.e. #DeterrenceDispensed] is inexcuseable.

OFC a privacy & encrypted-only eMail provicer would've to offer a #Keyserver to provide #Pubkeys for the eMail adresses of users...

Ideally something that literally allows automatic pulling like keyserver.mailprovider.example/emailadress@mailprovider.example.pubkey.

Seriously, the sheer fact that something as trivial as a #Cookie-#Stealer was successful is kinda embarrassing.

Like doesn't #Google / #YouTube have a "logout all devices" kinda button and allows to literally revoke all #Cookies

Cuz that's something so basic even #Keybase has it...
https://youtu.be/yGXaAWbzl5A?t=209

@evacide Never use #SingleVendor / #SingleProvider services and practice #ITsec, #InfoSec, #OpSec & #ComSec.

No, neither #Signal nor #Keybase nor #Threema or any provider will save anyone's ass from getting busted.

Use #XMPP - #OMEMO or XMPP - #OpenPGP / #GnuPG instead!

I do not plan on deactivating my #Keybase... By I plan on slowly ceasing my activity on it. So, if it suddenly goes away, so be it... But I won't be linking to it or promoting it in the future.

Just a heads up!

@travis @QasimRashid I don't use #Keybase for #Chat at all, but solely to publish my #pubkey...

@Sheril I recommend using #linktree & #Keybase to #verify oneself, as :verified: is a regular emoji one can just add to a profile.

Trastejant una mica #Hashnode he recuperat un article que tenia sobre #Keybase

Fa força goig tot i que miraré de completar-ho

https://bloc.in4matics.cat/keybaseio

@denebeim That's just the Twitter one - When I deleted all my Twitter posts, my proof broke so I figured I'd have it as my only post :)

Looks like the Mastodon proof broke a couple of years ago, one of the notes I read from the release notes was that since Keybase hasn't been touched since Zoom bought it, there was no point maintaining the proof system. Take that, #Keybase! :)

@denebeim That's just the Twitter one - When I deleted all my Twitter posts, my proof broke so I figured I'd have it as my only post :)

Looks like the Mastodon proof broke a couple of years ago, one of the notes I read from the release notes was that since Keybase hasn't been touched since Zoom bought it, there was no point maintaining the proof system. Take that, #Keybase! :)

@stux -- Heyo, is there a way to get in touch directly? It's regarding #Keybase proofs.

@stux -- Heyo, is there a way to get in touch directly? It's regarding #Keybase proofs.

I don't even use #keybase any more, but somehow I am still mildly upset that my keybase to #Mastodon proof didn't work :)

Anyone knows how to add #Mastodon IDs to #Keybase? I know Mastodon software has dropped Keybase authentication protocol support, but I'd be glad if I can find another workaround.

@engarneering Some additional background from the Mastodon dev team on removal of #Keybase support:

https://github.com/mastodon/mastodon/pull/17045