jarofgreen
Joined 15 years ago
Joined 15 years ago
Personally, I would have hoped by 2026 we had better IDE's and tools for managing code in text files such that developers with different preferences for a number of characters in a column or things like how you display comments can be accommodated. Yet still teams end up arguing about what standard to use.
Disagree. Personally that sounds like a massive barrier to reading the comment to me. Limited width column text is generally regarded as easier to read, make your comments easier to read. Especially as I probably have the code open in a limited width window, as that's what I expect from code.
Original posts
https://mathstodon.xyz/@andreasthom/117240535270608201
https://mathstodon.xyz/@andreasthom/117240536885387540
https://mathstodon.xyz/@andreasthom/117240537520615623
This story is someone on bluesky screenshotting someone on twitter without a link. The person on twitter screenshotted the source on the fediverse without a link. This is getting daft.
Specifically, my observation was lots of people use a collection of markdown files (or other data formats) in a git repository to crowdsource data. This ties in really nicely with a lot of static site generators.
I was interested in seeing if a tool could help data reuse and help people who aren't comfortable with git contribute.
Just checking, you do know that still counts as tracking and may fall under GDPR rules? GDPR was never just about cookies.
I missed this when it was launched and it's very interesting to see your rationale. If you ever want a chat some time get in touch, I'm working on https://opentechcalendar.co.uk/
My ulterior motive is to ask you to add open data feeds for basic group and event listing information to your site - a free and open API and standard formats like ICAL (Just listings information about the next event, not private info like members names). I would never encourage event organisers to use a platform that didn't do this, as then their data is essentially being held hostage and it's hard for them to spread their information around to other places.
You mention rsync which can be fine. But there are tons of other solutions, many that will have snapshot features. I use borg backup, for instance. https://www.borgbackup.org/
Also, look into scriping your server setup with tools like Ansible or PyInfra. There is always the risk that bad things happen to servers, and when you want a new server it's great to be able to spin things up in a matter of minutes. Tools like these are profesional best practices these days.
In fact, if you have a scripted server setup and a server that doesn't collect data itself you may not even need backups. What is there to backup? Just spin up a new server with your scripts and carry on.