#tanteksnarfed, do you have an issue to track this? or is this a won't fix? or ... ?
#snarfedno issue yet, no. feel free to file one, but it'd obviously need more investigation. eg not sure where it ultimately belongs btw silo.pub, bridgy, and github themselves
#tanteksnarfed, presumably it's too much work for Bridgy to fallback to the older GitHub API when the new API fails like this?
#snarfedhah, good point. low priority, yes, but doable! i'd happily consider accepting a PR
#tanteklow priority but doable is good enough to file an issue for
#Loqijalcine: tantek left you a message 42 minutes ago: What do (features on your website) do you want to finish / launch / start using *before* IWS? Can you add to your entry in https://indieweb.org/2018/Guest_Book ? See mine for example: "Working: for IWS 2018(link)"
#tantekalright, so manual for now for this comment, so I can get past it and file the issue
#Loqi[aaronpk] > What we really need is federated authentication, but that doesn't exist yet.
This sounds like a great use case for IndieAuth. https://www.w3.org/TR/indieauth/
IndieAuth is an OAuth 2.0 extension, which avoids the centralized problems with ex...
#aaronpkmy silo.pub integration isn't configured to do that automatically and I didn't think to edit the comment afterwards
#tantekaaronpk - made it harder to track down your original
#tantekso I could peer to peer directly reply to it
#tantek.comedited /GitHub (+916) "/* POSSE to GitHub */ POSSE reply to comment, and when POSSEing any reply, if issue or prev comment has indie permalink, be sure to in-reply-to that" (view diff)
#aaronpkyeah. I feel like most of the github comments I make aren't long enough to justify the link at the bottom
#Loqi[Tantek Çelik] I think IndieAuth makes a lot of sense as the way to implement a federated login protocol to provide a "simpler UX for OAuth2" login for Gitea as this issue is named.
It would also be possible to provide support for the "with GitHub" portion (as ori...
#aaronpkif the micropub client says to syndicate the post to github, but the in-reply-to URL is not a github URL, then my site checks the actual post i'm replying to and sees if it has a syndication URL that is a github URL, and uses that instead
#aaronpkit does mean that someone can trick me in to favoriting or replying to a random post on github/twitter, but I feel like that's a low risk right now
#tantekso if I supported showing reacji on my posts and you posted a :thumbs-up: to my reply http://tantek.com/2018/155/t1/ then your code would automatically syndicate that reacji to the github POSSE copy also?
#Loqi[Tantek Çelik] I think IndieAuth makes a lot of sense as the way to implement a federated login protocol to provide a "simpler UX for OAuth2" login for Gitea as this issue is named.
It would also be possible to provide support for the "with GitHub" portion (as ori...
#aaronpkhm I don't actualy remember if silo.pub supports reacji
cloud-maingo joined the channel
#aaronpkalso... your post doesn't link to the github copy
#Loqiancarda: tantek left you a message 7 hours, 53 minutes ago: re: what to work on after you get indiewebify.me stuff working, check out https://indieweb.org/IndieMark for step by step new things to add support for to your site, in incremental increasing order of challenge / functionality
#ancardaYeah, I'm reply to that very message, Loqi
iasai joined the channel
#ancardaI think I have level 1 nailed. I don't require JS to do anything on my site, but the experience is slightly enhanced if you have JavaScript. Might want to make sure it's not degraded in anyway (e.g. flash of unstyled content)
#ancardaHuh, I didn't know `h-entry` should use `<article>` (kind forgot about that tag)
#ancardaBookmark, yes -- I'd be happy to move off Pinboard to my personal website. I do have some private bookmarks, so I'll need to figure out how I can show them to myself (can I login via IndieAuth into my own website?)
#ancardaIndieMark Level 2 stresses notes. I have hundreds of posts I got from a silo some time ago, so I could do microblogging there too
#sknebelyou could. or build your own login system and have your own site run an indieauth endpoint, so you can use that to log into other sites instead of indieauth.com
#ancardaI can login today using Selfauth, I just can't initiate that login
#ancardaI really barely understand OAuth 2, so I don't want to get into that
#Loqi[indieweb] indieauth-client-php: Sample implementation and helper methods for an IndieAuth client.
#ancardaDon't worry, the source is safely held on GitHub now. Nothing bad will happen to GitHub :)
#cweiskeI feel vindicated for hosting my git repositories on my own server
renem, swentel and jeremycherfas joined the channel
#ancardaPeople doing POSSE/PESOS/etc..., are you also syndicating comments? e.g. I post an `h-entry` to my website, syndicate it to $silo, and $friend comments on $silo. Do you syndicate that comment back to your website, so it's visible there?
#LoqiBackfeed is the process of syndicating interactions on your POSSE copies back (AKA reverse syndicating) to your original posts https://indieweb.org/backfeed
#ancardaThat's half the reason I haven't just blocked Facebook in `/etc/hosts` (or similar), as I sometimes need to go use Facebook Messenger or reply to a comment
#swentelnever used facebook ever, so I'm good there heh
firmware joined the channel
#firmware i want to ask if can be made a system in wich ads are not used on websites but instead use mining 10% of CPU power of every visitor of a website, legally with a button to accept or not?
#swentelI'd block your site in an instant to be honest :)
#aaronpkYeah that sounds good. We've done that with Micropub and Webmention right? Probably just copy whatever those pages have
#ancardaSo, my website has been preloaded since about April this year. When do you think it's safe to just turn off port 80? Next year, perhaps?
#ancardaI wonder if that will make me ineligible for HSTS preloading in the future if they ever go to verify eligibility ... as I'd no longer have a service on port 80 to redirect people to 443.
#sknebelyou don't need port 80, it's just that *if* you have something on port 80 it needs to redirect
#sknebelin an indieweb context I'd be wary of non-browser tools though, which don#t know about HSTS
#sknebele.g. if I link to your site from mine, and accidentially write http://, my webmention sender will not figure out to use HTTPS if there's no redirect
#aaronpkI'm a bit scared of turning on HSTS cause it means basically never going back
#aaronpkBut I've run https on my site for a few years now so maybe it's time
#ancardaHonestly, that's why I turned it on; once I had SSL working, I preloaded the site so everything I built going forward *had to work with SSL*
#ancardaIs there a procedure for adding "Level 7" to that page? Sort of tempted to add that to list HSTS Preloading, CAA DNS records, HTTP/2, and maybe TLS 1.3 support.
#ancardaI have 3/4 of those - just waiting for TLS 1.3 to be more widely available
#ancardaaaronpk: If you have mandatory SSL (as in HTTP redirects to HTTPS), then preloading won't really make much of a difference - people already can't use the site without SSL
#aaronpkWell it's more like I become unable to turn off https ever
#ancardaWould you, though? If you've been using it for years, are you going to find a reason to turn it off tomorrow?
#aaronpkThis was more of a concern before letsencrypt, since https certs were kind of a racket and there was no guarantee theyd stay cheap
#ancardaI am worried about everyone using Let's Encrypt - they may get too big to fail. Hopefully other ACME providers will show up
#aaronpkYeah I've been surprised to see even major hosting companies using letsencrypt for their auto https features
#aaronpkeven github issues letsencrypt certs for custom domain github pages
#ancardaaaronpk: In some ways, I think you are already past the point of no return. Since you've been requiring SSL for years, many links to your website go to `https://`. Just now, I searched for your name and the first link on Google was `https://aaronparecki.com/`. You'd need to redirect HTTPS traffic to HTTP. Even with a 301, it could take weeks/months/years? until links are fixed, bookmarks are updated, etc...
#ancardaWould preloading actually make that worse? You'd still need to support HTTPS in some capacity for a few years while browsers are updated to no longer hardcode your domain
#aaronpkYeah, like I said, the last time I considered turning on HSTS was a few years ago, and I just haven't thought about it since
#ancardasknebel: Just how expensive are we talking?
#ancardaI wonder if CloudFlare, maybe Apple, could run ACME CAs. They both (claim to, at-least) care about privacy and security
#sknebelgood question, would have to look for sources. Let's encrypt spends a few million per year.
#aaronpkApple is in a good position to do it. They use CAs for all their provisioning anyway
#sknebelamazon and Google have CAs, but only for their customers
#sknebelApple does not seem like a company that would run such a service for public benefit
#sknebelalthough true, they have established root certs as far as I know
#ancardaWell, I actually think they would; they really care about privacy. Just an example from yesterday is building anti-Facebook tracking into Safari. They also push hard for HTTPS on apps - App Transport Security - for and security privacy reasons
#ancardaIt's much easier for Apple to argue "you can't disable ATS anymore" if they provide free SSL to the public
#ancardaAlso yeah, the internal CAs could now be accessible over a different ACME server, so it's possible to automate code signing
#Loqi[schmarty]: tantek left you a message 15 hours, 58 minutes ago: What do (features on your website) do you want to finish / launch / start using *before* IWS? Can you add to your entry in https://indieweb.org/2018/Guest_Book ? See mine for example: "Working: for IWS 2018(link)"
#Loqi[schmarty]: tantek left you a message 15 hours, 58 minutes ago: What do (features on your website) do you want to finish / launch / start using *before* IWS? Can you add to your entry in https://indieweb.org/2018/Guest_Book ? See mine for example: "Working: for IWS 2018(link)"
#LoqiIt looks like we don't have a page for "edit history" yet. Would you like to create it? (Or just say "edit history is ____", a sentence describing the term)
#Loqiwebfinger has -2 karma in this channel (-12 overall)
#tantekGee I wonder if that (name perpetuation, or what jwz would call "brand necrophilia"), could have anything to do with there being a well-corp-funded *OpenID* Foundation that has to do something to perpetuate its reason for existing
#snarfedbridgy facebook publish will keep working until august, but i'm starting to remove docs now
#LoqiSecure Scuttlebutt is a P2P system to sync message feeds, used to build (among others) social applications that work in off-grid/sneakernet scenarios https://indieweb.org/SSB
#LoqiIt looks like we don't have a page for "OpenID Connect" yet. Would you like to create it? (Or just say "OpenID Connect is ____", a sentence describing the term)
jjuran joined the channel
#tantekOpenID Connect is an authentication protocol built on OAuth 2.0, that in practice is not implemented to provide open identifiers across systems, nor does it have anything to do with [[OpenID]] (1 or 2), but is a way to connect (tie) you to one specific identity provider to use that provider’s services. http://openid.net/connect/
#LoqiSetup/Installation: Facebook - Social Networks Auto-Poster
How to setup Facebook in SNAP WordPress plugin and API
...
#snarfed(to be fair, i also ask for facebook cookies in https://facebook-atom.appspot.com/ . it's horrible practice, i hate doing it. silver lining is, that app doesn't actually store them anywhere...but still.)
#tantek_snarfed, also that's for *reading* not posting right?
#snarfedright, but the practice is just as horrible. cookies have no permissions or compartmentalization. i could easily go wipe out someone's account or do anything else i want with their cookie
#aaronpkThis is why we have OAuth in the first place lol
#aaronpkSo ironically, by Facebook preventing apps from using oauth, they are now effectively encouraging these other terrible behaviors because users have no other options
#snarfedwhich facebook is correctly using, and imposing reasonable policy to not allow the use case i'm working around (horribly) by asking for cookies
#snarfedeh. "encouraging" is maybe a bit too strong. but sure.
#snarfedwe castigate them for not protecting users' privacy enough, then complain when they restrict access. consistency is hard. :P
#dgoldsaw the setting in the gitea config file, so I did some noodling about
#dgoldhad some orking to do in between, but I'm super-pleased to have it functional
#[schmarty]i have a local gitlab setup that i have been itching to replace with gitea, so that is a great reason to do so!
[jgmac1106], AngeloGladding, yoroy, iasai, yoroy_, gRegorLove and eli_oat joined the channel
#@dsample↩️ I can see that point, but sites like OpenHub, Launchpad and other aggregation sites (GitHub could be one) can help with that, like. If we could also use OpenID for SSO, and WebHooks/WebMentions for comms, then we could potentially provide community across distributed remotes too. (twitter.com/_/status/1004111376422449152)
KartikPrabhu, gRegorLove, snarfed, AngeloGladding and [grantcodes] joined the channel
#[grantcodes]Also got my mf2 editor (for micropub clients) supporting just about every property I can think of 😃 With inline preview of images, audio and video. Will need to release it as a reusable react component once it's done
#[grantcodes]Guess I'll need to add a rich editor to get it to be suitable for just about anything
#[grantcodes]The biggest pain is always going to be going from client to server to micropub endpoint (really starting to loath cors). Especially with the media files, I'll need to think about that