It’s not that the link breaks, it’s that the counter of clicks in the little gray circle next to the link resets whenever the title differs from that inside the link. For example, I change the emojis around my study log title seasonally, so if i have t/log-title/000 in the link, it’ll reset the little gray number of clicks next to the link whenever I change the physical thread title. But, for some reason, if you remove the title from the link t/000 then you can change the actual thread title a million times without the click number resetting.
IIRC it used to be a problem in the book clubs because thread titles with kanji rendered into super long URLs of gibberish and clicking those links took forever to load if at all. I feel like the custom of filling out the thread title of the URL with an x started from there and now people do it as a habit.
Seanblue can probably confirm or correct me on that.
wow, reading through the responses leading to this, I’m like ok, I’ve arrived into the heart of WK culture, link editing etiquette, which I’ve been vaguely aware of, but I hadn’t yet been fully initiated into the ways. And now this - the origin story of such cultural heights
Ah that makes sense. I’ve observed this with Bunpro, if I copy this URL:
it becomes this: https://bunpro.jp/grammar_points/%E5%85%A8%E3%81%8F-%E3%81%AA%E3%81%84
Yeah, it’s because of URL encoding. Technically URLs don’t contain non-ASCII characters, so anything displaying “decoded” URLs with non-Western European languages, emoji, etc. is basically doing so as a user-facing nicety, but needs to convert back to encoded URLs for actually talking to other computer systems.
Clean “URL” that just work seems to be another standard called IRI, but not very well received for some or many reasons. (Having non-ASCII encoded was since 2005. This standard was updated just in 2020.)
Note browsers use URLs, not URIs, and while the goal was for URIs to supplant URLs, they basically never did so entirely so browsers went back to updating the URL spec at WHATWG. It’s not clear that the IETF which maintains the RFCs is on board with this, so now we have the funny situation where the URL standard says that URIs are just a outdated name for URLs and the URI standard says URLs are just a outdated name for a type of URI.
This is what browsers follow nowadays and actually contradicts the URI RFCs on that and makes it clear that encoded URLS should be ASCII and non-ASCII points should be URL encoded. Non-ASCII URLs always ran into the issue of “will they be accepted or won’t they?” and so the spec was updated.
Moved two logs that closed in the last few months down to the Closed section
Alphabetized one name into the Open section
(figured I would add this for clarity and to know when I last did anything)
As always, feel free to add new logs, change the details of your title, or, if you re-open a closed log, move it back into the top section. Adding your log to the list is voluntary and it will not be added/removed or have the title changed without you doing so yourself.
You can think of it as WK community being a school / university, some people stay and become teachers and professor and the like, but most people graduate at some point, or some people drop out, but new people come each year too!
Reading through the closed logs feels a bit like secretly reading an older sibling’s diary sometimes But I get so much inspiration from them, closed or no they are still stuffed full of resources and learning experiments. And sometimes I like to look at @chelzi 's study log because it’s just so dang beautiful and organized hehe
But they might not be closed forever! Knowing that mods can reopen them any time at the owner’s request makes me feel better about “what if life gets in the way and mine closes, too?”
^–^