I’ve tried this kind of format too but it didn’t stick for me as i was missing the rich context the sessions were able to provide for me. Specifically the lack of diagrams and other nice formatting that is possible in HTML files. I also tried linear as a broker in between for a while but it just blew up and became too tedious to navigate and ran out of sync fast. Also expensive on token overhead.
Currently what I task it to do is have one or multiple agent threads tied to a project work it and have this really token light skill laid out that leverages eleventy heavily and renders it as markdown file. Than paired with thisbit.ai (I made this and still am developing it) i just comment / voice over on all the bits from the article and have the agent take it from there again.
Also neither codex nor Claude code come even close to the lovely TUI renders of Gemini (Argon 4)
There’s only that many ipv4 addresses and I believe all 5G are shared ones. That’s why they’re among the most valuable ip ranges for scraping. You can’t just naively ban that IP or you’ll ban a large group of users
It should be a balancing act though, somewhere between what you said and my first sentence.
Rate limiting, or additional layers of input sanitisation for IP addresses known to have been malicious in the past.
It's unfortunate that good users will have to endure some difficulties because of bad users on the same network, but if security is the priority, then measures must be taken, you shouldn't just leave to door open to potentially known bad users / traffic.
IPv4 is a shared resource, but some ranges have worse reputations than others, and all are owned by organisations that have the ability to monitor and filter for malicious traffic. It gets into a fraught discussion about censorship, but it is possible for network owners to monitor for, and block / restrict traffic detected as 'bad'. It's just a matter of cost and scale, and those that put the effort in should have their users rewarded with fewer 'trust-issues' roadblocks.
The blocking of residential proxies might be the thing that moves the world to ipv6. These days what we need is a dynamic map of all the IPs running proxies so servers can block them. If every device gets it's own v6 address, you could block just the TV running the proxy. Modern crowd sourced security products could identify the proxies and share their IP live so you can ban and unban addresses as the device moves.
> It's unfortunate that good users will have to endure some difficulties because of bad users on the same network, but if security is the priority, then measures must be taken, you shouldn't just leave to door open to potentially known bad users / traffic
Is this like a corporate support response? I legit can't tell. Try explaining to a retail consumer why they can't buy from your site because they have TMobile service.
They’re saying T-Mobile should be monitoring traffic on their network and block traffic from bad actors that ruin it for everyone for everyone else? Or at least they do in the next paragraph.
When the bad actor is grandma who has an infected computer, T-Mobile will be dealing with a lot of support calls from objectively non-malicious actors.
>you shouldn't just leave to door open to potentially known bad users / traffic
Why not? If security is the priority, the worst that could happen from that is clutter in logs and higher resource use. Nobody wastes 0days spraying them on random hosts, and a real motivated attacker targeting your server will not be stopped by an ip blacklist.
Not sure about US but where I live I can manually set the access point of my phones mobile network and it gives me a unique ipv4 (new one each time in fact)
But if you’re statisfied with just that throughput and model capability that a M1 can provide, than I don’t think you are a well monetizable client anyway? I agree with the no moat as I use a wide variety of models but to only use my M5 128 would definitely not statisfy my needs, so on top of that I pay.
I'm satisfied with it for the most part, which isn't to say that local models can't be slow or don't do dumb shit that show their comparative lack of intelligence sometimes. But when I need speed or intelligence, I just press ctrl+p in my harness and spend a buck on OpenRouter.
It's my belief that we will (or probably have) hit a point where the majority of us receive diminishing returns from the sota models for the work we do. I don't need Astra or Mythos just to write some crud apps or refactor react to svelte, for example.
Mlflow does it pretty nice including session gathering and optional data enrichment (eg what files were touched, what model was used, git remote).
We use these session IDs for commenting on issues and stories touched by AI for context tracing.
I just wrapped around the Mlflow setup to make this simple CLI helper to set it up. Ofcourse the name suggests only Claude but it’s Codex, CC, GHCP and Agy. https://pypi.org/project/claudetracing/
I think a lot is memory really. For fun you can try pointing just about any model against the older kaggle challenges and it’ll come up with more or less the winning solution from memory. It’s here where you see a Gemma 27b perform about the same as opus 5.5
In jevs case I think the competing offerings will rear their head rather fast. The ability to label data like it does now leans itself well for distillation. And to switch out a model like fable for Astra is really not all that difficult. Yea jev is alone now. But before the end of the year another lab with the same offering will rear it’s head
> There's 1000 chatgpt clones but everyone still uses chatgpt. There might be 1000 jev clones soon enough but people won't switch unless there's something significantly better about it.
The fact that Jev will be cloned is exactly why brand and distribution matter even more. When 1,000 products do the same thing, you'll use the one you know.
These kinds of trivial CLI vibes tools save an evening and some tokens. And sometimes it’s also not something you think of, or done with better or worse taste than your own. I think it’s nice
Create a skill for this that you can invoke a new session in referencing your previous session id. Your instructions here read clear enough it seems to create it. Though a handover skill with this kind of behaviour in the same session might be more economical given the cache materials is already there.
the noise is pretty doable, and so is the heat, I find. I read these messages before I had the machine and expected far worse. The tok/s is for me the dealbreaker as I prefer to have multiple sessions. For nightly runs i do like it a lot, or to be a node in a mesh.
Currently what I task it to do is have one or multiple agent threads tied to a project work it and have this really token light skill laid out that leverages eleventy heavily and renders it as markdown file. Than paired with thisbit.ai (I made this and still am developing it) i just comment / voice over on all the bits from the article and have the agent take it from there again.
Also neither codex nor Claude code come even close to the lovely TUI renders of Gemini (Argon 4)
reply