392
results for "microformats hard"
-
Trying to add a talk with two speakers is hard, but OMG look at all the pretty microformats 2.
Loqi
at
2018-10-11 06:01
-
@downes check out issuer: https://github.com/concentricsky/badgr-ui/tree/develop/src/app/issuer @ottonomy said webmention wouldn’t be hard. Weekend hack. Remember webmentions dont require microformats but people parsing social feeds use them (http://jgregorymcverry.com/7689-2/)
Loqi
at
2018-10-04 22:28
-
@downes check out issuer: https://github.com/concentricsky/badgr-ui/tree/develop/src/app/issuer @ottonomy said webmention wouldn’t be hard. Weekend hack. Remember webmentions dont require microformats but people parsing social feeds use them (http://jgregorymcverry.com/7689-2/)
Loqi
at
2018-10-04 22:28
-
https://indiechat.search.cweiske.de/?q=microformats+hard
[jgmac1106]
at
2018-10-04 15:50
-
recurring events are hard no matter what UI you try to use to make them work, especially when they cross a DST boundary
tantek__
at
2018-09-26 02:30
-
recurring events is really hard. Making each a separate event is a good idea.
[kevinmarks]
at
2018-09-19 11:49
-
irc on mobile is hard :/
dmillar
at
2018-09-19 04:51
-
behind a flag, but in the main released branch? I've been trying to figure out how to handle that... implementing proposed changes that have not yet been accepted. I was considering doing it in a separate, unreleased git branch. I don't yet have a great way to pass flags to the parser, though it wouldn't be hard to add
willnorris
at
2018-08-23 20:52
-
miklb, that is in part because different consumers might look for different data points. There are no hard requirements. Your microformats “fail” when the application you are trying to feed the data to needs more.
Zegnat
at
2018-08-20 19:51
-
Worth filing an issue on considering base / resolving relative urls inside e-* markup. Not sure how consuming code would make sense of them otherwise. Though how hard is that for parsers
[tantek]
at
2018-08-17 22:12