#hedgedocleaks — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #hedgedocleaks, aggregated by home.social.
-
-
-
-
-
-
We just had a big problem with #CodeMirror highlighting and were not able to find a solution beside removing it all together. So we did that and opened an issue with them in the hope to get this resolved in a few days. The correct answer was given in 3 minutes. On a Sunday. Best support ever!
-
HedgeDoc just did the fastest support in our history. Report to fix in ~25 min. And it was totally random that that worked out like this. :D
-
HedgeDocBrine can’t hurt you!
-
HedgeDoc just did the fastest support in our history. Report to fix in ~25 min. And it was totally random that that worked out like this. :D
-
HedgeDoc just did the fastest support in our history. Report to fix in ~25 min. And it was totally random that that worked out like this. :D
-
HedgeDoc just did the fastest support in our history. Report to fix in ~25 min. And it was totally random that that worked out like this. :D
-
HedgeDoc just did the fastest support in our history. Report to fix in ~25 min. And it was totally random that that worked out like this. :D
-
“Looks like all browsers are supported. … except for IE. And you know what I can live with not supporting IE.”
#HedgeDocLeaks -
“Looks like all browsers are supported. … except for IE. And you know what I can live with not supporting IE.”
#HedgeDocLeaks -
“Looks like all browsers are supported. … except for IE. And you know what I can live with not supporting IE.”
#HedgeDocLeaks -
“Looks like all browsers are supported. … except for IE. And you know what I can live with not supporting IE.”
#HedgeDocLeaks -
My software architecture prof would be proud of us today. We wrote a full length proposal for how to deal with a complicated problem with multiple solutions and pro and contra lists and we used a truth table to understand a delicate permission problem with unique edge cases.
-
My software architecture prof would be proud of us today. We wrote a full length proposal for how to deal with a complicated problem with multiple solutions and pro and contra lists and we used a truth table to understand a delicate permission problem with unique edge cases.
-
My software architecture prof would be proud of us today. We wrote a full length proposal for how to deal with a complicated problem with multiple solutions and pro and contra lists and we used a truth table to understand a delicate permission problem with unique edge cases.
-
My software architecture prof would be proud of us today. We wrote a full length proposal for how to deal with a complicated problem with multiple solutions and pro and contra lists and we used a truth table to understand a delicate permission problem with unique edge cases.
-
My software architecture prof would be proud of us today. We wrote a full length proposal for how to deal with a complicated problem with multiple solutions and pro and contra lists and we used a truth table to understand a delicate permission problem with unique edge cases.
-
After questioning the library and the mocker library, looking at their bug trackers and contemplating how to communicate with the devs of those libraries, I checked the mocked variables and it turns out the problem was between the monitor and my chair.
And this dear children is why you should always start debugging by checking your basics and not assume that you did everything correctly. -
After questioning the library and the mocker library, looking at their bug trackers and contemplating how to communicate with the devs of those libraries, I checked the mocked variables and it turns out the problem was between the monitor and my chair.
And this dear children is why you should always start debugging by checking your basics and not assume that you did everything correctly. -
After questioning the library and the mocker library, looking at their bug trackers and contemplating how to communicate with the devs of those libraries, I checked the mocked variables and it turns out the problem was between the monitor and my chair.
And this dear children is why you should always start debugging by checking your basics and not assume that you did everything correctly. -
After questioning the library and the mocker library, looking at their bug trackers and contemplating how to communicate with the devs of those libraries, I checked the mocked variables and it turns out the problem was between the monitor and my chair.
And this dear children is why you should always start debugging by checking your basics and not assume that you did everything correctly. -
We just confirmed:
Our database does not do anything, if the function that actually does stuff is not called. We’re very contend with those test results. -
We just confirmed:
Our database does not do anything, if the function that actually does stuff is not called. We’re very contend with those test results. -
We just confirmed:
Our database does not do anything, if the function that actually does stuff is not called. We’re very contend with those test results. -
We just confirmed:
Our database does not do anything, if the function that actually does stuff is not called. We’re very contend with those test results. -
And it's time for a HedgeDoc 1 Release. How did this work again?
-
And it's time for a HedgeDoc 1 Release. How did this work again?
-
And it's time for a HedgeDoc 1 Release. How did this work again?
-
And it's time for a HedgeDoc 1 Release. How did this work again?
-
We at more than one occasion included some “This should never happen.” error messages in HedgeDoc2. Always funny when they then occur despite our insistence that that is not possible. Normally this happens in testing setups where some component is missing for something similar, but funny either way.
-
We at more than one occasion included some “This should never happen.” error messages in HedgeDoc2. Always funny when they then occur despite our insistence that that is not possible. Normally this happens in testing setups where some component is missing for something similar, but funny either way.
-
We at more than one occasion included some “This should never happen.” error messages in HedgeDoc2. Always funny when they then occur despite our insistence that that is not possible. Normally this happens in testing setups where some component is missing for something similar, but funny either way.
-
We at more than one occasion included some “This should never happen.” error messages in HedgeDoc2. Always funny when they then occur despite our insistence that that is not possible. Normally this happens in testing setups where some component is missing for something similar, but funny either way.
-
Today we had so much fun with all the differences between different databases and how they are all slightly different when throwing the exact same code against the different drivers. So much fun. #HedgeDocLeaks
-
Today we had so much fun with all the differences between different databases and how they are all slightly different when throwing the exact same code against the different drivers. So much fun. #HedgeDocLeaks
-
Today we had so much fun with all the differences between different databases and how they are all slightly different when throwing the exact same code against the different drivers. So much fun. #HedgeDocLeaks
-
Today we had so much fun with all the differences between different databases and how they are all slightly different when throwing the exact same code against the different drivers. So much fun. #HedgeDocLeaks
-
Currently working on HedgeDoc 2 with @emcrx and it’s so nice when past us thought things through for us.
“Ups the variable should be named differently.” -
Currently working on HedgeDoc 2 with @emcrx and it’s so nice when past us thought things through for us.
“Ups the variable should be named differently.” -
Currently working on HedgeDoc 2 with @emcrx and it’s so nice when past us thought things through for us.
“Ups the variable should be named differently.” -
Currently working on HedgeDoc 2 with @emcrx and it’s so nice when past us thought things through for us.
“Ups the variable should be named differently.” -
Currently working on HedgeDoc 2 with @emcrx and it’s so nice when past us thought things through for us.
“Ups the variable should be named differently.” -
The “Now that we done this, everything should work”-Counter is currently at 21.
-
The “Now that we done this, everything should work”-Counter is currently at 21.
-
The “Now that we done this, everything should work”-Counter is currently at 21.
-
HedgeDoc Dev-Weekend is going great.
We‘re really close of finally ditching typeorm for good and using knex.
Also the number of "I want to bite in my desk" incidents is the same as the number of times we got cake, so it all averages out.
#HedgeDocLeaks