File Name   Size Date


jq45tpg8udf.png 387.71 KiB
2019 12 02 - 21:11
   utah 111.46 MiB
2019 06 29 - 03:16
   work 74.42 KiB
2019 11 15 - 18:23


1970 01 01 - 00:00:008fe1e7: https://gjcity.seamlessdocs.com/f/AutoDraft
1970 01 01 - 00:00:0049b8fc: https://www.realtor.com/realestateandhomes-detail/117-E-4th-St_Palisade_CO_81526_M14363-98498#photo1
1970 01 01 - 00:00:0049b8fc: https://www.realtor.com/realestateandhomes-detail/2397-Sayre-Dr_Grand-Junction_CO_81507_M11190-01074#photo27
1970 01 01 - 00:00:0049b8fc: https://www.realtor.com/realestateandhomes-detail/349-Rosevale-Rd_Grand-Junction_CO_81507_M13043-24606#photo21
1970 01 01 - 00:00:0049b8fc: https://www.realtor.com/realestateandhomes-detail/207-29-Rd_Grand-Junction_CO_81503_M21144-24779#photo2
1970 01 01 - 00:00:008fe1e7: https://www.zillow.com/homedetails/537-Crawford-Ln-Palisade-CO-81526/13947330_zpid/?mmlb=g,0
1970 01 01 - 00:00:0049b8fc: moises ai
1970 01 01 - 00:00:0049b8fc: Face Climber
1970 01 01 - 00:00:005e2ff7: Song names: Deep Kissing, Bent-over business
1970 01 01 - 00:00:008fe1e7: USSAN00011618LT
1970 01 01 - 00:00:000c4a0c: https://www.amazon.com/LG-34UC80-B-34-Inch-21-UltraWide/dp/B074JKT894/ref=sr_1_2?keywords=BenQ+EX3501R&qid=1574206479&s=electronics&sr=1-2
1970 01 01 - 00:00:000c4a0c: https://sport.woot.com/offers/mens-printed-dress-shirt-2-pack?ref=w_cnt_sc_is_2_tl

https://electronics.woot.com/offers/pilot-electroluminescent-lightning-cable-2-pack-1?ref=w_cnt_sc_is_1_tl
1970 01 01 - 00:00:008fe1e7: https://eosna.sharefile.com/d-s5d3a33ca14a46b9a
1970 01 01 - 00:00:008fe1e7: https://eosna.sharefile.com/d-s4a0884b5e1e4fc1b
1970 01 01 - 00:00:00b22cbe: Markdown has always seemed to me less like a file format or a formal document syntax and more like a set of strategies for upsampling plain text into such a structured format by looking for the sorts of informal conventions people naturally use when they're writing plain-text documents.
Or - I should say, it infers structure from the sorts of things people did as a matter of course back when we had a network culture based on sending each other blobs of text via email or Usenet. I'm sure the original author of Markdown.pl was not intending to design a new structured document language at all, and simply wanted to pretty-up some plain text files for display on the Web. The structure was already there, the conventions were already in common use, and Markdown.pl was just one strategy for doing something useful with them.

I think it's easy to get people to use Markdown because it doesn't feel like writing in code, and it doesn't feel like writing in code because it's basically just the sort of thing we all did all the time before the web took over.

Ironically, then, I think it actually will make Markdown less useful to build it up as a rigidly specified uniform document protocol offering sophisticated formatting features. There's certainly value in having the various makers of tools doing this job work together toward a common understanding of the patterns people like to use, but it's far less important whether someone uses triple-tickmarks for quoting or four-space-indentation for quoting or whatever, so long as the tool can recognize that they are doing something, take a reasonable guess at what that might be, and then offer a simple way to correct that guess later if the user is particularly concerned about the way the text is being rendered.
1970 01 01 - 00:00:00cca19f: RUNDLL32 PRINTUI.DLL,PrintUIEntry /ga /z /n"\\usgjtj0prt01\Computer Lab (Xerox)"
1970 01 01 - 00:00:00cca19f:
1970 01 01 - 00:00:00cca19f:
1970 01 01 - 00:00:00282389: RUNDLL32 PRINTUI.DLL,PrintUIEntry /ga /z /n\\usgjtj0prt01\Computer Lab (Xerox)
1970 01 01 - 00:00:00282389: RUNDLL32 PRINTUI.DLL,PrintUIEntry /ga /z /n\\computername\printername