Elektrine lite

← Feed

@wrog@mastodon.murkworks.net

2026-03-10 22:37 UTC

@screwlisp @dougmerritt @mousebot @cdegroot @ramin_hal9001 @kentpitman … and a different model which perhaps maps closer to how people think about this. https://codeberg.org/martianh/mastodon.el/issues/340#issuecomment-11492926 Please note: Proposal 2 . reply-to-id can be a draft ⟹ creating chains of drafts . status quo = nobody's doing that yet Proposal 3 . drafts have split-points (= subdrafts) . many attributes (CW,NSFW,attachements,visibility) live on the split point . status quo = only one subdraft are **implementation** choices, not UIs in and of themsevles. That is, both should support the same UIs (for chains, anyway; P3 can't really do trees). I still much prefer P2. P3 looks to be more work/complexity to achieve less IMHO. (N.B. I've not deeply looked at the code, yet).

Replies (1)

  • @wrog@mastodon.murkworks.net 2026-03-10 23:20

    @kentpitman @ramin_hal9001 @cdegroot @mousebot @dougmerritt @screwlisp > (N.B. I've not really looked at the code, yet). meaning I may yet turn out to be wrong about what's difficult, meaning don't hold your breath on the pull-request (*) (Also, elisp seems to have changed a bit. I remain dismayed at how many Common-Lisp-isms crept into the language. I've mostly been in RMS's camp on this, but I'll admit that was based on how horribly elisp's common-lisp compatibility was implemented 20 years ago. Evidently this ship has sailed. And now that modern elisp compile is way better and does native code, it probably doesn't matter anymore). (*) Ideally, my architecture wanking will goad someone else into beating me to it.

    Open ##1444934