Hello! I'm Dan, a UK based full stack web developer with a love of open source software. Most of my free time is spent working on BookStack, playing video-games or getting distracted by one of many hobbies like 3D printing.
I primarily develop in PHP using Laravel, with VueJS being my front-end framework of choice, but I also dabble in Go, NodeJS, TypeScript and Android development.
Latest Blog Posts |
|
|---|---|
| Date | Post |
An easy-to-use and free platform for sharing documentation.
Evaluating the actual FOSS status of projects.
A simple twitter-feed-style RSS aggregator.
A system for managing batch sends to subscriber lists.
A basic HTTP/JSON based monitoring system.
An app for viewing and calculating thermocouple info.
An app to convert between RTD resistance and temperature.
More projects can be found on my Codeberg profile.
Chainguard have also raised over $700M in VC funding.
IMO, it would be more productive if they conceded to the inevitable unsustainable VC lifecycle, and donate whatever cash is left to the real heroes, like the PHP core team, community distro teams, and distro packagers, rather than making their lives more stressful to jump at marketing opportunities.
Glad to see pushback in the comments of the Chainguard CEO's explanation post on LinkedIn, after they broke embargo for the PHP fixes yesterday:
https://www.linkedin.com/feed/update/urn:li:activity:7518756994284077056/
I've been frustrated by Chainguard before when moderating the /r/opensource sub, due to their CEO's repeated attempts at marketing via scare-mongering news articles. which just so happen to feature Chainguard.
IT workers today:
For those using my RSS-reader app, new images are available to address the critical PHP issues:
Pull the new image (latest or v2.2.4 tag) and re-create your containers!
Creality are also starting to use Prusa's non-open-source "Open Community License".
I've called them out on it early:
https://www.reddit.com/r/Creality/comments/1xaq8q6/comment/phvmjju/
Let's see of they respond better than Prusa!
It's totally fun that the EU Cyber Resilience Act is forcing 5 years of required support, just as AI is making the future of software development as uncertain as ever 😑
Prusa seem to be temporarily ignoring GPLv3 obligations to share sources under the reasoning of waiting for wider customer deployment due to it containing security patches:
https://www.reddit.com/r/prusa3d/comments/1x6lypp/comment/pgwffjc/
I'm interested in getting people's view on this:
My failed attempt to get a home battery installed:
Perforce are starting to ask communities for input for next year's "State of Open Source Report" (In partnership with @osi and @EclipseFdn).
A warning: The results are usually gated behind a form requesting a lot of personal details (with lacking justification), and they previously performed a copyright takedown against me when I attempted to directly share the results with others:
https://danb.me/blog/perforce-open-source-report-link-takedown/
Review of my HP OmniBook 7 Aero laptop after six months of use:
TL;DR: Better than expected for the £700 price and for being a HP device.
Also, A reminder that Bitwarden have a history of warning flags when it comes to respecting FOSS:
"Bitwarden remains committed to open source security and transparency" says Bitwarden as they move to primarily distribute non-open-source clients:
Companies will always downplay their move along the rights ratchet (as per https://meshedinsights.com/2021/02/02/rights-ratchet/ by @webmink )
What I worked on in September:
TL;DR: Mainly the BookStack v26.09 release.
I've now added Anubis (https://anubis.techaro.lol/) in front of the site, allowing most top-level, common requests through, but challenging deeper exploration through the repos.
Still getting many requests, but now a minor portion are making it past Anubis, with less overall load. Will see how that plays out over the next few days.
Always fun to get new requests from big businesses asking me to quote them for BookStack on-premise licenses 😄
Tried to further understand how the Cyber Resilience Act impacts BookStack:
https://codeberg.org/bookstack/bookstack/issues/5713#issuecomment-24084459
Very awkward to understand, especially for a project like this.
Anyone have advice on handling a distributed mass requests (attack/scraping/ddos) for a cgit instance?
I'm seeing about 140 requests per second. I have IP-prefix based rate limiting, which has helped before, but this one is very distributed (looks like residential IPs across different countries).
| Time | Message |
|---|
| 22:58:09 | The info here is so out of date it might as well be historical fiction. Update it. |
| 23:00:24 | Thanks for allowing me to leave a message on your website! I really enjoyed exploring your content. |
| 23:02:39 | The design is pretty ugly if I'm being honest. Nothing about it makes me want to stay and look around. |
| 23:04:54 | Bookmark added. This is exactly the sort of site the internet needs more of. |
| 23:07:09 | I expected a lot more from this site. The articles skim the surface of topics without actually saying anything useful. |
| 23:09:24 | I hate green. |