If there's anyone working on an Open Source Slack (or Keybase) alternative, hit me up. I run a UI design agency and we'd love to help design a better interface for an open solution that we and others can use. Find my details in my profile, or go to http://fairpixels.pro
I think I heard that the matrix people are looking for ux/ui people to improve Riot. https://matrix.org
Do note that matrix.org is the homepage for Matrix, which is more about the protocol itself. https://riot.im is probably more relevant for design / UI / UX work.
Note that they will need UI/UX experience more and more as time goes on, especially if Purism's Librem 5 is fully funded.
I just changed phones and found this really simple. You can just store a phone number with Google and receive an SMS key if you forgot to print off a key before changing phones. Everything seems to be working pretty well for me and I noticed improvements since last using the app 1+ years ago, but obviously can't guarantee it's still being updated.
That might work with Google itself but TOTP based 2FA codes aren't specific to Google. They can be used out of band by anyone and the SMS approach wouldn't apply to anybody else.
There's a few. One's Mattermost: https://about.mattermost.com My company has been using it for a while.
We'd love to contribute (with design). Are you aware of anyone interested in collaborating. We're looking for something that we can use ourselves and thus contribute to crafting a better experience around the software.
Hi @fairpx, Mattermost team here, we'd love to have your help!
They don't really address the fact that every single Slack "leak" is from someone already part of the team taking screenshots of the conversation. How does any kind of encryption help that? Also doesn't mention everything you lose out on with this approach - like searching through message history. It's a neat product I guess, but mentioning Slack in every single line seems more to get eyeballs than a valid comparison…
Search could be done locally if the client downloads the whole message history. I don't know enough about how Teams works to know if that's actually something a client can do right now, but it should at least be technically possible. Another alternative is simply running a bot that indexes everything and provides search. You can run the bot in-house so you keep control over your data.
I think I'm more uncomfortable with the idea of entire message histories walking around on disks of laptops and phones (not to mention that's a giant problem on phones because of storage/horsepower) than I am with the idea of slack being able to read everything...
If there's anyone working on an Open Source Slack (or Keybase) alternative, hit me up. I run a UI design agency and we'd love to help design a better interface for an open solution that we and others can use. Find my details in my profile, or go to http://fairpixels.pro
I think I heard that the matrix people are looking for ux/ui people to improve Riot. https://matrix.org
yup, we are! if you’re interested in helping us (we’re the decentralised e2e encrypted open option) then would love to talk: i’m matthew at matrix.org.
I don't really get it. I have a Keybase account. It's attested on my social media accounts (including on HN). It includes a private key on my personal laptop and one on my phone. I haven't extended it to my work laptop because I don't want my company IT having access to a key that I've gone and told all my friends they can trust. So I'm confused about how this is supposed to work.
Search could be done locally if the client downloads the whole message history. I don't know enough about how Teams works to know if that's actually something a client can do right now, but it should at least be technically possible. Another alternative is simply running a bot that indexes everything and provides search. You can run the bot in-house so you keep control over your data.
I think I'm more uncomfortable with the idea of entire message histories walking around on disks of laptops and phones (not to mention that's a giant problem on phones because of storage/horsepower) than I am with the idea of slack being able to read everything...
There are better ways to do search, hash keywords then you can just search the hashes
A good article that covers what Keybase is, where they came from, what they try to do, and where they're trying to go -- although you couldn't tell from the headline. As in the article body, Slack is namedropped just for effect; Keybase Teams being a decent proof-of-concept of a popular kind of application to show that the ideas behind Keybase can be used to build real products. That being said, Keybase has been movi…
When we started Keybase, it was a hobby project to address shortcomings of PGP. Max and I both had just downloaded software packages and wanted to verify them, and it took us hours. At least one of them was bitcoin; I recall staring in awe as Max showed me the countless Gavin Andresen impostors on the popular PGP key servers. We really thought we'd stick up the Keybase directory, make some basic scripts, and move on.…
Excellent summary of your vision.
> (1) (...) Whether you're following a famous developer or you're looking up your own sibling, odds are in 2017 you know a public definition of them: a Twitter account, Reddit account, Facebook, etc.
What do you think about OpenPGP Linked Identities proposal [0] that does exactly what you described but in a decentralized way?
Search could be done locally if the client downloads the whole message history. I don't know enough about how Teams works to know if that's actually something a client can do right now, but it should at least be technically possible. Another alternative is simply running a bot that indexes everything and provides search. You can run the bot in-house so you keep control over your data.
I think I'm more uncomfortable with the idea of entire message histories walking around on disks of laptops and phones (not to mention that's a giant problem on phones because of storage/horsepower) than I am with the idea of slack being able to read everything...
Well, the clients could just keep indexes rather than the actual history, and then fetch the specific messages as needed when the search is performed.
On Android, I use FreeOTP; I can make backups with `adb`. Separately, I use KeepassXC ( https://keepassxc.org ) and store all my 2fa seeds in a dedicated (separate) 2fa database which I keep locked. You can also keep it in the same database as your password db if you want to trade the 2nd factor for convenience but still get the added benefit of one time passwords.
> I can make backups with `adb` does it follow that an attacker can make a "backup" of your 2fa codes as well, if they get ahold of your phone for a minute or two?
No, because you can (and should) disable usb connectivity/debugging.