Waiting for QuackDB the OSS spin off any second now

I've already created Haybarn which is Query.Farm's distribution of DuckDB:

learn about it here: https://query.farm/haybarn/

If my extension shows as "build failed" on https://query.farm/haybarn/status/v1.5.5/ how do I go about fixing it?

Presumably the issue is Haybarn-specific?

You can get in touch with me, or open an issue or PR as to why.

The CI extension build runs are still public on GitHub, but may have expired, if you bump your git sha ref it will rerun.

Took a bit of searching around to find the repo: https://github.com/Query-farm-haybarn/haybarn-community-exte...

Looks like this is the failed build https://github.com/Query-farm-haybarn/haybarn-community-exte... but logs have expired

I'll kick it off again for you.

Looks like flaky GitHub this time: https://github.com/Query-farm-haybarn/haybarn-community-exte...

DuckDB is still OSS btw. It didn't go proprietary like Redis or ElasticSearch.

For now..

MallarDB

I have a 36gb M3 Max. I tested it across quite a few different options: llama.cpp, oLMX, ollama with different options.

So far ollama managed to be the most performant of them all. I will get 30 to 40 tokes/sec with it when using the -mlx version of Qwen3.8.

Whatever the sauce the ollama folks baked into the mlx + MTP mix is currently working the best out of the box.

Hmm, perhaps I should switch to an MLX version… problem is, it took quite a bit of work to get llama-server (with llama.cpp) to serve my model(s) and allow requests in non-thinking (default) and thinking modes.

But 30-40 tokens/s would make a big difference.

Thanks for sharing! Did you observe a speed difference between ollamas mlx version and the mlx-community/Qwen3.8-27B-4bit from HF ran with mlx_vlm.generate (with MTP)? Or is it the same?

huh.. I'm a bit of local LLM noob so I wasn't familiar with mlx_vlm.

I gave it a shot now:

mlx_vlm.generate --model mlx-community/Qwen3.8-27B-4bit --prompt 'give me fizz buzz in rust' --enable-thinking --draft-kind mtp --draft-model mlx-community/Qwen3.8-27B-MTP-4bit --verbose

==========

Prompt: 58 tokens, 90.717 tokens-per-sec Generation: 145 tokens, 36.392 tokens-per-sec Peak memory: 17.419 GB Speculative decoding: 2.79 accepted tokens/round (1.79 accepted drafts/round, 89.4% of drafted, avg draft 2.00) over 52 rounds

Which is very close to ollama, thank you!

I'm not sure if I can get rid of the drafter model, if I understand correctly, the Qwen model already includes a built in draft headers, but just having --draft-kind mtp results in about 17 t/s.

Can be easily the price you will pay across Australia, depending on the time of day.

The problem is it's not the engineers that overthink it. The requirement for soc2 usually comes with the first "serious" customer. It is usually a big blocker on some fat contract and now the business makes it your problem for the next 6 months.

So what do you do? You engage and some 3rd party 1800-need-soc2 clowns which will hold your hand and implement all the cookie cutter solutions they know will make auditor happy (oh and btw, they know the auditor personally).

No, that's not a brag but a suggestion to take things into context and not apply soc2 as a cookie cutter solution where a 20k employee enterprise and a 20 people startup must share commonalities.

In a 20 people startup it's very likely that most engineers have access to production anyway and can inject malicious stuff directly, so PRs stop no one really.

It's an old phone getting a second life, the health of the battery is probably not a big concern at this stage.

It's not a concern untill the phone is bloated because of damaged battery. Also it can catch fire!

yeah but when the battery fails, you loose your "server".

i'm thinking more about long term.

Heh.. Russia is catching up with Australia!

Impressum (DE)

TIL waydroid...

Probably a slop of https://bellard.org/jslinux/

Have to agree. Unsure why the page is comparing with docker/cloud shell instead of jslinux/webvm.

This is a pretty harsh critique, while I see the agent related markdown the application seems measured and well applied. Hardly seems like slop; it's might be a one man show+ai agent but the direction and project composition feel like it's something that's logical and manageable.

I personally like the idea even as a p.o.c (inline with bellards work). I'd like to see how nostr & cloudflare workers providing out of band ops on what is effectively a container per tab.

I don't think that guesstimating that something is an AI slop is very harsh these days. It sure has the signs of one:

- HN User created 66 days ago

- In these 66 days it submitted 4 stories about this project

- The heavy lifting is all done by v86 project (not jslinux as initially suspected)

- The project is a "rebrand/fork" from another project by the same author - "traits.build".

- In the original project, the first commits that mention v86 seem to start at around 23rd of April.

To be clear, I don't really mind people vibing & slopping around. I just would want to have a disclosure about it.

Show dead and you see 23 posts about this exact same thing which gives me pause and makes me wonder, did this guy really post this 23 times?

Why? Or is there some program setup on a loop?

Either way,a legit Linux shell in a browser would be kinda powerful and even if this one isn't legit, Im intrested in adjacent projects...for instance this may be the only way to get a shell in a usable shell on iphone which would be neat and useful

i did. i am trying to get some traction on the project to hopefully collaborate on the development in the community.

thank you for this interesting analysis. however, i do disclose that it's agentic coding in yolo mode on my github page.

thank you!

Why this has to be all or nothing?

You can use the drug to loose weight while trying to understand the underlying problem.