ZegnatThat article says the design guidelines tell apps to not display it. But I guess the design guidelines have been changed a few times in the last years ;)
jeremycherfasZegnat, some of the apps that interact with the little silos pnut and 10C do this, but I think it s more a function of the app than of the silo. What exactly do you want documented?
Zegnatjeremycherfas, I would like a post’s parsed microformats to show what app/tool was used to create said post. Several people are already displaying this information, but it is never part of the parsed post.
ZegnatAs an aside to this, systems that use the microformats object as the storage for their posts (like Sink) could then also store the application in that object rather than using extra sidechannels for it
ZegnatI think it is not hard to show that publishing what tool you used is new, we also got some IndieWeb websites documented now. The big question is what property name makes the most sense. That is what is keeping me from putting it in Sink right now.
theReal33mhzpnut has just a little sprinkling of microformats, and the API includes source.id, source.link, source.name in posts and messages to say what app made it.
ZegnatThat makes sense in your usecase aaronpk. But not sure that makes sense for microformats as a whole. (Not to mention underscores are an illegal symbol.)
Loqipnut is a short-messaging social network silo in which messages have a limited length, and you can follow folks, and be followed by folks https://indieweb.org/pnut
[manton]For anyone who sends Webmentions to Micro.blog ([eddie], [aaronpk]...) I'm experimenting with a change this morning to add @username to incoming mentions so that they look more consistent with other replies. I think this'll help any confusing in the timeline.
[eddie]Sounds good! That’s a great solution, [manton] I was conflicted because I didn’t like how my replies didn’t match existing replies but I didn’t want to put @-mentions all over my site
[manton]Cool. Yeah, you shouldn't have to add the username yourself in these cases. Although if you do include a link to the username in the post, it won't try to add it again.
tantek(originally I was motivated by what Twitter displayed on tweet permalinks of the app name used to author the tweet and send it to Twitter's servers)
tantekwow this is a bit more dev, especially the format / syntax discussions, even if they're based on real world UI (as they should be). moving to #indieweb-dev (a bit slow this morning)
LoqiIt looks like we don't have a page for "Fever API" yet. Would you like to create it? (Or just say "Fever API is ____", a sentence describing the term)
sknebelVero is https://vero.co, an Instagram-like social network gaining some publicity in 2018-02, which claims to go for a model sustained by yearly fees and fees from in-app product sales instead of normal advertising models ("claims to" since it is for now free).
Loqiok, I added "http://orbitaloperations.cmail19.com/t/ViewEmail/d/1B72DF75601AC2EB2540EF23F30FEDED/6381983141E8A2A40F8C96E86323F7F9" to a brand new "See Also" section of /Vero
rainbow-zsh!tell jeremycherfas I saw your message on 10C. Responding re: authoring tool attribution in #indieweb-dev, since that’s where discussion appears to have migrated.
Loqi[jeremycherfas]: rainbow-zsh left you a message 32 minutes ago: I saw your message on 10C. Responding re: authoring tool attribution in #indieweb-dev, since that’s where discussion appears to have migrated.
KartikPrabhu, [emilykager], nitot, KapiX, tantek, leg, renem, snarfed, theReal33mhz and Trillium1 joined the channel
LoqiIt looks like we don't have a page for "difference between p-content and e-content" yet. Would you like to create it? (Or just say "difference between p-content and e-content is ____", a sentence describing the term)
LoqiIt looks like we don't have a page for "p-content" yet. Would you like to create it? (Or just say "p-content is ____", a sentence describing the term)