#dev 2025-01-04

2025-01-04 UTC
scattershot, gRegor, grufwub and benatkin joined the channel
#
vikanezrimaya content security policy is such a nightmare to work with, but surprisingly disallowing random inline scripts makes my code much cleaner
[qubyte] joined the channel
#
[qubyte] It has so many weird interactions (service workers and import maps come to mind), but I totally agree. Being strict with my CSP headers mace made my code and separation of concerns better too.
#
[qubyte] *made
#
[qubyte] CSP and service workers: https://qubyte.codes/blog/content-security-policy-and-service-workers
#
[qubyte] Import maps and CSP (near the middle) https://qubyte.codes/blog/progressively-enhanced-caching-of-javascript-modules-without-bundling-using-import-maps
nemonical, mooff, jonnybarnes, ttybitnik and Dryusdan joined the channel
#
capjamesg[d] What is a video?
#
Loqi video is a type of post whose primary content is a video file https://indieweb.org/Video
ttybitnik, GuestZero_, sebbu2 and rrix joined the channel
#
aaronpk everybody just calm down and stop rewriting your packages every damn year
#
aaronpk this post brought to you by me trying to update indielogin.com
#
aaronpk oof, upgrading thephpleague route from 3 to 5 is painful
#
aaronpk it all feels like such BS changes too, like I don't actually benefit from having to do this stupid rewrite
#
aaronpk maybe i can get chatgpt to do it for me
#
aaronpk jeez, that worked
#
aaronpk ok the v5 syntax is a little nicer
#
aaronpk which just reinforces my original frustration with how frustrated i was with v3 in the first place, just always seemed like a lot of unnecessary syntax rituals
[schmarty] joined the channel
#
[schmarty] 😮
#
[schmarty] looks like i have bayside stuff on route 5.x. they released phpleague/route 6.x in november!??
#
aaronpk oh no
#
aaronpk the website says 5 is current https://route.thephpleague.com/
#
aaronpk ah release notes say no API changes with 6, just dropping support for php 8.0
#
aaronpk https://github.com/thephpleague/route/releases/tag/6.0.0
#
[schmarty] yeah, looks like no new features, internal rewrites, and honestly a bit of a mess w/ 2 followup releases to fix bugs.
#
aaronpk lovely
#
aaronpk guess that's why it's not even listed on the site yet
#
carrvo[d] For some reason open source projects are supposedly more "mature" if they have active development on them. I might be able to understand that but I never really agreed. Instead I view those without development as potentially being more complete (reached a point to not need more: no bugs being found, features are sufficient, et cetera).
#
aaronpk active development doesn't need to mean changing your API every 10 months tho
#
aaronpk for example, the DB ORM I use says "Idiorm and Paris are now considered to be feature complete as of version 1.5.0. Whilst they will continue to be maintained with bug fixes there will be no further new features added from this point on."
#
aaronpk I helped patch it to support PHP 8.1 which was the latest release 2 years ago https://github.com/j4mie/idiorm/releases/tag/v1.5.8
#
aaronpk but it will likely need more changes in another PHP version or two
#
carrvo[d] Indeed. I understand active development since that is the easiest way to be confident that there will be a response to external factors (security updates, underlying runtime updates, et cetera).
#
carrvo[d] aaronpk, is filling in the testsuite on https://indieauth.rocks/ part of your plan too? I think SelfAuth and indieauth-client-php are good starting examples for "the wild".
#
carrvo[d] At least they were some of the first I came across.
gRegor joined the channel