#dev 2022-09-28

2022-09-28 UTC
jacky, aaronpk and geoffo joined the channel
#
vikanezrimaya
ugh the fact that quill still doesn't understand ?q=channel => { uid, name } is somewhat annoying
#
vikanezrimaya
maybe i should remember my php skills and make a PR
jacky, gRegorLove_, angelo and hazem joined the channel
#
jacky
heh if anything, I silently believe aaronpk both doesn't have time to add things to projects and also uses it as a lever to encourage us to make things
#
jacky
is using that as his rationate to be up brainstorming on things
gRegorLove_, jacky, kushal, bterry, bterry1, gRegorLove__, tetov-irc, [jgmac1106], [marksuth], [pfefferle] and geoffo joined the channel
#
Loqi
[itteco] iframely: oEmbed proxy. Supports over 1800 domains via custom parsers, oEmbed, Twitter Cards and Open Graph
kloenk and jacky joined the channel
#
gRegor
Revisiting https://github.com/indieweb/indieauth-client-php/pull/19, I'd like to get a new release if possible. I don't think there's breaking changes, so could be 1.0.2
#
Loqi
[gRegorLove] #19 Add support for IndieAuth metadata endpoint
#
gRegor
Are there any other updates we'd want to get in the new release?
#
[schmarty]
gRegor++ i'm hyped!
#
Loqi
gRegor has 11 karma in this channel over the last year (65 in all channels)
#
Loqi
[Vika] Since Kittybox (or more precisely, its IndieAuth library) doesn’t support omitting PKCE, I found myself unable to log into some apps like Together. Kinda sad, but that’s the price of being on the bleeding edge of the spec, with almost no support ...
#
vikanezrimaya
the funniest part is: Aperture also doesn't seem to work
#
vikanezrimaya
so I guess I'll have to ALSO implement Microsub myself
#
gRegor
This lib already supports PKCE in the current release
#
vikanezrimaya
I did plan to do that eventually
#
gRegor
Depends on clients updating to it, though. indiebookclub.biz uses PKCE
#
vikanezrimaya
gRegor: Quill supports the spec almost perfectly, only not being able to handle missing "scope" in token grant response.
#
vikanezrimaya
I should probably wait until either Quill patches things up or I write my own client and then make the scope parameter in the token grant response only show up if I chose a different set of scopes
#
vikanezrimaya
Considering I just found out that TypeScript is packaged in Nixpkgs and I can use it without messing around with NPM, and also compile ES2022 modules that run directly in modern browsers, I think I should just bite the bullet and write my own web UI for posting
#
vikanezrimaya
(I'm afraid of touching NPM since the drive wiping attack on people with IP addresses from "undesirable" countries)
#
gRegor
What do you mean by Aperture also doesn't seem to work? Doesn't support PKCE?
jacky joined the channel
#
gRegor
Aperture is also using indieauth-client-php, so once that PR is in, it can update to support PKCE.
#
gRegor
Er, *metadata-endpoint, not PKCE
#
vikanezrimaya
Aperture just fails outright.
#
vikanezrimaya
indieauth error
#
vikanezrimaya
The authorization code was not able to be verified
#
vikanezrimaya
i suppose i could try writing my own...
#
gRegor
Maybe it's that same missing scope issue
#
vikanezrimaya
OH WAIT A SECOND.
#
vikanezrimaya
I THINK I MAY OR MAY NOT HAVE A BUG SOMEWHERE?...
#
vikanezrimaya
im not sure i need to check
#
vikanezrimaya
AAAAAAAAAAAAAAAA
#
vikanezrimaya
goes into panic mode
jacky, jan6 and geoffo joined the channel
#
vikanezrimaya
i knew i should've used typescript for my JS shims
#
vikanezrimaya
i sometimes do wish JS would have never existed
[campegg], [chrisaldrich], null1 and jacky joined the channel
#
[aciccarello]
Our company uses a lot of TypeScript. It comes in handy a lot.
#
[aciccarello]
TypeScript support for reading JSDoc annotations has gotten pretty good for IDE tooling. It's handy for when you don't want to add a build tool, but there are limitations for sure and it can get verbose.
#
jacky
Yeah, I've been leaning on the JSDoc annotations, quite handy
#
jacky
that and auto-inference
gRegorLove_, gRegorLove__ and geoffo joined the channel
#
capjamesg
[James_Van_Dyne] What do you think re: a v0.3.0 release soon? Are there any functions we should add before then?
#
capjamesg
angelo Quite a few of the planned functions for indieweb.rocks are already available in indieweb utils :)
#
capjamesg
post type identification / homepage representative h-card / getting webmention headers / getting websub headers
[fluffy] and [James_Van_Dyne] joined the channel
#
[James_Van_Dyne]
[jamesg483] Yeah - I reckon we are. It’s been a while and people won’t use these latest changes unless there’s a release 🙂
#
capjamesg
There are four open PRs to close up then we can make a release.
#
capjamesg
Also, what do you think about this [James_Van_Dyne]: https://github.com/capjamesg/indieweb-utils/issues/41
#
Loqi
[capjamesg] #41 Proposal to allow access to HTTP headers and status code from send_webmention function
#
capjamesg
Oh wait I did that.
#
capjamesg
Never mind.
#
capjamesg
Do we need a SECURITY.md policy?
#
[James_Van_Dyne]
Nah, I don’t think so? Would effectively just say “Open an issue to let us know or email one of the Jameses”
#
capjamesg
I don't think so either.
#
capjamesg
What do you think re: v0.3 vs. v1?
#
[James_Van_Dyne]
Let’s keep it 0.3 for now.
#
[James_Van_Dyne]
v1 seems implies the api is completely stable / won’t change.
#
[snarfed]1
well, won't change in a backward compatible way
#
[snarfed]1
I change my libraries' APIs all the time, but generally don't bump major version unless I break compatibility in some way
barnaby joined the channel
#
capjamesg
[snarfed] Are there any good first issues on Bridgy?
#
capjamesg
Or granary for that matter.
#
capjamesg
On a completely separate note, aaronpk [KevinMarks] [snarfed] was there any collective agreement on this: https://github.com/indieweb/authorship/issues/4
#
Loqi
[snarfed] #4 do we need an h-feed authorship algorithm?
#
[snarfed]1
no movement afaik
#
[snarfed]1
re granary/Bridgy issues, definitely some, but start with any that you care about!
#
[snarfed]1
I'll happily weigh in on how good they'd be as intro issues
#
[KevinMarks]
There is the issue that a feed may not have an author but each entry has one or more (eg a feed of indie news or equivalent composite feed). Conversely, if its a single user blog, then repeating author per entry is redundant and it should inherit from the feed. Atom defines itself this way.
tetov-irc, barnaby, gRegorLove_, geoffo and gRegorLove__ joined the channel