There is an app by Sony that you are supposed to use to transmit location data to various models of their Alpha range of mirrorless cameras. It is terrible and no longer supported. The reverse engineered app, unlike the official app, actually connects to my camera and works reliably.

Announcement of the Agda fork by amy@types.pl:

The Agda developers have recently proposed codifying their official stance on LLM-generated contributions: they are "concerned about the negative effects of large language models (LLMs) on many individuals, our society, and our planet", but refuse to take any concrete action to address their own contribution to these.

Other extensions to the type theory are kept despite known inconsistencies (sized types), or being impossible to adopt without complete vertical buy-in (cumulativity, erased cubical), or simply for backwards compatibility (--guarded/@lock). In the best cases, these features are championed by a single maintainer, and keeping them well-tested against the continuous adoption of new features is a struggle when very little code uses them. Our plan is to focus on exactly one variant of the language ("full --cubical"), and to drop support for all the language features which are explicitly deprecated, inconsistent, or simply ill-understood in conjunction with this fragment.

I tried it out using Amélia's library (https://1lab.dev/) to show that free modules are projective. This is known to be equivalent to the axiom of choice and that informed the definition of projective to have mere existence of the lifted homomorphism. It was pretty ergonomic, details regarding homotopy levels were handled by hlevel and universe levels weren't bad. Automatic proof search worked with a sufficiently fleshed out structure

Build Golf! Code Golf, but for Builds! Uhhh, that's sort of it.

I remember being very slightly intrigued by the concept of code golf a long time ago. But I mostly took notice of people taking it in very esoteric directions, and even before that it was pretty much orthogonal to writing the kind of useful code I care about.

But just now my brain rubbed 2 neurons together, and made the connnection to another problem that has bothered me quite often. How do you do a minimal build of some thing without some "helpful" 300 LoC boilerplate. I want like, 2 files with 3 lines each and one command to run.

Okay, there will be a couple complications to consider to avoid this going down a hacky direction like Code Golf. Like, how much tooling do you depend upon? Do you have to install a package? How many (hundred) packages does that depend upon? (Looking at you React.) But the general idea is, how to you get (for a specific task or category of tool) in a minimalist way from plain-text in git to running machine code? (or like, HTML if you're building for the web) It's a challenge of taste more than discrete optimization! If tools will reign over others in this sphere, it should be because they cater to refined tastes!

Soooo, that's my prompt. Ideas in all directions welcome. Concept for actually practically realizing this? Overly complex unworkable scoring rules? Personal fave minmal project templates? Feel free to evolve on this, or not, I'm not your boss.

I enjoyed reading this, I figured some of y'all may too

TL;DR: In the last year, the Wikimedia Foundation has fired several union organizers, including those that worked on the Community Tech team - a team dedicated to building features for the volunteer community that edits Wikipedia.

As the Wiki Workers Union tries to get the Wikimedia Foundation to recognize their union, it is worth remembering that this is not the first time that the Foundation has worked against the community.

Wikimedia Enterprise is a betrayal of the volunteer movement community of Wikipedia editors, as the Wikimedia Foundation is providing privileged access to big tech AI companies to the Wikipedia corpus - a body of work that the Foundation does not own.

Movement volunteer communities contributed to Wikipedia under copyleft licenses - licenses that work to ensure that the work remains free (as in speech). The big tech AI companies do not license derivative works under copyleft licenses and often do not even attribute where the works came from.

This means that volunteers are working for big tech for free, and the Wikimedia Foundation is selling privileged access to that free labor.

It is against that backdrop that the current unionization struggle unfolds.

Dear god. Why are note-taking projects such a magnet for slop bros?

I'm on a bit of a quest to build up some self-hosted services for me and friends & family, partially because Ad- & AI-infested big tech slop was making me sick and also to become a better sysadmin. General requirement was notes available anywhere and decent editing on mobile.

I was about to rip my hair out, when every session for weeks digging into options ended in frustration. Every project with somewhat decent features had some meh aspects and became worse the longer I looked. And there are so many of them. You can drown your self in "Best FOSS Note-taking App in $(date +%Y)" listicles. Here's a list of over a hundred projects.

I suspect it's a bit of the shopping list problem. It's such a basic idea, that every ambitious clueless dev has it once while picking a hobby project. But note-taking also definitely has a place in toxic self-optimization / hustle culture. Some of the more developed project strike me as that.

I won't mention every basic note-talking project with a CLAUDE.md that I stumbled on, but here's some of the more disappointing lowlights:

• Joplin main developer was one-shot. Added agent instructions to the repo this year and some provisions for his personal vibecoding rig to .gitignore. Also it's not a bug if the AI chat button is visible even if AI features are disabled, because how would people find out about the AI features then?
• Notesnook seems okay-ish, but they're part of the mall ninja club. Business partnership with Kagi & Tuta.
• Standard Notes was the least suspect to me. Later found out they Copilot-Review all of their PRs. (same as Notesnook btw)
• I even considered going with a self-hosted binary of Obsidian. They don't get instant-disqualified by promoting themselves as AI-anything. And if you don't have a project you can trust, you might as well throw yourself at the most established option and pray.

I was running out of places to look for alternatives, when I remembered Open Slopware. You can guess how shocked I was, when note-software made up one of the biggest sublists in there. Through the shortlist of recommendations I ended up looking at Flatnotes. That project might be just enough notes for me.

I know copyright isn’t the way to address what’s wrong with tech, but this here is a great way to poison the well for medium-to-large enterprise companies leeching off open source: if your software requires the work to function, it’s entire source code needs to be published.

Considering using this for my more polished stuff just to irk the companies that would otherwise be happy to use it.

Building on the completed decompilation of The Legend of Zelda: Twilight Princess and the Gamecube/Wii compatibility later Aurora, another unofficial port's come to the PC.

(announcement post - release trailer)

Hi folks, I'm making another tech-stack recommendation. Previously, on Awful, I noted that below 87.5% availability, whether a service is up is effectively random chance. We've reached that point for GitHub's Platform, which includes components like Actions, Copilot, Pages, and the core API of issues and PRs. I do not have confidence in GitHub's owners or operators to remedy this situation, so I cannot recommend it professionally nor to neighbors. As a bit of nuance, note that Pages seems to have relatively decent availability and is often up even when the rest of GitHub is down, so static content hosted on Pages can be deprioritized for migration.

The thread is open on Lemmy. I'm interested in your thoughts, particularly around alternative forges, alternative paradigms for forges, community-driven plans for migration, strategies for migrating, and tools that ease the burden of maintaining many git repositories.

cross-posted from: https://programming.dev/post/49511045

Generative AI, namely LLMs, image and video diffusion models and especially the companies that make them plague the tech industry.

We got tired, so we decided to take things into our own hands and curate a list of projects that aren't complicit in the devaluing of labor by these companies.

Unlike projects that came before us, we want to highlight software that values the labor that goes into creating and not call out projects that use LLMs or Image/Video Diffusion models.

I'm not gonna dig up the links since I'm sure y'all're already tired of talking about quantum computing. I am going to insist that, while I professionally disagree with Filippo about plenty of things, I do not see any mistakes in their analysis here. Please start thinking about post-quantum cryptographic tooling today.

Welcome to the carnival! We've got fun and games. I asked vibecoders to complete three tasks. When folks complained about that, I offered up five more tasks. I did half of these and got average scores. How well did the community do? Scroll to the end to find out!

Was looking for a terminal that can render LazyVim. It's looking like Alacritty (definitely not ghostty).

Too early to see if it's viable. I'm doing my part in the GitHub trenches.

EDIT: They pinned my no-AI policy issue. I think they're pure of heart, lads.

Okay, previously, on Awful, we established that vibecoding can't produce working compilers. Let's try some other side projects of mine. I have important stuff to work on and a deadline, so I'm not matching these projects with my own submissions. Instead, I've laid out a psuedo-objective rubric and I'm going to say that par is 10/10 points.

Fun fact: there's a dedicated game engine for Nintendo 64 homebrew now. This is only its first release, but its looking pretty promising.

The engine's available on GitHub, if you wanna tinker with it.

GitHub's having another major departure - Linux distro Gentoo is starting its migration to Codeberg, with code theft from Microsoft's Copilot as a major reason why.

(This essay is based off of Iris Meredith’s "Becoming an AI-proof software engineer" - recommend reading that first.)

I’m tired of hearing about vibecoding on Lobsters, so I’ve written up three of my side tasks for coding agents. Talk is cheap; show us the code.

The original's been taken down thanks to the creator being harassed into silence by promptfondlers, but a fork was thankfully made, and taking contributions.

Currently in its very early stages, but it'll be a useful resource to identify slopified garbage and get it out of your life.

Credit to Kat Marchin for starting this.