• 0 Posts
  • 9 Comments
Joined 3 years ago
cake
Cake day: September 21st, 2023

help-circle
  • The scientific and social study of obesity has shown that it is a complex bodily disorder, the causes of which are multiple and varied, and may include genetic and epigenetic factors, diet and eating habits, socioeconomic status, and personal and social lifestyles.

    Wtf?

    Yes, there’s a lot involved, but excusing away obesity as genetic ignores that 99% of it is behavioural. Just look at the explosion of Type II diabetes, which is pretty much all caused by diet.

    Growing up, there were exactly 2 obese kids in our school, from first grade through 12th (across all grades). Those kids had a genetic cause to their obesity.

    Today we have a much higher rate - I’m not buying that genetics drastically changed over the last few decades.

    The elephant in the room is a combination of bullshit from governmental agencies (the lie of the food pyramid anyone?), nonsense from the medical community (fat in our diet isn’t the driver of cardiovascular disease or obesity, it’s unstable glucose, something that’s been well known since the early 90’s), pushing a high-carb diet in the 80’s, which was a lie that ran counter to what doctors advised for diabetetics since the 1930’s!






  • 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.


  • The final red flag was as that allegedly Russian authorities were messing with people’s deleted messages.

    I don’t know about “Russian authorities”, but the fact remains that if you can login anywhere and see your messages, then your public private key is stored in the server.

    Since Telegram requires authorization from an extant connection, I don’t know if that means your public key isn’t stored on the servers and it’s being sent from the authorizing device, or if that device is merely authorizing the Telegram servers to transmit that key to the new device.

    Since they have a full e2e chat feature (Private Chats), I’m going to assume the latter.

    So anyone who can get those keys can gain access to your chats.

    I still say Telegram is far superior to anything from Fuckbook/Meta, because it’s not integrated into everying you do (even those of us who’ve never once been on Facebook, and yet have ghost profiles), not to mention the Facebook app integrated into Android on many vendor phones.

    Even so, know Telegram for what it is - not ideal, just better than WhatsApp, and a step along the path to moving to more secure and privacy-respecting apps.l