My "production stuff":
- https://github.com/festivus-es/festivus - public holidays calendars for Spanish cities
- https://github.com/remote-es/remotes - companies hiring in Spain for remote positions
Usable WIPs:
- https://alexpdp7.github.io/selfhostwatch/ - track self-hosting package updates (such as YunoHost)
- https://github.com/alexpdp7/ubpkg/ - package manager for "upstream binaries"
- https://github.com/alexpdp7/termflux - Miniflux terminal client
@cadey I have a need to know the names of cool concepts.
Very nice article, by the way.
Hello I wrote a thing about how Android made a good privacy improvement and in the process apparently made key attestation far less useful for certain use cases https://mjg59.dreamwidth.org/70630.html
When it comes to non-free firmware I think there's two reasonable positions - treat it like non-free code running on a remote system (suboptimal, outside the scope of current free software priorities) or treat it like software running on the primary CPU (all code on the local system should be free software, no matter where it's running). I think the FSF's position is unreasonable: https://mjg59.dreamwidth.org/70895.html
@cadey I think it's extremely unlikely that you are not aware of https://en.m.wikipedia.org/wiki/Sturgeon%27s_law , but just in case. (I do not think it requires attribution. )
Soylent Green is people
@epilys I am a horrible person, because there's only like a 0.000003% chance you are in a scenario where this is not the worst idea ever but... you could invoke a program. pretty sure everything except Linux has a guaranteed known executable you could use, and there might be acceptable strategies if there is not.
https://survey.stackoverflow.co/2024/technology/#1-operating-system
27.7% of professional developers use Ubuntu as their "primary operating system for work". (Plus a few other Linux are there.) I don't really trust the survey (how can primary choices total more than 100%, and how WSL and Cygwin are there?), but if it's remotely close to reality, that "Linux is not viable for work"...
(Better data welcome.)
The way that "ChatGPT outputs libel about person X" was solved by adding a kill switch for his specific name doesn't really suggest these AI engineers have much influence over what their models are saying.
Once you're terminally online for a while you realize how much of online discourse is driven by a handful of terminally online people. After you scratch the surface of some "The X community thinks Y" statement, it turns out Y is just the opinion of two guys named John and Mike that are very prolific on some forum, have had a blog for 25 years, and last looked at X in 2012.
Russell Coker's blog is one of the remaining gems from the golden era where following blogs was *the* way to be updated. I still follow it through Planet Debian, which was another *AWESOME* concept that is becoming lost to the mists of time.
The latest link roundup is quite nice. I wasn't aware Nvidia was also on the RISC-V train. I'm not holding my breath, but I'm kinda eager to see if RISC-V shakes things significantly in a couple of years.
Honestly, we are currently out of ideas on how to restore access to Codeberg.org.
We are fighting with extreme traffic and high load for several hours now, we have done the typical procedure to identify and block misbehaving AI crawlers.
However, we are currently having a hard time figuring out details about the ongoing high traffic situation.
Pet peeve: do not create a repo on GitHub (or your favorite forge) until you have at least a README with a "why". (I normally wait until I have a small usable piece of code, even if it has no UI and needs to be used as a library or through a REPL.)
Or, well, do... I can always fantasize :D
(To me, GitHub is more of a social network :D)
just found out someone is building an independent JS-supporting terminal web browser in a memory-safe language: https://git.sr.ht/~bptato/chawan/
looks promising because so far all the other independent browsers other than Firefox are stuck using C or C++, which like ... have we learned nothing?
but also there's completely unhinged stuff like https://git.sr.ht/~bptato/chawan/tree/master/doc/localcgi.md (and I haven't thought about it enough to figure out whether "unhinged" is a compliment or not yet)
"If it's free you are the product" is up there with "you know Google once said 'don't be evil'" in the list of vapid clichés in 'critical' tech writing. Open software is free. Are users of any given open source system the product? Not really, eh? How about readers of free books and articles? Yeah, just stop repeating that. Being free isn't the problem. The business model of the entity offering the good is the problem.
I made a thing. Please do not hesitate to point me in the direction of more forms to fill. https://wtf-8.xn--stpie-k0a81a.com
Well, Visual Studio Code is in the Pop!_OS repositories as a .deb too. Only defaulting to that in the Pop!_Shop is an issue. Once you install the JDK and VS Code using the terminal and apt, there are few issues.
Graphical applications to install software on Linux have always been a source of pain.
At least, once installing JDK 21 from the Pop!_OS package repositories, the Visual Studio Code "Extension Pack for Java" that is offered has a decent experience in getting a Spring Boot application started using Spring Initializr.
(Not ideal because it creates a completely empty application that just displays an error, but otherwise the process is reasonably intuitive.)
Visual Studio Code offers a wizard to set up Java. It detects there's no JDK and prompts to download one. This means invoking the browser to download a .tar.gz and... that's it, 0 indication of what to do with the download.
Pop!_OS, in the latest supported version 22.04 has a valid OpenJDK 21 package that could be easily installed instead.
I like Flatpaks in principle. But precisely the *only* problems I have had with them is in "development" tools, which often require breaking out of the sandbox.
Computers are unnecessarily complex. My perception is that Linux is a viable operating system for general purpose computing (and even offers perceivable advantages over macOS and Windows), but for introductory software development I still run into too many papercuts.
Preparing to help to work with Java to someone that uses Pop!_OS and Visual Studio Code. The Pop!_Shop offers by default Visual Studio Code as a Flatpak. The Flatpak does not seem to provide reasonable instructions to install the JDK in a Flatpak situation. I revert and install Visual Studio Code through their official website, which offers a .deb package (which in my experience is easier). The integrated package installer hangs indefinitely installing the package.
@coder I created Django views to publish the scraped data. However, I did not want to expose this to the Internet.
So today, I set up a daily Kubernetes job that scrapes the website from the same cluster, and pushes it to GitHub Pages.
24 years later, I managed to top myself with an even more janky setup, by adding Kubernetes and GitHub Pages.
Around 2000, my university provided web hosting for students. This was static web hosting, of course. I wanted my website, and setting it up using HTML was too tedious. So I decided to create my website using PHP, run wget --mirror to scrape it, and upload it to the static web hosting service.
(I don't think that was a novel idea even back then.)
My current personal project is implemented with Django and I run with Kubernetes. This project scraps data and stores it in a PostgreSQL database.
@drewdevault@fosstodon.org I don't think it's such a hot take. My observation is that many successful big open source projects have "megacorp" contributors that do not intend to profit from the project *directly*. When they intend to benefit *directly* is when it tends to get messy.
Open source project governance is still a hard problem, of course. But a lot of software needs to be so large that megacorps are kinda required for sustainability.