tecc
That's interesting. What object storage software are you using? I'm guessing it could be fixed by changing [line 18 in libs/server/store.ts](https://github.com/notea-org/notea/blob/e853f121aa48e22d156515df98de2fd522f4f58c/libs/server/store/providers/s3.ts#L18) to include `err.name`, but I may be entirely wrong.
I use node 16.
Perhaps. I'll have to properly look into it later, since I'm slightly busy at the moment.
Okay, update on this issue: Since I can't test it myself at this moment, I wonder if downgrading `prosemirrror-model` to `^1.8.1` - I perused a bit through the lockfiles of...
Quick update on this issue: I tested it with the changes I made in #146, and it works fine.
Hiya! Could you possibly provide any screenshots or recordings of those bugs*? At a guess, however, I'd say some of these bugs are caused by the underlying Markdown editor, [outline/rich-markdown-editor](https://github.com/outline/rich-markdown-editor),...
 Is this better? I mocked it up whilst making the new editor.
Yes, there definitely will be, once I've managed to stabilise the image. There are also automatically published images that are bleeding-edge (the tag name is `main`, if you're interested) -...
I'm planning on making clear instructions for passwords soon, so yes. In the mean time, try to see if Netlify/Vercel allows you to set the password using environment variables.
Closing this issue as solved as the new editor has been added to Notea in 3c475670776b21788dd9afd84ee32a2ff3e36173, which includes the updated code block.