For me the biggest question is: “Will these City-ran grocery stores, be able to complete with the Walmart juggernaut?”

Yes, initially the city-ran stores will be placed in “food deserts”, but if the program is to succeed it need to go toe-to-toe with Walmart. Otherwise, the program won’t be able to reach the people who need it the most.

… and based on the article you posted, I’m sure Walmart won’t take this lying down. Walmart will have no second thoughts or remorse to sacrifice their suppliers in order to compete (thus, keeping customers flocking to their store).

You have a good point… and I’ve worked on both sides of the fence. Currently, I’m at the “healthy culture” camp, but it wasn’t always that way.

While I was working at companies that had a not-so healthy culture, there were things I did to “bring visibility” to these non-work tasks. However, I should add that at these types of companies didn’t really offer a lot of financial compensation for this non-work, but at no-time did anyone challenge my productivity.

Basically, I’d suggest:

1. Be (technically) opinioned and make it visible. Often, it’s not your boss you need to impress (as they see your work every day), it’s your boss’ boss. If you have a reputation within the company as a guru in something, it’s easier for your boss’ boss to “see” that you’re bringing “value” outside of you day-to-day tasks.
2. Bring visibility to these (side quest) discussions. At one company, I created a chat room to use as a sort of “technical self-help”(for all Engineers) and any DMs I got, I would ask them to funnel the discussion into the chat room. I asked them to do it “so others can find the answers to similar questions” and more importantly “to bring visibility to these discussions”. You, your boss, your boss’ boss can see how much time you invest in these topics and they can see that this help does not come for free.
3. If your not meeting your goals (or are stressed out) , due to these side-quests - tell your boss. Explain (as early as possible) that project X will slip if you keep focusing on unblocking others and let them decide what to do. If you followed-up with Point 2, you’ve got concrete evidence to justify where your time is being spent.
4. When people ask you “what are you doing?” (like during your Stand Up). Do not answer “nothing” or “supporting others”. Be detailed, mention the actual technical topics (and if you’ve got this chat room, reminding yourself is much easier).
5. Last bit, which might not be helpful. If it’s the same questions or some fundamental misunderstandings that your often answering: maybe offer a Dogo/training for anyone who’s interested. When you offer it, shout it from the highest tree top - it’ll go far in establishing yourself, in the company’s eyes, as a guru (even to those who don’t understand the topic) and it’ll (helpfully) reduce the amount of questions in that topic.

But from the companies perspective this is a net-gain.

You’ve just unblocked 10 people so they can continue to work… and even if their weekly individual productivity is 25% of yours, combined they’re doing more than twice the amount of work you’re doing and it only cost the company a week of your time.

Yeah, at times it’s frustrating and distracting, but hopefully you’re getting compensated for the knowledge you bring inaddition to the work you deliver.

Cloudflare provides 10 GB of free (forever) S3 compatible storage too.

Oh, I know the answer to this one: superbad.com (suitable for work).

OP, what bluGill said is exactly your problem (assuming your DMARC and friends are setup correctly).

The concept is referred to as “email (or domain) reputation”. The implementation details are closely guarded secrets, unique for each email receiver.

One of the metrics for establishing a positive email reputation the “How much email does your mail server sends?” : the more the better**

If you’re a large company, it’s fine… but if it’s just a personal domain with < 20 per week, you’re not going to establish a reputation and (depending on the receiver) you’re email might just get dropped.

The other (frequent) metric is: “Of the emails that are sent, how many are read, and how many are flagged as spam?” In order, for these crowd sourced spam filters to work, they need you to send large amounts of email. Receivers like Gmail/Google are pretty forgiving. However, Outlook/Microsoft are very aggressive, meaning if enough outlook users flag your email as Spam, then future emails sent to outlook from your domain will probably automatically be marked as spam. Obviously, these are all black boxes, so I can only offer my personal observations (take it worth a grain of salt).

As bluGill mentioned, there is a solution, but it involves moving your custom domain to a larger (re: paid) email provider. If you were to move to Google (for example), it doesn’t matter if your custom domain sends 5 emails per week. Those 5 emails are being sent from Google mail servers (using your custom domain) , which means they’re gaining the “reputation” of google and you can be certain that your emails will arrive, even if it’s (non-obvious) spam. Because, the email receiver assumes that Google will shut you down, if you’re a spammer.

It’s a sad state that one of the original “pillars of the internet” (email) has degraded to feed only the big tech companies… but unfortunately this has been the case for many years.

Thank you for finding that.

I got lucky, I bought a quest around July/August and needed to do the mandatory/initial OS install.

I ended up with v78 (August 3, 2025) release.

I didn’t realize there was a WiP announced in July 2025.

… makes the latest headset with a rather recent update (but NOT the very last ones, so be cautious!) rootable.

Any ideas which version(s) are susceptible? I couldn’t find it mentioned.

Actually, those steps are the ones necessary to recover from a hard brick (re: the device is unusable because you did something you shouldn’t have as root).

The actual process to root the device is simply running a few adb commands (so a prereq is having Developer Mode enabled).

Once you have ran the exploit, your root escalation is temporary until the device is rebooted or you take additional steps to persists your root privileges (thus, potentially leading you towards a hard brick).

source: The docs