Fabricio20

You know, personal anecdotes and all that, but a company I used to work with was applying for their b2b app as well and we got a denied with a screenshot of a completely unrelated app as well, and that was at least 5 years ago. We ended up just replying "That's not our app" and I think it got stuck in limbo after that as I don't recall hearing anything about it afterwards and then I left the company.

I feel like that's not a true cold GPS signal! Though I'm not arguing the parents scenario is realistic either. I got a GPS module for a drone I was building and it took 20 minutes to get a proper GPS lock from cold!!! I was sitting there watching betaflight doing it's thing wondering why the heck it takes so long when there's so many satellites in view!

The part about "tool-calling on other models didn't solve already" is what gets you, sure I could tool call deepseek, glm or any other model, but the latency is huge and you get no confidence score. I gave JEV a shot via OpenRouter and it has a reply in less than 400ms, it's fast enough and cheap enough that you can hook it up to a game loop for example (so highly state dependant) and it can do decisions in real time.

Blocking URL shorteners and google-ad links yes! Personally for me it's also the fact that this is effectively an unresolvable URL shortener, store that link somewhere and it will most likely be dead. Can't copy link anymore and paste it on a notepad or chat app to check it out later as there isn't a guarantee it will load at all (ie: the problem with url shorteners).

On the user side my experience with F-Droid is auto updates dont work and I constantly get a "repository not reachable" f-droid error every now and then popping up on my phone (that little small middle-of-screen toast) when im doing something else completely unrelated. Might be a regional thing.

I've used auto mode a few times and it's honestly pretty good, but I think this isn't just about auto mode, CC in particular has many other safeguards I've noticed even when not under auto mode (one that surprised me recently is a "risky command detected" that under bypass permissions stopped a tool call - the script had a RM /$var - had the var been empty somehow, it could've deleted the os).

I'm not surprised they are confident in promoting it to the default, it alongside the many other safety features in the tooling are honestly probably better than my exhausted review of every action.

Auto mode denies are also interesting, sometimes Claude wants to go off script to double check something (ie: waste time checking something slightly related that I know is not necessary/truth holds) and auto mode plainly stops it since it's off scope, nice bonus.

This was so bad for me I actually added a tool hook that `time`s the tool calls and adds it as [Execution took: Xm, Ys] at the end of every tool call, it helps a little (claude in particular after two executions tends to switch strategy entirely) but in general the agents still insist on cut/tailing the output rather than just dumping it to a file for example!

Now that I think about it, maybe I can have a tool hook that detects those cut/tail exessive piping and just strips them and dumps the full output to a temp file..

If only the piping wasn't execessively cutting too.. `cat | head -10` -> `cat | head -20` -> `cat | head -40` yeah.. I think at some point we need to start sanitizing our tool outputs so that this just isn't necessary at all, long term fixing the tools (ie: gradle outputs like 500 lines of logs for a ... build succeeded), maybe short term a small model in front would be better than all this cut loop fail. One can wish.

> Then you’re maintaining a stack of patches on top of the upstream until the end of time because the maintainers of the projects don’t want AI slop contributions, but now you depend on these changes for your own use so now you’ve created more work for yourself keeping your own fork up to date.

I thought about this but I currently maintain a fork of about ~6 things I use on my own, none of which I have any interest of contributing upstream because it'd be out-of-scope and put a burden on the maintainers that is unrelated to their primary goal. It has been an extremely easy experience with claude to keep those tools up to date on top of upstream.

StGit/Stacked Git is a proven tool for this and has worked wonders, I can literally just ask claude to fetch upstream and reapply stg patches on top and fix each patch if they break in order. I also keep extensive description of the INTENT on the stg patches so claude can easily figure out if something is no longer relevant (ie: somewhat implement by upstream) or where to land the code/hooks. I've added features, reworked how algorithms work (pathfinding related!) and small nits I hit on daily usage.

Even on a very churny upstream (one of the projects the single dev likes to refactor alot) it's still extremely chill and doesn't take more than an hour to get it updated when everything breaks. I can't say i care enough to setup a daily cron like a sibling suggested, but it would likely work just based off of this stg experience.

It's also nice, because some of those were actual bug fixes too which i have contributed back upstream! Maintaining your personalized fork is truly reasonable nowadays.

I've had some great success with Reolink. Decent video quality and the software is made with RTSP/RTMP support in mind, including a proper web portal on the camera so you don't even need the phone app for setup.

Not too sure if you are looking for non Chinese manufactured though, down here anything else is just way too expensive and lower quality anyway!

It's actually pretty darn easy nowadays and i'm so glad its the case! Frigate is amazing and the detection package is of your choosing (hardware dependant) and everything is customizable too.

Just got hit with this on all my sessions on CC, neither the old TodoList or the new Task tools are available to any session. Limiting it from the server side is truly amazing, I feel like it's related to Opus 5 possibly releasing today, but wow.

Opened the website to be greeted with only spam of huge walls of random text, seems people are abusing the fun out of it! Would love to actually have seen some interesting bot patterns from the authors comments.

Shebang! Notice the first line of the script: #!/usr/bin/env python3 marks the file to be executed by python. I think it's like a shell? linux? thing so that tooling can just execute the file without having to find the python interpreter (ie: _execute_ the file vs running python against the file).

Dont quote me on the specifics though, and honestly why it can't _just_ be a python file I couldn't tell you, claude code can very much run a python <filename> but maybe thats what the author tried to avoid (or the llm).

I also have a local rule for no em-dashes since it got way too annoying and i have the same concern that it dilutes the attention so it's the only rule i've kept in addition to "be concise".

Oh this is amazing! I have a few of their cube routers sitting around and I always hated how app-locked their firmware was when it really is just a wifi repeater with a few extras (mesh) on top. Root access will do wonders to bypassing the app now (and also disabling their ping-for-green-light mechanism which spams the network with a constant dns resolution to microsoft.com lol).

Also honest take this looks less like a "backdoor" (implies malicious - this is a link to a CVE after all) and more like a developer access credential/default credential that was burned into the firmware (i'd imagine the code remains but on a production run they randomize the key so its non-guessable but then you get lazy and dont run that extra step and this slips in/you burn the bare firmware with no production configs).

I see, so a coordination server is necessary which kinda somewhat defeats the "mesh" claim, though I do wonder if achieving this in a manner similar to DHT could eliminate the centralized entity controlling the servers at least, allowing the "peer-to-peer mesh" claim to be there in spirit.

Not that I have anything against the software or company to be clear, just that I wish one of these p2p vpns would be _totally_ actually independent of any coordination server or central entity!

You try that in 2026 and not only is your changes getting rolled back but your IP address is likely banned in advance anyway. Though to be fair I hear that even logged in your changes get rolled back, something about "reddit style moderators power tripping".

Though on the naming definition I think wiki is a good term for interlinking documents about _something_. I often associate the term wiki with game wikis, which more often than not at least require some form of account to edit. Wikipedia feels like an outlier (both in not being specific to any topic as well as technically allowing anonymous edits) even if it presumably is the first/originator of the name!

One thing I seem to struggle to understand is, a simple invite code system is showcased, but how does host Alice in one country know how to contact host Bob in another country with just the invite code? This seems to require a coordination server at least right, or does the invite embed some sort of information that'd allow Bob to directly reach Alice with just the invite code?

I specifically disabled claude memory in a project because it kept writing down thigns to memory that didn't need to be in memory, including severly wrong statements that then would confuse it later. At some point it got re-enabled automatically which had me ask claude itself to "turn it the fuck off" by which it promptly figured out that both ("autoMemoryEnabled": false, "autoDreamEnabled": false) are necessary and need to be at the user home settings, not in a project override (which is what I had with the original setup that eventually got ignored by a CC update).

I agree with other commenters here, if anything is worth being rememebered, it will be in code comments, git commit messages, CLAUDE.md or other formal documentation. The auto memory system just causes confusion and leaves stale and outdated information written down.

Its an interesting thought experiment as well, I originally thought that having the model write down memory files by itself would be a nice addition, but after playing around with it, it became clear to me that good as an idea turns out bad in practice because the model can't correctly gauge what deserves being stored as a memory.

One thing I see noone asking, is this not a case of optimization? Hidden reasoning means they dont need to process the output of all that, it stays internal within the model. Less cost for them -> less cost for us (even if they benefit mroe), compared to streaming all of those reasoning tokens out?

I also noticed on the wikipedia gallery theres an example that repeats frames for smoothness! 1-2-3-4-3-2 makes it naturally smooth if you have more than two frames.

I believe one big anti-incentive is rate limiting, especially nowadays. With IPv4 getting a range ban is somewhat effective, way less effective on ipv6 (theres a reason HE tunnelbroker is marked bad nowadays, discord bots doing music load balance over ips on tunnelbroker for pulling youtube audio data.. they ban a /64 but you balance over a /48 or bigger). I believe this was the main reason Discord disabled IPv6 (not sure if thats still the case, but it was back in the day since bans and api rate limiting was ip based).

Conveyor belts? What about those funny looking warehouse robots that are on wheels and just move pallets around, maybe an arm strapped to it? Surely there are myriad ways to do this more efficiently and precisely than a humanoid robot! Just look at Intel's Fabs for example with the ceiling robots moving the delicate wafers..

Browser!! The browser reads it as Number. If your rest api returns {"id": 1324535222364012585} for example, javascript will try and parse that as number from the response!!!

You can of course, change the api such that it does {"id": "1324535222364012585"} instead and voila, it will no longer try parsing it as number. Or the many other workarounds people have recommended above (like appending a prefix, or using a different encoding), but why is it trying to parse a number thats too big and instead of throwing it just rounds down without telling you????!

> bigints are smaller and faster, with less footguns

But be careful!! Javascript WILL interpret your bigints as Number() and round them down because they are too big without telling you!!!

Famously seen by every snowflake user that has interacted with Javascript, quite an annoying problem.

> Good old user research or talking to users to validate ideas, iron out issues in the user flows has become too slow for the new process

I haven't seen these in at least a decade in the industry!! Everywhere I used to work was always "PM wanted" or similar and the validation was always just QA making sure the thing works/does the bare minimum!!! Customer input was just for bugs.

I hope that with AI speeding up prototyping we can actually go the other way long term, where we go back to ACTUALLY talking to a customer and then quickly prototyping it to see if it is what they wanted. Figuring out what the customer wants remains the hardest part of software engineering, but at least right now its mainly because we just dont talk to the customer.

I just installed/upgraded to try out 4.8 and in only 3 messages I hit this bug! Seems something is broken on CC.

Not the same genre (at least for me). Timberborn is more like a colony builder (think Rimworld) than a city builder (SimCity/Cities Skylines). Its the micromanaging vs macromanaging, in a colony builder you are micromanaging what each creature does (such as timberborn or rimworld) while on a city builder you manage the city itself and invididual pawns are alot less important! Plus the survival aspect in that sense doesnt really add up when I'd like to play with the simulation aspects - education, traffic, crime, etc..!

Ever since the AI stuff started rolling around on coding i've seen MORE documentation, theres a big incentive to properly document your API endpoints so LLMs can figure it out from specs, and even when not documented the llms can also just read the code and figure it out directly (for libraries and similar). And at least in my experience they tend to document or write it down for future sessions too!