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/
What would be great is to have a collection of of css rules that implement slide layouts for #hedgedoc presentations, maybe under a common hashtag.
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! 
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!)
I need to test #hedgedoc !
Alternativas encriptadas y sin IA a Google Docs -> https://lifehacker.com/tech/the-best-ai-free-encrypted-alternatives-to-google-docs
#cryptpad #protonsuite #onlyoffice #hedgedoc #etherpad
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
#hedgeDoc does such a perfect job of taking markdown and spitting out HTML that I almost cried
--
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.
filippodb ⁂ 
Pretending to be a 
