somehnacct3757

If you're at a BYO party, bring some silly drink you never had before. Never had orangina? bring some to the party. try that CBD seltzer, etc. there's dozens of kitch drinks in every corner store.

At home, stop restocking. work thru your liquor cabinet, even the stuff you don't normally drink.

lastly, find other substitutes. night on the couch, you want a beer? get into herbal teas. make a bag of popcorn. there's so many fun treats out there.

If you are offered a shot or other social situation, don't beat yourself up for saying yes. the goal isn't to be perfect it's to replace most situations with an alternative.

I know I'm right, as I'm now sure the devs telling me no were right, but I'll be pushed out same as they were.

Young blood is naive and cheap and plentiful so they will always have the momentum advantage. They're the ones that promise the moon to other departments and then stay up all night covering their tracks when they were wrong.

Tweets are microblogs. RSS technology is fine for publishing them. The Twitter client only needs to be an RSS reader. Replies, retweets, and likes are empty calories for end users. They're the engagement bait social media uses to power an attention economy.

The fediverse copied the wrong features. There's no point for it to have an attention economy because no one is monetizing the attention. Therefore there's no need for the empty calorie features, and no need for my data to be on someone else's server.

Also why does this random guy have MY data? Why does he need to trust a new admin with my data for a succession plan to be possible?

I don't worry about any of this with my RSS feed. Mastodon federated at the wrong granularity.

From a computer's perspective there is only one sudoku puzzle. Writing a sudoku solver is a college level weekend exercise

The big bang rewrite of your brain isn't a possibility just like it isn't one for codebases. Viewing the riddle this way will let you put the fun part of your profession in the driver's seat. What will you change to make the 'impossible' possible?

It's less flavorful than cow meat as a burger patty, and it's enough of the flavor profile to notice.

I'm bullish on these products becoming the default restaurant vegetarian option, topping the last generation of plant-based burger brands. And for them to find success in less meat-forward recipes. I'm bearish on there being some sort of cultural or ethical revolution. That won't happen until it's cheaper than meat.

Now we are figuring out the right way to flip the switch. You get stuck in the long review queue every time you flip manifest versions, cuz your permissions list has likely changed.

Google's rollout has been the absolute worst; but hey, as you say, everyone who can't eat a bowl of shit and keep on smiling will simply disappear from the competitive landscape.

This change alone has caused me to reconsider a future on Windows. Who are they building this thing for? OS X already has a better developer story and SteamOS is nearing its inflection point for gaming. What is Windows good at? Having momentum?

Having a tight release loop is a good strategy. You will find mechanics that work over time and iterate on them, finding more and more reliable success. Eventually one will hit. You don't even have to avoid looking like shovelware. The mobile game audience doesn't care about that, it's more of a capital G Gamer gatekeeper thing.

Asking things to draw themselves is fun, I could just as easily ask an elephant holding a paint brush to paint itself and then enjoy the outcome. That's pretty much all there is to it.

I left out the bit how DALL-E also thinks maybe it's a honey badger, or a lemur with all black eyes, or some sort of sharp wood demon.

The blue one is the one that haunts me because it seems to be the most plausible

DALL-E itself was Clippy-like, blue, and bean shaped with eyes and mouth more expressive than a Zuckerberg VR avatar.

As for the family? There was none. DALL-E rendered itself on a pure black background

If the lack of a DOM doesn't do it, the extremely spartan service worker environment will take it out. Did they use XHR? SW only supports fetch. Did they use the window global? Don't have one of those either.

It's the stone ages right now. If you want to integrate with a third party in MV3 you are building a fetch wrapper around their raw HTTP API. Google thinks this is production ready

I sort of like the idea of UBO Minus, regardless of whether they do a full MV3 version of UBO later. It's more private than UBO could ever be. If it's enough, it's actually quite a nice extension.

Methinks a competitor ad blocker leaning into MV3 and claiming the 'first MV3 ad blocker' title last week was a glass of cold water for UBO devs. MV3 is happening, and usershare is at risk.

But, in addition to all that, I also think the main objective of MV3 is to hamstring ad blockers. Very very elegantly hamstring ad blockers.

The company was pretty bitter about it and switched vendors, and the CEO would often bad-mouth the vendor at speaking events with other small company teams.

Nobody was really nasty to the former colleague, although there was some light shade thrown their way as well.

You don't mention company size but if these are boutique shops or startups with sub 20 employees, and you aren't a role they regularly hire for, expect reputational damage to your new employer, you, or both in whatever sphere of influence your former employer has.

Instead, go read a full review written by a trusted curator.

I'd really like to see a rigorous calculation and explanation behind the decisions, because I think this could be a useful stat for comparing states' fiscal success relative to one another.

For example should the calculations include federal spend on federal employees? It's not really a reflection of the state's actions if the federal government happens to have a big agency headquarters there inflating the 'federal spend'.

When does this work?

It only happened once ever. But I just keep on checking.

The extension developer could add a malicious permission + new code to exploit it and it would look the same as using developer mode to add a Hello World extension

They left alone other imperative-but-dangerous aspects of extensions, such as the ability for any extension to watch what you type into password or credit card fields on any website. Actually that sort of extension is even easier to write in MV3 and Google will still need JS-reviewing wizards to give a guarantee an extension isn't snooping your passwords.

I don't think there's a consistent position from Google if the claim is they want to improve security via declarative syntax. I think Google is full of shit.

If you could implement a declarative language as powerful as an imperative one you could solve the halting problem.

So the switch from imperative to declarative is not free to make and Google has thrown the baby out with the bathwater. They just so happen to lose money every second that baby is alive. On the one hand, the decision to implement this specific declarative language is a malicious exertion of market force. On the other hand it's a stunning display of implementation incompetence. The language can't even reimplement the most popular existing extensions.

What's different is the classical permissions. Previously you could use the webRequest permission to execute custom JS functions in response to network activity. In MV3 you must now write a declarative rule instead using the declarativeNetRequest permission. By moving from an imperitive model to a declarative one, Google now has exacting control over what ad blockers can and can't do.

Gorhill's argument is that the stated reasons for MV3 do not align with the implementation. The example he gives is that Google claims the new API is more private. However you still need <all_urls> so the extension is as un-private as its MV2 equivalent. The only difference is that now Google controls what blocking you're allowed to declare and how much of it you're allowed to do.

There's a similar community discovery where MV3 implementation is provably counter to Google's claims of performance enhancement - MV3 extensions need to rehydrate state every 5 minutes as Chrome shuts down their service worker and for highly active extensions such as ad blockers this is actually less performant than the MV2 implementation with a long-lived background.

Basically, Google is full of shit.

Google makes no money off the Chrome Web Store and their initial attempts to restrict MV2 failed. The goal was for automated approval to suffice. Still, there was certain APIs that required human review.

Google could have continued restricting MV2 until they didn't need human review but they must have got the idea for MV3 at that point. They could also hamstring ad blockers and get some promo packet material.