tommy_axle

This sits in the right spot using the existing wg conf and tools.

Although the timing was suspicious it looks like they might be correct about the price. namecheap has the same price https://www.namecheap.com/domains/registration/results/?doma... (a bit cheaper at porkbun around $2.5K)

It wouldn't be a first: https://en.wikipedia.org/wiki/DRAM_price_fixing_scandal

Yes, definitely the official directory for apps/connectors where possible, which security and vetting is a priority. It's similar in some ways to how it was/is with mobile where you have the official store vs directly running an apk.

Vite is great and vite 8 was a huge speed-up so definitely a nice win for them. Remaining independent is always great but at the same time there are other "new homes" that could be worse so let's keep our fingers crossed and hope it works out.

If self-hosting the runners too then it's doable. Not 100% sure for Forgejo but with Gitea and act_runner it's possible and pretty economical if you have an extra mac mini.

Map to "jj" and call it a day since your finger is already on the home row

Also ctrl + [ is standard terminal/ascii for esc so that might be a bit more ergonomic than reaching for esc

Go version came in handy https://github.com/badsectorlabs/copyfail-go especially for systems without the very latest python (os.slice)

Slightly more readable Python version at https://gist.github.com/grenkoca/b82281a4706e936072979acf54b...

Could be worse (we'll see) as this could be a wild ride along with react2shell or some of the compromised packages as of late.

I wouldn't go that far. Right tool for the job as always. Axios offers a lot over fetch for all but the simplest use cases plus you get to take advantage of the ecosystem. Need offline, axios-cache-interceptor already exists. Sure you can do all of those things with fetch but you need more to go with it taking you right back to just using axios. Also is no one annoyed that you can't replay fetch like the xhr? Same with express: solves a problem reliably.

OpenClaw acquisition at work.

Pick a decent quant (4-6KM) then use llama-fit-params and try it yourself to see if it's giving you what you need.

Nah, prepending will lead to a messier diff than the parent example.

I'm guessing this is also calculating based on the full context size that the model supports but depending on your use case it will be misleading. Even on a small consumer card with Qwen 3 30B-A3B you probably don't need 128K context depending on what you're doing so a smaller context and some tensor overrides will help. llama.cpp's llama-fit-params is helpful in those cases.

More like redux vs zustand. Picking zustand was one of the good standout picks for me.

With all the buzz about orchestrating in the age of CLI agents there doesn't seem to be much talk about vim + tmux with send-keys (a blessing). You can run as many windows and panes doing so many different things across multiple projects.

If doing it directly fails (not surprising) wouldn't the next thing (maybe the first thing) to do was to have AI write a codemod to do what needed to be done then apply the codemod? Then all you need to do is get the codemod right and apply it to as many files as you need. Seems much more predictable and context-efficient.

so like GraphQL?

My guess is business (if they are doing well on the platform)

I see a service like this as being in the ip lookup API category (like ipinfo.io) but I wanted to mention that for this (and IP lookup, captcha etc) I would expect that if the service is down then you allow the registrations then review later, and not simply prevent all registrations.

Ok so taylorswift is reserved but taylor_swift and realtaylorswift can be used? It seems like impersonation would still be a problem.

An aside: it looks like there is a certificate error for https://certkit.com/ as it's for *.mscertkit.com (this was on Chromium + Linux)

You want it to be as close to deterministic as possible to reduce the risk of the LLM doing something crazy like deleting a feature or functionality. Sure, the idea is for reviews to catch it but it's easier to miss there when there is a lot of noise. I agree that it's very similar to an offshore team that's just focused on cranking out code versus caring about what it does.

Technically writing calls is also taking the downside.

Not the OP but yes you can definitely get a bigger quant like Q6 if it makes a difference but you also can go with a bigger param model like gpt oss 120B. A 70B would probably be great for a 128GB machine, which I don't think qwen has. You can search for the model you're interested in on hugging face often with "gguf" to get it ready to go (e.g. https://huggingface.co/ggml-org/gpt-oss-120b-GGUF/tree/main). Otherwise it's not a big deal to quantize yourself using llama.cpp.

There was more also going on in that time-frame: several interest rate hikes, no fix for section 174 changes by the end of 2022. Maybe someone will pinpoint whatever had the largest impact in a detailed study.

Not sure, most were probably created just for this hackathon so I'd expect few if any. It's just a good way to see how far one can take it with vibe coding. It's easy to crank out smaller apps these days so marketing and distribution will be more important going forward.