338 results for "microformats hard"

  • without either of those (link to the h-entry with the problem, and/or markup from the h-entry with the problem), it's hard to verify whether implied u-url is at fault or not
    [tantek] at 2022-12-11 21:40
  • regrets saying it b/c it _is_ not too hard to do 😬
    [jacky] at 2022-12-04 21:00
  • science is hard
    [tantek]3 at 2022-08-25 22:24
  • research is hard
    aaronpk at 2022-08-25 22:24
  • apologies! "naming is hard"
    [snarfed]1 at 2022-08-04 18:57
  • RDF being hard != something not being RDF
    [Simon_Gray]1 at 2022-06-21 16:52
  • Is there a video of this? Really hard to follow all this audio only
    gRegor at 2022-04-29 21:50
  • ↩ That was an awfully formatted “auto-tweet”. Sorry about that. Microformats are hard to get right I guess

    Loqi at 2022-03-07 10:20
  • unrelated to this specifically, but about the parsing spec: since I was gone, has there been any discussion about how multi-line plaintext values are parsed? the way parsers currently handle line breaks and img src and alt text in p- and struct value keys can make them hard to use
    barnaby at 2022-02-23 20:57
  • But if we are indeed talking about writing stuff like ical/vcard entries in plain readable text I was always fan of reStructuredText interpreted text and directives. The goal of rST, driven by the hard to extend nature of old ST, was to have as much as possible forward compatibility and extension points if we want to put in structured data or other features.
    ccx at 2022-02-23 15:59
Sort by:

Filter results by:

Tag

Query took 0.01s.


Search tips

Exclusion
+foo -bar
Logical OR
foo OR bar
Exact phrase
"foo bar"
Partial words
foo*
Particular fields only
title:foo
domain:example.org
nick:somebody
after:2016-11-23
before:2016-11-23
date:2016-11-23