tantekWelcome to Tantek's public PBwiki/favicon.ico/feedlogo.giftag:tantek.pbworks.com,2007-01-22:11695079672024-03-25T 3:03:52ZPBworks
This is an Atom formatted XML site feed. It is intended to be viewed in a Newsreader or syndicated to another site.
2024-03-25T03:03:52Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited Markdown'TRON' (1982) This would also work for songs, albums, and books, which are sometimes disambiguated with a parenthesized year. There is potential to expand the parenthetical syntax beyond year and link to other citational information, like author, precise date of publication. see citation styles documented in https://microformats.org/wiki/citation-formats#styles for ideas for extending this, or separate citation text formats that are recognizable for auto-marking up with h-cite. This could work for anything that accepts (URL) for hypermedia. E.g. _Tantek Çelik_ (https://tantek.com/ .h-card .vcard #main-card) for a classnames and ID attributes. The appending of classnames and ID attribute values inside the URL parenthetical would appear like noise to plain text readers so it's not great, but it would be a way to minimally invasively add the ability to add class and ID values to any bit of hypermedia. It could potentially be used for any inline phrase content like: *bold* (.class1 .class2 #id) Which would be discouraged for general text comms usage, however could be useful for folks using this for writing notes or a markdown replacement. Ideally there would be a more human-reader-friendly way (emojis?) to indicate type of a Capitalized Proper Noun (person, place, etc.) which could be turned into a class name in the markup. (not sure how to unobtrusively visually indicate an ID), to avoid many/most uses of class names and ID attributes in normal readable plain text. Emoji space Capitalized Proper Noun? 👤 Tantek -> h-card 📅 IndieWebCamp -> h-event Or we use human readable labels (name:value pairs) derived from citation and library formats, e.g. Category: cat1, Category: cat2, ID:A123), and then have a separate mapping for a set of common Categories (from libraries) into classnames. Category: Person (or Organization) -> h-card, then a catch-all for random one-word categories to h-* equivalents which would handle some like: Category: Event -> h-event, Category: Feed -> h-feed. Could also work for additional properties like start/end datetimes (From: time1, To: time2) or shorter (time1-time2). Needs research into plain text equivalents of specific kinds/pieces of structured data to see which are common enough to be worth doing something with or building on. Hyperlinked images (now supported in https://tantek.com/cassis.js auto_link) Expanding upon the previous, if the "linktext" were a URL ending in .jpg .gif .png (URL2), then make a hyperlinked image, e.g.: URL2.png or inline: URL2.png (alt-text, URL) or URL2.png (URL, alt-text) Make similar adjustments for Video with hyperlink, Video with poster, Video with poster and hyperlink. Perhaps the parenthetical space/comma delimited items have potential beyond two values, especially if each item inside has a "type" that can imply its usage, e.g. video-URL.mp4URL2.png (alt-text, URL, .class, #id) video-URL.mp4 (alt-text, poster-URL.jpg, URL). OnlyURL, .class, #id) Only works to have one Video with hyperlink Expanding upon Hyperlinked images, if the URL2 ended in .mp4 .mov .ogv, then make a video with fallback hyperlink, e.g.: URL2.mp4 URL ]]>false2024-03-25T01:03:52Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited Markdown7. Indented text should mean blockquote or just pre-wrap (friendlier), not code block (based on normal readability expectations and normal non-coding usage being preferred over coder-specific usage). Outline of use-cases clusters Markdown problems are a key motivation for replacing Markdown with something simpler and better fitting its primary design goal, however a good replacement should have its own set of direct user use-cases to help fulfill scope and not exceed it. These fall into the following categories (which could be implemented as modules, or even function options) textinline text semantics & styling & shortcodes (abbreviation, italic, bold, underline) auto-linking (URLs with or without http, @-mentions, @-@s) auto-embedding (images, videos, iframes) hyperlinking (text, images) and other attributes on content (e.g. alt text)underline, emoticons to emoji) block semantics & styling (headings, lists, paragraphs, blockquotes, preformatted, figures, code blocks) auto-linking (URLs with or without http, @-mentions, @-@s, ^n footnotes) auto-embedding (images, videos, iframes) hypermedia (linked text, images) and other attributes on content (e.g. alt text) Considering also: more HTML inline semantics (time, data) more HTML block semantics ? additional use-cases from BBCode, MyCode, AsciiDoc, reStructuredText, e.g. inline styling: strikethrough, monospace block semantics: citations / bibliography use-cases brought up in IndieWeb chat: citations / bibliography call-outscall-out Leaving out for now: table layout and& styling Consider sorting use-cases by how many different https://en.wikipedia.org/wiki/Lightweight_markup_language attempt solutions for them. Modest solutions summary Solutions for Markdown's problems can be derived by going back to Markdown's original design principle, and (re)starting from that. A summary of modest proposals for fixing these problems based on what people type and/or what looks *good* in plain text: easily speakable easily listenable / understandable easily web searchable unique-ish hashtag usage look good/better in context of https://en.wikipedia.org/wiki/Lightweight_markup_language .. Good words to consider — short, positive, 1-2 syllables, evocative of functionality text write link rich mark — potential association / complementary / competitive with "markdown" chat — association with broadlybroad implementations ... Past improvement ideas Some ideas for improving Markdown that seemed like decent incremental improvements, but later I decided they weren't that much better, or far more drastic solutions/changes were needed. Expand Link Styling Syntax ]]>false2024-03-21T18:03:36Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited Markdownzeromark — similarly, zero markup is the goal, like not even "a little bit" (as crept immediately into classic Markdown) ... Rejected — ideas at one point that don't work markdoubtMarkDoubt — why inject doubt name in any means? CommonText — already overloaded with libraries, functions, npm. too wordy. positive: clear alternative to CommonMark ... Avoid — naming patterns to avoid negative words — avoid negative associations lots of syllables — 3+ syllables take longer to speak and will likely be shortened if adopted, so shorten in advance very common word or phrase — likely to be overloaded and hard to discover via web search Consider words (or pair of words) that are positive direct describe functionality two syllables total easily speakable easily listenable / understandable easily web searchable unique-ish hashtag usage .. Good words to consider — short, positive, 1-2 syllables, evocative of functionality text write link rich mark — potential association / complementary / competitive with "markdown" chat — association with broadly implementations ... Past improvement ideas Some ideas for improving Markdown that seemed like decent incremental improvements, but later I decided they weren't that much better, or far more drastic solutions/changes were needed. Expand Link Styling Syntax ]]>false2024-01-25T02:01:24Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited MarkdownHTML (Hyper Text Markup Language) Yet rather than generating: <abbr title="abbreviation">ABBR</abbr> which<abbr title="Hyper Text Markup Language">HTML</abbr> Which has some accessibility challenges presentation (hiding of the expansion), aexpansion). A perhaps more accessible and be to generate: <abbr aria-labelledby="html_hyper_text_markup_language">ABBR</abbr>aria-labelledby="abbr_abbreviation">ABBR</abbr> (<span id="abbr_abbreviation">abbreviation</span>) <abbr aria-labelledby="html_hyper_text_markup_language">HTML</abbr> (<span id="html_hyper_text_markup_language">Hyper Text Markup though that should be tested to see if it works well in screen readers and other accessibility tools %5B%5D(https://tantek.com/) https://tantek.com/ %5BTantek%5D(https://tantek.com/) ]]>false2024-01-25T02:01:36Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited Markdownfalse2024-01-23T23:01:54Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited Markdownfalse2024-01-23T22:01:45Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited MarkdownPrefixing a line with "> " indicates a blockquote. Example post of mine with "> " lines that was POSSEd to GitHub Markdown as expected: http://tantek.com/2018/064/t1/ Additional '>' chars for nesting blockquotes, e.g. ">> " This use of '>' for quoting has been in use by plain text email/usenet since the 1980s if not earlier. Naming Naming is hard. Nonetheless people have asked me for a name for this fixed, corrected, or replacement for markdown, so here are some thoughts (that I've searched and not found any critical collisions for) tmark VITA / -vita- a mnemonic for the order of video image text-alt/alink or text alink this is growing on me, especially for the mnemonic usefulness VITAL - similar mnemonic, Video Image Text-Alternatve Link, and when fully expanded: VITAL (Video Image Text-Alternative Link) - it also expresses the ABBR (Abbreviation) construct. textup — focusing on the positive, uplifting text, rather than being down about mark(up) writeup — similarly, focused on writing rather than markup or not marking up Name to frame it as explicitly excluding markup: markdownt markdont markdonot / markdonut markzero — distinguish clearly that "down" is not enough, zero apparent markup is the goal, it should look like plain text punctuation and formatting nomark — make it very clear that the key design principle is NO markup, only punctuation that reads well on its own. like NoSQL. zeromark — similarly, zero markup is the goal, like not even "a little bit" (as crept immediately into classic Markdown) ... Rejected — ideas at one point that don't work markdoubt — why inject doubt into a name in any means? ... Auto linking In general auto-link any URLs. See below for exceptions for auto link embedding instead. Auto link embed URLs (implemented in http://tantek.com/github/cassis auto_link) class names inline in documentation, e.g.: validate your h-card with indiewebify.me, and make sure you have a u-url to your home page! examples of HTML attributes with values inline in documentation, e.g.: make sure to put rel=me on hyperlinks on your home page to your other profiles Naming Naming is hard. Nonetheless people have asked me for a name for this fixed, corrected, or replacement for markdown, so here are some thoughts (that I've searched and not found any critical collisions for) tmark VITA / -vita- a mnemonic for the order of video image text-alt/alink or text alink this is growing on me, especially for the mnemonic usefulness VITAL - similar mnemonic, Video Image Text-Alternatve Link, and when fully expanded: VITAL (Video Image Text-Alternative Link) - it also expresses the ABBR (Abbreviation) construct. textup — focusing on the positive, uplifting text, rather than being down about mark(up) writeup — similarly, focused on writing rather than markup or not marking up Name to frame it as explicitly excluding markup: markdownt markdont markdonot / markdonut markzero — distinguish clearly that "down" is not enough, zero apparent markup is the goal, it should look like plain text punctuation and formatting nomark — make it very clear that the key design principle is NO markup, only punctuation that reads well on its own. like NoSQL. zeromark — similarly, zero markup is the goal, like not even "a little bit" (as crept immediately into classic Markdown) ... Rejected — ideas at one point that don't work markdoubt — why inject doubt into a name in any means? ... Past improvement ideas Some ideas for improving Markdown that seemed like decent incremental improvements, but later I decided they weren't that much better, or far more drastic solutions/changes were needed. Expand Link Styling Syntax Update: the Markdown link syntax is not like anything anyone ever types in email. Ditch it. ]]>false2024-01-23T22:01:25Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited MarkdownExisting Problematic Syntax Suggested Improved Syntax *italic* personal use-case, but requested (btrem, others previously) **bold** *bold* - with word boundaries on both sides __underline__ _underline_ , _underlined phrase_ - with word boundaries on both sides ]]>false2024-01-16T05:01:33Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited MarkdownConsidering also: more HTML inline semantics (time, data) more HTML block semantics ? from BBCode, MyCode, AsciiDoc, reStructuredText, e.g. inline styling: strikethrough, monospace block semantics: citations / bibliography use-cases brought up in IndieWeb chat: citations / bibliography call-outs Leaving out for now: table layout and styling Consider sorting use-cases by how many different https://en.wikipedia.org/wiki/Lightweight_markup_language attempt solutions for them. Modest solutions summary ]]>false2024-01-10T03:01:39Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited Markdownfalse2024-01-08T01:01:33Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited Markdownfalse2024-01-08T01:01:41Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited Markdownfalse2024-01-08T01:01:43Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited Markdownfalse2024-01-07T19:01:25Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited Markdown!%5Btext icon%5D(http://w3.org/Icons/text.gif) http://w3.org/Icons/text.gif (text icon) %5B!%5B%5D(http://w3.org/Icons/text.gif)%5D(http://indiewebcamp.com/text) http://w3.org/Icons/text.gif (https://indieweb.org/text) http://w3.org/Icons/text.gif https://indieweb.org/text %5B!%5Btext icon%5D(http://w3.org/Icons/text.gif)%5D(http://indiewebcamp.com/text) http://w3.org/Icons/text.gif (text icon, https://indieweb.org/text) http://w3.org/Icons/text.gif (https://indieweb.org/text, text icon) http://w3.org/Icons/text.gif (text icon) https://indieweb.org/text <iframe src="URL-to-embed"> (Markdown has no explicit syntax of its own for iframes) %5BURL-to-embed%5D — note: if the URL-to-embed has an image file extension, convert to an <img> tag, similarly to <video> or <audio>. The use of an explicit brackets %5B...%5D around an image or video filename may make it more obvious in plaintext that the URL is intended to be viewed inline rather than hyperlinked <iframe aria-label="text summary of embed." src="URL-to-embed"> (Markdown had no explicit syntax of its own for iframes) %5BURL-to-embed%5D (text summary of embed) — a single space between URL & parenthetical alt is preferred for plain text readability but could be optional %5BURL-to-embed%5D (text summary of embed) https://indieweb.org/embedembed, https://indieweb.org/embed) — hyperlink the entire resource to a link %5BURL-to-embed%5D (https://indieweb.org/embed, text summary of embed) %5BURL-to-embed%5D (text summary of embed) https://indieweb.org/embed # H1 # ## H2 ## ### H3 ### #### H4 #### ]]>false2024-01-04T05:01:52Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited Markdown_Tantek_ (https://tantek.com/) — combining prior underline syntax and parenthetical URL work as well. This notation could indicate an explicit preference to attach the link to the previous underlined phrase, avoiding potential false positives of links inline after underscores (unsure of any cases of that). Rejected: Tantek https://tantek.com/ — will likely have too many false positives, and URLs delineated by spaces probably indicate an author intent to keep the URL explicitly visible this would work better than the prior example syntax, _Tantek_ <https://tantek.com/> — since <URL> was/is widely used in plain text emails (before Markdown), and the <...> notation could indicate an explicit preference to attach the link to the previous underlined phrase, avoiding potential false positives of links inline after underscores. However rejecting this because CMoS 6.110 discouraging use of angle brackets to delineate URLs (or anything besides "typesetting instructions", which is quite fitting for HTML tags) %5BTantek's site%5D(https://tantek.com/) _Tantek's site_ (https://tantek.com/) — minimal use of _ to markup a phrase to be underlined, trailing paren link is used by iOS paste linkedtext into txt. Tantek's site (alt-text URL) or also allowing URL2.png (URL alt-text) or inline: URL2.png (alt-text URL) or URL2.png (URL alt-text) To be forgiving of allowing either order since it may be easy to forget a specific order. Also allow comma delimited inside the parentheses for syntactic sugar: URL2.png (alt-text, URL) or also allowing URL2.png (URL, alt-text) Makeor inline: URL2.png (alt-text, URL) or URL2.png (URL, alt-text) Make similar adjustementsadjustments for Video with hyperlink, Video with poster and hyperlinkhyperlink. Perhaps the parenthetical space/comma delimited items have potential beyond two values, especially if each item inside has a "type" that can imply its usage, e.g. video-URL.mp4 (alt-text, poster-URL.jpg, URL). Only works to have one "free text" item inside (and only for alt-text for a media URL), all other items must have no spaces, or be URLs to poster image(s), or alternate formats, or a page hyperlink. Video with hyperlink Expanding upon Hyperlinked images, if the URL2 ended in .mp4 .mov .ogv, then make a video with fallback hyperlink, e.g.: URL2.mp4 URL ]]>false2024-01-04T02:01:54Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited MarkdownPrime Directive From the main description: The overriding design goal for Markdown’s formatting syntax is to make it as readable as possible. The idea is that a Markdown-formatted document should be publishable as-is, as plain text, without looking like it’s been marked up with tags or formatting instructions. it overrides or takes precdenceprecedence or comes first before I've looked at many Markdown extensions, and most violate the principles implied by the design goal(s) description. Most extensions look like line-noise gibberish (much worse than HTML markup), thus their use-cases would be better solved with HTML - no need for such extensions to exist. Just use HTML. Inspiration from empirical usage Another excerpt: ...the single biggest source of inspiration for Markdown’s syntax is the format of plain text email. /italic/ - with word boundaries on both sides. some email prior art for this, no personal use-case, but requested **bold** *bold* - with word boundaries on both sides __underline__ _underline_ , _underlined_phrase__underlined phrase_ - with word boundaries on both sides Allow but discourage: _underlined_phrase_ - less readable than _underlined phrase_ *%5BABBR%5D: abbreviation *%5BHTML%5D: Hyper Text Markup Language ABBR (abbreviation) - restrict to all caps single word, word boundaries on both sides, e.g. HTML (Hyper Text Markup Language) %5B%5D(https://tantek.com/) https://tantek.com/ %5BTantek%5D(https://tantek.com/) _Tantek_ https://tantek.com/ — this could work, or, more explicitly: _Tantek_Tantek (https://tantek.com/) — trailing paren link is used by iOS paste linkedtext into txt. The (...) notation could indicate an explicit preference to attach the link to the previous underlined phrase, avoiding potential false positives of links inline after underscores (unsure of any cases of that). Tantek (https://tantek.com/) — — literally what iOS pastes into a txt from linkedtext, this would roundtrip. roundtrip as a single linkedword. This would also roughly "support" the Markdown Markdown link syntax, while however the brackets in the visible visible link text, which may also useful. Questioning — due This also has the least punctuation necessary to CMoS 6.110 discouraging use of angle bracketsdistinguish an intent to delineate URLs (or anything besides "typesetting instructions", which is quite fitting for HTML tags)link (parenthetical URL) from the linktext (just the prior space delimited word or hyphenated-phrase) _Tantek_ <https://tantek.com/>(https://tantek.com/) — since <URL> was/is widely used in plain text emails (before Markdown),combining prior underline syntax and the <...>parenthetical URL work as well. This notation could indicate an preference to attach the link link to the the previous underlined phrase, avoiding potential false positives positives of links links inline after underscores.underscores (unsure of any cases of that). Rejected: — this mightwill likely have too many false positives, and URLs delineated by spaces probably indicate an author intent to keep the URL explicitly visible _Tantek_ https://tantek.com/ — this would work better the prior example syntax, however still indicates an author intent to keep the URL explicitly visible _Tantek_ <https://tantek.com/> — since <URL> was/is widely used in plain text emails (before Markdown), and the <...> notation could indicate an explicit preference to attach the link to the previous underlined phrase, avoiding potential false positives of links inline after underscores. However rejecting this because CMoS 6.110 discouraging use of angle brackets to delineate URLs (or anything besides "typesetting instructions", which is quite fitting for HTML tags) %5BTantek's site%5D(https://tantek.com/) _Tantek's_site_ https://tantek.com/ — this could work, or, more explicitly: _Tantek's_site__Tantek's site_ (https://tantek.com/) — minimal use of _ to markup a phrase to be underlined, trailing paren link is paste linkedtext into txt. Questioning — due to CMoS 6.110 discouraging Tantek's site (https://tantek.com/) — minimum use of angle bracketspunctuation, an entire line being a parenthesized URL visually attaches it to delineate URLs. _Tantek’s_site_ <https://tantek.com/>the prior entire line of text. Useful for linking an entire block or list item of text _Tantek's site_ (https://tantek.com/) Allow but discourage: _Tantek's_site_ (https://tantek.com/) — same reasoning as above.this is better, however the added "_" between words still feels forced (and inconsistent with use of * or /) _Tantek's_site_ (https://tantek.com/) Rejected: _Tantek's site_ https://tantek.com/ — URLs delineated by spaces probably indicate an author intent to keep the URL explicitly visible _Tantek's_site_ https://tantek.com/ — all the added "_" feel forced, and seem to reduce readability, plus URLs delineated by spaces probably indicate an author intent to keep the URL explicitly visible _Tantek’s_site_ <https://tantek.com/> — rejecting due to CMoS 6.110 discouraging use of angle brackets to delineate URLs. Tantek's site https://tantek.com/ have too many false positivespositives, and a URL on a line by itself may indicate an author intent to keep the URL explicitly visible in the context of lines before and after !%5B%5D(http://w3.org/Icons/text.gif) http://w3.org/Icons/text.gif !%5Btext icon%5D(http://w3.org/Icons/text.gif) http://w3.org/Icons/text.gif (text icon) Good ideas Here are few additions, that I'm convinced are good ideas based on real-world evidence for their need, and real-world publishing experience Hyperlinks with link text We could allow a hyperlinked text block as such: linktext URL or optionally with URL parenthesized with < > (a common plain text email convention) or ( ) (English parenthetical applying to previous word/phrase) linktext <URL> linktext (URL) with URL parenthesized with ( ) (English parenthetical applying to previous word/phrase). is converted to: <a href=URL>linktext</a> Details: If linktext ends with ":" (consider any (sentence or phrase termination) punctuation like:".!?,;:-—*/" - others?) then the linktext is NOT linked to the URL. "something: URL" is a common enough plain text pattern that expresses an intent to show the URL visibly inline that it is better left as-is, with the URL visibly linked to itself. or inline: linktext URL, or linktext <URL>, or linktext (URL), where linktext includes underlining: like _link_text_ URL_link text_ (URL) then the entirety of styling. Use of other stylistingstyle phrasings like *bold* or or /italic text/ URL. Rejected hyperlinked text ideas linktext URL Reason: too likely to have false positives, and URL on its line by itself may be intended as part of a visible linebreaks list. linktext <URL> URL delineated with < > (a common plain text email convention) Reason: CMoS 6.110 discourages use of angle brackets to delineate URLs. Hyperlinked images (now supported in https://tantek.com/cassis.js auto_link) Expanding upon the previous, if the "linktext" were a URL ending in .jpg .gif .png (URL2), then make a hyperlinked image, e.g.: URL2.png URL where each is on a line by itself, or inline: URL2.png URL is converted to: <a href=URL><img src="URL2.png" alt=""/></a> Consider instead: URL2.png (URL) and inline: URL2.png (URL) Alt text for images (2019-078 supported in https://tantek.com/cassis.js auto_link) Another variant of the above, if the URL ends in .jpg .gif .png, text following was not a URL, then use the text following as an image alternate: URL.png or: URL2.png URL (alt-text) Consider instead: URL2.png (alt-text) (URL) but the two parenthesized lines in a row look awkward. URL2.png (alt-text URL) or also allowing URL2.png (URL alt-text) To be forgiving of allowing either order since it may be easy to forget a specific order. Also allow comma delimited inside the parentheses for syntactic sugar: URL2.png (alt-text, URL) or also allowing URL2.png (URL, alt-text) Make similar adjustements for Video with hyperlink, Video with poster, Video with poster and hyperlink Video with hyperlink Expanding upon Hyperlinked images, if the URL2 ended in .mp4 .mov .ogv, then make a video with fallback hyperlink, e.g.: URL2.mp4 URL ]]>false2023-12-05T07:12:57Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited BodyOptimizationMetricscholesterol levels goals: LDL<130, HDL>40 ( >60 is protective), TRG<150. maintain. Total = LDL + HDL + TRG/5. 2011-007 doctor says not to worry about total as long as LDLs are low, and HDL (which is protective) can artificially inflate the total. 2021-238 doctor said to not even bother talking about "total" because it doesn’t accurately convey health (protective effect of HDLs over LDLs). 2023-320: LDL: 100, HDL: 76, TRG: 63 2023-244: not measured 2023-135: LDL: 110, HDL: 76, TRG: 75 2022-311: LDL: 108, HDL: 77, TRG: 64 2022-108: LDL: 109, HDL: 91, TRG: 68 2007-07-12: LDL:131, HDL:74, TRG:66 2007-02-13: LDL:100, HDL:73, TRG:73. blood glucose levels - measured after 8-12 hour fast (no food, only water). goal: <100. 2023-320: 92. D:41.5. ferritin: 197. a1c: 5.4 2023-244: 91 (new best!) 2023-135: 106 (had vitamins that morning, including chewable vitamin C). D:44.3. ferritin: 242. a1c:5.5. 2022-311: 97. D:n/a. ferritin: 323. 2022-108: 104. D:41.7. ferritin: 292. 2007-07-12: 101±5 post workout which due to adrenaline can be higher. 2007-02-13: 95. blood pressure: goal: <120 2023-317: 100/50 after bicycling to doctor's office 2023-270: 100/60 after bicycling to doctor's office 2022-311: 100/50 after bicycling to doctor's office 2022-108: 110/60 after bicycling to doctor's office 2021-235: 90/45 (new best) after bicycling to doctor's office 2009-03-30: 116/68 (after bicycling to doctor's office from home) 2007-07-12: 105/65 "blood pressure of an athlete" - dr. 2007-02-13: 124/70 heart rate (resting) : 2023-317: data missing / 98% O₂ on pulsimeter 2022-311: 60bpm / 98% O₂ on pulsimeter 2022-108: 59bpm / 99% O₂ on pulsimeter 2021-235: data missing 2020-038: data missing 2010 - data missing 2009-03-30: 63bpm best at the time body percentage body fat / weight - measure at the same time every day. goals: ≤12% / ~160lb 2023-314: 17% / 176lb (home) 2023-270: 17% / 172lb (home) 2023-244: 17% / 169lb (home) 2023-134: 19% / 176lb (home) 2022-311: 19% / 176lb (home) ]]>false2023-11-10T19:11:28Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited Whistlefalse2023-11-02T17:11:07Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited Markdownfalse2023-09-29T05:09:14Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited BodyOptimizationMetricscholesterol levels goals: LDL<130, HDL>40 ( >60 is protective), TRG<150. maintain. Total = LDL + HDL + TRG/5. 2011-007 doctor says not to worry about total as long as LDLs are low, and HDL (which is protective) can artificially inflate the total. 2021-238 doctor said to not even bother talking about "total" because it doesn’t accurately convey health (protective effect of HDLs over LDLs). 2023-244: not measured 2023-135: LDL: 110, HDL: 76, TRG: 75 2022-311: LDL: 108, HDL: 77, TRG: 64 2022-108: LDL: 109, HDL: 91, TRG: 68 2021-235: LDL: 135, HDL: 83, TRG: 78 2007-07-12: LDL:131, HDL:74, TRG:66 2007-02-13: LDL:100, HDL:73, TRG:73. blood glucose levels - measured after 8-12 hour fast (no food, only water). goal: <100. 2023-244: 91 (new best!) 2023-135: 106 (had vitamins that morning, including chewable vitamin C). D:44.3. ferritin: 242. a1c:5.5. 2022-311: 97. D:n/a. ferritin: 323. 2022-108: 104. D:41.7. ferritin: 292. 2021-235: 110 (had vitamins that morning, including chewable vitamin C, may have impacted?). Other measure: ferritin:317. 2007-07-12: 101±5 post workout which due to adrenaline can be higher. 2007-02-13: 95. blood pressure: goal: <120 2023-270: 100/60 after bicycling to doctor's office 2022-311: 100/50 after bicycling to doctor's office 2022-108: 110/60 after bicycling to doctor's office 2021-235: 90/45 (new best) after bicycling to doctor's office 2020-038: 115/65 2009-03-30: 116/68 (after bicycling to doctor's office from home) 2007-07-12: 105/65 "blood pressure of an athlete" - dr. 2007-02-13: 124/70 heart rate (resting) : 2022-311: 60pbm60bpm / 98% O₂ on 2022-108: 59bpm / 99% O₂ on pulsimeter 2021-235: data missing 2020-038: data missing 2019-028: 65bpm doctor measured (after biking to doctor's office). measured 60 myself after 2010 - data missing 2009-03-30: 63bpm best at the time body percentage body fat / weight - measure at the same time every day. goals: ≤12% / ~160lb 2023-270: 17% / 172lb (home) 2023-244: 17% / 169lb (home) 2023-134: 19% / 176lb (home) 2022-311: 19% / 176lb (home) 2022-109: 17% / 170lb (home) 2021-235: 16% / 168lb (home) ]]>false2023-09-05T07:09:15Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited WatchFilmsCreed, Creed II Dopamine Empire Records Flight of the Navigator The Fountain +1 Gaslight (1944) Léolo Like Crazy Sullivan's Travels (rec by Debs) The Grand Budapest Hotel(rec by Juliane) Up In The Air (rec. by Jane McG 2015-255) Valley Rising (on Netflix) again: A Few Good Men Blade Runner 2049 Rain Man FavoriteFavorite movies you should see My top favorites (roughly to date as of 2021)2023) Contact Gattaca (especially if you are considering getting your 23andme.com profile — Update: actually just don't) Helvetica Interstellar Objectified Paycheck The Martian Tomorrowland TRON TRON: Legacy And moreMore favorites, by variousin clusters: Favorites cluster 1 Batman Begins Bourne Identity Chitty Chitty Bang Bang The Conversation Enemy of the State Hackers Inception The Matrix Real Genius WarGames Favorites cluster 2 Doctor Strange Edge of Tomorrow Le Fabuleux destin d'Amélie Poulain Fifth Element Star Wars IV-VIPaycheck Run Lola Run Tenet Favorites cluster 3 Black Panther (2018) Blue Crush Gattaca (especially if you are considering getting your 23andme.com profile — Update: actually just don't) Run Lola RunStar Wars IV-VI Wall•E Favorites cluster 4 Blade Runner (original and 2049) Fifth Element Logan's Run Not favorites per se, but recommended for at least a viewing and perhaps a discussion Her Rain Man Favorite TV shows you should watch Occasionally good TV shows seem to appear. I rarely sample most TV, so I'm willing to be convinced that there may be other TV shows out there that don't suck. non-fiction: CosmosbyCarlSagan (7 DVD Set) EvolutionBoxedSet (8 hour PBS special produced by WGBH Boston, narrated by Liam Neeson) Fringe Loki ... 1970s Movies Movies made/released in the 1970s I recommend (in addition to any above) Enter the Dragon (1973, on Netflix as of 2019) ... Aside: many previous favorite/memorable 1980s movies are somewhat (or very) problematic when re-evaluated with modern lenses, so I've deliberately left out several. Definitely worth in-person discussion. 1990s Movies The Crow (1994) Hackers (1995) ... Return to FrontPage. ]]>false2023-06-26T23:06:45Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited TantekInterviewsin 2019 2019-03-17 The Big Web Show: 186: Tantek Çelik—web standards, toolchains, and the decentralized web (download MP3 audio, 45 MB, 1 hour 5 minutes) in 2012 1 hour 35 minutes) (original offline: http://5by5.tv/webahead/46) 2012-04-26 The Big Web Show: Jeffrey Zeldman speaks with Tantek Çelik, web standards lead at Mozilla (Tantek Çelik on Mozilla & Microformats: Big Web Show) (download MP3 audio, 24.3 MB, 52 minutes) 2012-02-14 A List Apart: The Vendor Prefix Predicament: ALA’s Eric Meyer Interviews Tantek Çelik 2012-02-06 Mozilla Hacks Web Developer Blog: Tantek Çelik about the importance of Web Standards 2012-01-18 How would SOPA and PIPA affect your organization? (video, 33 seconds) in 2011 W3C launches Community Groups (original offline: http://www.netmagazine.com/news/w3c-launches-community-groups-111333) in 2010 er sikrere enn Flash (English translation, related(related blog post)post, original offline: http://www.idg.no/computerworld/article176452.ece ) 2010-08-30 digi.no: Legger grunnlaget for vakrere webapps (English translation,( related blog post)post, original offline: http://www.digi.no/849689/legger-grunnlaget-for-vakrere-webapps ) 2010-07-19 PeachpitTV: Tantek Çelik discusses HTML5(video recorded 2010-06-28) tags: HTML5, web apps, native apps, open web applications platform 2010-03-11 monkinetic on Future of DiSo: Interview: Tantek Celik, Conceptualizing DiSo 2.0 in 2008 2007 SXSW: The Vloggies Show: Tantek Çelik interview by Irina Slutsky(video) tags: box model hack, microformats, online video, vlogging Other Press Mentions Collecting until they merit their own page. questions about HTML5 video (original offline: http://www.zdnet.co.uk/blogs/500-words-into-the-future-10014052/a-few-key-questions-about-html5-video-10022196/) - quotes from my "If you want to publish %5BH.264%5Don the Web and you are not doing it for any profit, you have a waiver - it was till 2016 and it was extended indefinitely - if you are not going to make any money off your videos. Whatever the definition is of that. Publishing video is expensive, it takes up bandwidth and there is usually some sort of business model involved where people are trying to recoup some costs. I'm not sure if that falls into the commercial area or not - and I don’t want some consortium to be the judge of that." - this is actually a fairly accurate/reasonable transcription of what I said - nicely done ZDNet. Return to TantekÇelik / FrontPage. ]]>false2023-06-07T01:06:19Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited TxtShorthandsfalse2023-06-06T22:06:18Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited HouseRulesNo illegal drugs. If you partake of such things, please do so off the premises and downwind. No pets*. If you have pet, please leave it at home. Your pet may be awesome to you, and I might trust you, but I don't trust your pet to behave in my house. This is due to past bad experiences with other people's pets (OPP) emitting bad smells, shedding, peeing, throwing up, and crapping, and the respective time and money cost and inconveniences for cleanup, repair, replacement of damaged areas and items. *There is a short list of HousePetExceptions. No VW (See TxtShorthands). No one related to VW (past or present) is allowed on the premises, and discussions related to VW are strongly discouraged. Let's focus on the positive rather than the poisonous. B are now banned. Specific examples: NickStarr and friend Ben. 2008-10-16 Tara Brown's iPhone missing after party at her place, NickStarr's friend Ben (lastname unknown) stronglysuspected. See tweets fromTaraBrown and SeanBonner (2). See also photoofBenandNickStarrtakenthatnight, near where Tara's iPhone was stolen from.Yes this has happened — specific example from 2008 removed. Return to FrontPage. ]]>false2023-06-01T21:06:41Ztag:tantek.pbworks.com,2007-01-22:1169507967 edited ShortURLPrintExamplefalse