curbstickle

Please take a look at rules 7&8; tag and disclose as required

Unfortunate, but also happens sometimes

Sorry I don’t have a better answer!

So thats the caching portion not being 100% - using the ID for the search, try it twice, that has worked where the first fails but the second query shows up, specifically for the id you want

https://github.com/Lidarr/Lidarr/issues/5498

AFAIK still not a closed out issue.

Well I used to use VGA for my monitors, now its mostly displayport.

Seriously though, prom+Loki+alloy+a few other things to Grafana, with alerting in grafana.

Lwn has a pretty solid overview:

https://lwn.net/Articles/1024387/

There are a lot of small things that played a role, so I don’t think I’d be able to give a good shortened version.

Decommissioned USFF business PCs if you want something that can handle a lot and a bit larger is OK.

In that size I’d say OrangePi or Radxa, but depends in your use case for which.

Please add the appropriate tags (see rule 7) and disclosure if required (rule 8)

Thanks!

Edit: Locking for now, please update and if you have questions, feel free to ask.

OP did not make it and can’t do a disclosure, its not required.

Noting it is because Claude is involved is a nice-to-have, not a requirement.

You’re also handling bluetooth and wifi functionality with that permission, fyi.

Please tag and disclose as appropriate, refer to rule 7 & 8.

Completely agree

My current decision is between a new Motorola signature 27 with graphene (running under the assumption Linux will be able to make the jump there, which isn’t an unreasonable conclusion to jump to), or getting a mostly basic flip phone that can hotspot and using a umpc with it.

Where Linux phones have failed for me is the limited options for phones and on the actual phone part, so I feel like separation that out with a nice umpc and letting a phone be a phone is a worthwhile option.

We’ll see how things play out though!

The permission structure sucks.

Its a silent drop (no errors are returned), webview breaks connected to WiFi even without a local resource being requested, it lives inside nearby_devices so giving permission there includes this (and gives a broader spectrum of access such as Bluetooth and WiFi).

Its just shuffling the problem around.

Also, fuck Google.

The problem with graphene, unfortunately.

It doesn’t actually get away from google, at best its plugging holes in a (to me) sinking ship.

The solution is to avoid google going forward, for many reasons.

Haven’t been brought to 17 yet thankfully.

My long term solution is to not use android. My short term solution will likely be to use android even less, and be even more pissed at Google.

I wish it would because there’s no way to stop someone from creating an alt to promote their own projects and claim “they didn’t know it was AI” when they knew full well it was.

They will have to wait 30 days every time. This hasn’t been an issue for any post so far.

AGENTS.md in a repository are used to guide development.

That is not entirely true.

It can be. Yes, it provides agents with contexts - rule centralization, commands, conventions - which may be useful for external tooling for a project that runs on code live like this. It isn’t exclusively used for project development, which makes its presence not an indicator.

I see at least one: if the project doesn’t have a clear no-ai policy, then assume it is AIP. But that’s not my proposition at the moment.

Also discussed in the meta thread about this, and what results is projects being called an AI project that are not projects developed with - or even designed to allow interaction with - AI.

Also a non-starter.

Edited to add: What needs to be avoided is nonsense like the recent debacle caused by people being unfamiliar with Akedemy, causing a series of nonsensical posts about KDE being “all in on AI”.

Misinformation is one of those things I will not compromise on.

I was just asking for a precision, but that’s because I didn’t check archives enough

There is precision in the detailed rules post.

If you want to see the prior meta discussions, you can look at my post history. I don’t often make standalone posts, so they are quick to find.

Its pretty far from perfect actually, and will often result in both false negatives and false positives.

Not a viable solution.

Just like the discussion last time on this - every user will not be able to be a forensically review.

This is demonstrated clearly with how you misunderstood the role of the agents.md file in the other thread, that was for AI to be used with the app, not for the app development.

So if you’d like to propose this, and people would like this, you’re going to need to include how or its simply unworkable as a rule. And I don’t see any option for how this could be realistically implemented.