[fluffy]Yeah a thing I’ve been meaning to build for my site is a feed customizer that lets people pick and choose which posts to display with a live preview.
[fluffy]okay so here’s a thought… peopel are always talking about feeds with a session key for the purpose of post privacy, but there’s good reasons not to do that. However, having a session key that ties feed preferences to a user? that feels totally kosher.
[fluffy]also the click-through on an entry could theoretically have the session embedded in the entry link and that can be like, oh cool this person wants to see more like this, or it can present UX to the person who clicked through anyway
[fluffy]there would still be some trickiness with like… what happens if someone shares a customized feed item? and if they do it as an atom share, the feed URL gets shared too, so that can cause issues
[fluffy]or, alternately, this is another use case for bearer tokens provided via TicketAuth et al: the feed reader is then identifying the user as part of the feed fetching.
[jacky]I think that the light tracking/adjustment done there _might_ need to be something in the reader but I'm guessing you mentioned this to help people manage their own subscription _to you_
tomlarkworthyprobably to specific for use with https://indiewebify.me/ but it demonstrates flipping the dialog to what you want to do (e.g. login with facebook) and then telling you the steps to achieve that (relmeauth backlink)
[KevinMarks], gRegorLove and gRegorLove_ joined the channel
sparseMatrixheh, sometimes you just gotta knuckle down and read the docs from the beginning. I've been trying to wrangle nginx, which as some of you know, is completely new to me. After reading up a bit over coffee this morning, I discover that the sites-available/sites-enabled methodology is deprecated. A quick check shows that the preferred method, conf.d/, does in fact have a configuration file in it (which I no doubt created in pursuit of some
sparseMatrix...so, looking at this nginx config file, it seems to be a narrative in a procedural scripting language, that is to say, top to bottom, right to left command interpretation/logic evaluation
sparseMatrixI might just be wrong though... nginx may be returning protocol status asynchronously (sending back a 404, for instance) and then carrying on with the 'unreachable' code
[chee]today i'm continuing to try to deal with my mental block on that the base microformat for `image` appears to be `u-photo`, which causes me the greatest of semantic unease. because most of the images i want to post are not photos
[girrodocus]Really useful you sharing this @sparseMatrix! Tonight I will be following a digital ocean tutorial that includes the site-enabled/sites-available method. First time I’ve ever set up nginx or a web server. Total noob.
[KevinMarks]one example of converged naming - we use `name/summary/content` for 3 levels of detail in as many places as possible, though for certain kinds of things `title` seems more natural than `name` in English. in h-card the difference between `photo` and `logo` is significant, and you can likely have both.
[chee]i was going to try to syndicate new tracks from my site to soundcloud, but it turns out the part of their site for creating apps has been replaced with a disabled google form that says "sorry"
[chee]it looks like the best way to push a feed to soundcloud is with IFTTT. i guess they got themselves an API key before Soundcloud replaced their app creation flow with nothing
@BiswasSholanki↩️ Joined the session on webmentions @ChrisAldrich. Definitely an eye opener. Will there be anymore later? I would love to know if there is a way to insert webmentions by server sites which do not support it, so that there is less dependency on them? What say? (twitter.com/_/status/1392890530841862146)
[tantek]that is, that classname is expressing the semantic of "this post is a video", rather than just "this is a video" (which is what the <video> tag is expressing). make sense?
[chee]yes! that makes sense. thank you, tantek. i guess what was bothering me was when i want to say "this post is a picture" my only way to say that is "this post is a photo", which is not true for a lot of these. i really want to say "this post is a ✨Visual Artwork✨"
[tantek]you're right, that's an unfortunate mismatch between what appears to be the precision of "u-photo" and the intent of "this *post* is a still image"
[tantek]and what others said is correct, the history here is that "photo" posts were a strong motivator / driver of this design, though I don't think there was every any intent to be strictly limiting "photo" posts to only actual photographs
sparseMatrix@lahacker I really appreciate the offer, but I'm running linux all over, Idk even if I can zoom that....and no cameras on those machines for sure
barnabywaltersthe indieweb way of supporting comments is using webmention and h-entry markup, to reply to a post on one site from another site https://indieweb.org/comment
plodenI went looking for examples, and figured that if there were a "mainstream" way to support comments, indieweb.org would be demonstrating/dogfooding it
sknebelfor the microformats parsers we sort-of have a policy of going for something permissive because we want them to be widely used infrastructure, and I think most of them are MIT licensed.