And it's also the kind of solution a misaligned agent would implement:
Make sure users are happy about their experience but also optimize resources.
The obvious solution is to route users based on feedback.
1,583 karma · joined December 7, 2015
And it's also the kind of solution a misaligned agent would implement:
Make sure users are happy about their experience but also optimize resources.
The obvious solution is to route users based on feedback.
Sometimes the SDK is a zip of the developer workspace in a pseudo working state with no clear records of all that's been patched.
Vendors providing binary only kernel and system images containing god knows what is not uncommon either.
I'm convinced now that arm hardware vendors are simply incapable of even understanding what proper software support is. I'm sure some of their devs do their best but management does not care. By the time the chip ships, efforts move to making the next thing so they never properly finish the software side.
The point is do users want ads? Or more reasonably, should platforms offer a paid, ad-free, experience.
> No, it’s not about the [...]
Am I the only one who can no longer read past something like that? Article may or may not be AI generated, but on first glance I get a bad vibe and I loose all interest.
Now some people would like to use that top of the line Apple silicon but without MacOS that comes with it. I doubt this is a huge threat to apple but it's also not a huge market for them. From what I understand they are not actively impeding it but not actively helping it either.
I actually won a M2 laptop a while ago. I resold it, new in box still shrink wrapped because I did not care for MacOS, just a personal preference. People like me are a minority though.
Commenting because I am struggling with this too, claude code seems to be so verbose no matter how I prompt it.
The play store results were ATROCIOUS and user hostile, forcing account creation, full screen video ads and other BS.
I remembered I had f-droid and I found a perfect, no bullshit app that does exactly what I needed and no ads.
Can you see the docs folder with the git project?
It was in auto mode. So it immediately saw a docusaurus site (good) but instead of stopping there, it installed nodejs from a static binary download (no root access so only way), ran npm install, started the dev server and confirmed the project worked.
That is some crazy amount of leeway for an intent based classifier. I'm not surprised it's full of holes, and it seems to be 100% by-design.
Most improvements on that front has been happening on the application layer, where the app attempts to retain functionality even though the underlying network conditions are changing, to various degrees of success (mostly not that great).
There is about 3.. Broadcom, Qualcomm and MediaTek. Together they control I believe 100% of wifi chips used in routers and APs. Often it's sold as a package / system on chip so it's also the main cpu.
On the client side there is a little bit more competition but not much.
I install Linux on a wide variety of hardware for both work and personal reasons.
I don't read the detailed changelogs religiously but after years of paying some attention to them I can understand most of it and see where the industry is investing developer efforts, what cool new hardware is gaining support and what new security or performance features people are focusing on.
The only way this works is to use the same exact model and weights right? So that you can replay the text generation as it would have been originally done, and compare output?
And then what, if there is no match do you need to retry with all other known models that could have been used?
Or are models sufficiently similar that they are interchangeable for this type of watermark?
And what if a competing or open source model was used? I can't see how the watermark would work.
And if you have access to a non-watermarked output? How can you prove they are not simply using another key? How can you be sure the text is not watermarked? From the explanations, you can't.
Even before LLMs, most teams don't bother cleaning up. The best you'll see is feature branch getting squashed on merge.
AI is not really a factor here. Teams/orgs that did not care before still won't, only 10x more.
Demo the work, keep changing. Don't worry about the amount of changes, don't worry about nice commits. You are free to explore and produce as much changes as required.
Then use AI agents to clean up the history and produce a nice change set that you can ship in a more traditional way, small clean commits.
That is an interesting idea I guess. AI agents can be used to clean up git histories, not only produce large amounts of code.
Somehow, I think heavy LLM users don't really care about a clean git history / changesets? May be if the project or existing workflow you are bound to requires it you will do the extra steps but really I don't see it being done much.
Are you really going to review these small changes? So far the example I saw from agents are terrible. Full of drive-by, unrelated changes here and there. Mostly harmless or OK changes, but not focused.
My point was not to use http only as a finished solution, but to let the admin front the http-only service with their TLS termination solution of choice.
Do you want a caddy service embedded with every web app you self host or are you running a single one serving all your apps?
From my understanding if you want acme http challenges to just work with let's encrypt you probably need to use a single, separated caddy to front all your apps.
In that case if I ship a caddy service pre configured to do TLS termination with my app it's just more trouble for you no?
You say caddy. The next person will say nginx-proxy-manager. The next will say DNS challenge let's encrypt behind wireguard VPN. The next will say Traefik. The next will say CloudFlare tunnels.
Everyone has their preferred solution and its always the best and simplest.
The best is almost not to do it at all. Just have a docker image serve http/1.1 and document that a reverse proxy is required to expose the service.
There are simply too many ways to do it and every sys admin/hobbyist has their own preferred way.
For the anonymous and authenticated caching issues the author goes into, I think once again it is useless for self hosting. Just embed a performant web server like nginx for example that is pre configured to serve static files. Use proper headers, and predictable/simple paths. Self-hosted versions are going to be low traffic and just need to work.
Have advanced settings for more control, but keep the default simple and working out of the box with minimal dependencies.
I think the name is confusing because the term 'query' is already used to refer to http requests in general.
Just the title of the RFC confused me.
You have to take their words for it but how can you trust crooks?