InnerScientist

Well, you can do that too by just marking the time range and repeating the appointment every day(/monday/...).

Just use multiple calendars?

I use Davx^5 and radicale to sync one (my own) calendar but you could also have multiple and distribute as needed.

Not sure if that would work, a restart resets all progress. If the program didn't finish inside the 8 hour workday then it will never progress. Add to that that the ai will use the same amount of ram no matter how much you slow down the CPU and you'll still slow down the PC immensely. The small models also aren't smart so they would break often too.

Edit: Does a working PoC exist? Shouldn't be hard to (dis)prove.

Press x to doubt.

Ignoring the question of "could current ai do this?", the fact remains that most PCs that can get infected either can't run the model (not enough ram) or run it with an immediately noticeable spike in CPU usage (100% for hours/days) or a spike in GPU usage that would block most other tasks to a standstill.

I'm not a car expert or planning to be.

Anyways I'm going to build my first car by hand.

I have set up Tor secret services in the past to do this.

The service exposed the SSH port which could then be accessed from anywhere as long as you can connect to Tor.

That's load bearing free time, better not touch it.

I don't know anything about Talos but can you try it in a VM with a test disk? That should answer all your questions and show you possible pitfalls.

You get One(1) DDR5.

They are at the mercy of not being shit listed by companies.

That is if they can't pay for the products through the revenue of the review. Though ofc they still have to have ads or sponsors. Much more important is if they are financially stable and convicted enough not to sell out.

for a homelab I don't think it's feasible to fully review the source code of everything you install

Here's what you can actually do:

• Consider if you actually need the application and stop applications you don't use
• Don't allow public access unless it is necessary, consider VPN/reverse proxies with client authentication (if supported)
• isolate applications that don't need to talk to each other
• • see also rootless podman, firewalls, virtual machines, etc
• • don't forget network access, if everything runs on 127.0.0.1 and every service shares it then they can all talk to each other! (See also network namespaces or VMs)
• Don't reuse passwords
• keep software up to date
• actually evaluate the quality of the project if it needs access to sensitive information
• • see open issues, closed issues that stand out
• • check for audits or at least a history of good effort™

Sure you wont always catch ai slop this way but you don't need to read a line of code to at least be reasonably sure your arr stack won't get to the family photos.

Can't have shit in Detroit.