Comments on
lichess.org/@/dboing/blog/first-post-notes-from-feature-first-day/aQLMw1HNI am testing blog stuff... switched an old draft about past tests to public... anyone is welcome to add same nature comments, about blog features, and I would even ask if anyone as any clues about how other lichess text features are evolving here. I might make another blog if enough material..
I did find very early that the Blog feature has the most qualities of all lichess text features.. And the caveats to that have been lifted, namely it can also lead to discussion. in forum.
> starting points for such project (not very active depends on participation i guess.)
This is not about the blog directly, hijacking my own blog discussion, like any other thread in a forum (my perspective about forum is more of an agora flavor).
I wish that some of the blog features set would "contaminate" other text features.. Like the private inbox messaging.
I get that resources go up when allowing multi-user text objects, or i suppose that it what explains why blog is fully featured (with some default font sizes and such TBD), while forum is not as editable, for as long. There are many participants, not just the op. However, how does resources impact climb when comparing with inbox messaging? I guess it might depend on blog length limit.. which i should try (that is blog discussion matter).
Somethings that blogs are not good at, as well as inbox, is the ability to make modular points addressable, contrary to forum (and team forum, which do share some extra text features from blog and inbox for privacy now).
Posts in forum can be referred to for precise discussion progress. Moreover, there is a pagination map while in given page which can serve as a global thread navigation hint so that we end up being able to jump through connected discussions, and retrace our from our jumps back to where we were without thought train derailing. The pagination is not the feature directly, but its thread chunking or metering side-effect is the navigation feature.
None of that in long blogs (not sure, memo: test), and even longer inbox messaging. Not all inbox messaging is of the casual chat category, sometimes before going to forum, we may need to have private serious discussions, that may span over many scroll buffers, sometimes even days earlier. The time stamps are very approximative and sometimes their first appearance does not follow the input order that really happens when considering both local computers timings (not as bad a problem, as the lack of proper referring).
I know that now team forum could work around that inbox problem for long lasting discussions and need to trace back good past information contained in the past. I have tested the privacy settings from many ways one can access lichess (not through API yet, if team forum content is interfaced there, but i assume it would not have more permissiveness than the interactive access). But I recently had a hard time convincing someone to extend our inbox conversation there for proper threading and navigation, given that we both are able to type walls of text, and express many thoughts in dense paragraphs. (me i also need the editing given my high syntax and typo error rate). I guess, while private messaging will always be private, having team new privacy, is on one hand, not well known (i did test also google search when privacy at "only leaders"), and also, could be changed, it is not part of the feature name as much as Inbox is. I don't even use the non-text features in my teams.. So somehow, if the features from team forum, were an alternate option instead of the chat spirited inbox feature, I would have a better time with inbox.. (it used to be more like forum, before the overhaul, was it last year or the year before)....
lot of material for many feedback thread. but maybe a blog is more visible or sustainable (and updatable with new information).
accumulating material here. If my test blog does by some maximum improbability principle generate participation here, i would delete this post. I am making a copy right after the CAPTCHA for a draft blog.
