Rhetorics adlai

[MasterInQuestion]

[[
[ adlai @ CE 2024-10-09 12:32:29 UTC:
https://github.com/orgs/community/discussions/139005#discussioncomment-10892037
    Thank you for taking this conversation seriously.
    Your comment would be much more helpful if there were approximately the same amount of your text as link text.
    Lacking mouseover highlights like the ones in Wikipedia articles: the current ratio is difficult for folks at my grade of ADHD. ]

---- (1)

[ MasterInQuestion @ CE 2024-10-09 13:20:55 UTC:
https://github.com/orgs/community/discussions/139005#discussioncomment-10892671
    The primary problem is the bad segmentation:
    Things of high relevance scattered far away each. ]


----

[ MasterInQuestion @ CE 2024-10-08 13:13:09 UTC:
https://github.com/orgs/community/discussions/139005#discussioncomment-10880095
    Semantic analysis indicated which being probably a misplaced reply:
    Intended for a different thread. ]

---- (1)

[ adlai @ CE 2024-10-09 12:20:11 UTC:
https://github.com/orgs/community/discussions/139005#discussioncomment-10891887
    "Semantic analysis indicated <&>which being</&> probably a misplaced reply: Intended for a different thread."
    The emphasized words are not necessary, in conversational modern English.
    You could include "it was" although the verb of being is usually omitted, if you're not tilting against the grammar police. ]

---- (1)

[ MasterInQuestion @ CE 2024-10-09 13:54:38 UTC:
https://github.com/orgs/community/discussions/139005#discussioncomment-10893079
    Bad prosody. Also bad binding without.
    Which do matter. ]


----

[ PoweredByEnergyDrinks @ CE 2024-10-10 11:55:38 UTC:
https://github.com/orgs/community/discussions/139005#discussioncomment-10903429
    Add the ability to reply to comments on the main thread.
    Often times we leave comments on the PR and not a specific part of the code.
    You are unable to respond to these comments in a thread. ]

---- (1)

[ adlai @ CE 2024-10-10 15:48:58 UTC:
https://github.com/orgs/community/discussions/139005#discussioncomment-10906077
    Should be possible, ideally, to "bubble out" threads that began from micromanaged code-review:
    With some agile UX, rather than requiring developers to draft comments in some separate editor:
    And then double-down on heckles, by pasting their NACKs repeatedly like a NOP stuffing cache critter. ]

---- (1)

[ MasterInQuestion @ CE 2025-01-24 14:58:02 UTC:
https://github.com/orgs/community/discussions/148713#discussioncomment-11944280
    Relevant:
https://github.com/orgs/community/discussions/139005#discussioncomment-10906827
    “Well, I draft comments in professional text editor.
    And scarcely counted on the page's UI:
    That may never provide the adequate functionality possibly matching the professional toolchain.” ]


----

[ sb-oth @ CE 2024-10-10 16:08:03 UTC:
https://github.com/orgs/community/discussions/139005#discussioncomment-10906282
    I would prefer to also show the exact time and date in addition to, for example "committed last week". ]

---- (1)

[ MasterInQuestion @ CE 2024-10-10 17:54:02 UTC:
https://github.com/orgs/community/discussions/139005#discussioncomment-10907232
    Exactly this: https://github.com/orgs/community/discussions/139005#discussioncomment-10723577 ]

---- (1)

[ adlai @ CE 2024-10-10 17:58:35 UTC:
https://github.com/orgs/community/discussions/139005#discussioncomment-10907270
    Still boosts some "number of times same comment has appeared as top-level answer rather than upvote" bogus metric, that ultimately collapses into "entire discussion disruptive; Beta feedback" cornucopia-partyhat-emojicon. ]

---- (1)

[ MasterInQuestion @ CE 2024-10-10 18:16:05 UTC:
https://github.com/orgs/community/discussions/139005#discussioncomment-10907386
    Such might present some technical difficulties for them:
    As they seem to have difficulties getting their AI system working alright...
    https://github.com/orgs/community/discussions/107059#discussioncomment-10596225 ]


----

[ MasterInQuestion @ CE 2025-01-10 02:42:54 UTC:
https://github.com/orgs/community/discussions/139005#discussioncomment-11793221
    Linked post missing:
    https://github.com/orgs/community/discussions/139005#discussioncomment-11137587
    (by #discussioncomment-10713581 @ 2024-11-04T09:52:59Z)

    Happened recently.
    Probably similar mistake?
    https://github.com/orgs/community/discussions/5972#discussioncomment-11647245 ]

---- (1)

[ adlai @ CE 2025-01-10 08:10:19 UTC:
https://github.com/orgs/community/discussions/139005#discussioncomment-11795159
    Firstly thank you for your tireless work, to improve the structure of these discussions:
    By searching out and providing the cross-references between comments!
    I hope GitHub will improve the UX of this part of the site:
    Because it gets quite unwieldy, when the discussions are popular like these feedback solicitations.

    I also remind you my earlier request: that you provide some annotation for these links.
    Your readers might have limited time and attention.
    And when confronted with a long list of linked comments: might not read any of them, if there is no explanation of why you have linked any individual one.

    I also have a difficult time understanding some of your English usage; for example,
    "(by #discussioncomment-10713581 @ 2024-11-04T09:52:59Z)"
    .
    The preposition "by" has several possible interpretations.
    You could use the more precise "from", i.e. that you are talking about a link from within the comment referenced.
    However perhaps you meant "next to", which is also a possible interpretation of "by"? ]

---- (1)

[ MasterInQuestion @ CE 2025-01-27 23:45 UTC:
https://github.com/MasterInQuestion/talk/discussions/43#20250127_2345
    Future refactoring maybe inevitable for such contexts.
    That not initially well-arranged: rearrangement cannot be essentially avoided.
    https://github.com/orgs/community/discussions/39463#discussioncomment-11293956

    "from" may as well be misinterpreted as "since", at that context.
    "by" better connects the previous "Linked".

    Intricacy be the language.
    "克己奉公" ("Refrain Self Hold Justice"):
    It may mean both ends, at the same time. ]
]]