#ZegnatNo, not in this specific case. Note how the content starts with “RT @estherschindler”. This isn’t the content of the actual tweet that is being reposted.
#ZegnatIt is a little weird. It seems to be saying the h-entry is a repost, but the content of the h-entry is different from the post it is “reposting”. Edge case?
#ZegnatOh, look, Loqi can still fetch the original retweet, even though I can’t access it in my browser at that URL
#sknebelsure, but I would have put the retweetet tweet in the h-cite and the "RT @..." just as text only decoration
#ZegnatYes, that would have worked. I am guessing this is somehow limited to what the Twitter backup is giving? Some more recent retweets may not include the RT prefix.
#skippyindeed. the raw export, and the generated outut from Granary using that export, constrains my ability to tailor the content precisely.
#skippywhen I start posting directly from a micropub endpoint and syndicating to Twitter from there, I'll have more control over the formatting, I think.
#skippysuggestions for proper markup are appreciated.
#skippyexplicit hand-holding on how to do it properly is specifically appreciated! I'm still struggling to comprehend all of this.
#Zegnatskippy, I tend to tweak my markup on a per-post basis, but that is bringing a lot of mf2 fundamentals with me in the back of my mind.
#ZegnatAnd honestly there is never one-true-way when it comes to microformats. Just look to make available for parsing any data you would want to see available if you were interperting a page :)
#skippysure. but i dont want to get into lovingly hand-crafting markup for all 9K tweets in my export. I'm already resigned to the fact that I've lost a lot of media elements when I brought them in.
#ZegnatGWG: I’d say allowing a code to be used twice. That’s something that happens a lot with stateless implementations.
#aaronpkif you're using JWTs for anything, another common error I see is people forgetting to actually validate the JWT signature
#GWGZegnat, I have purging the code once used as a feature exactly.
#aaronpktho that's more an implementation detail thing rather than a spec thing
#GWGAaronpk, you saw how I was storing my tokens. Same for my codes. Not stateless
#ZegnatNice GWG :) stateless ones have to make sure to set short time limits and validate those limits, but even then a code can theoretically be used multiple times. Having state and making sure replay attacks are impossible is good.
#GWGZegnat, I have the WordPress database there anyway, so I have a place to store stuff.
#GWGI am just missing a bunch of safety checks before I will ask for some third party checks.
#aaronpkstateless tokens aren't really useful anyway until you want to either run a bunch of front-end servers and avoid sharing a common database, or if you are operating at a massive scale like google
#GWGI had a bunch of questions of a general nature I was trying to figure out
#ZegnatQuestions of a general nature are good too. Might even be worth turning those into a FAQ. General questions are often shared by many, and asked by few
#GWGSuch as how to explain the relationship between username and password and url
[manton] joined the channel
#[manton][aaronpk] I'm surprised I've never run into this, but is there a prefix convention in Micropub for custom fields in JSON that are likely server/client-specific and not really proposals for broader support? In q=config for example, I was considering adding "microblog-something": "whatever" if I need to convey some extra data to my clients.
#Loqi[manton]: tantek left you a message 1 week, 3 days ago: any particular reason your notes put permalink/published date inside the entry-content instead of the entry-meta like your articles do on http://www.manton.org/ ? (also your articles have author in entry-meta, whereas your notes don't seem to, deliberate? or theme omission?)
#aaronpk[manton]: yep, vendor prefixes from microformats
#ZegnatThere is also mp- right? If they are not supposed to be stored as part of the mf2 blob, but exist only to instruct the micropub server to do a specific thing?
#loqi.meedited /email (+285) "tantek added "Possible IndieAuth via email brainstorming: ask them for their email (like Slack and nearly every other service), then do rel=me discover on their domain, if their domain rel=me links to that email, treat their domain as IndieAuth, send a..." (view diff)
#loqi.meedited /email (+139) "tantek added "^^^ addendum, obv have a blacklist of bigco email providers domains that no one owns as a personal domain (gmail.com, hotmail.com, etc.)" to "See Also"" (view diff)
radedwork, snarfed, snarfed1, singpolyma and pstuifzand joined the channel
#tantek!tell chrisaldrich the /credentialing pages reads like vapor and has zero connection to the indieweb. there's is some bad history in this space, so unless you have real world indieweb examples, I'd like to delete that page until they exist.
#[jjdelc]hi guys, has there been a change in ownyourgram recently? I probably had an incomplete micropub implementation but had to make some changes to continue receiving updates
#[jjdelc]apparently the request changed from being multipart to the mp endpoint and now uses the media endpoint and posts a list with the url obtained from the media endpoint
#aaronpkYou can choose which version you want on your settings page
#aaronpkIt may have upgraded you to the media endpoint version when it detected your media endpoint when you logged in
#aaronpkBut no, none of that has changed in several months
#[jjdelc]uhm.. I see, maybe I had been tweaking with it and not remember
#aaronpktantek: thinking about relmeauth again... if I had an h-card on https://parecki.com that had both mailto:aaron@parecki.com and https://aaronparecki.com in it, do you think that would also work to associate my email address with my domain name? (Assuming you're given my email address to start and want to find my canonical domain)
#tantekyou don't even need the h-card. as long as those links had rel=me on it, that would be enough
#tantekin terms of privacy, security, control etc.
[kevinmarks] joined the channel
#[kevinmarks]we had problems with that before with rel-me, where people linked to a common project and rel-me chaining decided they were the same person
#tantekwhich took many days of brainstorming, at least one meetup, and some prototyping
mindB and [aaronpk] joined the channel
#[aaronpk]Oh yeah I guess it's a shared domain relmeauth problem for URLs too, aside from even involving email addresses
#[aaronpk]singpolyma: lol that *might* work, not sure how many http clients would do that tho
#singpolyma[aaronpk]: it's a standard part of the URL and HTTP specs, major browsers and tools like curl and HTTP libraries for lanugages I've tried support it
#singpolymasome browsers give a warning to users visiting interactively, which is a pain, but that's not your main use case
#[aaronpk]Even passing that url string? I thought most clients made you pass the user part in separately
#singpolymaI am not prepared to answer for "most" but I have used user-parts in URLs with clients in PHP and Ruby with no issue
#singpolymathe main downside is that it can't be "just a static site" server side. need at least some server config to do the routing, or a dynamic site
#[aaronpk]Huh well I'll happily make that page redirect to my domain if it is requested with the username
#tanteksince pretty much no one deals with such http ... @ ... URLs
#singpolymaWell, I think the idea here is discovery from email address. So the user just enters an email address and the client infers the https://
#tantekon another topic, if you were using .dev for your local version of your site, you can't any more in typical browsers, because .dev is on the HSTS pre-load list
#LoqiIt looks like we don't have a page for "local dev setup" yet. Would you like to create it? (Or just say "local dev setup is ____", a sentence describing the term)
#tanteksigh I thought we documented how to do this
#[aaronpk]Yeah I made an SSL cert for mine so I can keep using it
#LoqiIt looks like we don't have a page for "local development" yet. Would you like to create it? (Or just say "local development is ____", a sentence describing the term)
#tanteklocal development is (or local dev, local dev setup) the practice of having a version of your site on your local machine like a laptop that you can use for development purposes, even when offline.
#LoqiIt looks like we don't have a page for "local dev" yet. Would you like to create it? (Or just say "local dev is ____", a sentence describing the term)
#Loqiok, I added "https://indieweb.org/HTTPS#Local - how to get an HTTPS cert for your local dev setup" to a brand new "See Also" section of /local_development
#loqi.meedited /local_development (+104) "tantek added "https://indieweb.org/HTTPS#Local - how to get an HTTPS cert for your local dev setup" to "See Also"" (view diff)
#Loqiok, I added "https://rauchg.com/2014/7-principles-of-rich-web-applications" to the "See Also" section of /js;dr
davy_, davy__, GWG, [mrkrndvs] and [jgmac1106] joined the channel
#tantekwell I've run out of time to try to implement event location map / location POSSEing so that's not happening for this week's HWC
snarfed and leg joined the channel
#skippyis a "repost" expected to be an unmodified share of some link / content; or can a repost also contain original commentary from me about the thing I'm reposting?
#aaronpkIf there's any additional content then it's not a repost anymore
#LoqiA repost on the indieweb is a post that is purely a 100% re-publication of another post. The act of reposting is an umbrella term that covers the general practice of republishing another post typically on the same service or silo, but more and more across sites https://indieweb.org/repost
#LoqiA quote tweet (also known as a "retweet with comment") is a reply on Twitter to an original tweet that displays the entirety of the original in a reply-context below the reply text https://indieweb.org/quote_tweet
#skippyso the indieweb community is drawig a distinction; where the UI and interface at twitter uses a single "retweet" mechanism for both kinds of reposting.
#aaronpkquote tweets work completely different from retweets on twitter tho
#aaronpkthey can have a separate reply thread for example
#Loqi[Eugen] @lifning The next version of Mastodon will be usable only via a plane cockpit interfaceI jest, but I can't really add options for every new thing when people already complain there's too many options.