bornfreddy

Only 7 out of 1800 cancelled, according to the article.

I didn't try telling to be concise and stop pampering me yet (but good idea, tomorrow), however I found that instead of me writing agent instructions, it works much better if I tell claude to write instructions for itself. I do check if they make sense of course, but its wording works much better than mine.

Then this is not the same situation, I agree. That sucks. I hope you find a company that shares (and rewards) your values.

This might not describe you, but I've met quite a few people who made similar claims. The problem usually wasn't that their counterparty didn't want to hear the truth. More commonly, the problem was that these persons assumed (and were convinced) that they knew the truth. Truth is rarely absolute and someone claiming to know it is a red flag in my book. Double so if multiple persons indicated their disagreement. Again, not knowing the exact question and answer it is impossible to say if you are an exception, but even if you are, you need to improve communication skills - what good is knowing "the truth" if others reject it?

That said, best of luck on the job hunt! Sometimes it just takes some time for the right opportunity to come along.

Interesting question, it looks like they are / will be brushelss:

> Group will gradually embed new technological improvements from 2024 on its EESM: stator hairpin, glued motor stack, *brushless* and hollow rotor shafts.

[0] https://www.evspecifications.com/en/news/6ec9484

That said, what sibling says about the maintenance problems is very true. :-/

That's actually a great idea! Easier to setup and use than VM (hello ssh), safer than docker, and still pretty cheap. Thank you for the idea!

> My pet peeve with the NY Times online is that there's no escaping the upsell screen after logging on.

I know this is not your point, and you should not be forced to do this, but uBlock Origin has a very nice filter which can hide DOM elements on the page if you set it up. Lifesaver with annoying webpages.

Sorry for late reply, just noticed your post.

We are talking about different threat models. I trust Google not to hack my phone, but I don't trust them not to spy on me. So yes, running a Google binary blob in privileged mode occasionally is preferred to running non-privileged Google binary blob all the time (otherwise push notifications do not work on GrapheneOS, IME).

I never used App Lounge but always F-Droid directly, or Aurora Store, so I can't comment on that.

But more importantly, you seem to confuse my rant against GrapheneOS not supporting MicroG as an endorsement of /e/OS. I know they have their set of problems, some of which you outlined. However if my goal is to limit communication of my device with Google as much as possible, then they (/LineageOS) still win. Which is a pity, I like GrapheneOS security focus otherwise, but my primary priority is degoogling my phone as much as possible (and no, it is not possible to do it completely without serious tradeoffs I am not willing to make).

High revenue and profit are not relevant - employees cost money, so if company feels it could do without them, the layoffs happen. Low revenue and loss would be another reason for layoffs too, of course.

> There is no privacy advantage by using MicroG compared to Google play services. You still connect to there service all the same giving privileged access to your device.

...assuming you are connected all the time, or at least that the services are running all the time. In my case they are not. I only enable them every once in a while, when I need to be alerted of something. This might not be how most people use their phones, but I do it because there is no way to preserve any privacy at all if you are running Google services 24/7 (sandboxed or not).

I see Google services as malicious software - not security malicious (Google can't risk that) but privacy malicious. This is why I care more about ability to turn them on / off than about what kind of access they have. Even inside the sandbox, as regular apps, they have way too much info about me.

As I said: I would prefer sandoxed MicroG, but given the available options non-sandboxed MicroG is preferable to sandboxed always-on Google services.

You are missing the point. MicroG allows me to disable it when I want to, and push notifications still work when I (rarely) need to enable it.

It's not about security, it is about privacy. While MicroG in theory could bypass NetGuard, I very much doubt that anyone would bother. My privacy is not that precious.

But as I said, neither solution is great. How about sandboxing MicroG too?

Great experiment, hilarious! It would be interesting to see how 2 separate Claudes (or GPTs, or...) would behave - would they develop similar personalities?

It's not about Stainless, it's about Anthropic.

No Google Maps or Android Auto on my phones, so I don't care much about privileged access - they have none anyway.

No, microG is definitely not talking to Google all the time, NetGuard would warn me if it did. I would assume it is not even running when I disable it (which is easily done, as opposed to stopping Google Services in GrapheneOS) - but to be fair I didn't actually validate that.

I kind of like GrapheneOS otherwise, this is by far my biggest gripe. I can even survive the icons. But avoiding Google (and other big tech) is the reason I am not on a cheaper and more convenient phone with regular Android, so if GrapheneOS refuses to support an alternative to Google Play Services, I'm not too happy about it. If there are real problems with microG then I'm sure the authors would be interested in a better solution too.

Page won't open, but archive.is has it: https://archive.is/bfPZc

That privileged plug in /e/os makes push notifications work, and you can enable just those and leave Android Auto, G Play Store and whatnot disabled. Not much privacy risk - I think?

On the other hand, while GOS is running Google services sandboxed, they are still running and have access to internet. If you try enabling them only when you need push notifications, they will break - notifications stop coming.

Neither system is optimal - can we please get microG sandboxed on GOS, pretty please?

I guess this is very similar to what happened to demo scene, in some way. The limits are what makes these problems interesting, and once we have better machines / tools, the incredible skill is no longer prerequisite, making everything less interesting for participants. Sad, but - such is life...

Of course - but I would like others to do it too. :-)

Really? IME, if you use a different session to write tests and if you plan ahead (meaning: you are the driver) you can easily cover all the cases you can think of, and then let AI suggest and implement those you missed. It us easy to fall into trap that you do not need to think though.

My main grief with AI-generated docs is that they (unless the instructions were very clear on this) by default describe the path to the current code and how it is an improvement over what was before, instead of just explaining its purpose. I see this all the time when reviewing other people's code... Fortunately it is easy to add a generic instruction to project-wide CLAUDE.md to avoid this problem, but it would be nice if this skill came out of the box.

Their app is still running all the time. I do not know what exactly it is collecting, but I'm sure it sends a lot of information to Google. Even just the fact that Google knows my IP (which is otherwise dynamically assigned) at any time is too much.

On the other hand, if you try selectively enabling and disabling the service, the push notifications stop working. LineageOS + MicroG is a much better solution if you only need them occasionally and if you prefer an app which does not actively (try to) spy on you.

Doesn't matter, it's still just $40.

Unless you want push notifications.

They didn't lose the key, they just didn't know which one is the correct one, where the lock is, and how the unlocking is done.

That's a huge misrepresentation of fair source licenses. They prevent competing with the original vendor, but still try to retain Right to Repair as much as possible, for example:

> The Fair Core License, or FCL, is a mostly-permissive non-compete Fair Source license that eventually transitions to Open Source after 2 years.

Well no, there is no need to develop domestic capability. Put laws in effect which disable foreign capabilities and which reward domestic ones, and they will be developed. No endeavor from government needed (which is a good thing, since governments are not really great at doing such stuff).

I see where (both of you) are coming from, and I'm very privacy conscious (=paranoid) myself, but in this case, as a user, I wouldn't actually mind. It seems to me you would be tracking flows instead of users, which is fine in my book. Now, including Google fonts on every page, using their tag manager, analytics, captcha... That gives me the creeps. Waaay too much information about each and every user. But generic origin query params? Yeah, ok. :shrug:

This. For privacy, it is much better to avoid Google Play services (which are the only supported solution for push notifications in GrapheneOS).

> Presumably they don’t much consider legality.

Or the operation is not even illegal where they come from?

Well yeah, and there is KDE 3 which was awesome. But for most of the projects their point stands.