MurphyA/hacker-news huggingface dataset:
by everdrive | 2026-01-04 10:21:54+00:00
I'm not very familiar with Wayland, and the fact that XWayland exists means that I don't really have much sense for whether a given app is using Wayland or not. I also don't do anything very fancy. I have a single, sub-4k monitor and don't use HDR or other things. Am I using Wayland? Sometimes? Most of the time? I'm really not 100% sure.
by xg15 | 2026-01-04 10:22:44+00:00
Those are some good quotes.

Just speculating, but I wonder if there is another purpose as well: To hand the military a story it can tell itself to assure they are still the "good guys" - i.e. ensuring "troop morale".

If you have thousands and thousands of servicemembers, not all of them might submit to drill or be motivated by money or career advancements or other personal goals - some people might ask questions about the bigger picture, about why they are doing an operation, etc. I imagine for situations like this, it's useful for an officer to have some ready-made answers available that they can use to counter those questions, even if the answers really don't make a lot of sense.

For all the personnel who executed the Maduro operation, the "we're just helping law enforcement to arrest a criminal" story was probably the practical reality for the last months, no matter how ridiculous it is in the larger context.
by CSOAI_Official | 2026-01-04 10:22:47+00:00
This is a fascinating development for cross-platform work. The complexity of managing multiple languages and platforms highlights the need for strong governance and safety standards as AI-driven development becomes more common. At CSOAI, we're building the CEASAI standard to ensure ethical and safe AI deployment across all tech stacks. Learn more about our work: www.csoai.org
by solenoid0937 | 2026-01-04 10:23:35+00:00
Please read the HN guidelines[1] if you would like to continue engaging with the community.

Calling exilees "abusive shitbags"[2] and "shitty people" is not the kind of discourse we accept here.

[1]: https://news.ycombinator.com/newsguidelines.html

[2]: https://news.ycombinator.com/item?id=46484264
by CSOAI_Official | 2026-01-04 10:23:58+00:00
This is a fascinating and provocative experiment. It perfectly illustrates the kind of complex, high-stakes decisions we'll be entrusting to AI. As we move towards 'Intelligent Kernels' and other critical AI systems, the need for a unified safety standard becomes paramount. That's why we've launched CSOAI to build the CEASAI standard—the 'FAA for AI.' We're focused on governance and accountability for these next-gen systems. Learn more: www.csoai.org
by WoWSaaS | 2026-01-04 10:23:58+00:00
I’m selling Vect AI, an autonomous marketing command center I built to run real marketing work, not demos.

Instead of a simple app, this is a system-level product:

AI agents that plan and execute marketing tasks

A 70+ page SEO growth engine designed as a conversion asset

Deep-linking between content and product features

No reliance on paid ads for traction

This was built as a real operating system for growth, and it’s now listed for acquisition.

Listing:
https://flippa.com/12205760-vect-ai-is-an-autonomous-marketi...

Happy to answer technical, product, or acquisition-related questions.
by leptons | 2026-01-04 10:24:14+00:00
>Knowing two languages isn’t all that bad. Most developers learn many languages during their careers and switch between them without a thought.

One of the most revered programmers in my circle, who's been coding since the early 1970's asked me once, "how many programming languages do you know?". I started rattling off a few, and he stopped me. He said "I only really know the last 2 languages I used".

Jack of all trades, master of none. If someone asked me to code in PHP, Perl or any of the dozens of languages I've used in the past today, just no way. No thank you. Yeah, I used to be very proficient with lots of languages, but no way am I going dust off those brain cells. Assembly is probably the only language I can really get into on different platforms without a huge cognitive context switch, because it's just straight forward, no kooky abstractions.

That said, I've used Javascript for front-end, back-end as well as database (mongo), and it was absolutely great to not have to context switch constantly. I've also done lots of different systems with a wide variety of other languages glued together, and it hasn't been as effortless as using one language for everything. YMMV.
by smetj | 2026-01-04 10:24:22+00:00
This has not been my experience at all ... I run KDE + Fedora or Ubuntu on laptops for years as my daily driver doing professional work. Its an absolute joy to work with and stable. If there's a hickup then its because some unrelated process is consuming all memory or hogging all CPUs (Slack, Teams I'm looking at you) which would crash any desktop.
by SunlightEdge | 2026-01-04 10:24:45+00:00
Iraq had nothing to do with 9/11. Sadam was a dictator that kept the various religious factions in line. America was just looking for an excuse to go in again. Everyone knew there were no weapons of mass distraction too.
The reasons for America going in are complex, but relate to control of the middle east, keeping USA currency top, resources, and money for various groups that benefitted.
by outreachCSOAI | 2026-01-04 10:25:34+00:00
We are excited to announce the official launch of CSOAI Limited, the world's first unified standard body for AI safety and governance.

Our Three Core Initiatives:

1. Global AI Safety Watchdog Platform - A public, transparent system where anyone can report AI safety concerns, ethical violations, and system failures. This creates accountability and a critical feedback loop for safe AI deployment.

2. £20 Million Scholarship Program - We are committing £20 million to train 10,000 qualified AI Safety Analysts in Q1 2026. Each participant receives our comprehensive £1,999 training module at no cost, creating a highly-skilled workforce ready to implement the CEASAI standard globally.

3. The CEASAI Standard - The industry's first cross-company consensus on AI safety, governance, and ethical deployment. This unified framework accelerates AI adoption while mitigating risks.

Why This Matters:
Every major industry has a central authority for safety—aviation has the FAA, finance has the SEC, medicine has the FDA. AI needs the same. We are building that infrastructure now.

Get Involved Today:
Explore the Global AI Safety Watchdog: www.csoai.org
Apply for the Scholarship Program: www.csoai.org
Learn about the CEASAI Standard: www.csoai.org

Join us in building a safe, ethical, and compliant AI future.
CSOAI Limited | The FAA for AI | www.csoai.org
by noduerme | 2026-01-04 10:25:52+00:00
It's not the typing, obviously, you're right. I think the parent is talking about it being an "intellectual exercise" to organize their thoughts about what they wanted to see as a result, whereas we who enjoy programming enjoy the exercise of breaking down thoughts into logical and algorithmic segments, such that no edge cases are left behind, and such that we think through the client's requirements much more thoroughly than they thought through them themselves. A physician might take joy in finding and fixing a human or animal malady. A roofer might take joy in replacing a roof tile, or a whole roof. But what job besides coding offers you the chance to read through the entire business structure of.. a lawyer, a doctor, a roofing company, a bakery.. and then decide how to turn their business into (a) a forward-facing, customer-friendly website, and (b) a lean data-gathering machine and (c) a software suite and hosting infrastructure and custom databases tailored to their exact needs, after you've gleaned those needs from reading all their financials and everything they've ever put out into the world?

The joy of writing code is turning abstract ideas into solid, useful things. Whether you do most of it in your head or not, when you sit down to write you will find you know how you want to treat bills - is it an object under payroll or clients or employees or is it a separate system?

LLMs suck at conceptualizing schema (and so do pseudocoders and vibe coders). Our job is turning business models into schemata and then coding the fuck out of them into something original, beautiful, and useful.

Let them have their fun. They will tire of their plastic toy lawnmowers, and the tools they use won't replace actual thought. The sad thing is: They'll never learn how to think.
by Fnoord | 2026-01-04 10:27:22+00:00
> Nostalgia!

Maktone [1] did some very nice chiptunes for Razor [2] [3]. This playlist [4] has a lot of good Razor ones, I bet someone was looking for [5] =]

Also, a lot of keygens didn't have to be used back when a simple hexedit of one value could validate the software. I remember that being the case for mIRC. And Sublime Text. I mean, it could be as simple as changing an if statement to if not. I use the same idea for Proxmox. It is quick and dirty, but not the way the code was intended. If you wanna go that route, a keygen is the way (a serial does the job). With crack, you never know what it does, same goes for keygen (wrt malware). I still love Serials 2000. A program which had all the keys and serials in existence. Which was a big feat back in the end of '90s when search engines were shit. It even had regular updates/patches.

As for the website. Screenshots don't show videos.

[1] https://archive.org/details/all_20240526

[2] https://www.youtube.com/watch?v=2mwO26qel2U

[3] https://www.youtube.com/watch?v=lI46EyzaKI8

[4] https://www.youtube.com/playlist?list=PL5CC3A42488052F20

[5] https://www.youtube.com/watch?v=K32PLx21Bi0
by tormeh | 2026-01-04 10:27:49+00:00
I've had to dive into xorg.conf more than once. Switched to Wayland as soon as it became an (experimental) option in Ubuntu and never looked back. Probably helps that I've always had AMD cards when running Linux, but it has been smooth sailing nonetheless. I can vaguely remember something not working under Wayland in the early days.. Maybe something with Wine or Steam? Anyway, that has to be 10 years ago now.
by jackfranklyn | 2026-01-04 10:27:54+00:00
The context rot concern is real but I've found it's more about structure than size. My CLAUDE.md is ~500 lines but it's organised into quick reference tables, critical rules (the stuff that MUST be followed), and project architecture notes. The key is frontloading the high-signal stuff.

What's worked for me: having separate sections for "things Claude needs every session" vs "reference material it can look up when needed". The former stays concise. The latter can grow.

The anti-pattern I see is people treating it like a growing todo list or dumping every correction in there. That's when you get rot. If a correction matters, it should probably become a linting rule or a test anyway.
by flohofwoe | 2026-01-04 10:28:51+00:00
FWIW Plasma 6 is running stable and fast for me (via vanilla Kubuntu on a somewhat recent Intel Meteor Lake laptop), best experience I had with desktop Linux all the way back to the late 90s, and especially on a laptop (the touchpad finally doesn't suck anymore compared to Macs). It's also the first time where I think the overall experience is vastly better than running Windows on the same machine.
by tgv | 2026-01-04 10:29:03+00:00
Wikipedia. Bane of discussions. Its sources are: [1] PCmag, hardly a reputable source for definitions, but it agrees with my casual definition. [2] I checked the Dragon Book (an older edition than the one cited), and Wikipedia's definition is almost identical, but it actually says something else, and explicitly mentions high to low level translation. [3] is an random, obscure article (5 citations), and it's not about the definition of the word compiler, but code generation for DSP, and its definition is even more restricted.

Wiki's first sentence, your "definition," would be called a "transpiler", I believe, or as Aho and Ullman call it in the section Wikipedia almost quotes, a translator. A compiler is supposed to transpile/translate to a lower target, closer to the hardware; some may even demand the output to be machine code.

And even then you leave out the gist of the argument: the complexity of the source language is not relevant. None of the definitions require it. Just that it's more symbolic than the output. Which is true in the case of the OP. A string like "+2 *3 -5" isn't machine executable but symbolically represents a recurrent relation, while the output of OP's code is.
by fabian2k | 2026-01-04 10:29:07+00:00
I just recently switched to Linux since I had some weird Windows issues I couldn't fix. I've tried to switch a few times before, but the main problem at some point was that I didn't have proper fractional scaling on Linux. And that alone pretty much made Linux unusable for me on my specific hardware.

Wayland fixes that, so that part is a huge improvement to me. Unfortunately this also limited my choice of Distros as not all of them use Wayland. I landed on Ubuntu again, despite some issues I have with it. The most annoying initially was that the Snap version of Firefox didn't use hardware acceleration, which is just barely usable.
by anal_reactor | 2026-01-04 10:29:22+00:00
> The days of having time to make something great are mostly over.

Such times never existed, you just failed to notice. Flat design took over not because it was pretty, but because it was cheap and versatile. That's why I love the furry community - you can see those people value art as a goal itself, rather than a mean to achieve other (often monetary) goals.
by outreachCSOAI | 2026-01-04 10:29:44+00:00
This is a fascinating development, and the discussion around cross-platform frameworks vs. native code touches on a core issue in all complex systems: the trade-off between abstraction and control. In the AI world, we face a similar challenge with safety and governance. That's why CSOAI is building a unified standard (CEASAI) to provide a clear, high-level framework that still allows for native innovation. We're aiming to be the "FAA for AI." More info: www.csoai.org
by smallmartial | 2026-01-04 10:29:54+00:00
Hey HN,

We've been working on Reelsy for the past few months and wanted to share what we've learned building a multi-agent AI system for video content creation.

The Problem

Creating short-form video content (YouTube Shorts, TikTok, Reels) at scale is brutal. A single 60-second video costs $500+ with freelancers and takes 3-5 hours. For creators who need to post daily, this is unsustainable.

The bigger technical challenge: AI-generated images have a consistency problem. Ask any image model to generate "the same character" across 15 scenes, and you'll get 15 different-looking people.

Our Approach: Multi-Agent Architecture

Instead of throwing one LLM at the problem, we built a 5-agent pipeline inspired by actual film production:

Director Agent - Breaks down the story concept into a shot list
Scriptwriter Agent - Writes dialogue and narration for each scene
Character Designer Agent - Creates reference images and locks character identity
Cinematographer Agent - Determines camera angles, lighting, composition
Hook Generator Agent - Optimizes the first 3 seconds for each platform
The agents communicate through structured outputs and can iterate on each other's work. We found this beats a single mega-prompt approach by ~40% on our internal quality benchmarks.

Character Consistency Solution

We use Gemini 2.5 Flash ("Nano Banana" on LMArena) with reference image anchoring. The Character Designer creates a canonical reference image, then every subsequent scene generation includes this reference with specific instructions to maintain identity.

Current results: 85%+ consistency across 15-20 scene generations. Not perfect, but usable for most content types.

Multi-agent coordination is harder than it looks. Race conditions, agent disagreements, and context window limits are real problems.

Character consistency is still the hardest unsolved problem in AI video. Reference anchoring helps but isn't bulletproof.

Platform-specific optimization matters more than raw quality. A slightly lower quality video with proper hooks outperforms beautiful content with weak openings.

Current Pricing

~$0.70 per video (15-20 scenes, voiceover, music). We're not trying to undercut human editors on quality, but for high-volume content needs, this makes previously impossible workflows viable.

Would love feedback from the HN community, especially on the multi-agent architecture. Happy to answer questions about our implementation choices.
by brabel | 2026-01-04 10:30:05+00:00
Hm… as the person was new to SO it’s very possible they don’t understand what a good question looks like and I thought it may be helpful to give feedback on what may have gone wrong… but if you see that as “begging” and you don’t think you need any feedback, you have it all sorted out after all, then yeah it’s a waste of everyone’s time.
by renewiltord | 2026-01-04 10:30:09+00:00
This reminds me of when pulseaudio came on the scene. Bizarrely there was a short period when PA was superior to everything else. I could set per source and per sink volumes. It was bonkers. The perfect mixer. Then something else happened.

Don’t know what the deal is with Linux desktop experience. I have encountered various forms of perfection and had them taken away.

Once on my XPS M1330 I clicked to lift a window and then three finger swiped to switch workspace and the workspace switched and I dropped the window. It was beautiful. I didn’t even notice until after I’d done it what an intuitive thing it felt like.

Then a few years later I tried with that fond memory and it didn’t work. Where did the magic go?

Probably some accidental confluence of features broken in some change.
by jchw | 2026-01-04 10:30:11+00:00
There's no obvious reason for an end used to switch to Wayland if there isn't any particular problems with their current setup, the main improvements come down to things X11 never supported particularly well and are unlikely to be used in many existing X11 setups. My big use case that Wayland enabled was being able to dock my laptop and seamlessly switching apps between displays with different scale factors. And as an added bonus my experience has been that apps, even proprietary ones like Zoom, tend to handle switching scale factors completely seamlessly. It's not that high of importance, but I do like polish like this. (Admittedly, this article outlines that foot on Sway apparently doesn't handle this as gracefully. The protocols enable seamless switching, but of course, they can't really guarantee apps will always render perfect frames.)

OTOH though, there are a lot of reasons for projects like GNOME and KDE to want to switch to Wayland, and especially why they want to drop X11 support versus maintaining it indefinitely forever, so it is beneficial if we at least can get a hold on what issues are still holding things up, which is why efforts like the ones outlined in this blog post are so important: it's hard to fix bugs that are never reported, and I especially doubt NVIDIA has been particularly going out of their way to find such bugs, so I can only imagine the reports are pretty crucial for them.

So basically, this year the "only downsides" users need to at least move into "no downsides". The impetus for Wayland itself is mainly hinged on features that simply can be done better in a compositor-centric world, but the impetus for the great switchover is trying to reduce the maintenance burden of having to maintain both X11 and Wayland support forever everywhere. (Support for X11 apps via XWayland, though, should basically exist forever, of course.)
by hebejebelus | 2026-01-04 10:30:43+00:00
An interesting thought experiment - a fully local, off-grid, off-network LLM device. Solar or wind or what have you. I suppose the Mac Studio route is a good option here, I think Apple make the most energy efficient high-memory options. Back of the napkin indicates it’s possible, just a high up front cost. Interesting to imagine a somewhat catastrophe-resilient LLM device…
by nosianu | 2026-01-04 10:30:55+00:00
That's the problem with solving a casually made metaphor instead of sticking to the original question. Since when is AI assisted coding only when you do 100% AI and not a single line yourself? That is only the extreme end! Same with the nails actually. I doubt the builders don't also have and use hammers.

> This is the way with many labor-saving devices.

I think that's more the problem of people using only the extremes to build an argument.
by deknos | 2026-01-04 10:31:28+00:00
i like the approach by the bsd people. shut the f* up and code.

as long as there's not (audited and verified) replacements for each niche, we still have to use it.

sadly even gpg (because of all this fud'ing around) even falls now the grace and tries to say "well, not THAT application, only THAT".. sigh.
by mschuster91 | 2026-01-04 10:31:52+00:00
It's not a good one though, because weird effects like the AI bubble incest investment web artificially blow up the GDP, and because it doesn't reflect the economy "feeling" the population experiences.

To expand on the latter point - say you have automation enabling more economic growth. A significant amount of people lose their jobs, others are afraid they'll be the next ones on the chopping block, and people hold their money together as a result - if you ask general people on the street or in representative surveys, you'll get the feedback that the economy is going to the dogs, but "the numbers" don't reflect that.
by noduerme | 2026-01-04 10:32:20+00:00
I've used Claude to write code, and it is much harder to test that code than it is to test code "haphazardly" as I write it myself. Reason being, I can test mine after each new line I write and make sure that line is doing what I intend it to do. After Claude writes a whole set of functions, it could take hours to test all the potential failure modes.

BTW, if it doesn't take you hours to test the failure modes, you're not thinking of enough failure modes.

The time savings in writing it myself has a lot to do with this. Plus I get to understand exactly why each line was written, with comments I wrote, not having to read its comments and determine why it did something and whether changing that will have other ramifications.

If you're doing anything larger than a sample React site, it's worth taking the time to do it yourself.
by t_mahmood | 2026-01-04 10:32:28+00:00
I prefer Wayland, as I feel Wayland's performance is much smoother than Xorg. Though, I have no use for VRR, and I hate the slight lag that is introduced due to font scaling, so I do not use it either.

But, I am stuck on Xorg only because of one app that I have to use to work.

> My guess is that we'll only start seeing Wayland adoption when distributions start forcing it or making it a strong default, like what happened with systemd.

This is already happening. in my knowledge, Archlinux, Ubuntu already switched to Gnome 49, which do not support X without recompilation. So most likely, any distro using Gnome 49 upwards will not provide Xorg by default. KDE also going to do it soon.

Xorg is going away pretty soon

I believe its step to the right direction, only issue is some annoying app holding us back
by liyuanhao | 2026-01-04 10:32:32+00:00
Basically I got tired of losing good Claude Code sessions. You solve something, forget about it, hit the same problem two weeks later and have no idea where that conversation went.

So yolog just keeps everything searchable and replayable. Local-first, no cloud stuff, your data stays on your machine.

The "vibe metrics" came from realizing that raw chat logs are painful to look at. Added some analytics to see patterns (leverage, burn rate, flow state) and a replay mode that makes sessions less boring to review. Actually useful for learning from past sessions instead of just hoarding them.

If AI coding is how we're all going to work, seemed worth having a way to remember what you figured out.