Fork me on GitHub

unpopular opinion: slack threads are a half-assed attempt at nested comments

Eccentric J20:04:37

How should it work ideally?


I suspect by 'nested comments' they mean something like what you have on reddit


like, here we are stuck on this level, unable to comment on comments in an analogous fashion. the comments we are making here are one level down from an original "comment". it is not obvious how to "go to the next level down". in an odd way it is worse than "half-*ed" because half would likely be half of whatever max levels there areat reddit...or something like that :)


I don't want nested comments on a chat app though


you have your wish then :)


I think slack threads do fill a required feature, probably not in a good way


my problem is more with the way people use it


Classic example: I'm having a conversation at work with 3-4 people. It's a chat, so we are all talking, things are mixing, normal chat stuff, like if we were on IRC or on a whatsapp group


then people will start launching threads on certain comments


and all of the sudden, I'm still talking to the same number of people, 3-4, but I have to click click click to read the different messages that are being added to multiple threads


So. Annoying.


that does sound undesirable


In my case its more apathy; this fulfills my needs, but I'd be ok seeing what reddit-styled-threads are like


for an environment like this*


This is a popular opinion. 🙂 Flowdock did threads so much better

jeff tang12:04:17

This is a very contentious issue, perhaps only a step away from a bona-fied Holy War:


Hey I'm trying to setup a Windows 10 dev, more for help starters/write tutorials I'm using Windows "native" ssh C:\Windows\System32\OpenSSH\ssh.exe And "vanilla" git C:\Program Files\Git\cmd\git.exe My ssh-add -l show my key. its "active" But every time that I "git pull ..." or "git clone" it ask my password (prompt in the shell itself) It's really annoying. How to setup this in windows?


Here a terminal dump

C:\Users\Enzzo Cavallo>ssh-add -l
16384 SHA256:RsgFwbjBDMvweal2LkGv1RfDDerCKH8vjRqTnqG6nDU [email protected] (RSA)

C:\Users\Enzzo Cavallo>ssh  -i .ssh/id_rsa
warning: agent returned different signature type ssh-rsa (expected rsa-sha2-512)
PTY allocation request failed on channel 0
Hi souenzzo! You've successfully authenticated, but GitHub does not provide shell access.
Connection to  closed.

C:\Users\Enzzo Cavallo>git clone [email protected]:souenzzo/
Cloning into ''...
Enter passphrase for key '/c/Users/Enzzo Cavallo/.ssh/id_rsa':
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.


The same problem bothers me as well. Not really a solution to the problem but a workaround is use HTTPS and use "store" as the cred helper.