#jamietannasnarfed no worries - I think if you had issues publishing we should find out what went wrong, it may have been api issues / rate limiting perhaps?
#Loqijamietanna: [snarfed] left you a message 3 days, 1 hour ago: hah, we forgot to update the redirect_uri on the meetup API app to brid.gy instead of localhost. mind doing that when you get a chance?
[LewisCowles], jjuran and KartikPrabhu joined the channel
#@davidfqIt's encouraging to see how people are getting more and more into personal websites. The next step would be to being able to take the conversation out of Twitter. #webmentions #indieweb (twitter.com/_/status/1230437227714502656)
[jeremycherfas], [grantcodes], [jgmac1106] and [LewisCowles] joined the channel
[KevinMarks], [Rose], jamietanna, KartikPrabhu, [jgmac1106], [LewisCowles] and [snarfed] joined the channel
#[snarfed]jamietanna i'm thinking about cutting new releases of granary and oauth-dropins soon to get the meetup support out there. let me know if you're interested in helping! instructions are in the readmes, they're pretty straightforward, and i can add you on pypi
#Loqi[snarfed]: jamietanna[m] left you a message 7 hours, 29 minutes ago: no worries - I think if you had issues publishing we should find out what went wrong, it may have been api issues / rate limiting perhaps?
#Loqi[snarfed]: jamietanna[m] left you a message 7 hours, 25 minutes ago: no worries - I think if you had issues publishing we should find out what went wrong, it may have been api issues / rate limiting perhaps?
#Loqisivy has 3 karma in this channel over the last year (5 in all channels)
#sknebel[manton]: do you have automated builds for demo pages using the themes? if yes, adding an automated check for the parse result could be a thing?
#jgmac1106ohh that would be cool. I have to download, install post, check, edit, post, check, edit, over and over again for each theme
#jgmac1106….but doing it as a session….could be the intro to microformats session always offered but that leads to a nice outcome of themes that parse correctly
#jgmac1106other thing I need to work on are the page building demos for people I have encouraged to sign up. Those will be fun to do, not this weekend though
#[manton]That's interesting. I don't have any automated checks for the themes but could add something. That would also be helpful for people building custom themes.
#jgmac1106^^^^ wow that does sound like a great hack day goal….he hears whispering through the web
#[manton]I'm working on starting a directory of user-submitted themes for people who have taken existing Hugo themes and tweaked them for Micro.blog. Those are very unlikely to have full Microformats.
#[manton]I kind of already have a hack day goal related to replies but we'll see. 🙂
#jgmac1106ohh yeah you have been writing a ton about your thinking, been fun to read
#jgmac1106I know I hate my decontextualized replies but the only way I can avoid it is to use convulted hashtags
#jgmac1106I haven’t figured out how to seperate replies from my notes feed using Known. JeremyCherfas has been working on that too
#[jeremycherfas]S’easy. If you don’t use micropub to create the replies, then Known knows they are a reply, and you can eliminate them from the RSS you share with m.b
#[tantek][manton] count me in for reviewing mf2 in micro.blog themes. Happy to help improve while also figuring out how we can improve our tools like IndieWebifyMe to make it easier for more people to check / improve their mf2
#[tantek]sivy, why first class post "types" in Goldfrog? Why not first class post creating UX first?
#[tantek](sivy, background, many of us are moving / moved away from any kind of explicit post typing in the UI because it's awkward for users, makes them think more than necessary, and creates bad storage legacy as a side effect)
#[tantek][jgmac1106] that's an excellent /repost use-case! Someone post something that includes something you previously posted! Can you add that along with your citation to /repost#Why?
#jgmac1106will do, though I should probably look at the mark up and wrap it an h-cite, I just included the CC license link
#[tantek]sivy, let people create posts with whatever aspects (text, photos, location etc.) that they want to create, in any order, while they're creating
#[tantek]avoid the "pick a post type!" pop-up menu nonsense. that's pretty much dead UX
#[tantek]also users really don't care or want to learn about post types, so don't make them
#[tantek]"first class post type" makes it sound like its the center of the design, including exposing to users
#[tantek]otherwise what do you mean by "first class"?
#jgmac1106and I track down where the u-url-url typo I was making emerged from Known. It uses: “u-url url” I must have copied and carried aling with me and then made typo along the way
#jgmac1106but what tantek was talking about, post type discovery, Known doesn’t do well. It has templates for each post type
#[tantek]a review is just one post in the lifecycle of experience with a specific item
#[tantek]because Known decided to go down that path before we had concluded that post type first UI was a dead end
#jgmac1106Is there a reason I should not switch the rel=permalink to rel=canonical in my Known templates speaking of which
#jgmac1106the beauty to me sivy is then you do not have to worry about the publishing ux at all, if micropub clients map to your site and you build views using post type discovery,….having to design all that publishing UI isnt needed
#jgmac1106posts on untappd are an interesting case study, you can have a review of an item, venue check-ins, and people tags all in one post
#aaronpksivy: for sure, but you don't need explicit post types for that either. for example i can POSSE a post that has a photo to twitter, regardless of what kind of post it is. for example some of my food posts have photos
#aaronpkdo i want to write code that says "if posttype == food || posttype == photo || ..." no, I want to write "if post has a photo"
#aaronpkyeah it's a pretty fundamental difference, but it really simplifies things in the end
#[tantek]it's super important to design this properly to start with, otherwise you'll end up rebuilding later anyway
#[tantek]this is why we're dissuading you from going down the explicit post types path. it's literally a dead end
#[tantek]sivy, correct, you will need heuristics for your POSSEing
#[tantek]also there's a lot of work on that for Twitter as a target in particular in /Twitter#POSSE - for lots of different sets of features, short notes, long notes, with a title (article), with photo(s), replies etc.
gRegorLove, swentel, KartikPrabhu, jjuran, chrisaldrich and SpencerDub joined the channel
#jackyPOSSE is something I wonder a bit about nowadays
#LoqiURL design is the practice of deliberately designing URLs, in particular, permalinks, typically for a better UX for everyone who creates, reads, and shares content https://indieweb.org/URL_design
#aaronpkyes, that's a general nested microformats thing
#aaronpkwhatever element has the h-card, you add the u-author class to that same element and then the h-card becomes the value of the "author" property
#aaronpkit makes more sense with examples, let me see if i can do this real quick
#@fluffy↩️ Short version:
1. Own your data
2. Use intrinsic HTML features to provide simple protocols for data/service discovery (microformats, <link rel>, etc.)
3. Keep the APIs for interop simple
Much of the inter-site communication is via Webmention which is incredibly simple. (twitter.com/_/status/1230600504000077828)
#LoqiInrupt is a startup with the goal of “personal empowerment through data” (similar to the own-your-data IndieWeb principle), and is based on the Solid project, relying on Javascript and RDF https://indieweb.org/Inrupt
#aaronpk[tantek]: i don't think elevator pitches need to survive attempts at use or development to be successful pitches 😂
#[tantek]and if it's not exactly delivered as they expect it they're like, meh I don't get it, make it easy for my entitled attitude or else I don't care
#[fluffy]I try to keep my “elevator pitch” answer generic enough and then focus in on the aspects they care about
#aaronpkthat's the point of a pitch, to get you interested enough to learn more
#[fluffy]like I find it frustrating how much mindshare ActivityPub has gotten given how… well, difficult it is to set anything up with it, and how at its core it’s basically always going to be stuck reinventing Twitter/Tumblr-likes.
#[tantek]ActivityPub has mindshare because of Mastodon, not because of any elevator pitch
#[fluffy]Or at least trying to fit everything into a Twitter/Tumblr-esque mold.
#[fluffy]But part of the pitch is “it’s a W3C recommendation,” ignoring that so is most of IndieWeb
#[tantek]ActivityPub is educating people to expect more from the web and that's a good thing
#[fluffy]My frustration about ActivityPub is mostly because people keep on asking me to add support for it into Publ but like. Every time I stare down that rabbit hole, the rabbit hole stares back.
#Loqi[𝔰𝔞𝔩𝔱 𝔪𝔞𝔯𝔰𝔥] Are you interested in a federated alternative to Goodreads that doesn't use Amazon?because I'm making a federated alternative to Goodreads that doesn't use Amazonhttps://github.com/mouse-reeve/fedireads
#[fluffy](but not things that are behind a login wall, like the vast majority of facebook)
#[fluffy]I also like that IndieWeb mechanisms give me a choice of how I share stuff. Like, a lot of my music posts are soundcloud embeds, but I’ve switched a bunch of them over to bandcamp as I’ve turned them into actual album releases, and in the future I could switch to self-hosting my own audio and using <audio> tags or whatever.
#[fluffy](which I also do on occasion but I don’t like the UX and don’t feel like building a better one just yet)
#[fluffy]Something I’d really like to see improved in the IndieWeb ecosystem is the ability to change URLs more freely. That’s actually a big part of the thing I wrote hoping to be a keynote for IndieWeb Summit. 🙂 Well, being able to handle change in general.
#aaronpksome aspects of that are hard, but some also work automatically
#[fluffy]like, oops, there was a typo in my entry title, it sent out webmentions to things, then I changed my typo and that changed the URL because SEO slugs
#[fluffy]or then the constant headache of “http or https?” rel=canonical only fixes future stuff, it doesn’t help with past mixups.
#aaronpkpretty sure the webmention spec already addresses that in updates?
#[fluffy](and canonical doesn’t handle the typo-changed-a-url thing either)
#[fluffy]Doesn’t it rely on redirections though? That doesn’t help with the http vs https thing.
#[fluffy]Or does it always adopt the new rel=canonical?
#aaronpkyes but you should be serving a redirect at the old url you published anyway
#[fluffy]I don’t redirect http to https though, and that’s on purpose.
#aaronpkand if you do that, then you send a webmention from that URL, and the receiver should recognize that the URL is now a redirect to the new URL
#[fluffy]My http pages provide https as the canonical.
#aaronpkserving the same content on http/https is a different challenge, and also not related to webmention
#[fluffy]It’s related in that there’s multiple URLs that resolve to the same content.
#aaronpkanyway if you have specific issues like this, they would benefit from being tracked as actual issues instead of chat
#[fluffy]Sure, this also was a tangent from another discussion :)
#[fluffy]I do probably need to rework how Pushl handles changed URLs, on that note.
#[fluffy]… oh it looks like I already noticed and fixed that deficiency
#[fluffy]okay so yeah I see that the webmention spec itself never, um, mentions rel=canonical. But supporting that would lead to obvious spoofing attacks. Hm.
#aaronpkright, because webmention is limited to the http and link verification steps rather than interpreting what a page means
#[fluffy]but that doesn’t help with, say, sites that allow multiple domains (example.com vs www.example.com, or questionable.content vs. starwars.horse or whatever)
#[fluffy](the latter isn’ treally an issue because QC’s many domains all redirect rather than serve up the same content but still)
#[fluffy]But it’s still a vagary in the spec, and I’d like to at least get some clarification of a thing that an endpoint should do.
[manton] joined the channel
#sknebelI wouldn't treat them as a redirect, because the owner could just send a mention with the canonical as the source, this check just protects against duplicates if the content is available and multiple urls