Almost never now, and I used to go to lots. In fact I've launched https://opentechcalendar.co.uk/ to try to promote virtual tech events that include community participation instead.
"Ask TechPosts.eu: Is there an EU Cloudflare alternative? I'm interested in CDN, DDoS mitigation and basic web security." Links to https://techposts.eu/post/153
A listings site for virtually attending FOSDEM. The live streaming is great but the official site only lists sessions in the local Brussels time zone. You can choose your time zone here: https://virtuallyattend.teacaketech.scot/fosdem/2026/
I'm James based in Scotland. For 7 years I ran Open Tech Calendar listing mainly in-person tech events.
After a pause I'm now relaunching Open Tech Calendar to list virtual events - this shift in focus is due to personal life changes that mean that virtual events is what I'm interested in, and looking at other sites that are now doing a great job listing in person events in Scotland. I know virtual events aren't as popular, but when I talked about this on social media, people suggested many reasons that virtual events may be preferred - public health, child care and other caring duties, people in rural areas.
I am specially going for events that include community participation - I'm keen to avoid "this virtual tech event could have been a video" and instead encourage events that people can get involved in.
We are also provide Open Data exports and are keen to encourage events to provide Open Data we (and others) can just import and reuse. Happy to help with options for that.
Brief word on the tech: I'm collecting data in a GitHub repository, then building that into a SQLite database with an Open Source library, then it's a Django site to provide all the filter options and open data feeds I wanted to provide. It's hosted on one virtual machine with Apache caching content.
So:
Constructive feedback on the project and site welcome!
If you know any good virtual tech events, do add them! You don't have to be the organiser. There are details how on the site, or just comment here with details.
This seems to be about hosting an Sqlite database on a static website like GitHub Pages - this can be a great plan, there is also Datasette in a browser now: https://github.com/simonw/datasette-lite
But that's different from how you collect the data in a git repository in the first place - or are you suggesting just putting a Sqlite file in a git repository? If so I can think of one big reason against that.
Yes, I'm suggesting hosting it on GitHub, leveraging their git lfs support. Just treat it like a binary blob and periodically update with a tagged release.
It's not clear if you are suggesting accepting contributions to the SQLite file via PR from people (but accepting contributions is generally the point of why people put these on projects on GitHub).
But if you are I wouldn't recommend it.
PR's won't be able to show diff's. Worse, as soon as multiple people send a PR at once you'll have a really painful merge to resolve, and GitHub's tools won't help you at all. And you can't edit the files in GitHub's web UI.
I recommend one file per record, JSON, YAML, whatever non-binary format you want. But then you get:
* PR's with diff's that show you what's being changed
* Files that technical people can edit directly in GitHub's web editor
* If 2 people make PR's on different records at once it's an easy merge with no conflicts
* If 2 people make PR's on the same record at once ... ok, you might now have a merge conflict to resolve but it's in an easy text file and GitHub UI will let you see what it is.
You can of course then compile these data files into a SQLite file that can be served in a static website nicely - in fact if you see my other comments on this post I have a tool that does this. And on that note, sorry, I've done a few projects in this space so I have views :-)
I'm not OP but I'll guess .... lock files with old versions of libs in. The latest version of a library may be v2 but if most users are locked to v1.267.34 you need all the old versions too.
However a lot of the "data in git repositories" projects I see don't have any such need, and then ...
> Why not just have a post-commit hook render the current HEAD to static files, into something like GitHub Pages?
... is a good plan. Usually they make a nice static website with the data that's easy for humans to read though.
It's not just package manager who do this - a lot of smaller projects crowd source data in git repositories. Most of these don't reach the scale where the technical limitations become a problem.
Personally my view is that the main problem when they do this is that it gets much harder for non-technical people to contribute. At least that doesn't apply to package managers, where it's all technical people contributing.
There are a few other small problems - but it's interesting to see that so many other projects do this.
I ended up working on an open source software library to help in these cases: https://www.datatig.com/
Here's a write up of an introduction talk about it: https://www.datatig.com/2024/12/24/talk.html I'll add the scale point to future versions of this talk with a link to this post.
Some of it is different, but the basics are still the same and still relevant. Just today I've been working with some of this.
I took a Django app that's behind an Apache server and added cache-control and vary headers using Django view decorators, and added Header directives to some static files that Apache was serving. This had 2 effects:
* Meant I could add mod_cache to the Apache server and have common pages cached and served directly from Apache instead of going back to Django. Load testing with vegeta ( https://github.com/tsenart/vegeta ) shows the server can now handle multiples more simultaneous traffic than it could before.
* Meant users browsers now cache all the CSS/JS. As users move between HTML pages, there is now often only 1 request the browser makes. Good for snappier page loads with less server load.
But yeah, updating especially the sections on public vs private caches with regards to HTTPS would be good.
reply