3 ms·

You can tell it was built for Silicon Valley. The marginally lighter gray tone on unsent messages is only noticeable by design-aware people on fancy IPS monitor

by gomox 6y ago

You can tell it was built for Silicon Valley. The marginally lighter gray tone on unsent messages is only noticeable by design-aware people on fancy IPS monitors. Messages are reordered semi-randomly.

breatheoften 6y ago
I frequently send - edit send - edit the same message in an effort to reduce the number of typos. Recently i've realized that this actually introduces more typos -- where a large number of phrases are duplicated or corrected typos reapplied. There's something wrong with slacks operational transform or CRDT implementation or whatever they use to get edited messages to converge
- paxys 6y ago
  > slacks operational transform or CRDT implementation or whatever they use to get edited messages to converge I'm pretty sure they have none of that, considering you can only edit your own messages. So what's likely happening is that two quick edits are reaching the server at the same time and overriding each other.
  - breatheoften 6y ago
    I could be wrong but i'm relatively sure that I reach message states that do not directly correspond to anything i typed into the editor -- which i wouldn't expect if the edited state was always sent in full rather than as a delta on a previous message state. I suppose it's possible that the corruption happens on the client side tho -- 1. initiate edit action and get editable view of snapshot of text 2. server acks some previous edit request causing some client state related to the message to update and promote a previous edit in some way 3. hit save after finishing editing -- and some delta operation on the client side updates a different message state than the one i initiated edit action from ...
    - viraptor 6y ago
      This is just super unlikely as you describe it. There's no reason for deltas and fancy mechanisms when you can only edit your own messages. It would be a waste of resources to do it like this for short messages.
      - breatheoften 6y ago
        I don't know the specific implementation mechanism -- just guesses. But that doesn't mean my observation of the behavior of the bug is unlikely. And also -- there is not a hard requirement that only one editor exists -- the same user could use multiple devices at the same time. Consider that and you might find your assumptions to be invalid.
- jlokier 6y ago
  It's almost as if you're describing LinkedIn... (Where a message sent doesn't match what was typed sometimes.)
outworlder 6y ago
IPS monitors are not 'fancy'. Not in 2020.
- hackmiester 6y ago
  This take is illustrative of just how much of a bubble HN is. I don't mean to disparage at all, but IPS monitors are far from universal.
gomox 6y ago
Did some poking around with Chrome dev tools. The RGBA value for the "unsent" text is #1d1c1db3. Normal "sent" (or "attempting to send but haven't yet decided sending will fail" is #1d1c1d. The RGBA value (alpha = 0.7) ends up being equivalent to #616161 when rendered over white background which the Slack default skin does. Demo for reference: https://jsfiddle.net/9smqe8y7/ https://jsfiddle.net/9smqe8y7/

by gomox 6y ago

breatheoften 6y ago

I frequently send - edit send - edit the same message in an effort to reduce the number of typos. Recently i've realized that this actually introduces more typos -- where a large number of phrases are duplicated or corrected typos reapplied. There's something wrong with slacks operational transform or CRDT implementation or whatever they use to get edited messages to converge

paxys 6y ago
> slacks operational transform or CRDT implementation or whatever they use to get edited messages to converge I'm pretty sure they have none of that, considering you can only edit your own messages. So what's likely happening is that two quick edits are reaching the server at the same time and overriding each other.
- breatheoften 6y ago
  I could be wrong but i'm relatively sure that I reach message states that do not directly correspond to anything i typed into the editor -- which i wouldn't expect if the edited state was always sent in full rather than as a delta on a previous message state. I suppose it's possible that the corruption happens on the client side tho -- 1. initiate edit action and get editable view of snapshot of text 2. server acks some previous edit request causing some client state related to the message to update and promote a previous edit in some way 3. hit save after finishing editing -- and some delta operation on the client side updates a different message state than the one i initiated edit action from ...
  - viraptor 6y ago
    This is just super unlikely as you describe it. There's no reason for deltas and fancy mechanisms when you can only edit your own messages. It would be a waste of resources to do it like this for short messages.
    - breatheoften 6y ago
      I don't know the specific implementation mechanism -- just guesses. But that doesn't mean my observation of the behavior of the bug is unlikely. And also -- there is not a hard requirement that only one editor exists -- the same user could use multiple devices at the same time. Consider that and you might find your assumptions to be invalid.
jlokier 6y ago
It's almost as if you're describing LinkedIn... (Where a message sent doesn't match what was typed sometimes.)

outworlder 6y ago

IPS monitors are not 'fancy'. Not in 2020.

hackmiester 6y ago
This take is illustrative of just how much of a bubble HN is. I don't mean to disparage at all, but IPS monitors are far from universal.

gomox 6y ago

Did some poking around with Chrome dev tools. The RGBA value for the "unsent" text is #1d1c1db3. Normal "sent" (or "attempting to send but haven't yet decided sending will fail" is #1d1c1d. The RGBA value (alpha = 0.7) ends up being equivalent to #616161 when rendered over white background which the Slack default skin does. Demo for reference: https://jsfiddle.net/9smqe8y7/ https://jsfiddle.net/9smqe8y7/