justaboutanyone

How does that work with multiple credit agencies?

While pinyin might be "better", there's still a lot of room for something better than it

At this point, it might be moot. Too many people are assuming it's still a closed-source thing and will dismiss it.

Due to the closed source nature, every mojo announcement I see I think "whatever, next"

If the actual intent is to open-source, just do it, dump out whatever you have into a repo, call it 'beta'

This failed when I put in an australian postal code.

Shell programming is high density inter-language glue. You simply have more options of implementations to call out to and so less to write.

I can trivially combine a tool written in rust with one written in js/java/C/whatever without writing bindings

First thing a public spacex would want to do is sell off all the non-spacex crap

This sort of thing will be great for the SpaceX IPO :/

Running llama.cpp rather than vLLM, it's happy enough to run the FP8 variant with 200k+ context using about 90GB vram

For Qwen2.5-72B-Instruct-Q5_K_M at 32k context, I fed it a 26k token file (truncated fiction novel) asking it to summarize, and it input processed at 224 tok/s and output generated at 3 tok/s. Not really good enough for interactive use without frustration. Not just from watching it reply, but also the long wait for it to actually read the book.

On the same hardware gpt-oss-120b at 128k context, I fed it a longer version of the input (a whole novel, 97k tok), and it input processed at 1650 tok/s and output generated at 27 tok/s. Just fast enough IMO

You can run large-ish MoE model at good speeds, like gpt-oss-120b, it's snappy enough even with big context.

But large and dense at the same time is a bit slow.

Running a local LLM will be a load of money for something much slower than the api providers though.

We may as well have the LLMs use the hardest most provably-correct language possible

What is the article text for those stopped by the paywall

It really feels like more than 1 in 20 driving around the 101/280

Where are the RVA23 boards that have been hinted at for so long?

Perhaps people will move to stricter programming languages try to counter the slop issues

People are still going to read the PR regardless of how it was created.

Punching through just a firewall is much easier than punching through a typical NAT+firewall setup

https://tailscale.com/blog/how-nat-traversal-works

There are some address source selection problems if you're still using any ipv4 for the local services https://blog.ipspace.net/2022/05/ipv6-ula-made-useless/

> Except silicon, power, and water

Various chemicals too, https://haz-map.com/Processes/97

Has there ever been an effort to port PF over to linux, or to create an adaption layer that makes things compatible?