Notices tagged with microformats
-
Tantek ()'s status on Tuesday, 03-Sep-2024 21:47:00 EDT 
Tantek
Twenty years ago this past February, Kevin Marks and I introduced #microformats in a conference presentation.
Full post: https://tantek.com/2024/044/t1/twenty-years-microformats
Aside: This is an even shorter summary of that post from ~200 days ago, which #Mastodon readers never got due to a Mastodon #federation bug (details in https://tantek.com/t5Yo1).
Since early 2023, here are the top three updates & interesting developments in microformats:
1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.)
* Wikipedia, Threads, omg.lol
2. Proposal to merge #microformats2 h-review into h-entry, since in practice (e.g. on #indieweb) reviews are just entries with a bit more.
3. #metaformats adoptions, implementations, iteration -
Tantek ()'s status on Tuesday, 03-Sep-2024 17:02:00 EDT
Tantek
Twenty years ago this past February, @KevinMarks.com (@KevinMarks@xoxo.zone) and I introduced #microformats in a conference presentation.
Full post: https://tantek.com/2024/044/t1/twenty-years-microformats
Aside: This is a summary of a longer post from ~200 days ago¹, which #Mastodon readers never got due to a Mastodon #federation bug (instances returned 202 for post inbox delivery, but did not show post to followers or on local profiles, details in https://tantek.com/t5Yo1).
I wrote a retrospective last year: https://tantek.com/2023/047/t1/nineteen-years-microformats
Since then, here are the top three updates & interesting developments in microformats:
1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.)
* Wikipedia, Threads, omg.lol support
2. A proposal to merge #microformats2 h-review into h-entry, since reviews are in practice (e.g. on the #indieweb) always entries with a bit more information.
3. #metaformats adoptions, implementations, and iteration
More details:
¹ https://tantek.com/2024/044/t1/twenty-years-microformats -
Tantek ()'s status on Saturday, 22-Jun-2024 01:02:00 EDT
Tantek
Happy 12 years of https://indieweb.org/POSSE #POSSE and
19 years of https://microformats.org/ #microformats! (as of yesterday, the 20th)
A few highlights from the past year:
POSSE (Publish on your Own Site, Syndicate Elsewhere) has grown steadily as a common practice in the #IndieWeb community, personal sites, CMSs (like Withknown, which itself reached 10 years in May!), and services (like https://micro.blog) for over a decade.
In its 12th year, POSSE broke through to broader technology press and adoption beyond the community. For example:
* David Pierce’s (@pierce@mas.to) excellent article @TheVerge.com (@verge@mastodon.social): “The poster’s guide to the internet of the future” (https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon):
“Your post appears natively on all of those platforms, typically with some kind of link back to your blog. And your blog becomes the hub for everything, your main home on the internet.
Done right, POSSE is the best of all posting worlds.”
* David also recorded a 29 minute podcast on POSSE with some great interviews: https://podcasts.apple.com/us/podcast/the-posters-guide-to-the-new-internet/id430333725?i=1000632256014
* Cory Doctorow (@craphound.com @doctorow@mamot.fr) declared in his Pluralistic blog (@pluralisticmamot.fr) post: “Vice surrenders” (https://pluralistic.net/2024/02/24/anti-posse/):
“This is the moment for POSSE (Post Own Site, Share Everywhere [sic]), a strategy that sees social media as a strategy for bringing readers to channels that you control”
* And none other than Molly White (@mollywhite.net @molly0xfff@hachyderm.io) of @web3isgoinggreat.com (@web3isgreat@indieweb.social) built, deployed, and started actively using her own POSSE setup as described in her post titled “POSSE” (https://www.mollywhite.net/micro/entry/202403091817) to:
"… write posts in the microblog and automatically crosspost them to Twitter/Mastodon/Bluesky, while keeping the original post on my site."
Congrats Molly and well done!
In its 19th year, the microformats formal #microformats2 syntax and popular vocabularies h-card, h-entry, and h-feed, kept growing across IndieWeb (micro)blogging services and software like CMSs & SSGs both for publishing, and richer peer-to-peer social web interactions via #Webmention.
Beyond the IndieWeb, the rel=me microformat, AKA #relMe, continues to be adopted by services to support #distributed #verification, such as these in the past year:
* Meta Platforms #Threads user profile "Link" field¹
* #Letterboxd user profile website field²
For both POSSE and microformats, there is always more we can do to improve their techniques, technologies, and tools to help people own their content and identities online, while staying connected to friends across the web.
Got suggestions for this coming year? Join us in chat:
* https://chat.indieweb.org/dev
* https://chat.indieweb.org/microformats
for discussions about POSSE and microformats, respectively.
Previously: https://tantek.com/2023/171/t1/anniversaries-microformats-posse
This is post 15 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/151/t1/minimum-interesting-service-worker
→ 🔮
Post glossary:
CMS
https://indieweb.org/CMS
h-card
https://microformats.org/wiki/h-card
h-entry
https://microformats.org/wiki/h-entry
h-feed
https://microformats.org/wiki/h-feed
microformats2 syntax
https://microformats.org/wiki/microformats2-parsing
rel-me
https://microformats.org/wiki/rel-me
SSG
https://indieweb.org/SSG
Webmention
https://indieweb.org/Webmention
Withknown
https://indieweb.org/Known
References:
¹ https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me
² https://indieweb.org/rel-me#Letterboxd -
Tantek ()'s status on Wednesday, 14-Feb-2024 01:03:00 EST
Tantek
Twenty years and two days ago, @KevinMarks.com (@KevinMarks@xoxo.zone @KevinMarks) and I introduced #microformats in a conference presentation.
I wrote a long retrospective last year: https://tantek.com/2023/047/t1/nineteen-years-microformats
Since that post nearly a year ago, here are the top three updates & interesting developments in microformats:
1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.)
* Wikipedia: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me
* Threads: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me
* omg.lol profile links by default: https://home.omg.lol/info/profile-items
2. A proposal to merge h-review into h-entry, since reviews are in practice always entries with a bit more information:
* https://github.com/microformats/h-entry/issues/32
3. #metaformats adoptions, implementations, and iteration
* There was growing practical interest in metaformats, so I updated the spec accordingly
* A half dozen implementations shipped: https://indieweb.org/metaformats#IndieWeb_Examples
* Active discussion for evolving metaformats to support more real world use-cases: https://github.com/microformats/metaformats/issues
Hard to believe it’s been 20 years of iterating and evolving microformats, to #microformats2, growing adoption as #IndieWeb building blocks, distributed verification (those green checkmarks) in #Mastodon and across the #fediverse, and implementing metaformats parsing to standardize parsing various meta tags for link previews into equivalent microformats2.
From last year’s activity, it’s clear there’s more use-cases, implementer interest, and community activity than ever. Looking forward to seeing what we can build in 2024.
Post Glossary
h-entry
https://microformats.org/wiki/h-entry
h-review
https://microformats.org/wiki/h-review
link-preview
https://indieweb.org/link-preview
metaformats
https://microformats.org/wiki/metaformats
microformats
https://microformats.org/wiki/
microformats2
https://microformats.org/wiki/microformats2
rel-me
https://microformats.org/wiki/rel-me -
Tantek ()'s status on Wednesday, 14-Feb-2024 01:03:00 EST
Tantek
Twenty years and two days ago, @KevinMarks.com (@KevinMarks@xoxo.zone @KevinMarks) and I introduced #microformats in a conference presentation.
I wrote a long retrospective last year: https://tantek.com/2023/047/t1/nineteen-years-microformats
Since that update nearly a year ago, here are the top three interesting developments in microformats:
1. Growing rel=me adoption for distributed verification:
* Wikipedia: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me
* Threads: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me
* omg.lol profile links by default: https://home.omg.lol/info/profile-items
2. A proposal to merge h-review into h-entry, since reviews are in practice always entries with a bit more information:
* https://github.com/microformats/h-entry/issues/32
3. #metaformats adoptions, implementations, and iteration
* There was growing practical interest in metaformats, so I updated the spec accordingly
* A half dozen implementations shipped: https://indieweb.org/metaformats#IndieWeb_Examples
* Active discussion for evolving metaformats to support more real world use-cases: https://github.com/microformats/metaformats/issues
Hard to believe it’s been 20 years of iterating and evolving microformats, to #microformats2, growing adoption as #IndieWeb building blocks, distributed verification (those green checkmarks) in #Mastodon and across the #fediverse, and implementing metaformats parsing to standardize parsing various meta tags for link previews into equivalent microformats2.
From last year’s activity, it’s clear there’s more use-cases, implementer interest, and community activity than ever. Looking forward to seeing what we can build in 2024.
Post Glossary
h-entry
https://microformats.org/wiki/h-entry
h-review
https://microformats.org/wiki/h-review
link-preview
https://indieweb.org/link-preview
metaformats
https://microformats.org/wiki/metaformats
microformats
https://microformats.org/wiki/
microformats2
https://microformats.org/wiki/microformats2
rel-me
https://microformats.org/wiki/rel-me -
Tantek ()'s status on Tuesday, 22-Aug-2023 15:43:00 EDT
Tantek
Threads.net now supports the #indieWeb #microformats #openStandard rel-me for distributed ✅ verification!¹ (supported since 2023-08-09)
My Threads profile already had my domain since it was created from my Instagram profile.
View source on https://www.threads.net/@tantek and you can see the #relMe on a link tag:
<link rel="me" href="https://tantek.com/" />
Instructions to add yours:
* Add your domain to your Threads profile "Link" field. That’s it.
Longer explicit steps: https://indieweb.org/rel-me#Threads
Thanks especially to @timothychambers.net (@tchambers@indieweb.social, @timothyjchambers@threads.net) for requesting rel-me support² which one Threads engineer “decided to hack it together” one night!³
You can view Tim’s profile @tchambers@indieweb.social for a real world example of a Mastodon profile showing a green text ✅ verified link to a Threads profile.
Tim made several good points in his request:
“… a small, but disproportionately helpful addition would be to support this "rel=me" feature in your profiles. That could launch well before full ActivityPub, & show the first real integration to open social web standards”
Microformats (and IndieWeb) standards in general are deliberately designed as small, incremental building blocks which are disproportionately helpful as Tim says.
These small building blocks which directly enable user features are usually something a web developer can code at least some (often complete!) support for in one day/night which makes them particularly appealing as a way to rapidly support open #socialWeb standards used by the #fediverse and beyond.
Incrementally implementing microformats & IndieWeb standards⁴ also demonstrates good will and good intentions for supporting the #openWeb.
This is day 44 of #100DaysOfIndieWeb. #100Days
← Day 43: https://tantek.com/2023/171/t1/anniversaries-microformats-posse
→ 🔮
Previously:
* 2023-02-01 Wikipedia.org supports multiple rel=me links: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me
¹ https://www.threads.net/@mosseri/post/Cvu2eXurRbB
² https://www.threads.net/@timothyjchambers/post/CupCvChAxI8
³ https://www.threads.net/@0xjessel/post/Cvu7-A4viZu
⁴ https://spec.indieweb.org/ -
Tantek ()'s status on Tuesday, 20-Jun-2023 19:52:00 EDT
Tantek
Two anniversaries today: microformats (18y) and POSSE (11y).
Happy 18 years of https://microformats.org/ #microformats!
Most prominent this past year (again) has been the littlest #microformat that could:
rel=me — AKA #relme, now effectively the standard for #distributed #verification on the web:
* https://microformats.org/wiki/rel-me (originally introduced in 2004¹)
with support added in the past year for:
* #GitHub multiple rel-me links²
* #Wikipedia User page rel-me link³
, which is surprising since when it was conceived, the #IndieWeb community was in a period of very rapid innovation & iteration.
POSSE itself replaced a previous term, "POSE", short for “Publish Once Syndicate Everywhere”, which had only been around a year or two at most (I’m still looking for the first use of the "POSE" abbreviation for that meaning).
Since “publish once” was vague enough to include practices of publishing once on a social media silo, or in someone else’s garage⁵, we needed to clearly express the requirement to use your own site instead, first, as the source of your truth. Cross-posting to other sites & channels, is a second, optional step, ideally with a permalink linking back to your original post so viewers can easily discover and use your site.
That distinction was enough for POSSE to express a strong creator-owned-first publishing model that resonated and grew. Every time a silo shutdown⁶ at the end of its incredible journey⁷, removing posts & permalinks from the web, POSSE was there for people who were tired of losing their data, permalinks, & profiles, and wanted an alternative.
This is day 43 of #100DaysOfIndieWeb. #100Days
← Day 42: https://tantek.com/2023/160/t1/mastodon-activitypub-follow-form-bridgy-fed
→ 🔮
Glossary
permalink
https://indieweb.org/permalink
POSE
https://indieweb.org/POSE
POSSE
https://indieweb.org/POSSE
silo
https://indieweb.org/silo
References
¹ https://gmpg.org/xfn/11#me
² https://tantek.com/2023/032/t1/years-relmeauth-replace-openid
³ https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me
⁴ https://tantek.com/2012/173/t1/posse-core-indieweb-approach
⁵ https://tantek.com/2023/001/t1/own-your-notes
⁶ https://indieweb.org/site-deaths
⁷ https://ourincrediblejourney.tumblr.com/ -
Tantek ()'s status on Thursday, 16-Feb-2023 20:01:00 EST
Tantek
Nineteen years ago last Saturday, @KevinMarks.com & I introduced¹ #microformats @OReillyMedia ETech 2004, building on "semantic (x)html".
We’ve come a long way since, from methodologies to #microformats2, from publishing to peer-to-peer #IndieWeb use-cases.
We named #microformats only after we had established a pattern of real world examples; even our talk proposal was named RealWorldSemantics², and provided examples in that broader theme.
This exemplified important implicit values in ordering our efforts:
1. get real world things working first, not just theory
2. name them after a pattern emerges, not just solo efforts
3. grow the pattern with proposals, prototypes, iteration, evolution
The examples at that point in time:
* XFN — using rel-values for blogroll semantics, and the technology that defined rel=me in v1.1³, now the standard for decentralized social media verification on Mastodon⁴, GitHub⁵, elsewhere, and the basis of RelMeAuth⁶
* XMDP — XHTML MetaData Profiles, notably using an HTML class⁷ with a particular value 'profile' to indicate presence of a specific semantic structure
* XOXO — XHTML Outlines, formalizing existing usage of (X)HTML elements for outlines, also using an HTML class with a particular value 'xoxo' to express a semantic
Growing the pattern:
* rel=license — solved page licensing better than before, since widespread adopted
* VoteLinks — new rel values, prototyped, only one consuming implementation (since defunct)
And further brainstorming:
* recommendations — initial rel="recommendation" idea eventually evolved to hReview, and today’s h-review
* syndication — helped motivate HTML5 <time> element, eventually led to hAtom, and today’s h-entry
* playlists — led to various ideas, proposals, & demos⁸, still not really solved today
The mid-2000s were a time of eager experimentation, when we were learning that very small bits of markup (yes, hence the name) could be used to build some very useful capabilities on top of the open web platform.
A few observations with the benefit of years of experience since we proposed “microformats”:
One: Many microformats succeeded because we solved an existing problem, with existing *complex* solutions, by providing a drastically *simpler* solution.
XFN instead of FOAF. rel=license instead of Creative Commons RDF in HTML comments.
By doing so, we skipped the often harder problem of defining & refining a problem worth solving, a use-case, or user scenario.
Two: A few microformats succeeded because they solved existing problems, re-using *existing established* open solutions in other formats, reformatted into native HTML.
hCard from vCard. hCalendar from iCalendar.
This methodology leveraged years of prior hard open standards work by numerous others across numerous organizations, and deliberately avoided the bikeshedding trap of renaming things (or any other kind of non-trivial “clean-up”) while reformatting, thus making it easy for developers of one technology to see the 1:1 mapping and use the other.
The primary downside with this approach was formats that were larger than perhaps necessary for HTML-specific use-cases.
Eventually for microformats2 vocabularies, we adopted a subset approach, looking for web publishing use-cases for each feature, making h-card smaller than hCard, and h-event smaller than hCalendar.
Three: Success in a search engine was not enough, and sometimes attracted more bad actors than good. @KevinMarks.com, myself, and others at Technorati built search engine indexing and use of rel-tag and hReview, which helped evolve their specifications. A few other small search engines indexed rel=tag markup, however none remain today. hReview was adopted by Google which led to it being heavily spammed.
This pattern repeated itself with other microformats, and eventually we shifted from:
→ of course search is the first obvious use-case
→ search is one use-case among others
→ we need primary use-cases outside of search for longterm ecosystem success
Which leads to the fourth observation.
Four: Publishing alone is not a use-case. There must be multiple consuming code use-cases (beyond search) for a microformat to succeed longterm.
From individual features to whole microformats vocabularies, we learned that not only did there need to be sufficient content being published already, without microformats, that could benefit, but there needed to be good enough consuming code use-cases that benefited users (not just developers). The #IndieWeb community has been exceptionally helpful in both defining such use-cases and iterating on them with implementations.
We still get questions of the form: What’s the best way to mark this up?
I used to very much believe that if you could mark something up more semantically, you should spend the time & effort to do so. This drove a lot of early experiments with markup, and did provide some eventual benefits, most notably when semantic HTML elements provided good hooks for accessibility tools such as screen readers.
Now we know the answer to the question of “How should I mark-up this content?” must be accompanied by specific use-cases for consuming code of that markup.
If there is no consuming code use-case, it is not worth the time to add the mark-up (never mind the maintenance effort over time).
Sometimes one single consuming code use-case is sufficient to justify the time & effort to add more semantic mark-up. If that markup helps screenreaders, then it’s worth it. More often than not however, there must be multiple (again, beyond search) consuming code use-cases for it to be worth adding semantic markup, and certainly for developing new markup, whether microformats features or new microformats.
This focus on and repeated asking of questions like:
* What is the (consuming code) use-case?
* Or how does it benefit readers of this content?
has helped focus our modern microformats efforts on actual benefits to humans first, and machines second (if at all).
If you think of IndieWeb use-cases for existing or new microformats, come join us in the developers chat:
* https://chat.indieweb.org/dev
If you think of other use-cases or want to chat about modern microformats methodologies in general, join us in the microformats chat:
* https://chat.indieweb.org/microformats
This is day 32 of #100DaysOfIndieWeb #100Days
← Day 31: https://tantek.com/2023/044/t1/unified-sent-box-universal-outbox
→ 🔮
Post glossary:
h-card
https://microformats.org/wiki/h-card
h-entry
https://microformats.org/wiki/h-entry
h-event
https://microformats.org/wiki/h-event
h-review
https://microformats.org/wiki/h-review
hAtom
https://microformats.org/wiki/hatom
hCalendar
https://microformats.org/wiki/hcalendar
hCard
https://microformats.org/wiki/hcard
hReview
https://microformats.org/wiki/hreview
rel-license
https://microformats.org/wiki/rel-license
rel-tag
https://microformats.org/wiki/rel-tag
rel-values
https://microformats.org/wiki/existing-rel-values
XFN
https://gmpg.org/xfn/
XMDP
http://gmpg.org/xmdp/description
XOXO
https://microformats.org/wiki/xoxo
Previously, previously, previously:
* https://tantek.com/2019/044/t1/15-years-ago-introduced-microformats
* https://tantek.com/2014/042/t2/ten-years-ago-introduced-microformats-etech
* https://tantek.com/2011/042/t2/years-ago-presented-microformats-etech
* https://twitter.com/t/status/701095802
References:
¹ https://tantek.com/presentations/2004etech/realworldsemanticspres.html
² https://tantek.com/log/2004/02.html#d04t1311
³ https://gmpg.org/xfn/11#me
⁴ https://docs.joinmastodon.org/user/profile/#verification
⁵ https://hachyderm.io/@nova/109790530971147702
⁶ https://tantek.com/2023/032/t1/years-relmeauth-replace-openid
⁷ https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors
⁸ http://microformats.org/wiki/events/2007-12-11-open-media-web -
Tantek ()'s status on Wednesday, 13-Feb-2019 03:29:00 EST
Tantek
15 years ago @KevinMarks & I introduced #microformats @oreillymedia ETech 2004 real world semantics, before #RDFa #microdata etc.
Slides: tantek.com/presentations/2004etech/realworldsemanticspres.html #HTMLFirst & inline #CSS+#JS <15k; faster than JS-only.
Prev: https://twitter.com/t/status/433494367601717248
Since then:
* drop the (X), just HTML
* meta tags still web alchemy, even more bloated DRY rot
* h-entry superceded hAtom/hentry/rel="bookmark" - microformats.org/wiki/h-entry
* recommendations: hReview still more reliable than anything from Google (https://aaronparecki.com/2016/12/17/8/owning-my-reviews). Use h-review today microformats.org/wiki/h-review
* syndication: h-feed publishing/consuming growing rapidly. microformats.org/wiki/h-feed
* music playlists still unsolved for any cross-site/service use-cases
blogged 15 years ago:
* tantek.com/log/2004/02.html#d12t0012 -
Tantek ()'s status on Monday, 11-Jun-2018 16:45:00 EDT
Tantek
my #SFAllHands⚡️intro
* 8 yrs #openweb#standards@Mozilla[1]
* may know me from #CSS[2] #microformats[3] #indieweb[4]
* recently Standards Outreach w@david_bryant
* editing CSS2.2, #CSSscrollbars
* interesting Vouch[5]
* controversial opinion: technical contributors@Mozillashould be actively using their own website, even if just one blog post a year
[1]https://wiki.mozilla.org/Standards
[2]https://wiki.mozilla.org/CSS
[3]microformats.org
[4]https://indieweb.org/
[5]https://indieweb.org/Vouch- vouching as a practical decentralized solution to commenting, with some trust without requiring a hard-identity, designed to reduce abuse etc. as we have seen in centralized social media, but distributed across the web peer-to-peer -
Tantek ()'s status on Saturday, 29-Apr-2017 12:59:52 EDT
Tantek
Wednesday #100DoPPd97
Setup microblog/@t
Great #microformats& #indiewebsupport!
rel=me h-feed Micropub WebSub etc.
Micro.blogis using Micropub as their standard modern posting API:
*http://help.micro.blog/2017/api-posting/
For publishing, in addition to RSS & JSON,micro.blogpublishes rich structured feeds with microformats2!
*http://help.micro.blog/2017/api-feeds/
As well as subscribes to your own personal site feed(s) using WebSub! (which I’m doing withmicro.blog/t)
Last but not least, instead of proprietary "verified" mechanisms,micro.blogis exclusively using the very well established rel=me microformat for website verification:
*http://help.micro.blog/2017/web-site-verification/
micro.blog, at early rollout time to Kickstarter backers, is already one of the most (if not the most) indieweb friendly services out there.
Well done Manton! -
Tantek ()'s status on Saturday, 29-Apr-2017 12:52:50 EDT
Tantek
Wednesday #100DoPPd97:
Setupmicro.blog/t
Great #microformats& #indiewebsupport!
rel=me h-feed Micropub WebSub etc.
Micro.blogis using Micropub as their standard modern posting API:
*http://help.micro.blog/2017/api-posting/
For publishing, in addition to RSS & JSON,micro.blogpublishes rich structured feeds with microformats2!
*http://help.micro.blog/2017/api-feeds/
As well as subscribes to your own personal site feed(s) using WebSub!
Last but not least, instead of proprietary "verified" mechanisms,micro.blogis exclusively using the very well established rel=me microformat for website verification:
*http://help.micro.blog/2017/web-site-verification/
micro.blog, at early rollout time to Kickstarter backers, is already one of the most (if not the most) indieweb friendly services out there.
Well done Manton! -
Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca (bobjonkmanformer)'s status on Monday, 12-Sep-2016 20:01:53 EDT 
Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca
Now @Andrew_Sullivan_Cant shows off #Indieweb starting with #microformats -
MMN-o ✅⃠ (mmn)'s status on Sunday, 14-Feb-2016 04:58:50 EST 
MMN-o ✅⃠
@discussthang Then why are you talking about Twitter and Json objects? The rendered text contains #microformats to identify addresses, attachments etc.
All stadeus content and data are available under the