MarkDown War(karound)s: MD5 Strikes Back

Gąska

Continuing the discussion from More stupid Git errors THIS TIME IN FIRST-PERSON!:

No, because Discourse doesn't work. Like, there are actual bugs that makes things impossible. There's no excuse for ***\**** producing 3389dae361af79b04c9c8e7057f60cc6.

Neither is there excuse for ***3389dae361af79b04c9c8e7057f60cc6*** producing 3389dae361af79b04c9c8e7057f60cc6.

PJH

=-o

accalia

wait...... WTF?

i thought we had learned this lesson by now and.....

no, nevermind there is no sanity.

Magus

3389dae361af79b04c9c8e7057f60cc6

Just for fun...

hungrier

2389dae361af79b04c9c8e7057f60cc6
3389dae361af79b04c9c8e7057f60cc6
4389dae361af79b04c9c8e7057f60cc6

b14a7b8059d9c055954c92674ce60031
b14a7b8059d9c055954c92674ce60032
b14a7b8059d9c055954c92674ce60033

So the Discosolution for the MD5 bug that never should have been there in the first place involves hardcoding the MD5 values and swallowing characters whenever it's detected. A+ job, this is how good developers fix bugs in their software.

abarker

@Gaska said:

Neither is there excuse for 3389dae361af79b04c9c8e7057f60cc6 producing ae361af79b04c9c8e7057f60cc6**.

@hungrier said:

So the Discosolution for the MD5 bug that never should have been there in the first place involves hardcoding the MD5 values and swallowing characters whenever it's detected. A+ job, this is how good developers fix bugs in their software.

riking

@hungrier said:

A+ job, this is how good developers fix bugs in their software.

With the composer, it's not so much a "fix" as it is a "band-aid".