For anyone who seems uninterested, ask if they’d like to be arrested for murder simply because they biked past a place every day.

For anyone looking for great talking points about this issue, I highly recommend “Taking Control of Your Personal Data” by prof. Jennifer Golbeck, published by The Teaching Company, ISBN:978-1629978390, likely available at your local library as a DVD or streaming.

You apparently forget he said Twitter needed major before he bought it.

It’s by design. 🤦🏼‍♂️

Right.

And a football team doesn’t need a quarterback.

🤦🏼‍♂️

Yes, many of them are assholes, doesn’t change the need for the leadership.

Great writeup, I really appreciate it, especially the point about locking the bootloader and isolation - it’s all about the threat model of a user.

It’s annoying, frustrating, and most of all, disappointing that we get just noise between these projects, rather than mutual respect with clarification of the differences, and the different use-cases, for them. Instead we get adversarialism because some people think only their way is the right way (such as this post).

I run Lineage on a couple devices that can’t get any thing else. Some people on the Graphene side would (and have) chastised me for running an “insecure” rom. Well, I know my risks, and the value I get from this device, and I mitigate my risks through layered security (as all risks are) - I’m addressing my threat model.

The issue with the Graphene team is they have the stereotypical, arrogant, condescending attitude of tech people.

I’ve been that tech person at one time in my career, and got it trained out of me by good leadership decades ago.

The crap they’ve said, to me (not something I heard second hand), while asking for help was such a major turn off (and in my help desk career would’ve had them in for re-training), that I gave up on using Graphene. Their attitude was looking for ways to blame me instead of trying to determine why things were misbehaving.

What if I had a true, difficult issue later, this is what I’d have to deal with? I had dismissed the reports I’d read about the team, until I experienced it first hand.

So no thanks. Graphene is dead to me now…I will never… Let me repeat that NEVER use or recommend the system to anyone, unless the team changes. And that’s a damn shame, because I really wanted to use it on my phones going forward, and even bought Pixels specifically to use Graphene.

Change Windows. You can’t take shit down during the work day.

Everywhere I’ve worked (many very large companies, banks, telecom, outsourced IT, etc) teams have coverage schedules, so I suspect this article is misleading.

Someone has to mind things 24/7, this is done via scheduling.

And the more critical you are, the more on-call you are. I had one role where I was on call 24/7. Things rarely broke enough for me to be called, but I never once resented when I was called. I’d rather get woken up at 2am because my help is needed than have the risk that our systems aren’t ready for the day.

I looked at storj.io a while back, prices seemed good.