HedgeDoc security issue response time was quite good this time around: Monday evening we got the report and started working on it and today we released the new version. That is a response time of ~48h.
#HedgeDoc #SecurityResponse

What a luck #dropbox destroyed its paper product, which was my favorite #quicknotes tool and last tie to dropbox.Now using #hedgedoc and never been that happy.Amazing tool. Once again #opensource rules.And that #vim support,what a touch of genius! :-)

Kurze Frage: Kann jemand eine öffentliche Instanz von https://hedgedoc.org/ empfehlen, die man im wissenschaftlichen Kontaxt nutzen kann. Die Instanz der GWDG funktioniert nicht mit meinen Accounts der TUD und Slub.

Dienstvorstellung: HedgeDoc-Pad

Mit unserem kollaborativen Markdown-Editor könnt ihr in Echtzeit gemeinsam schreiben, strukturieren und dokumentieren – ideal für Teams, Lehre und Projekte.

Einfach, flexibel, direkt im Browser nutzbar.
Mehr Infos: https://academiccloud.de/de/services/pad/

This month marks three years since I have been using @hedgedoc . It started with a quick installation on a server with @yunohost to prepare notes on my mum's computer and the app has stayed with me until today.

If you write your #presentations using #markdown with #hedgedoc/#revealjs, here's another slide template you might find useful: A quadrant layout: https://gist.github.com/cboulanger/81131e81e4320b71400431fbc88b90c5

Abbiamo sistemato i bug di #hedgedoc: a mio parere il miglior modo per scrivere testi online con #Markdown e poi condividerli!

Un grazie a chi ci ha segnalato i bug e a @magostinelli per il lavoro: ora tutto funziona alla perfezione!

https://hedgedoc.devol.it

Per provarlo:
Niente inviti, ma la registrazione è un po’ "avventurosa":
Clicca su "Entra" (sembra un login, ma non è!)
Inserisci email + password
Clicca "Registrati" (sì, è contorto… ma ne vale la pena!)

@opensource

Today was a HedgeDoc Release record I believe. 3 hours including work on the fix itself, testing and some nasty container problems at the end.

And with only two people. Last time took 2 hours longer iirc.

REMEMBER: Deletion of https://demo-archive.hedgedoc.org

As announced in July of last year already, we're deleting the archive of the old demo instance soon. In 2 weeks from now on - so on February 3rd, 2025 - the instance with all its notes and media files will be removed. In case there's anything which you need to backup, do that now. There won't be any way to recover your notes afterward.
The new demo instance is wiped daily, please seek a new place for your notes to live on.

Currently we're trying to implement somewhat useful printing for #HedgeDoc 2 and it’s always amusing how everything can break sometime:

e.g this code block in Chrome

I worked the whole weekend on #HedgeDoc 2 and tested quite a lot of collaboration, which has it’s problems still, especially if you run the software in hot reload develop mode and so on, which leads to weird behavior sometimes.
But the whole experience was miles ahead of what sorry excuse of collaborative writing #clickup has.
Just now two people writing something and multiple times, the sync breaks and / or replaces part of the text the other person wrote.
I can’t work like this

Thinking about it, we pulled the #hedgedoc release as soon as signs of broken encoding solidified. As far as I can tell, Node.js 22.7.0, the culprit of that brokenness, is still available, even though corrupted text in a widely used language runtime seems *slightly more critical* than in some random text editor.

HedgeDoc 1.10.0 is available again. We believe the encoding bugs are a regression in Node 22.7.0 and not caused by our code.
The Docker images are now based on Node 20. #hedgedoc

The #hedgedoc bug looks very much like https://github.com/nodejs/node/issues/54543, which only triggers when V8 decides to optimize the buffer code path, making the whole thing trigger at random.

Please be aware that we are currently investigating a problem with the fresh #hedgedoc 1.10.0 release after reports of broken notes. We pulled the release, PLEASE DON'T INSTALL IT.

https://matrix.to/#/!oaRMJImPLfUnnXzwnN:shivering-isles.com/$DRQsNvHmY-1wiFzD7q1ZxpkZZvy1Bwrlp5I090UD50k?via=shivering-isles.com&via=matrix.org&via=envs.net

Entscheidungsbäume sind manchmal praktisch.
```flow
st=>start: Start
fr=>condition: Bin ich bei Mastodon?
ok=>condition: Hostet du eine eigene Instanz?
nok=>operation: Dann wird's aber Zeit.
ok2=>end: Klasse
nok2=>operation: Schade

st->fr
fr(yes)->ok
fr(no)->nok
ok(yes)->ok2
ok(no)->nok2
```
#hedgedoc #fedilz #markdown

A couple of assholes were abusing the free demo #HedgeDoc server to hell and back. It is currently shut down. A couple of bad actors ruin a great public service for everyone.

All of the time and effort that goes into mitigation could be spent so much better on other things. I hate this so much.

(to make this clear: the software itself is just fine if you self-host it! this is just about the demo instance that was provided for free (but also with no guarantees))

https://community.hedgedoc.org/t/status-of-the-demo-instance/1634/4