#bignosejeremycherfas: thanks. 'twas a bit of both (I'm very jaded on sites that promise an article but hide it behind a bunch of programs I don't accept).
#jeremycherfasBignose: I suspected as much. I’m the same, sometimes.
#KevinMarkswhich is a shame because woodwind is very close to what cleverdevil was asking for
#cweiskeClients and servers must support creating posts using the x-www-form-urlencoded syntax, and may also support creating posts using the JSON syntax.
#[cleverdevil]I still believe that real traction is going to require a native mobile app for iOS and Android, along with a *really* nice and easy to use web app for desktop, or native apps there.
#[cleverdevil]Getting parity with silos in terms of user experience is going to be really tough.
#tantekcleverdevil really curious what makes you think "require a native mobile app"
#LoqiProgressive Web App (PWA) is a web site that a client can progressively enhance into a standalone app that's comparable with a native app https://indieweb.org/PWA
#[cleverdevil]Plus, it gives you integrations with other apps through things like "share sheets."
#[cleverdevil]While they're *available* in PWAs, there aren't really any successful ones that have shown market traction.
#tantekso as a product manager, a *new* "native" app has to really prove why it needs to be native
#[cleverdevil]That's true, and actually, with some of the toolkits that are available today, its pretty easy to build out "native" apps that are really just web apps under the hood.
#[cleverdevil]You want this so you can appear in the various app stores
#[cleverdevil]Slack, for example, is pretty much a web app that is deployed across desktop, mobile, and web.
#KartikPrabhuso... this is a comparison between "old tech" and "emerging tech"
#tantekI think you're setting the right bar though, an indieweb mobile web app needs to "feel" like old/past silo *native* apps
#jaduncan[m]Yes. I want something I can hand to my nontechnical friends, and some of them find the FB UI the limits of their abilities. I don't want a site as user-hostile as FB to be their only choice.
#KevinMarksHaving just Got a new phone, having to reinstall and log into all the native apps is really annoying
#KevinMarksWhereas web apps have my passwords stored because of Chrome
#tantekKevinmarks I think that pain "annoying" is correct. Having just setup a minimal iPod touch for intl travel, I like being very aware of every account I'm giving the iPod in case of it being compromised.
#[cleverdevil]I think having a good responsive web app that supports things like push notifications (a PWA, as tantek calls it) is an awesome first step.
#[cleverdevil]!tell Zegnat the reason for the t.co links is that I used Twitter's "embed Tweet" system to generate the markup to put in my post and I believe that they transform everything to t.co links.
#ZegnatWell, yes, but Twitter’s JS is blocked on my end. So I see your blockquotes. And I was wondering if there was a reason for the URLs in those not being expended.
#[cleverdevil]Ah, yeah, the markup itself came from Twitter.
#ZegnatI mean, I understand why Twitter would put those t.co-s there. But I assume the blockquotes are part of your own markdown. It was just a thought that struck me, doesn’t seem to make a lot of sense to have minimised links in one’s own markup
#LoqiXRay is an open source API that returns structured data for a URL by parsing microformats and following other indieweb algorithms, and is part of the p3k suite of applications https://indieweb.org/XRay
#[cleverdevil]Awesome. Either a Known plugin or a CLI tool based upon Granary would be cool.
#snarfedmaybe, but if it works, don't worry about it
#[cleverdevil]I guess I'd start with a simple CLI tool that I can feed a permalink to a tweet, and then just generate some basic HTML markup that I can paste into my Known site when I want to embed a tweet.
#[cleverdevil]Then, potentially a Known plugin that automatically converts permalink tweets to Twitter embeds.
#[cleverdevil](That'd be better, but I expect would take longer, and I'm much better with Python than with PHP)
#snarfedoh embedding. if you want twitter's official embeds, yeah, that's not granary
#[cleverdevil]I think I likely do, but I'm not married to it.
#snarfedit's literally just inserting the tweet id into the embed template string
#[cleverdevil]The way it worked for me when I embedded these tweets in my post was that I clicked on "Embed Tweet" on the Twitter site, which gave me a <blockquote> containing the full tweet, and a little bit of JavaScript to transform it on the site for people who have JS enabled.
#snarfedright. you can take that blockquote, remove the text, and change the tweet id each time, and it will work for any tweet
#snarfedif you also want the tweet text, you can fetch a granary URL and extract it from the returned JSON. https://granary-demo.appspot.com/ , click on twitter, log in, enter the tweet id in the activity id box, choose format json-mf2, and you'll get a sample granary URL (with API token) that you can change the tweet id in
#snarfedif you get ambitious, your known will have its own twitter api key that you can substitute in
#[cleverdevil]Ah, but that would require JavaScript to be enabled for anything above and beyond the permalink to show up, right?
#Loqibenwerd has 102 karma in this channel (127 overall)
#tantekany notes or blog post about that excellent conversation?
#gRegorLoveI'll review. I've definitely just been copy-pasting for my indie event posts
#benwerdI didn't document, but the conversation was around misinformation (perhaps because we were in a media environment). Talking about how the bigger problem is clickbait, lack of context, and single points of failure for content distribution.
#tantekhmm it was in the Moz weekly project event description also, just removed