megous

Rule no. 1: you don't announce your security by obscurity methods :)

I wonder if the judge would be in favor of companies proactively going into people's houses at random to check on their belongings, if they don't have inappropriate photos somewhere, or whatever.

It's harder to do, but conceptually the same. So sad it's not being done. Very disturbing.

They could do it when people are not at home. There'd no problem, nobody would even notice.

There's no issue with mega. There are third party apps and as long as you don't login to mega.nz with their website you're fine. And they also have SDK you can use that they'll not be able to control/manipulate without your knowledge.

The browsers disagree.

Difference is Trump wanted 20% and Iran like 2%.

Never met a chemist did you?

Or a musician, or a philosopher, or a biologist... :D

Such a limited life.

All projects spiral into chaos unless there's a person or more who try to reduce the growth of entropy, all the time, framework or not.

And these days, LLM agent will just re-use existing patterns if prompted correctly, regardless of who in the team is using it or whether or not there's a public well known framework in place or not. So consistency should not really be an issue anymore even in a team.

It's not a html variant. It's just a bunch of web components. Takes like 30s of looking at actual source code to figure that out.

You don't need it anywhere, unless you want to use dataset property.

Saying to your subordinates they can kill 20 or so untargeted people per whatever their AI marked as a target is exactly that: accepted 5% "combatant" worst case kill ratio as a policy. And the reality of erasing thousands of families during the night attacks on their homes and just killing them all without distinction, checks out.

https://en.wikipedia.org/wiki/List_of_entire_families_killed...

And Israelis will absolutely automate all that even further, even if this was just half automated early on. Their companies already advertise the capability with real videos from Gaza, killing unarmed people.

System specific stuff is probably quite limited, it can be a short dynamic segment at the end of the system prompt, perhaps.

If it's always the same prompt, can't they have it pre-cached globally for all?

Some arbitrary threshold set by a completely demented US president (25% of government budget or whatever nonsense that idiot asked NATO peers to spend, probably on american mil. tech) has nothing to do with how european countries would/are able to defend themselves.

Forking and maintaining Linux does not take teams of people. I've been at it for > 10 years and maintained support for my 15 or so various SBCs/mobile devices, writing drivers, debugging, cleaning things up. It's a weekend project every 3 months + whatever you want to put in for development.

And there are others doing it for projects like Armbian, openwrt, etc.

US should be split up so it can't do any more damage to the world. Americans can't be trusted with putting that much power in the hands of a few people anyway.

Say you have something easily paralelizable, like 150 decompiled binaries, and you want to produce documentation for what each does. You can run 50 subagents in parallel (eg. kimi swarm) to analyze it all in a few minutes in 3 batches instead of doing it serially which would take half a day.

Most of the software is this way, it seems. Military intelligenece in our country were recently changing configs on peoples routers without their knowledge or consent to get rid of similarly dangerous thing on several types of tp-link routers.

And if you ever looked inside the firmwares of these IoT Linux boxes (be it sip phones, payment terminals, ip cameras, routers, modems, etc.) you'd not want it anywhere near anything that needs to be secure. OpenWRT or your own thing, or very strict isolation, or nothing.

I actually tried a few of the steps, but whatever.

The problem is not that you can make LLM perform whatever tool calls you want.

The problem is that those tool calls are not scoped to what you can access. Eg. tool call should not allow the LLM to access anything that you should not be able to access if you had access to the tool calls directly.

So in a sense the problem is not string interpretation confusion (like with SQL injection), but data access controls.

You can certainly make it produce a lot of design rules of thumb. You can make it do the research for each of those based on the literature. And you can then make the machine sort out the rules of thumb by effect and quantify them meaningfully.

Then you can make it process existing good designs and make it propose a general design/routing methodology (and it's own scripts/tools for calculating/optimizing the "thumb" rules that would be used throughout) for initial placement/routing of key components based on all the collected data.

Then you may have enough context and tools to have it make use of them during design.

What's special about it, other than more constraints, more things to take into account, and having to simulate/test more - so the need for some specialized SW?

They are different constraints than the ones in SW development, but is there some fundamental difference that prevents replacing the human in the loop with AI in the loop?

Americans are always funny,... being proud they can have one day a year where they can breath a highly toxic air created by others or are forced not to ventilate their house and spend their day with a >2000ppm CO2 headache/drowsiness (or from the other PoV, proud they can inflict this on fellow Americans, even better).

"And if you don't like this, you can just git out!"

All the while they're stripped of dignity in the eyes of people abroad, by their aggressive/genocidal government's foreign policy actions.

It's still better general OS than any alternative. :)

Recent update resulted in 100% permanent CPU load in the background, when doing nothing with the app. Basically unusable on a notebook (hot+noise, unexcusable for do nothing "api/command coordination" terminal app). Dunno if they fixed it, since I could not use it on the notebook and I do not have this issue on my workstation.

Messaging protocols are useful even if everyone is not on the same app. In the past I was chatting with my google using friend via some third party jabber server where I had an account. It was useful and didn't require us to be "in the same app". We both were using both different apps and different server providers.

To add to others. You can tell Kimi or whatever these days to write you a GTK4 mobile apps for a lot of pet use cases and it will. The result will also be a few C files and a meson build file, that will build on the phone itself with just gcc/binutils (I run arch linux, so no separate dev packages for deps like gtk, etc. that I need to install). You can install opencode or whatnot on the phone itself, and tell the phone to build you an app, and it will. If you need it changed, you can just ask for the changes on the phone itself and agent will update the app's code and re-build it on the phone itself. It will not need the 30+ GiB monstrosity of whatever Adroid needs to just build a hello world app and a separate computer.

The app will also build and run on your desktop without any/many changes, if you need that.

I got a fairly nice linphone GTK4 phone frontend app this way. So it's not just for toy apps. FOSS/Linux phones are well positioned for this self-building/self-updating prompt based software development, because you don't need separate computer and shitton of SDKs and a permission from the overseer to build/install the apps, and while phone UI is shit for manual programming, it's not at all shit for writing prompts.

OV5640 will not get better just by aging. You should adjust your expectations.

You're behind times. We call it upstream and downstream these days... it also brings so much more of the needed clarity.

He's a prince of whales.

So prosecute them for those other things, no? Instead of helping criminals grow their business by banning non-harmful stuff and giving them monetary growth opprotunities.