Slack
Noisebridge | About | Visit | 272 | Manual | Contact | Guilds | Resources | Events | Projects | WGs | 5MoF | Meetings | Donate | V · T · E |
Communications Channels | Wiki | Discuss | Slack | Jitsi | Pad | Meetup | Discord | Trello | Github | IRC | VR | Twitter | 5MoF | YouTube | Blog | Zine | Contacts | Mailinglist | Guestbook | BBS | V · T · E |
Slack is a multi-platform chat application used by Noisebridge for internal discussions. It is similar to IRC and Discord. Our slack is located here, but will require an invite to access. You can get an invite to our public (anyone can access) Discord, here. |
Note, Slack in this context is different from the Slackware Linux distribution's "Slack".
Who to invite?[edit | edit source]
Slack is for communication supporting Noisebridge the physical space. If you want to invite someone, they should satisfy the following:
- "Do you want to hang out with this person again?" and
- "Has this person been coming around for a little while?".
How to get an invite?[edit | edit source]
Slack requires an invitation to join, unlike Noisebridge's IRC channel.
It's recommended that you meet up with someone knowledgeable in the space and talk to them about Slack, or if all else fails, request an invitation on Noisebridge-discuss.
How to access?[edit | edit source]
Our slack is located here, but will require an invite to access.
Slack is available for *desktop* download here, and in the *mobile* app stores on iOS and Android. It is also available via IRC or XMPP clients.
Why slack? Replacements?[edit | edit source]
Some are not comfortable with slack as it is (add!):
- corporate entity
- not free
- archives and logs all messages and sends SMTP transcriptions by default to all users unless they otherwise select to disable that feature, which can be used in court. "Both the California Evidence Code and the Federal Rules provide that admissions by a party opponent do not constitute hearsay. (See Cal. Evid. Code § 1220; Fed. R. Evid. 801(d)(2).)." This principle is *anti-thetical* to PFS (Perfect Forward Secrecy) principles of robust secure communications methodologies and protocols.
Requirements[edit | edit source]
- free open software
- stored messages
- encrypted
- realtime chat
- api/extensible
Alternatives[edit | edit source]
- rocket
- irc (not used, missing archive feature; [UPDATE: archival is a "mis-design" and bad for security, IRC can be logged as well read up on the /log feature in many popular clients, e.g. irssi.])
- Riot
- Mattermost
- SILC (end to end encrypted, free and open source, distributed or [multiple servers can share messages between each other providing message coherency to users more robust than "federated" services like Mastodon. Heavily audited and vetted by w00w00, Coverity, OpenBSD developers and more over the course of a decade+. PFS can be tuned to have arbitrarily slow or fast key rotations, messages from users are encrypted *from* the server eavesdropping as well, especially with use of private message signing.)
- PSYC2 (end to end encrypted, distributed, free and open source, multiple client implementations, the lead developer is excellent, worth looking into more deeply)
- DISCORD!
Digging in teh weeds[edit | edit source]
URL Schemes[edit | edit source]
Unauthenticated profile image serving:
- https://ca.slack-edge.com/T027UKEC9-U0287F36C-c918fbf7d24a-512
- https://ca.slack-edge.com/T027UKEC9-U0287F36C-97adbaa76911-512
The last bit after the "-" is the image size requested, generally 48-512
Unauthenticated, non-domain restricted image proxy server:
Emoji sets:
- https://a.slack-edge.com/bfaba/img/emoji_2016_06_08/sheet_apple_64_indexed_256colors.png
- https://b.slack-edge.com/bfaba/img/emoji_2016_06_08/sheet_apple_64_indexed_256colors.png
Custom emoji:
[[User:|]] ([[User talk:|talk]]) 18:10, 12 June 2017 (UTC)
Terms, etc.[edit | edit source]
https://slack.com/terms-of-service
https://slack.com/terms-of-service/user