pull down to refresh
Sometimes I vibe my concepts before working on them, just to see them take life. Then I rewrite everything because 7 times out of 10 it's done in the worse way possible.
Not our fault: https://github.com/stackernews/stacker.news/issues/2866#issuecomment-4068189184
let's hope coinos fixes this stat
the "team" is not just the 3 guys maintaining the code.
Darth, with the same logic then you're part of the "team", too.
I can assure you that this is cause and effect:
- cause: openclaw/molt/whatever hype
- effect: random bots online
yup https://github.com/stackernews/stacker.news/issues/2860
Our bi-directional pipeline allows for lossless structure translation, but it has its own opinions when it comes to markdown serialization.
We can probably store the markdown syntax style on each rich node, for example:
- Point 1
- Point 1.a
* Point 1.b
* Point 2can be translated to these rich nodes:
ListItem
- Text: Point 1
- Markdown: DASH
- ListItem
- Text: Point 1.a
- Markdown: DASH
- ListItem
- Text: Point 1.b
- Markdown: STAR
ListItem
- Text: Point 2
- Markdown: STARDecoratorNodes, such as mentions and media, don't support formatting because they're essentially React components, so that's expected for now but not for long! The underlying library now added support for carrying formatting over to React decorators[1].
The second bug I see is that inline code doesn't support superscript and subscript, which is weird because they're fully supported formats, heck even underline work lol.
I'll include a bugfix to the second bug in the enhancement pack 1. The first bug will see a fix during Stage 4, because we need[1] to update the library and check what will break (I suspect a lot since we heavily modified it).
Thank you!!
technically we don't need that update and we can do it ourselves, but the less divergence the better ↩
I just disable it on every device, I want everything on full maximum ultra brightness.
...
...
maybe that's why I see everything kind of "darker" now...
official issue on github
TIL we have one already: https://github.com/stackernews/stacker.news/issues/1089
Welcome to virtual cursors! Browsers can't normally land a cursor in "non-editable" elements, but everything in compose mode is editable ... so we fake a cursor!
It can be pretty janky and to make it less janky we implemented a way to insert a paragraph if you click at the top or bottom side of an element. Let us know if you encounter any issues or odd behavior!
I see, I don't have a Samsung device right now but I'll find a way to get that keyboard and find a fix.
The problem (or the advantage, perspectives) on Android is that every keyboard can have their own IME[1] implementation, leading to bugs almost always unique to each keyboard. We're doing great efforts in trying to squash them all because we care and we're not easily comfortable in asking people to "just use another keyboard".
IME is what controls autocorrect and characters that need to be
composedlike Japanese ones ↩
🗿