#Loqi[gRegor Morrill] “Our level of discomfort with others’ transparency is reflective of our discomfort with our own shortcomings.”
— Wendy Holland, Mission Gathering sermon on February 4, 2018
#tantek.comedited /Leaders (-90) "that was an odd Loqi bug to fix, concerning that I somehow snuck a string into the static "See Also" heading that Loqi added" (view diff)
tantek and renem joined the channel
#tantek!tell aaronpk interesting that your post permalink https://aaronparecki.com/2018/02/08/1/ doesn't show your own follow-up replies to my comment! I'd expect to see the whole thread there.
#Loqiaaronpk: tantek left you a message 1 hour, 4 minutes ago: interesting that your post permalink https://aaronparecki.com/2018/02/08/1/ doesn't show your own follow-up replies to my comment! I'd expect to see the whole thread there.
#aaronpkIt'll happen when I implement threading. There's nothing special about my own replies tho
[eddie] joined the channel
#[eddie]The worst part about iOS development? Code signing and device provisioning. The latest build of Indigenous (full of bug fixes) works fine in my device and simulator but fails when building for TestFlight
#jeremycherfasThat phony760 is so weird. I happen to have Slack open at the same time, and there the message shows as a bunch of black blocks and double border thingies.
#LoqiIt looks like we don't have a page for "removing irc spam" yet. Would you like to create it? (Or just say "removing irc spam is ____", a sentence describing the term)
#ZegnatThe Spam section has a link to the GitHub archive, I didn’t duplicate that link again in the section I wrote. Maybe should have. I’ll do that now.
#ZegnatAh, crap, I was editting to so now I have a conflict with cweiske’s edit
#vanderven.se martijnedited /IRC (+174) "/* How-to remove spam */ Put the edit screenshot in the right list item, add information on where to find the files." (view diff)
#Zegnatjeremycherfas, please see if the How-to on spam is more clear now :) I originally wrote it trying to create a step-by-step guide any one could follow
#Zegnat(though it still depends on having a regular expression compatible text editor :( )
#@sl007@OKNRW@derarndt Seit 4 Jahren arbeite ich an einem dezentralisierten CMS – einige der Technologien (Micropub, Webmention, ActivityPub) sind inzwischen W3C-Empfehlungen. Also nicht falsch verstehen, Eure Idee ist toll. Aber BITTE überlasst das Digi-Feld bundesweit nicht auch noch den Rechten. (twitter.com/_/status/961898047549661184)
#jeremycherfasThat's great for me, and I do know what I'm doing with BBEdit! So I'm armed and dangerous.
#ZegnatI really like BBEdit, one day I might buy it. I’m on the evaluation edition.
[kevinmarks] joined the channel
#jeremycherfasI bought it a long time ago and it is almost certainly overkill for me, but I really like things like multi-folder grep.
#[eddie]Nope, it just worked for me. That said it worked after I submitted two PRs so, you’ll want to be sure you have the latest code from aaronpk’s branch
#dgoldhow do I check the scope being acquired by indigenous
#[eddie]Hmmm that’s a good question. I think I need to add that in to the account debug screen because I don’t think there is currently a way to see that 😕
#[eddie]Headed out to an appt, be back in an hour or two
#ZegnatIf the auth token is in de debug screen, you can make a request with that to your token endpoint yourself dgold. The token endpoint will tell you what scopes that token has.
eli_oat joined the channel
#ZegnatLooking at the aperture code, I think we can also cheat if you need some scopes in there without regenerating the token in indigenous. But probably best not to start of with a hack :P
#ZegnatIn your case `curl -H "Authorization: Bearer %%%" https://tokens.indieauth.com/token` on the command line should do the trick. just replace %%% with the actual token.
snarfed and leg joined the channel
#jeremycherfasZegnat You remember that business about finding out the fields Known will accept by using a GET to the endpoint? Does it have to be an authenticated request?
#ZegnatIt has to be a POST request. It can probably be done with either your current session (as you have it in the browser), or by passing the API key in a header
#Zegnatdgold. Hmm. Then I can’t comment I’m afraid. I don’t run Aperture my self :(
#jeremycherfasZegnat, but "Many pages report some basic information about them by making GET requests, so for example, making a GET request to the same /status/edit endpoint will return, among other things, available syndication methods and the type of object being created."
#[gerwitz](If it doesn’t have “veg” in the title, it’s probably not gerwitz-compatible)
#dgold[gerwitz]: jeremy's 'cast does veggie. and bread
#dgoldhe had a great one a little while ago about US Food Policy in the 70s and 80s, got to speak to some of the architects of the policy too
#jeremycherfasThe hard thing about working on Known's "each page is an endpoint" thing is that each type of page requires a different signature for authentication. Which is a real pain.
#jeremycherfas!tell cweiske should I uninstall my older version of shpub before getting the new one?
#jeremycherfasAnd weirdly, the commands that used to work with the old version, like shpub-0.6.0.phar server now give an error "shpub-0.6.0.phar: command not found"
#[eddie]!tell aaronpk: Does Aperture have any way to funnel posts into the notifications channel? The Microsub spec defines a home and notification channel but I’m not sure how Aperture deals with those right now
#aaronpknow that there's a micropub endpoint, you can write posts to the notifications channel
#aaronpkone of my plans it to make Aperture handle home page webmentions and have those go into the notifications channel. but you could kind of hook that up manually right now if you wanted
#[eddie]Does the notification channel exist? Where I could Micropub to it? Or no, it doesn’t exist in Aperture yet?
#aaronpk[miklb]: my site recognizes when a post has a Twitter POSSE copy, finds the twitter URL, then passes that to silo.pub to send my copy of the like to twitter
#aaronpkit was a bit of code to make that work but not too bad. and silo.pub doing all the API work made it a lot easier
#[miklb]I hadn’t thought about silo.pub, I was looking at using the existing bridgy one in GWG’s plugin. I guess I need to look at what is returned in the micropub like/repost to know exactly what property I can check for. Thanks
#[miklb]this feels like it is moving from an itch to a blocker and I want to solve it once and for all
#[eddie][miklb] a like/repost would return the url of the item liked or reposted. So you would want to first, check if the url is a Twitter url. If so, Bridgy/silo.pub it. Secondly, if it’s not a twitter url, parse it for microformats and check for any twitter u-syndication links, if so Bridgy/silo.pub it
#[miklb]GWG has probably already done the heavy lifting for that second part in WordPress, I’ll just need to find the function to tie into
#snarfedbridgy publish also checks for synd links itself, so alternatively, you could just attempt to bridgy publish everything, and let it fail on non-syndicated posts
#[miklb]thanks, I’d rather get more familiar with micropub, and particularly, your plugin for it. I might be too intimidated to submit any PRs, but we’ll see.
#[miklb]s/intimidated/embarrassed don’t know how to write unit tests/
#[eddie][miklb] I work as a programmer full-time professionally. Over the course of the last decade, I have written less than 10 unit tests 😉 you are in good company
#[eddie]That said I desire to write more, but things get in the way, in hobby projects and in the everyday 9-5 world
#snarfedalternative perspective: i work as a programmer full time too. over the last two decades, i can probably count on one hand the things that have fundamentally changed the way i work. unit tests are at the top of that list, unequivocally for the better.
#Loqisnarfed has 30 karma in this channel (338 overall)
#snarfed(not that i code much at work recently, but that's a different story)
#snarfed[eddie]: over the medium and long term, unit tests will save you significantly more time than they take to write
#ZegnatI have also had a hard time fitting unit tests into my workflow. Because I am often just working off of a very specific specification on the inputs and outputs already.
#[eddie]I think Unit Tests are amazing. If you can, do it :thumbsup: But never be ashamed that you can’t write them. They are, as Snarfed pointed out a time saving optimization
#[eddie]They are totally on my list of things to start doing
#aaronpkI find it really hard to write unit tests for larger projects, especially when there's a UI involved. but I'm a huge fan for libraries and other self-contained parts of a project.
#snarfedagreed! unit testing UI is still hard, selenium etc notwithstanding. but yeah, that still leaves a huge majority of code very testable.
#[eddie]Hopefully I’ll be able to get into it more at work, we use Angular and so part of our current programming cycle, one of our people has started up integrating the Angular testing stuff into our programming environment
#dgoldoh, wow, my notes on getting Watchtower & Aperture working are looong. I don't think I can get these made into blogposts
#[miklb]I just haven’t found the right environment and timing to learn them. Maybe if what I come up with for the micropub plugin will be my first foray. I trust snarfed to be helpful in the PR
#snarfed[eddie]: aha yeah, understood. still doable, but often harder
#aaronpkdgold: you could send a PR to the readme from them
#Loqi[aaronpk] XRay: X-Ray returns structured data from any URL
#ZegnatI find I am writing a lot of code that depends on HTTP stuff. And just having to do all the Request object mocking already turns me off of writing the tests. But I’ll get over that some day.
#dgold:) that was one of the two that I was looking at - that and Compass
#aaronpkZegnat: yeah that's harder for sure. I spent a long time doing the setup for that in XRay but it's totally worth it now.
#ZegnatDiactoros actually seems to come with a really nice Request serialiser and unserialiser. Now that I have done some projects with that lib, I have been thinking about writing tests again.
#snarfedwhile you all are here, feel free to beta test a new feature on https://brid.gy/ i just deployed!
#[eddie]GitHub integration on Bridgy Publish, allows you to post a like of a GitHub repo to your site and then syndicate that into a GitHub repo star. Or post an issue or comment on your site and copy that GitHub
#Loqi[cleverdevil] While I think a Gallery object would be nice, eventually, I am not convinced that its necessarily the best way to go here. Its my understanding that pretty much all Entities support attachments, so doing it in the near-term in a more cross-cutting wa...
#Loqi[Tantek Çelik] Made it to my destination safe and sound.Figured out the next big thing I want to build for my site for the #newwwyear:* POSSE issues^1 and replies to GitHubas part of my #indieweb 2018 stretch goal of owning/POSSEing all* my public posts, specifical...
#stephenpieper.netcreated /User:Stephenpieper.net (+154) "Created page with "https://stephenpieper.net I've been adding bits and pieces of Indieweb structure to my personal Worpress site. Plugins mainly but I'd like to learn more."" (view diff)
#[jjdelc]I suppose since I'm making the endpoints, my protocol understanding questions are dev related
#Loqi[tantek] Proposal: we close all classic mf (AKA mf1) examples-in-wild pages as of 2017, noting that 1. They have been so successful (millions of WP blogs etc.) that no need to track individual examples anymore, and 2. Anyone adding microformats today should b...
#tantekooh interesting - there's a double-auth scenario here
#tanteksnarfed, in the OAuth prompt to Authorize Bridgy, there's a list of "Organization access" and they're all green checkmarked, except for one, which has a grey x instead next to it, and a "Request" button
#snarfedtantek: yup that's common. orgs can choose their default level of oauth app access
#tantekclicking the Request button puts up a dialog box "Send request for approval?"
#snarfed(doesn't really apply to this bridgy feature)
#tantek"Owners will receive an email regarding your request. "
#snarfedthat request goes to the org owners, not to bridgy
#tantek"By requesting this approval, you are asking owners of the ACME organization to allow this application to access private organization data and modify public organization data."
#tantekwhy is Bridgy requesting access to private organization data?
#snarfedhuh, bridgy only asks for the public_repo scope, which afaik is only public data
#tantekis there a way to further constrain the OAuth scope request to not trigger that?
#snarfedgithub's language may not pay enough attention to the scope
#tantekyes it still shows only Public repos for all orgs
#tanteksnarfed, given the recent scares about github accounts going away (people deleting) and getting replaced by new users with same username, where such accounts used to host libraries that got included in things, this is worth thinking about
#@weekstweetsThis morning, the creator of go-bindata deleted their GitHub account and someone else created a new account under the same name. Another reason to pay closer attention to the provenance and security of your software supply chain. https://lnkd.in/dvWXU_4 (twitter.com/_/status/961304627596623874)
#snarfedagain, fortunately, not a vulnerability for bridgy specifically
#tantekmy point is people are more "sensitive" about looking at anything related to Github and security right now, so "Authorize snarfed" being the big green button while the header at the top says "Authorize Bridgy" is likely to raise some red flags
#tantekwhich yes means I'm willing to serve as another contact for that
#snarfedi probably still wouldn't use the bridgy username. juggling multiple github accounts sounds like a bad time, ongoing, for an iffy workaround to a narrow problem
#aaronpkMultiple user accounts are annoying for sure
#snarfedyeah, slightly better. still not sure of the admin tax though
#aaronpkProbably have a better argument to make to request it for an org than a user anyway
#snarfedfirst let's see if anyone actually uses this feature, and if anyone else cares about the UI nit, then maybe it'll be worth revisiting
#snarfedalthough, actually, this is totally unrelated to where the code is hosted. it's just about which github account owns the oauth app. which makes it maybe easier to admin.
#[eddie]snarfed: for what it’s worth I thought “That’s very strange that it says Authorize Snarfed... oh well it’s a Beta” if I came in from outside the community and saw it I would have been pretty confused. That said, I’m not the most security conscious so I very well might have used it anyway
#@weekstweetsThis morning, the creator of go-bindata deleted their GitHub account and someone else created a new account under the same name. Another reason to pay closer attention to the provenance and security of your software supply chain. https://lnkd.in/dvWXU_4 (twitter.com/_/status/961304627596623874)
#tantekback to auto-linking, in particular, @-names
#tantekthere was a question of whether that should be done publish time or view time, also clientside or serverside (which I think is orthogonal?)
#snarfedlol, and you're still not signed up for bridgy github 😂
#tantekgiven that most services that use @-references allow username renaming (and account deletion / recreation by another party), there is the risk (and likely real examples already out there) of autolinked @-names that no longer refer to who they used to when the authoring was done
#tantek(snarfed, sorry, this is what happens with depth-first traversal)
#tanteke.g. CASSIS auto_link does the simple/dumb thing of "just" prefixing with twitter.com/
#tantekwhereas now I'm thinking there needs to be a *publish-time* auto-linking step which captures the *user-id* of the @-name at publish time, and stores that in the post content
#tantekand then the auto-linker should turn that *user-id* into an actual linked @-name at view-time (whether on client or server)
#tantekfor all @-names in a post, the server should discover their user-ids and store them at publish-time as @-name,user-id pairs in a sidetable, for future auto-link resolution
#tantekfor all *links* in a post, the (publishing) server should store the publish-time archive.org URL for each (because of course the publishing server is already pinging archive.org to Save each link right? which returns the archive.org URL for it) in a sidetable
#tantekthese are both sidetables on the post in storage
#tanteksidetables must be updated whenever the post is updated
#tantekwhile keeping any changes/history? e.g. if an @-name to user-id changes, that's worth warning the user about (and likely keeping the original @-name to user-id mapping)
#tantekand for archive.org links, just keep each version with each update
#tantekthat's enough information to auto-link to the current @-name for any given user-id captured at publish-time.
#tantekand if (when?) you find out a link (domain?) has broken, you add it to a deadlinks table (manual update?) which then is a clue to the auto-linker to use the most recent archive.org URL from that sidetable instead
#tantekKevinMarks: I think the cross-service @-mapping is orthogonal and pretty sure it doesn't complexify this at all
#[kevinmarks]The concrete example is instagram, which will remap @'s if the instagram userid has been mapped to a different twitter id and verified by OAuth
#tantek"this" meaning the need to fix the auto-linking for changes in usernames over time
#[kevinmarks]So if I @ name without a domain, the context is messy
#tantekthat's already true without considering the username changing / re-use problem
#tantek1. if you @-mention a name in an IG caption/comment, that will always link to instagram.com / thatname and never be updated, regardless if the owner of "thatname" changes it to "anothername"
#tantekso either those @-mentions break or you end up with old captions/comments linking to new/different accounts than they did when they were written!
#tantek2. if you person-tag someone in an IG photo, that *does* get auto-updated
#tantekIG person-tags are storing their IG user-ids and then displaying (linking) the @-name at view time
#tantek(yes I have found specific examples of this, but with private accounts that I can't share publicly. you should be able to verify the above with a pair of accounts and publishing from one referencing the other, renaming the other)
#tantekso step one - anyone who is auto-linking @-names or links, get and save the user-id for each @-name at publish time, and get and save the archive.org URL for each plain text URL at publish time
#tantekthen in the future you can do step two and improve your auto-linking code to use said storage (either always or when necessary)