#LoqiCSRF or Cross-Site Request Forgery is an attack that OAuth and IndieAuth clients (relying parties) need to be aware of, wherein victims unknowingly follow a link to a relying party callback URL prepared by an attacker https://indieweb.org/CSRF
#Loqimigration in the context of the indieweb refers to the process of moving your indieweb site from any one or more of one CMS / web host / DNS provider / URL design / domain name to another https://indieweb.org/migration
#LoqiIt looks like we don't have a page for "changing identity" yet. Would you like to create it? (Or just say "changing identity is ____", a sentence describing the term)
#LoqiJekmentions was a service that works as webmention endpoint and saves the received webmentions in a GitHub repository (shut down in 01-2016) https://indieweb.org/Jekmentions
#sknebelthat was a thing, the source should still be around
#sknebelalthough I guess it could be a client feature where you clone an existing post
#sknebelat least for event posts that has been requested before I think
#skippyi have a very specific use case, so its not likely a generally useful thing. Probably better for me to write my own publishing page with the data template I want, rather than shoehorn this into Quill or micropub.
#skippybut then I need to implement indieauth, and all that... *sigh*
#skippyi want a dead simple way to upload new content to my https://skippy.is/ site. Every post has the same format. Right now I'm cooking up a custom micropub endpoint to take the Quill input and create the specific output I need.
#Loqi[skippy] Do you know what I want for my kids? Happiness.
#skippybut it seems so backwards to build up that way. submit the data I want, rather than manipulate the data I get...
#sebselHm, but that does sound more like a display-thing, right? If you change the way your site renders certain elements, you don't have to duplicate it all?
#skippybut i'll still need to manipulate what I get, since i want to resize photos server-side when i get them, rather than require me to resize them on my phone before uploading.
#skippybasically, I want to select a photo, and write a title. the photo should be embedded with the alt text of "skippy is {{ title }}".
#skippyi'm still futzing with micropub, and learning. it's a fun diversion from $work.
#skippyspeaking of, I have a meeting to attend now!
#LoqiJSON (abbreviation for JavaScript Object Notation) is a data serialization format often used by HTTP APIs, growing in popularity instead of XML, and also the canonical output of microformats2 parsers https://indieweb.org/JSON
#aaronpkSo it seems like that app would need a way to tell the server to send push notifications there
#grantcodesPerhaps differently per reader? Or by the server but then the server would probably want to link to a reader to actually view the notification.
#aaronpkOr if indigenous ran a server it could subscribe to the notifications channel
#aaronpkThere's also those generic push notification apps that we could take advantage of
#grantcodesYeah I was going to go down the route of subscribing to the channel on the reader server but will be a lot of polling at the moment :P
#aaronpkYeah I'm gonna add something like WebSub to Aperture channels eventually
cweiske joined the channel
#aaronpkBut I do think eddie shouldn't have to run a complicated server to send push notifications
#grantcodesThe only issue I see with non-readers sending notifications is linking to somewhere where you can actually read / take action on the notifications
#sknebeland (in non-web cases) having something setup to receive those
#aaronpkMost notifications have a url by definition, like the original post of the comment
#aaronpkBut that's of course not the case for clustered notifications
#sknebelan option could be to have a configureable url prefix, so you could send a notification for together.domain/?url=<post>
#grantcodesYeah in general they have urls but not always
#grantcodessknebel: think it's very likely you'd have different readers on different devices though so you wouldn't always want to use one reader to read your notifications
#sknebelgrantcodes: sure, that'd have to be per push-subscription
#[eddie]“eddie shouldn’t have to run a complicated server to send push notifications” unfortunately that is the definition of a server that sends push notifications to iOS devices “run a complicated server”
#[eddie]But I will have to have a server running that has my certificates from Apple that allow push notifications to be sent through to iOS. Whether I have a micropub endpoint, a WebSub subscription or a third type of forwarding mechanism, those should all be fairly simple considering the server has to exist and push content to Apple anyway
#[snarfed]you probably already know, but you can use services to send push notifs instead of running your own server with apple certs. pushover, pushbullet, etc
#@aswath@Paul__Walsh@PaulSweeney Built on OAuth & email auth code. ID is owned page, listing email id & OAuth prov who allow two-way links (currently Twitter & Github). A 3rd party verifier w "4-way dance" bw user, OAuth IdP, indieauth verifier & RP. (twitter.com/_/status/977267309910904833)
#[eddie]I looked at https://indieweb.org/reply-context but I couldn’t really find anything like what I was looking for. Does anyone know of any good examples of markup for reply contexts where the post being replied to is an article and some content from the article is being quoted in the reply context?
#[eddie]Content and Summary don’t seem right because it’s not a summary of the entire article and content seems wrong because it’s only a subsection of the content
#skippyanyone using Known in a container? I'm trying to figure out how best to use different tools for different sites on the same host. I have a WP multi-site in /var/www/html; and a PHP Docker container mounting /var/www/html into the container. That makes it hard(er) for me to easily add other PHP-powered solutions at docroots of other domains...
#gRegorLoveI use h-cite e-content when I'm /quote a book, so would probably do similar in a reply-context.
#gRegorLoveWithout a specific consuming case, I think `content` or `summary` is fine.
#[eddie]Okay :thumbsup: I’ll go with summary for now since I use content for full-length notes
#sebselI had a fancy solution with one nginx based docker that automatically created a https cert via Letsencrypt for any docker you brought up with a host-name in the env.
#sebselNot really using it anymore, I believe, but it worked.
#[eddie]oh cool. I’ll take a look at that too gRegorLove!
#skippyi think i could create all my sites as sub-dirs under, say, /srv; and then mount /srv into my PHP container. That way they'd all share the same PHP root, but have different docroots under /srv....
#skippysebsel: I use Caddy. it handles all the Lets Encrypt for me. :)
#LoqiDocker provides a way to package an application into a "container" that includes all the dependencies it needs to run https://indieweb.org/Docker
#skippyi dislike my source code apps living in containers because it requires more effort. WP has auto-upgrades of the source PHP files. I dont relish the notion of babysitting container upgrades for each WP release.
#skippyso I made a container that run php-fpm with the modules I need/want.
#skippyand i mount the source directory from my host into the container, so that the paths are the same between host and container. caddy proxies php requests to localhost:9000 where php-fpm in the container executes the code.
#kartikprabhu.comedited /trends (+114) "Facebook trends show that Elon Musk has deleted Facebook pages for SpaceX and Tesla" (view diff)
#skippythis set up was fine, before I started eyeballing Known.
#skippyrunning WP and Known at the same time presents a challenge. Unless I want to run one (or both) of them on localhost and use Caddy to proxy public requests to the localhost instance?
#skippyI'm still figuring out how much complexity i want to take on.
#sebselI still don't see why you can't just add another php-fpm container then? But then again, I'm quite new to Docker myself, and your setup sounds complicated already.
#skippyyes, i could use another php container. that seems sub-optimal to me, because they're the same container contents, just listening on different ports.
#@aaronpk@Paul__Walsh Not just from *a* trusted source, since that's what got us into this mess in the first place. IndieAuth is all about letting each person choose an auth provider they trust, even if that is themselves. It's the original goals of OpenID built on OAuth. (twitter.com/_/status/977284631253860352)
#Loqimusician is someone who creates music typically by playing instruments though sometimes by electronic sequencing, and is often a composer of said music too https://indieweb.org/musician
#Loqirel-feed is the standard for linking to multiple (potentially alternative) h-feeds from a site's homepage using the code rel="feed" on those links https://indieweb.org/rel-feed
#tantekaccording to that page it's still actively in use so maybe I'm confused - thought I saw it get deprecated in the HTML spec
#swentelbecause I added 'microformats' feed from aaron as a source in the channel and it found 168 entries, so I'm asuming it's parsing both /syndicated and /all rel="feed" links
#swentelaaronpk, but generally, what do you recommend? microformats or json feeds, or it doesn't really matter?
#aaronpkMicroformats usually gives the best result since it has things like photos, in-reply-to, likes, etc. JSONFeed tends to be the next best, RSS/Atom last
#aaronpkExcept for wordpress sites where the Microformats are almost always messed up because of bad backcompat parsing so I usual subscribe to the XML feeds for those
#LoqiA feed is a dynamic set of posts, typically listed in reverse-chronological order, often only the most recent n (like 10) of them https://indieweb.org/feed
#swentelok, thanks, fixing the markup on my site now, and then ready to start on the android reader :)
#tantek"Another benefit of this is that if there is ever a new syndication feed format, you don’t have to wait for browsers to be updated with the new MIME type to recognise it as a feed." which is exactly what has now happened with JSONfeed
#aaronpkBridgy uses rel=feed from my home page to find my html page with all my posts
#Loqi[aaronpk] Except for wordpress sites where the Microformats are almost always messed up because of bad backcompat parsing so I usual subscribe to the XML feeds for those