buc.ci is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
RE: https://social.anoxinon.de/@codebergstatus/117636595327014447
apparently #NameSilo just suspended the entirety of #Codeberg or rather its domain Codeberg.org, effectively nuked an entire code platform.
...without proactively informing them? Without telling them why?
What on earth is going on over at NameSilo?
#FreeSoftware #FOSS #FLOSS #dev #development #Forgejo
🥳 New Kitten web site release!
The Kitten web site now has full-text search.
Written, of course, in Kitten.
The index is created lazily on the server in ~0.3 seconds (on my machine) the first time a route is requested after a server restart.
During dev, it’s fast enough that you don’t feel it during hot reloads :)
For the geeks among you, the search features Porter stemming (via the stemmer package), prefix matching on the last query term (which you can see in action in the screenshot), Damerau–Levenshtein distance (so we’re forgiving of little typos), as well as a few code-related optimisations like decomposing camelCase compounds (so WebSocket also matches “web” and ”socket”), etc.
(Oh yeah, and it uses the nifty new baseline URL text fragments feature¹ to have the browser take you straight to the search term in the body of the text.)
Enjoy!
💕
¹ https://developer.mozilla.org/en-US/docs/Web/URI/Reference/Fragment/Text_fragments
#SmallWeb #SmallTech #Kitten #web #dev #NodeJS #JavaScript #HTML #CSS #peerToPeerWeb
🥳 New Kitten release!
• Event routing within nested components is now more intuitive and logical.
e.g., a button on a form that was written into the slot of a layout component by a page. In this case, the event is routed to the page first, since the form was written into the slot by the page, whereas, previously, it would have been routed to the layout component.
Also, if the initial target doesn’t implement a handler for it, the event is now also delivered to the component around the element (in this case, the layout) and any other ancestors it might have.
• Components that `update()` themselves now retain the props and slot content from their last render. Again, this just means they work as they should now.
• Markdown pages now get linked anchor headings by default and you can turn the feature on for your own Markdown blocks in JavaScript pages by including the new headling-links attribute in your <markdown> tags in Kitten’s tagged template strings. e.g., kitten.html`<markdown heading-links>…</markdown>`
• New `preserve` attribute lets DOM elements opt out of morphs (e.g., when you want to retain the text entered into a text-field while morphing the rest of the page using Kitten’s Streaming HTML workflow).
• Miscellaneous bug fixes and improvements.
See the change log for the full list of changes including illustrative code samples:
https://codeberg.org/kitten/app/src/branch/main/CHANGELOG.md#2026-11-16
Also, I’ve reworked the Reference section of the Kitten web site so it’s no longer just one big dump of information. It’s now split into multiple pages, organised by section, and includes much nicer internal navigation:
https://kitten.small-web.org/reference/
You can install and play with Kitten from the Kitten web site:
Enjoy!
💕
#Kitten #SmallWeb #SmallTech #web #dev #HTML #CSS #JavaScript #TypeScript #NodeJS
This is the sort of thing I'm referring to with https://buc.ci/abucci/p/1794739419.625208
The "How complex systems fail" tretise was written in 1998 by someone with experience in system failures, but whose views are by no means the last word on the subject and were not even at the time it was written. Also, I suspect the austerity economics we've all been suffering under since that time has led to significant degradations compared to the state of things in 1998.
There is a certain irreducible complexity in socio-technical systems, but I think in reality we are far away from having systems that are so well engineered that most failures are attributable to it. Human accountability for deploying potentially dangerous systems that are too complex to analyze matters regardless.
#dev #tech #software #engineering #complexity #ComplexSystems
While that's often true of complex systems, I think this misses the point, dangerously. We can and frequently do engineer out this kind of complexity. That's what engineering is and is for. The failure in these instances is that this appears not to have been done, or not done adequately.
Socio-technological systems have existed for millenia. Yes, things are more complicated now. But that does not justify throwing up our hands and saying "welp, complex systems, no way to know". There are ways to know: you engineer the system such that when something goes wrong there is an analysis to be done that reveals causes. If that analysis is not possible, you're not finished engineering. Deploying a poorly engineered system is a fault traceable to individuals, and they ought to be accountable.
We are today awash in systems that have not been engineered properly, software systems especially. Don't let that blind you or lead you to fatalism.
@mathew @futurebird Oh no joke. This week, I got pulled back into a dev project I hadn't touched for a couple months. I could recognize my own work and read all the code and comments, but darn... for hours, I had no idea why I did the things I did or how to apply it to a new function we needed.
After interrogating it for a long while, trying to rebuild what I built before (to see if my fundamentals would guide me toward the conceptualization path I previously tread), I had to step away in frustration. It was clear in my comments that I *had* thought what I did before was obvious and needed no additional documentation.
As soon as I stopped looking at the code, the underlying concept logic from all those months ago flooded back. Looking again at the same code, it all suddenly became obvious once more.
Human brains are fascinating machines.
(Better hurry up and write better documentation for the next brain that needs to work on this.)
the real reason behind the Microsoft Outlook outage
(Post taken from the Debugging Memes Channel, for more content, get the invite link to join here: https://arcanechat.me/channels )
#Microsoft #microsoftoutlook #outlook #dev #developers #developerjokes #programming_humor
One of the exciting new features in the Kitten API version 1 release I made over the weekend is automatic updates.
When automatic updates are on, a deployed Kitten server will:
1. Check for updates to Kitten as well as the installed Kitten app at an interval that you can customise.
2. Correctly handle updates between major (breaking) Kitten versions. (In other words between Kitten API versions, e.g., from 1 to 2, 2 to 3, etc.) This includes ensuring that the installed app has a compatible version before upgrading and seamlessly handling app upgrades across breaking changes.
3. Rollbacks: if, for whatever reason, an upgrade fails, it is automatically rolled back (this includes your databases).
The only thing you need to add to your apps to take advantage of this is an `engines.kitten` entry to your package.json file set to the API version your app has been tested with (currently, should be “1”).
You can also, of course, manually update both Kitten and your app before the next check via Kitten Settings (see second screenshot) and you can also set up a webhook so that pushing to your main or release branch updates the app immediately on a single server.
If you app has a release branch, that’s what Kitten checks for updates and you can deploy, e.g., from `main`, using `git push origin main:release`. Otherwise, Kitten will check your default branch, which is usually `main`.
For more details, see:
⁃ Updating Kitten: https://kitten.small-web.org/reference/#updating-kitten
⁃ Versioning: https://kitten.small-web.org/reference/#versioning
You can get and play with kitten at https://kitten.small-web.org
Enjoy!
💕
#Kitten #SmallWeb #SmallTech #web #dev #HTML #CSS #JavaScript #automaticUpdates #deployment
🥳 New Kitten Release
• Node.js runtime upgraded from version 24.2.1 to 24.2.2.
• A cosmetic simplification of the update history in Kitten Settings (the page no longer reproduces change log entries, choosing instead to link to them).
Full change log: https://codeberg.org/kitten/app/src/branch/main/CHANGELOG.md#2026-11-11
Enjoy!
(Deployed servers will automatically update at their next check interval. You can update manually from Kitten Settings or by running the `kitten update` command.)
💕
#Kitten #SmallWeb #SmallTech #kittenRelease #web #dev #NodeJS #JavaScript #peetToPeerWeb
I present my new browser game: RealCity Transit. Play real world city maps and manage your fleet of public transport. Based on real #OpenStreetMap and #WikimediaCommons data.
Still an alpha phase, so don't be shy and share your feedback with me. Also, hopefully my hosting will withstand the map data flow :-)
https://ambience.sk/games/realcity/
#games #game #gaming #gamedev #retrogaming #osm #indiedev #indiegame #indiegames #tech #technology #wikipedia #browsergame #dev #html
🥳 Kitten API version 1 is now live!
This has been the culmination of seven years of work and a “two-week” breaking change branch that turned into seven-months.
There’s too much to list in a single post but Kitten today is a very different beast to Kitten in April.
Highlights:
• Automatic updates with rollback even across API versions (breaking changes)
• New stateful Kitten Components API
• TypeScript support (and Kitten is now itself written in TypeScript)
• Improved cryptographic properties with the use of non-extractable keys via the Web Crypto API and XChaCha20-Poly1305 instead of AES-GCM for encryption
• Consistent event handling and emitting methods across the page, session, and global scopes
• Considerably increased test coverage across the unit, regression, and end-to-end tests
• Lots of hardening and security fixes
For full details, please see the change log: https://codeberg.org/kitten/app/src/branch/main/CHANGELOG.md#2026-11-07
This is the first of the triplets to be born. Hopefully Catalyst and Meow and will be following soon. Kitten is the foundation so the better it gets, the better anything built with it gets.
I’m updating the Small Technology Foundation site (and our other sites) in preparation of today’s mammoth Kitten release that’s taken me seven months to prepare and it’s quite lovely to refactor something you could previously only do in HTML (see the IDs and class name) into Markdown and have it just work. The whole reason for this crazy round of dev was to ensure that Kitten is as rock solid as possible as its the foundation of Catalyst and Meow. (This is just a little thing – Kitten’s an entirely different beast in terms of stability, consistency, and security than it was in April.)
PS. If you’re wondering about the <${FundUs} /> bit, that’s a Kitten component being instantiated in the Markdown. You can import them just like you can in JavaScript (and in the upcoming release, TypeScript) pages by including a script section in your front-matter.
#Kitten #SmallWeb #SmallTech #markdown #authoring #JavaScript #web #dev
🆕 By Jacob Bachmeyer and Richard Stallman
#dev #Haskell #FunctionalProgramming #ProgrammingLanguages #ComputerScience
This is an excellent thread and I recommend reading the whole thing. I'd like to say that it's getting at why competent software developers are implementing gradient ascent while LLMs+test suites are implementing generate-and-test or hillclimbing. People who know and understand a codebase are able to make changes to it that have a high probability of being improvements according to however you measure that. Stochastic code generation filtered by a static test suite is expected to be orders of magnitude slower at achieving the same improvement. This is a fundamental GOFAI result (the "knowledge-search tradeoff" or the "representation problem") but it applies to a wide swath of optimization problems.
Let's also not forget that optimization generally can only occur in small worlds, while humans---software developers and users alike---exist in large worlds. Databases, physics engines and other simulators, and research tools all have an open-ended space of possible applications ("extension") that cannot be anticipated, let alone tested for, in advance. Understanding the intended inner workings ("intension") of such systems is crucial to building them in such a way that they can support and continue to grow with their evolving applications.
Why estimating how long it will take to write a piece of software is hard, why using units of time isn’t very helpful, and why breaking the process down into small chunks is ultimately how to do it.
what happens to a child who isn't loved properly???
(this and more in the Debugging Memes channel, get the invite link for that and other channels at https://arcanechat.me/channels )
#dev #developer #programmer #programming #developerjokes #programmerhumor #jokes #js #javascript
then they ask why we burn out and go gardening
#dev #developer #c #assembly #coding #programming #programmer #opensource #ai #javascript #typescript #meme #joke #humor #llm #rust
"But there's a human in the loop" excuse doesn't pass a smell test and cannot hold up to scrutiny.
It turns out a beef hot dog is actually filet mignon if a person eats it and gives a thumbs up, according to the LibreOffice contribution guidelines.
#AI #GenAI #GenerativeAI #LLM #code #tech #Dev #FOSS #LOSS #LibreOffice #NoSlop #AISlop #slop
So, I'm curious... Because I've had a _day_... How many of you had to deal with outdated OSs/distros/PHP versions today?
Like the kind shit that made upgrading 23 steps instead of 1 or 2? Or the kind of shit that made upgrading impossible and you're having to migrate a client to an entirely new instance because you don't have a safe path to upgrade in production?
Because again... I've had a _day_.
shared by a friend of mine, after the recent Linus Torvalds news. although I wouldn't know if strictly speaking intended to be related
#noai #noslop #slop #ai #llm #antiai #freesoftware #opensource #foss #floss #linux #kernel #dev #ensloppification #slopnation
How people with standing desks look replying to an #email, keep rocking it pals
note: this post is from the Debugging Memes Channel in #ArcaneChat, to join click here:
discover that and many more channels at:
https://arcanechat.me/channels
#memes #fun #meme #channel #decentralization #encryption #e2ee #ArcaneChat #DeltaChat #linux #opensource #gnulinux #developers #development #dev
While the linked post's/article's warning is specifically about the upcoming US midterm elections, I think its reasoning is more broadly applicable. Observing that current AI dovetails perfectly with the MAGA political project, it applies also to the rhetoric about the inevitability of AI. That, too, stems from a limitless authoritarian impulse and represents an attempt to impose a particular will on all of us. The various forms of defeatism accompanying such rhetoric, which includes the different flavors of AI doomerism, serve only to help such authoritarians achieve their goals.
This view also highlights that there is no middle ground, no compromise, with LLM proponents. Like MAGA, they have no limits themselves, which they repeatedly express openly. How could they possibly compromise?
#AI #GenAI #GenerativeAI #LLMs #Agents #Anthropic #OpenAI #MAGA #doom #tech #dev
Almost _all_ the cost of software is in the future. That's part of why _any_ new feature is alluring. It _appears_ inexpensive from here. Turns out the cost is just unknown.
YAGNI (you aren't gonna need it) doesn't just apply to functions, methods, or classes. It applies to entire feature sets that sound neat, fun, or interesting. Someone has to maintain that shit for the lifespan of the software unless it's explicitly deprecated which simply doesn't happen, in my experience.
I keep re-discovering that I don't write code for the same reason as a lot developers I encounter.
A lot of folks seem to enjoy _writing_ code. I do not like writing code. It _is_ a great way to solve certain problems though and I absolutely _love_ solving problems.
This leaves me in a position where I'll often argue against adding a feature. Not because I don't want to write it but because it doesn't _solve_ a problem. It usually relocates or obfuscates a problem.
I _love_ talking people out of writing code. The _thinking_ is the work. The _code_ is the literal codification of an idea. The _work_ was having the idea and refining the idea to the simplest model possible.
I do not find a lot of folks who share my type of reasoning about software and development.
Somehow the folks who used to _enjoy_ writing code now want the random-word-generator to write their code.
They don't want to think, or write. What the hell is it the want to do?
#dev #tech #web #CloudFlare #SecurityTheater #WhatIsTheHuman
Little tip when linking to source code in your docs, etc.
You can link directly to lines using anchors if the web view of your source control system supports it. e.g., for Codeberg:
https://codeberg.org/small-tech/jsdb/src/branch/main/lib/QuerySanitiser.js#L264
However, that’s brittle and will break as you add/remove code above it.
A more robust way is to use text fragments, which are newly available across major browsers¹. e.g.,
The latter links to the same place and will also break if, say, you remove the method or rename it, but it will survive code changes in the rest of the file.
#dev #tip #git #codeberg #textFragments #URLs #linking #code #sourceControl
I have finished in-app guides and localization for #Banaget. It is now in English and Ukrainian. Two steps closer to release.
(Mas será que eu me incluo nisso? Tento evitar...) :vidaDeProgramador:
🥳 Just released: Auto Encrypt¹ version 6.2.1
This isn’t what I ordered!
• An order/CSR identifier mismatch now fails fast and loud with an `Order.identifiersMismatchError`
If the ACME server offers to provision a different set of identifiers than the one that we requested, we now fail immediately. Previously, we were logging a warning and validating all remaining authorisations, only to fail at order finalisation with a `badCSR` error (RFC 8555 § 7.4).
Full change log: https://codeberg.org/small-tech/auto-encrypt/src/branch/main/CHANGELOG.md
Enjoy! 💕
¹ Auto Encrypt automatically provisions and renews Let’s Encrypt TLS certificates on Node.js https servers. https://codeberg.org/small-tech/auto-encrypt#readme
#AutoEncrypt #ACME #LetsEncrypt #TLS #SSL #certificates #SmallWeb #SmallTech #freeSoftware #NodeJS #JavaScript #JS #web #dev
🥳 Just released: Auto Encrypt¹ version 6.2.0
If at first you don’t succeed…
• Transient ACME server failures are now retried up to four times and obey the Retry-After header, falling back to exponential back-off if one isn’t provided.
• Vastly improved error handling.
• Some bug fixes.
Basically, Auto Encrypt now does it’s very best to provision you that certificate even when things go wrong.
Full change log: https://codeberg.org/small-tech/auto-encrypt/src/branch/main/CHANGELOG.md#6-2-0-2026-09-05
Enjoy! 💕
¹ Auto Encrypt automatically provisions and renews Let’s Encrypt TLS certificates on Node.js https servers. https://codeberg.org/small-tech/auto-encrypt#readme
#AutoEncrypt #ACME #LetsEncrypt #TLS #SSL #certificates #SmallWeb #SmallTech #freeSoftware #NodeJS #JavaScript #JS #web #dev
If you want a modern ImageOptim replacement that does WebP (including conversion to WebP), I’m just playing with the open source Alic macOS app and it’s working great.
https://github.com/blopker/alic
The screenshot shows my settings for having it convert whatever is dropped on it into lossless WebP and save it with the same file name but with a .webp extension.
#web #design #dev #images #imageProcessing #WebP #compression #Alic #ImageOptim #openSource #macOS
A little responsive intro card layout solution on @codepen
https://codepen.io/thebabydino/pen/yygxwZy?editors=1100
#CSS #cssGrid #code #coding #frontend #web #dev #webDev #webDevelopment #cssLayout
🥳 Auto Encrypt version 6.0.0 released
This is mostly a bug fix, code quality, and modernisation release.
Auto Encrypt automatically provisions TLS certificates for Node.js servers – like Kitten¹ – using Let’s Encrypt.
https://codeberg.org/small-tech/auto-encrypt
• 100% test coverage (on both Pebble and Staging).
• Zero type errors.
• Bug fixes and better error handling.
• Security improvements.
• Moved from Tape + c8 + Tap Monkey to node:test + Test Monkey².
• Minimum Node version bumped to 24.19.0.
Full change log: https://codeberg.org/small-tech/auto-encrypt/src/branch/main/CHANGELOG.md#changelog
¹ https://codeberg.org/kitten/app
² https://codeberg.org/small-web/test-monkey
#SmallWeb #SmallTech #AutoEncrypt #https #TLS #Kitten #LetsEncrypt #NodeJS #JavaScript #dev
The ternary operator is all fun and games until you end up with a branch coverage drop without a line number for the culprit (because one of the branches is covered).
#dev #programming #JavaScript #unitTesting #coverage #ternaryOperator #branchLogic
🔐"How not to get owned while packaging?" Get some #dev #security essentials for the whole #toolchain at #openSUSE.Asia Summit. Day 1, Room 1. #DevSecOps #Linux #OpenSource https://events.opensuse.org/conferences/oSAS26
Which #Discord communities/"servers" for the following Open Source software projects, would you most like to see re-established/migrated into an #OpenSource , non-walled-garden forum software (such as their own dedicated #Flarum website)?
**Check all that apply**
Note 1: Community membership sizes may be listed as approximates, may be out of date (Qwen knew from 2024), but none the less, give a useful ballpark. **Were any fairly large Open Source communities in Discord missed? Please reply, stating so.**
Note 2: Flarum 2.0 will be coming out soon, **has great mobile support** (important to younger-generation adoption), and is also lightweight. An #RSS feed add-on/plugin, Open Source, is also offered. 👍 Having said this, I approve of any Open Source, non-walled-garden forum software, such as #Discourse (but it requires a beefier server, uses node.js, alas, and runs in #Docker)
#Blender #LinuxMint #LibreOffice #laravel #dev #DataSovereignty
| Blender Community (~95,000+): | 3 |
| LibreOffice (~25,000+): | 3 |
| Reactiflux (75k+): | 1 |
| Vue Land/Vue.js (119k+): | 1 |
| Electron desktop app framework (21k+): | 1 |
| Laravel (48k+): | 2 |
| Tailwind (36k+): | 2 |
| Debian (has PHPBB, poor mobile support): | 2 |
| Linux Mint (has PHPBB, poor mobile support): | 1 |
Maybe I'll OCR it just to be like that?
Edit: Yes, I'm aware that you can copy some of the text. However, no matter what I do not all the text comes along. Either way, adding right-click->Copy ought to be trivial.
(This is not a request for advice; nor a pinboard for complaints about Google, Chrome, the web, or me; nor a place to opine about why such things might happen in complex pieces of software).
Hey folks, can you help me out with a little something: trying to come up with a good number of files limit for a file scan (for Kitten so you don’t hit heap memory limits if you run it from the wrong directory by mistake) and I’d love some statistics from real JavaScript/TypeScript Node.js projects of the number of files in them (excluding .git and node_modules).
Would you be kind enough to run the following command in Terminal in your largest projects and let me know what number your get (along with a short description of the project):
find . \( -name "node_modules" -o -name ".git" \) -prune -o -print | wc -l
Thank you :)
#Kitten #SmallWeb #SmallTech #NodeJS #web #dev #stats #helpWanted
is the mass market #xmpp client ready yet, son?
#dev #developer #jokes #meme #programmer #programmer_humor #humor
Hi 🩷 does anyone know of freelance or even training opportunities for young developers in Gaza? There’s a very enterprising student looking to make and sell apps, but there are geo-specific barriers to doing it through app stores for Palestinians, unfortunately.
Please contact me directly - text or contact@divyampersaud.com
I have his CV, too, if you personally have opportunities 🙏🏾
Two quick macros for Helix Editor that you can add to your configuration that are helpful during web dev:
```toml
[keys.normal.m]
t = "@i<lt>🏷️<gt><esc>a<lt>/🏷️<gt><esc>b*vNc"
e = "@ctry {<ret><esc>Pji catch (error) {<ret><esc>"
[keys.select.m]
t = "@i<lt>🏷️<gt><esc>a<lt>/🏷️<gt><esc>b*vNc"
e = "@ctry {<ret><esc>Pji catch (error) {<ret><esc>"
```
The first one, m → t, wraps your current selection in an HTML tag that you can begin writing the name of.
The second one, m → e, wraps your current selection in a JavaScript try/catch block and drops you into the catch.
If you have any you’ve written and use, do let me know :)
I think the most important question is: why does anyone comply with what one incurious, self-centered, and self-important man, Linus Torvalds, says?
Why is that most important? Because Linux does not belong to Linus Torvalds. It belongs to the world. Torvalds only gets to dictate if the people who are best-positioned to take that power from him fail to do so. From where I sit (as an outsider), he should have been removed from the project, or at least have his dictatorial power removed, long ago, and the primary problem is that there is no structure or will to actually do that.
Under these conditions Linux is a hierarchical, and therefore right-wing, project. The project allows a single man to dictate the future evolution of a global good. Let's drop the illusion that it is "free" or "open" till that changes.
I've taken part in numerous computer science research projects that involved IRB review. I believe the system can work, even for cases like the above post. But Google and Stanford are bad actors that are taken at their word, and no system, IRB based or otherwise, is going to function properly if it cannot appropriately metabolize this reality.
I was once in a meeting where a Google X person gushed about a project that used smartphone sensor data to detect earthquakes. The calculus being set up here is that detecting earthquakes is a social good that outweighs any particular individual's right to privacy and even outweighs their right to know that their smartphone is being used in this way, let alone consent to it in any meaningful way. (*) Let me be clear and say I reject this framing, but it does appeal to a lot of people, even well-meaning ones. A mess.
#Google #IRB #ethics #EthicsReview #ComputerScience #research #ResearchEthics #tech #dev
update-notifier-crash on Ubuntu 24.04 wrote 1 Tbyte of garbage to syslog before I noticed and stopped it. I noticed because it filled the disk.Unbelievably annoying behavior. I guess that'll teach me to ignore an update notification rather than figuring out how to disable it forever.
I realize this is beside the point, but personally I view the fact that code review is not considered interesting as a serious failure of computer science education. I'm invested in the latter, so it stands out for me.
On the whole writers tend to love to read. I think they love it in part because their education led them to realize that learning to read well is both a good in itself and helps you become a better writer. Programming languages were designed to be human readable so that humans could read them. Yet we have a couple generations of people writing code most of whom were never explicitly taught how to read it, let alone learn to love reading it.
#tech #dev #software #SoftwareDevelopment #ComputerProgramming #ComputerScience #ComputerScienceEducation
To be more precise, whoever controls the software attempts to establish a parasitical relationship with a host ("user") using the software as attachment mechanism. One successful class of parasite leads its hosts into believing they are benefiting from the arrangement even as they are being led into a burrow to have eggs implanted in their carapaces. Some parasites recruit potential hosts in active construction of parts necessary to create novel attachment mechanisms.
I like Kim and her work on StopGenAI well enough, but this post of hers is unwarranted and unfair in my view, as is the fact that several people chose to block me in response.
If you read the full context, which I link below, you'll see the objection boils down to the fact that I used the word "current" in a critique of LLM-based generative AI systems, in an attempt to be precise about what I was saying. Obviously people should block whomever they want for whatever reason they want, but I am not going to be cajoled by threats and ultimatums like this one into making sweeping claims just because other people want to see that. I've been crystal clear about my critique of generative AI for over 3 years now and my writing on it here stands for itself. I have no record of it but people who know me know that I was also quite critical of the hype around GANs in the late 2010s.
For context, here's my post: https://buc.ci/abucci/p/1782335950.858712
and here's Kim's objection: https://zeroes.ca/@kimcrawley/116807184909806502
which reads:
If it weren't for your "current" modifier, your comment would be great.For reasons I don't understand the thread rapidly degrades from "this post would be great without that one word" to "you invited a murderer into my house": https://zeroes.ca/@kimcrawley/116810548823823670
The conviction that technology is neutral is not itself neutral. It paradoxically functions as the conviction that this neutrality is a good thing so as to positively sanction the technological development of more "neutral" tools.(this is my own transcription from the video; any errors or discrepancies are mine).
He says this in the context of an argument that, especially in digital/online contexts, neutrality is conflated with truth, reason is identified with data and a quasi-scientific objectivity, and these conflations are damaging to democracy.
#internet #dev #tech #LLM #GenAI #GenerativeAI #democracy #politics
scala> type Something = Nothing => Nothing#dev #tech #software #math #scala #TypeTheory
// defined alias type Something = Nothing => Nothing
scala> summon[Something =:= Nothing]
-- [E172] Type Error: ----------------------------------------------------------
1 |summon[Something =:= Nothing]
| ^
| Cannot prove that Something =:= Nothing.
1 error found
rsync thing has me thinking about the difference between the "free as in beer" model of free software and the "free as in freedom" model the FSF originally put forward. There are important differences, and it's meaningful when a project changes from one model to the other, which is one way to narrativize what's happened to rsync.I think "free as in beer" software is more appropriately called "Libertarian and Open Source Software", or LOSS. Among other things it involves no obligations on other people, and expects no obligations in return (*). But this means it's an everyone for themselves, anti-communitarian endeavor. We should be honest about this. We should also be honest when a project changes state from FOSS to LOSS, because that's a meaningful change, and actually is a loss in my view.
I continue to believe that enthusiastic embrace of AI/LLM coding tools is a leading indicator of an impending FOSS→LOSS transition.
It seems to me at least one driver of the uproar over rsync is that a bunch of people thought it was a FOSS project but it had, in a short period of time, converted into a LOSS project and the shock was jolting (understandably). As a FOSS project, rsync served a community function, leading people to depend on it, make assumptions about its longer-term stability, and so on. Those are reasonable expectations of a communitarian project. As a LOSS project, rsync is under no obligations to anyone and the maintainer(s) can change the software at any time, for any reason, at their discretion alone. It seems rsync is a LOSS.
#tech #dev #software #SoftwareDevelopment #FOSS #freedom #rsync #AI #GenAI #GenerativeAI #LLMs
Open up chat to myself. Send a chat for each todo item. Use a reaction emoji to indicate status (done/cancelled/etc). Reply to the chat to add additional information and/or surface the item. All of it is shared among all devices, encrypted, and generates notifications. The one feature I'd like that I haven't figured out how to hack manually is scheduled reminders. An XMPP chat app that had scheduled messages could do it! I haven't found an XEP specifically about this but XEP-0471 might be bent to this purpose.
As a low-vision user I already have to lean heavily on my short-term memory to successfully navigate the web. I also constantly use screen magnifiers.
When I select some text on a web page and hit "copy", then go to some other document and hit "paste", and what comes out is different from what I selected, my cognitive load suddenly spikes. The problem is compounded by the fact that I'm very likely zoomed so far into the desktop that I don't even see the text I thought I'd selected. Naturally I begin wondering whether I made a mistake, whether I selected more text than I intended, whether I didn't hit Ctrl-C enthusiastically enough for it to register, etc etc etc. What ought to be a simple and routine command turns into a mystery to solve. To me this feels like a hallmark of poor design.
(Please note that I will probably block you if you respond with advice or fatalism; see above regarding causing spikes in cognitive load).
I love this post for several reasons, one being that it got me thinking. The Bad Tech aside, generally speaking modern software development seems hyperfocused on change at the expense of stability. git has countless features for managing changes to source code. What's the equivalent tool for managing the stability of finished software? What's the tool that tells you "Great! You're done now, congratulations!"
Surely there are pieces of software that are mature enough that we do not need to keep updating them (*) with new features. The industry seems to provide little fanfare or reward for reaching or even approaching such an end state.
#tech #dev #software #SoftwareDevelopment #coding
Kagi started as an AI company that wanted to slurp up the internet to provide a question "answering" service not unlike what Google is proposing to replace web search with. Perhaps they've toned this rhetoric down a bit on their blog recently but there's no evidence I'm aware of that the business has changed mission. All of this is still available on Kagi's own blog---including the fact that they used to be kagi.ai---yet somehow it's controversial to point it out. If you're looking for a web search engine that isn't likely to turn into a slop extruder, Kagi is probably not going to be the one. Try @Mojeek@mastodon.social or Marginalia. This list might be helpful too.
#web #search #dev #tech #software #AI #Kagi #WebSearch #InternetSearch #InformationRetrieval
Why people working on software where something serious is at stake would throw out known gradient to use a code generator + testing is beyond my capacity to understand.
https://1password.social/@1password/116580082041363054
#AI #GenAI #GenerativeAI #LLM #VibeCoding #Software #SoftwareDevelopment #tech #dev #security #InfoSec #PasswordManagers
Do instructors just not teach the code-data duality anymore? Data is code is data is now a mystery?
#ComputerScience #tech #dev #coding #software #SoftwareDevelopment #literalism #LinkedIn
#tech #dev #security #cybersecurity #InfoSec #Vercel #breach #OAuth #AI
I realized that if I was writing a program and it didn't always work, I had a choice: I could either fix it, or call it AI.--David Parnas
#AI #GenAI #GenerativeAI #AgenticAI #LLMs #Claude #ClaudeCode #ChatGPT #tech #dev #software #SoftwareDevelopment #SoftwareEngineering
In light of what I've seen, LLM use seems to provide the illusion of addressing both kinds of complexity in the short-term while it increases essential complexity in the long-term. It may or may not reduce some accidental complexity; the verdict is still out, as far as I can tell. Judging from the recent leak of the Claude Code front end source code, LLMs seem to introduce an enormous amount of new accidental complexity.
To the extent that LLMs are in the category of what Brooks calls automatic programming, this quote he shares from David Parnas is important:
Automatic programming always has been a euphemism for programming with a higher-level language than was presently available to the programmer.The "higher-level language" LLMs trade in is English, which Dijkstra has strongly argued makes for a poor programming language. But even if, contra Dijkstra, it turns out LLMs somehow change that equation, we are still stuck with Brooks's argument that higher-level programming languages largely only address accidental complexity. They do not get at the essence of what makes creating software systems difficult.
Taken together, all this seems to suggest that LLM use in coding is a net negative, and if the above is to be believed it will result in worse outcomes, not better, over the long haul. Definitely re-read Brooks and see if you agree.
#AI #GenAI #GenerativeAI #AgenticAI #LLMs #ClaudeCode #software #tech #dev #SoftwareEngineering #SoftwareDevelopment
What appears as critique – yearning for smaller, weirder, more human spaces – often functions as brand repair. Netstalgia becomes a strategy: it restores trust without redistributing power, softens anger without changing infrastructures and reframes structural problems as matters of vibe, design or community feeling."Am I working on change, or am I working on brand repair?" is an important question to ask oneself regularly, it seems to me. It's especially relevant for the tech sector, open source, and computer science.
#AI #GenAI #GenerativeAI #LLM #tech #dev #software #OSS #FOSS #ComputerScience
#tech #dev #computers #AI #GenAI #GenerativeAI #advertising #InformationPollution
I’ve made this point before about how inane AI hype is now, but a computer beat the best chess player in the world in 1997. No one pretended, after 1997, it wasn’t worthwhile to have humans compete in chess. In fact, the world of chess developed strict protocols around computer use and you can get banned from tournaments if you use a computer program as you play. You are certainly shamed and mocked.#AI #GenAI #GenerativeAI #AIHype #LLMs #writing #tech #dev #coding #SoftwareDevelopment #SoftwareEngneering #softwareAI and writing needs to be treated the same way. I do think people should be shamed for using AI to help them write creatively. It’s an embarrassment, and a form of cheating.
You don't have to pretend that Claude Code's source code is lovely just because you like using it or are impressed by whatever madness is going on around AI right now.
#AI #GenAI #GenerativeAI #LLMs #Anthropic #Claude #ClaudeCode #ClaudeCodeLeak #AgenticAI #tech #dev #software #SoftwareEngineering #SoftwareDevelopment
Buddy. I've written COBOL. I spent several years working almost daily with a 3-million-line monstrosity of a COBOL program. I was working on another app that interfaced with it, but in that work I occasionally had to read the code and in a few cases modify it. Granted I haven't spent as much time looking at the leaked Claude Code source code (and won't lol), but nevertheless I confidently declare that Claude Code is worse. "Spaghetti code" doesn't come close to describing this thing.
#AI #GenAI #GenerativeAI #LLMs #ClaudeCode #ClaudeCodeLeak #Anthropic #Claude #tech #dev #SoftwareEngineering #SoftwareDevelopment #software #COBOL #LinkedIn
#AI #GenAI #GenerativeAI #github #tech #dev #SoftwareDevelopment
I worry that few smaller companies or startups will survive, and the country will be pockmocked with half-constructed data centers and obsolete equipment. This is not like the dot-com crash that left useful and unused fiber optic networking.
hashtag#AI hashtag#GenAI hashtag#GenerativeAI hashtag#software hashtag#tech hashtag#dev hashtag#AssetBubble hashtag#PrivateCredit
I'm not going to name and shame but I'm in the midst of a conversation on this, which is why it's top of mind.
I think some of the strange shifts we're seeing in high-profile folks in tech who already had authoritarian impulses---which, let's be real, is uncomfortably common among tech workers---is that they are groping for ways to embrace taking power that do not run afoul of other values they've endorsed. This really can't be done unless the person was already pretty antisocial, so we see weird behavior such as running self-serving "surveys" about AI with foregone conclusions, microaggressions and dissembling, attacks and other forms of hostility, being "one shotted" or conflating a computer program with humanness, etc. It's really a general problem, in that view, given how the US regime has shifted away from social democracy/liberalism into a much more brash, violent, and authoritarian stance. There are a variety of ways to cope with such a shift, one being to embrace it while bursting into a cloud of internal contradictions.
#FOSS #OSS #OpenSource #software #tech #dev #SoftwareLicensing
1. Conventional Programming Languages: Fat and FlabbyIn the abstract, he states:
Conventional programming languages are growing ever more enormous, but not stronger. Inherent defects at the most basic level cause them to be both fat and weak: their primitive word-at-a-time style of programming inherited from their common ancestor--the von Neumann computer, their close coupling of semantics to state transitionsand later
For twenty years programming languages have been steadily progressing toward their present condition of obesitydoubling down on the body shaming and ableism. He clarifies later in the lecture that what he means by "von Neumann programming language" is one with assignment statements and manipulation of variables. Applicative (i.e. functional) languages are what he means to contrast with these stateful languages.
Several figures of that time, including Peter Landin of "the next 700 programming languages" fame, were unashamedly in love with the lambda calculus and the prospect that it could usher in a full algebraization of computer programming. Backus is interesting because here in a high-profile lecture he's explicitly referring to issues of state as making programming languages "fat" and "flabby". I suspect many of his peers felt similarly even if they weren't using such nakedly ableist metaphors.
#ComputerScience #SoftwareDevelopment #tech #dev #ableism #FunctionalProgramming #StatefulProgramming #ImperativeProgramming #SideEffects #effects
For the uninitiated, what are typically called side effects include:
In what sense, then, are they "side"? And what on earth is being "managed"? Isn't that what we mean by "programming"?
#ComputerScience #SoftwareDevelopment #tech #dev #politics #FunctionalProgramming #SideEffects #effects
Getting the whole argument just right is fiddly, but the basic idea is this. You feed some kind of theory into the AM/AS, which is a black box. It churns on this and spits out a result, which is added to the theory (I'm neglecting the case that the result is inconsistent with the theory). It can now churn on theory + result 1. For any given and potentially very large N, after doing this long enough, it's churning on theory + result 1 + result 2 + ... + result N. Whatever it spits out will be dependent in particular on results 1 - N. When N is large enough, unless you know these results you will not be able to understand what it outputs because the output will almost surely depend critically on one or more of results 1 - N. In other words, the output will look like noise to you. If the AM/AS is appreciably faster at producing results than people are at understanding them, there will be an N beyond which no one can understand the output up to that point. It'll become indistinguishable (unable to be distinguished) from random noise.
If you're into software development, this would be analogous to a software system that generates syntactically-correct code and then adds that code as a new call in a growing software library. If you were to run this long enough, virtually all the programs it generated that were short enough for human beings to have any hope of reading and understanding would consist almost entirely of library calls to code generated by the system. You'd have no idea what any of this code did unless you studied the library calls, which you wouldn't be able to do beyond a certain scale. If the system were expanding the library faster than you could read and understand it, there'd be no hope at all.
I'll leave it as an exercise to the reader whether this is a desirable thing to do and whether it's happened yet. I would offer, though, a question to ponder: what reason is there to believe that a random number generator hooked up to an inscrutable interpreter produces human flourishing, for any given meaning of "human flourishing" you care to use?
#tech #dev #mathematics #AutomatedMathematician #AutomatedScientist #AI #GenAI #GenerativeAI #ThoughtExperiment
At least in the way I use computers as a low vision person, pop-ups are extraordinarily anti-accessibility. Yes, even tooltips and alt-hovertext, depending on how they're done. Some websites are close to unusable because of these things.
In retrospect I might have written non-sense in place of nonsense.
If you're in tech the Han reference might be a bit out of your comfort zone, but Andrews is accessible and measured.
It's nonsense to say that coding will be replaced with "good judgment". There's a presupposition behind that, a worldview, that can't possibly fly. It's sometimes called the theory-free ideal: given enough data, we don't need theory to understand the world. It surfaces in AI/LLM/programming rhetoric in the form that we don't need to code anymore because LLM's can do most of it. Programming is a form of theory-building (and understanding), while LLMs are vast fuzzy data store and retrieval systems, so the theory-free ideal dictates the latter can/should replace the former. But it only takes a moment's reflection to see that nothing, let alone programming, can be theory-free; it's a kind of "view from nowhere" way of thinking, an attempt to resurrect Laplace's demon that ignores everything we've learned in the >200 years since Laplace forwarded that idea. In that respect it's a (neo)reactionary viewpoint, and it's maybe not a coincidence that people with neoreactionary politics tend to hold it. Anyone who needs a more formal argument can read Mel Andrews's The Immortal Science of ML: Machine Learning & the Theory-Free Ideal, or Byung-Chul Han's Psychopolitics (which argues, among other things, that this is a nihilistic).#AI #GenAI #GenerativeAI #LLM #coding #dev #tech #SoftwareDevelopment #programming #nihilism #LinkedIn
#SearX #SearXNG #SearchEngines #AlternateSearchEngines #MetaSearchEngines #web #dev #tech #FOSS #OpenSource #AI #AIPoisoning #AISlop #AI #GenAI #GenerativeAI #LLM #ChatGPT #Claude #Perplexity
The future lies in embracing statefulness and effectfulness in self-modifying code. Unlike the bureaucratic procedure of rule-based coding, this style of programming is more like surfing, or performance, or gardening. Your task as a programmer is to plant a seed of code that unfolds into something beautiful, possibly guiding it as it unfolds if you have the mastery. I'll leave as an exercise for the reader what the soil is in this metaphor.
(I'm only half joking!)
One of my favorite "security challenges" is the "verify your email" one. By this point my email has been verified so many times it should have top secret clearance.
#Mozilla #Firefox #DarkPatterns#antifeatures #AISlop #NoAI #NoAIWebBrowsers #AICruft #AI #GenAI #GenerativeAI #LLMs #tech #dev #web
"Politics" isn't only about institutions. It's about organizing large numbers of people to do something they wouldn't otherwise do. Corporations organize large numbers of people to do things they probably wouldn't do if they weren't paid and/or didn't need the money to live. 10,000 people wouldn't spontaneously get together and spend the best hours of their days for months building a commercial jet airliner if there weren't corporate structures in place and a society that keeps them close enough to deprivation that they will do this in exchange for money.
#FOSS #OSS #OpenSource #software #OpenSourceSoftware #tech #dev #SoftwareDevelopment #politics #economics #corporations
Here's a post from an official Firefox Mastodon account suggesting such a master kill switch does not exist yet, but will be added in a future release:
https://mastodon.social/@firefoxwebdevs/115740500373677782
That's not as bad as it could be. It's bad they're stuffing AI into a perfectly good web browser for no apparent reason other than vibes or desperation. It's very bad if it's on by default; their dissembling post about it aside, opt-in has a reasonably clear meaning here: if there's a kill switch, then that kill switch should be off by default. But at least there will be a kill switch.
In any case, please stop responding to my post saying there's a master kill switch for Firefox's AI slop features. From the horse's mouth, and from user experience, there is not yet.
Furthermore, when there is a master kill switch, we don't know whether flipping it will maintain previous state of all the features it controls. In other words it's possible they'll have the master kill switch turn on all AI features when the switch is flipped to "on" or "true", rather than leaving them in whatever state you'd set them to previously. Perhaps you decide to turn the kill switch on because there are a handful of features you're comfortable with and you want to try them; will doing so mean that now all the AI features are on? We won't know till it's released and people try this. So, in the meantime, it's still good practice to keep an eye on all these configuration options if you want the AI off.
#AI #GenAI #GenerativeAI #LLMs #web #tech #dev #Firefox #Mozilla #AISlop #NoAI #NoLLMs #NoAIBrowsers
AI is intellectual Viagraand it hasn't left me so I am exorcising it here. I'm sorry in advance for any pain this might cause.
#AI #GenAI #GenerativeAI #LLMs #DiffusionModels #tech #dev #coding #software #SoftwareDevelopment #writing #art #VisualArt
In a GitHub issue about adding LLM features:
I definitely think allowing the user to continue the conversation is useful. In my own use of LLMs I tend to often ask followup questions, being able to do so in the same window will be useful.In other words he likes LLMs and uses them himself; he's probably not adding these features under pressure from users. I can't help but wonder whether there's vibe code in there.
In the bug report:
Wow, really! What is it with you people that think you can dictate what I choose to do with my time and my software? You find AI offensive, dont use it, or even better, dont use calibre, I can certainly do without users like you. Do NOT try to dictate to other people what they can or cannot do."You people", also known as paying users. He's dismissive of people's concerns about generative AI, and claims ownership of the software ("my software"). He tells people with concerns to get lost, setting up an antagonistic, us-versus-them scenario. We even get scream caps!
Personally, besides the fact that I have a zero tolerance policy about generative AI, I've had enough of arrogant software developers. Read the room.
#AI #GenAI #GenerativeAI #LLMs #calibre #eBooks #eBookManagers #AISlop #AIPoisoning #InformationOilSpill #dev #tech #FOSS #SoftwareDevelopment
#Cloudflare #SecurityTheater #surveillance #web #tech #dev #DarkPattern
#AI #GenAI #GenerativeAI #LLMs #tech #dev #DataScience #science #ComputerScience #EcologicalRationality
- browser.aiwindow.enabled
- browser.ml.chat.enabled
- browser.ml.chat.menu
- browser.ml.chat.page.footerBadge
- browser.ml.chat.page.menuBadge
- browser.ml.chat.page
- browser.ml.chat.shortcuts
- browser.ml.chat.sidebar
- browser.ml.enable
- browser.ml.linkPreview.enabled
- browser.ml.pageAssist.enabled
- browser.ml.smartAssist.enabled
- browser.tabs.groups.smart.enabled
- browser.tabs.groups.smart.userEnabled
- extensions.ml.enabled
- sidebar.notification.badge.aichat
Enter "about:config" in the browser bar and then search for each of these and disable them, turn them off, or set them to false as appropriate.
Depending on which version of Firefox you have you may not have all these configuration options.
Check your smartphone browsers too!
#firefox #mozilla #AI #GenAI #GenerativeAI #SmartIsSurveillance #tech #dev #web #NoAI #AICruft #antifeatures
#firefox #mozilla #AI #GenAI #GenerativeAI #SmartIsSurveillance #tech #dev #web