10
thread your Philthy feature requests
(awful.systems)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Apr 2024
10 points (100.0% liked)
FreeAssembly
75 readers
1 users here now
this is FreeAssembly, a non-toxic design, programming, and art collective. post your share-alike (CC SA, GPL, BSD, or similar) projects here! collaboration is welcome, and mutual education is too.
in brief, this community is the awful.systems answer to Hacker News. read this article for a solid summary of why having a less toxic collaborative community is important from a technical standpoint in addition to a social one.
some posting guidelines apply in addition to the typical awful.systems stuff:
- all types of passion projects and contributions are welcome, including and especially those that aren't programming or engineering in nature
- this is an explicitly noncommercial, share-alike space
- don't force yourself to do work you don't enjoy, or demand it of others
(logo credit, with modifications by @dgerard@awful.systems)
founded 7 months ago
MODERATORS
I'm fairly certain they did based on how it works -- if that's the case, I consider it fairly low hanging fruit to swap to something more sensible. this'll break our compatibility with other instances in a minor way if we do it since we won't be rendering posts in the same broken way, but I feel like the risk is fairly minor. I'll check on this and post an update once I get started on the rebrand for the frontend
I was percolating on this. And here’s a maybe-nasty workaround that may even be usable in federated manner (I have no idea if this is even viable, need to learn some AP)
Internally store posts in raw and some kind of decorated-raw format, where the “decorator” is essentially some frontmatter that specifies rendering/renderer properties. Think
<!-- renderbits: […..] -->\n\npostgoeshereUpside of this approach is that if it is federable (and again, dunno, will need to check still 😅), it can allow each instance to self-handle as needed, along with providing own fallbacks and stylemaps
not a bad idea! there might be an existing format that’d handle this well. I need to confirm what format Lemmy uses for styled text interchange — I think it might just be markdown?
looks like both markdown/source, and html? this and this is what I drilled down to
so the frontend uses markdown-it which is fairly popular; I think the problems with it are the settings they configured for
markdown-it's parser, and the almost 800 lineMarkdownTextAreamaking interacting with the damn thing so clumsy. we can probably get a pretty good improvement out of changing to a sanermarkdown-itconfiguration and swapping theMarkdownTextAreacomponent for something well-supported from NPM