66 points by zaptrem a day ago
I was learning about Wikipedia recently and thought it was interesting there was a global, public page specifically for writing random stuff to learn how to use their editor. I assumed there would be something like this on a per-user, invisible to the public level, but not a global level like this page.
Yeah, because it’s a PITA to align everything by hand.
But the spaces around | make it easier to read, than, say, CSV.
I agree it's great, but that risk is so major that I stopped using it. "There's a 50% chance that your editor will invisibly corrupt the data you enter, and another 30% chance to corrupt the entire file" is just not usable...
Especially in Zed where the only way to switch hard tabs is buried in the settings menu, and impossible to change per buffer.
> Yeah, because it’s a PITA to align everything by hand.
For now. I get the feeling we'll have tooling everywhere that does this soon.
I was recently tab-completing a Markdown table and whatever autocomplete model I had just fixed the table up without any intervention.
Yeah, it’s not terribly hard to do that even without AI (Prettier can do it, for example). But there’s a lot of places where the tooling just isn’t available. Then again, it’s probably not a big deal if your GitHub comment markup isn’t perfect.
I think the root of the problem is, almost everything else you use in Markdown is easy to do by hand. There’s just no good syntax for tables like this, I guess.
That's putting it lightly, since Mediawiki templates are Turing-complete.
I'm not up to speed on my parsers anymore, but I believe Parsoid remains the most complete implementation, while mwlib is a reasonable compromise.
https://www.mediawiki.org/wiki/Alternative_parsers#Known_imp...
I just went back to check whether I have a sandbox on Wikipedia. Turns out I do: https://en.wikipedia.org/wiki/User:Susam_Pal/sandbox
I am not a regular contributor to Wikipedia but the little time I have spent contributing there has exposed me to its very elaborate culture, with barnstars being one artefact of that culture, alongside policy acronyms everyone seems to know by heart, WikiProjects organised around every imaginable topic, userboxes that are little badges that say something about you, etc.
By the way, I added a few userboxes for the Logo programming language, in case there are any Wikipedians out here who happen to love Logo: https://en.wikipedia.org/wiki/Category:User_logo
Tried to edit on my mobile (T-Mobile - US) and got this:
Your IP address has been blocked from editing Wikipedia.
Blocked by Xaosflux
Block will expire in 7 months
I've had the desire to contribute so many times, but each time I was blocked. I don't think Wikipedia accurately measures how much contribution they lose because of the hostile treatment of new editors and what I believe are poorly implemented editing policies. Their policies likely haven't been revised since a decade or more, they should do a survey about it.
I'd wager that most wikis use the MediaWiki software, which is what Wikipedia runs on.
One particular thing that comes to mind though, is that Fossil (https://fossil-scm.org/) has a private local-only sandbox: https://fossil-scm.org/home/wikiedit?name=Sandbox. It saves to your browser's persistent storage, but never on the server.
If you really want something private, there is https://en.wikipedia.org/wiki/Special:ExpandTemplates (or of course just hit preview and dont save)
It's interesting to think about how complex the wikipedia text is compared to something like github flavored markdown or even standard html tables (although I guess it eventually renders into standard html so it's not more complex than the latter when all other html elements are considered in addition to <table>)
For example the swatch internet time infobox is dynamically updated
{{short description|Alternate time system by watch maker Swatch}} {{Infobox | image = [[File:Swatch beat Logo.svg|200px|alt=Logo of Swatch Internet Time]] | caption = Logo of Swatch Internet Time | title = Time{{efn|at page generation }} {{purge|(update to view correct time)}} | label1 = 24-hour time (UTC) | data1 = {{nowrap|{{#time:H:i:s}}}} | label2 = 24-hour time (CET) | data2 = {{Time|CET|dst=no|df-cust=H:i:s|hide-refresh=yes}} | label3 = .beat time (BMT) | data3 = {{nowrap|@{{#expr: floor( {{#expr:{{#expr:{{#expr:{{#time:H|now + 1 hour}}3600}}+{{#expr:{{#time:i}}60}}+{{#time:s}}}}/86.4}} )}}}} }}