Shorts are treated as a privileged feature; they aren't going to simply hide them just because a few of us have the unmitigated gall not to watch them. That's not to their benefit. Youtube and the other platforms want to manipulate users into getting on that particular hamster wheel, and the app's UX reflects that. In that, it's not dissimilar to how streaming services routinely prioritize engagement maximization over user experience. If it takes you a few more clicks to find your continue watching list, that's your problem.
I'd be surprised if the algorithms have much say on when and where shorts show up in your feed versus just inserting them into specific spots in your feed that were determined by a whole lot of user testing to see what's most effective. There might be some logic to tweak it, but overall placement is probably fairly uniform across users.
I would expect (but cannot prove) that these hostile patterns decrease engagement on the individual level.
But maybe the effort to cater to people who avoid this stuff isn't worth it, or maybe they find it doesn't really discourage us from finding what we want, or the value of this stuff is so high that they find a sufficient number of converts over time.
If it's a strategic play, it's a terrible one that douses usability in gasoline and sacrifices it at the altar of visual novelty for no real gain. Apple has spent literal decades working on and refining their Human Interface Guidelines for different devices. Between Tahoe and Liquid Glass, they seem to have just tossed them on the bonfire for no justifiable reason.
VisionPro was meant to literally overlay its interface over your field of vision. That's a very different context and interaction paradigm. Trying to shoehorn the adaptations they made for it into their other, far more popular interfaces for the sake of consistency? It's absurd.
> Apple has spent literal decades working on and refining their Human Interface Guidelines for different devices
Things like “human interface guidelines” get written by nerds who dive deep into user studies to make graphs about how target size correlates to error rate when clicking an item on screen.
Things like Liquid Glass get designed by people who salivate over a button rendering a shader backed gradient while muttering to themselves “did I cook bro???”
They’re just two very orthogonal cultures. The latter is what passes for interface design in software these days.
It's like the KDE developer who reluctantly gave out the script to set "border offset" from a window back to 0 (i.e. how close you could snap/drag the window to the border of the screen). He had defaulted it to something like -5 (i.e. at minimum, 5 pixels between the edge of the screen and the window, no matter WHERE you tried to place it), because "otherwise, how would you use the negative space, bro?". I.e. left-clicking JUST outside the window brought up a context menu for the window. WTF? I've been doing GUIs since 1987. Don't make "clicking outside the window" a way to interact WITH the window. I very nearly threw KDE out before he gave the fix.
No, no, no! Stop that! The em dash is an wonderful little punctuation mark that's damned useful when used with purpose. You can't turn it into some scarlet glyph just because normal people finally noticed they exist. LLMs use them because we used them, damn it.
For god's sake, are we supposed to go back to the dark ages of the double hyphen like typographic barbarians in the hopes that a future update won't ruin that, too? After all the work to get text editors to automatically substitute them in the first place?
What's funny is that, when people first started noticing that LLMs tended to like the em dash, I'd mentioned to a friend that I hoped—rather naively—it might lead to a resurgence and people would think to themselves "huh, that looks pretty useful." Needless to say, I got that one wrong. Are we really going to sacrifice the poor em dash just because people can't come up with a better signifier for LLM text?
Oh, no thanks. The emdash is lazy writing, through and through, for the same reason a parenthetical expressed any other way might be. LLMs overuse them the same way humans do: to pack in context where it doesn't belong. I'd happily lay the emdash and all its terrible cousins upon the sacrificial altar to see a renaissance in editing and proper sentence construction.
Fair enough. I fully recognize just how easily it gets abused, and "used with purpose" is doing a lot of heavy lifting in my original comment. That said, if someone's going to engage in sentence sprawl, I'd much rather an em dash get abused in the process than some of the alternatives. Bad em dashes are at least less ambiguous than a chain of a commas mashing meaning into mush, and they provide an obvious visual break that jumps out at the reader.
Em dashes are strong; they can take the abuse. While I'm right there with you on dreaming of a renaissance in quality writing, that's likely more fantastical than my own hopes that we'd see a resurgence in quality em dash usage. At this point, I'd probably settle for outright stagnation in writing ability.
I’ve never seen an LLM use an em-dash the way a thoughtful human is most likely to use them, in a parentheses-like pair. It’s just too bad there’s way too many idiots who cannot notice such subtleties.
I first learned about em dash reading the GNU Texinfo manual in the 1990s. Now I have to wear a red, slightly long horizontal line on my shirt, and passersby shun me.
These questions are almost always more complex and nuanced than simply left or right. I agree with you on the second part to a degree—insomuch as the modern media landscape pushes people to quickly label shooters and tends to disincentivize any sort of nuance—but might you be doing the same here?
The charging document[0] said that his mother claimed "that over the last year or so, Robinson had become more political and had started to lean more to the left – becoming more pro-gay and trans-rights oriented." There's also a text message he sent, which said "since trump got into office [my dad] has been pretty diehard maga." That's it. Acquaintances said "he wasn't too fond of Trump or Charlie [Kirk]," but we still haven't seen much that explains the specifics of why beyond the gay and trans rights angle. A former high school classmate said "[w]hen I knew him and his family, they were like diehard Trump" and that he was politically conservative and supported Trump "ahead of the 2020 election."[1]
As for what changed and why, we don't know. Did he stop supporting Trump because of gay and trans rights? Did he still believe in other conservative ideas? Simply labeling him as a leftist implies a cohesive ideology, but ideology is rarely so simple or straightforward even for normal people who don't decide to commit political assassinations.
Beyond that, a lot of even ideologically-motivated shooters have some awfully peculiar and non-cohesive ideologies. If the suspect agrees with 80% of a particular tribe's most common views, but that last 20% consists of some truly batshit ideas that have very little if any support, are they still a member of that tribe? Would that tribe even want them? Would they themselves want to be part of that tribe? Plenty of conservatives who believed fully in the movement's ideas broke with Trump in 2016 solely on the basis of his personal character.
They can also grab onto ideas from other tribes, to the point where investigators wind up crawling through something that's less a cohesive political ideology and more a smorgasbord of ideas they pinned together. I mean, hell, you've got to have a screw or two loose to think a political assassination is going to somehow lessen--let alone stop--anti-gay and/or anti-trans sentiment. Run that idea past pretty much any left-leaning politician, activist, or political junkie, and they'll tell you you're a moron, likely right before giving the FBI a call.
If you dont believe even his mother, theres tons of other evidence. The anti fascism messaging on his bullets. The text messages to his partner saying a Kirk was full of hate.
> I mean, hell, you've got to have a screw or two loose to think a political assassination is going to somehow lessen--let alone stop--anti-gay and/or anti-trans sentiment. Run that idea past pretty much any left-leaning politician, activist, or political junkie, and they'll tell you you're a moron, likely right before giving the FBI a call.
Straight cope and Im pretty sure I dont need to say why.
> If you dont believe even his mother, theres tons of other evidence. The anti fascism messaging on his bullets. The text messages to his partner saying a Kirk was full of hate.
Sigh. That's not what I claimed. I can accept his mother's limited statement from the charging document at face value, and still point out that we still know very little about his ideological leanings. Why did she consider him moving left? Was it just because of gay rights? Did his other views shift as well? Was the shooter's motivation more about the political side of things, or some misplaced idea that they were somehow protecting or helping their partner?
I have no clue, but I want answers to these questions if only because they can contribute to the effort of better understanding radicalization pathways and the process by which some random kid decided to commit an act of political violence.
We know that shooters rarely have cohesive, logical ideologies. The fact that a shooter decides to become a shooter in the first place is evidence that their personal ideology has shifted in some truly extreme ways that puts them--or should put them--outside the normal political discourse. Put another way, radicalization can take people to some truly unexpected places and it's entirely reasonable to want a nuanced view before jumping to affix labels because while labels can help us understand some things, they can also obscure other aspects and create entirely separate problems. Especially when those labels then get for partisan purposes and to undermine the political discourse.
As for the casings? We've got memes and video game references.[0] The most overtly political parts are "hey fascist, CATCH" with a video game code thrown in for good measure and an 19th century folksong that later became an anti-Mussolini resistance anthem. The others are memes. Do they all have meaning for the shooter? Obviously, since he went through the effort to engrave the casings. At the same time, their immaturity and oddness should be pointed out as well, as they undermine the idea that this was some sort of rational consequence of a cohesive political ideology.
> Straight cope and Im pretty sure I dont need to say why.
Perhaps you should re-read the sentence before trying to read something into it that wasn't present? My point was simple: even setting aside the ethical aspects of the question (simple answer: outside of baby Hitler hypotheticals, it's bad--and even with Baby Hitler, most people will acknowledge they're trying to leverage his future actions to make literal baby murder pencil out because they recognize that baby murder is a prima facie immoral act), political assassination is an insanely stupid means to shift public opinion and pretty much any politician, activist, or advisor--whether on the right or left--will tell you the same thing. Feel free to substitute right-leaning for left-leaning in my original comment if "left-leaning" made the sentence read as something I hadn't intended. I certainly didn't intend to suggest that somehow only left-leaning folks are capable of recognizing that political assassination is a very bad idea with tons of unintended consequences. Anyone with even a basic grasp on history is more than capable of knowing how dumb it is.
Hell, we've got literal case studies showing how political assassinations tend to blow up in everyone's face. The CIA has a list of coups and political assassinations that pretty much all resulted in serious blowback that undermined their intended outcomes--and often resulted in the very thing they wanted to prevent.
So, yeah, I think that if the shooter shopped the idea that murdering Charlie Kirk would somehow magically make things better for gay or trans people to gay and trans advocacy groups--or influential figures on the left more broadly--they'd almost unanimously tell him he's a moron and notify the FBI even if they thought Kirk was a pox on American political discourse. It's an insane proposition, and only in the mind of someone who has serious problems would it somehow make sense.
I also think that the reverse situation--where the shooter wanted to benefit some conservative constituency or ideology by murdering a liberal political activist and shopped the idea around conservative politicians and activists--would likely result in the same call to the FBI.
> Was the shooter's motivation more about the political side of things, or some misplaced idea that they were somehow protecting or helping their partner?
I respect the effort you are putting in, but you are answering a question that was not part of this thread: what was his motivation.
The question in this thread was somewhat simpler: was he on the left?
Because the context of this discussion was the twitter thread where people and bots were en masse assigning MAGA affiliation to killers, just like they did in the Charlie Kirk situation.
And the answer is unequivocal: Robinson was not MAGA or groyper, he was on the left.
The problem with using modern pressure treated wood for outdoor furniture is less any cancer risks like with the old CCA treatments, and more that it's just a bad choice for a bunch of different reasons.
Modern copper-based treatments--e.g. ACQ or CA--still cause skin and eye irritation. If you try to sand it so that people sitting in your new chair don't get a nasty splinter somewhere best avoided, you can compromise the effectiveness of the treatment (even when the treatment gets full penetration, it's still most effective on the outer layers you're now sanding away). Plus, while the dust you create when working with it might not include arsenic, it's still nasty to breathe in and can cause respiratory problems. Staining P/T wood can be a whole ordeal in itself, and because interact much more closely with furniture than say a deck, any imperfections will be more noticeable.
Even then, it's not like P/T furniture isn't going to require ongoing maintenance in the future. At which point, you're better off with something like cedar or white oak. Hell, with a decent outdoor grade finish and proper care, even untreated pine is going to last for years without rotting away underneath you.
With a product this simple to make and prices of wood and finishing chemicals what they are I don't know if I'd even bother with finishing, but just remake.
Basic weatherproofing treatments for basic lumber ? There's tar, which nobody does at home. There's wood oil. What else is there ? Do I have other options ?
- My outdoor furniture use a wood oil plus polyutherane.
- My indoor furniture use just wood oil.
But that’s only in general. There are other considerations like impact resistance and spills that can stain the wood so you have to decide what combination of wood type and treatments work for your goal.
"wood oil plus polyurethane" sounds interesting. NSo you've had no problems with the two reacting badly to each other ? I'll be drilling screws in, so maybe the wood oil adds extra protection where screws penetrate the polyurethane layer.
I realize it's just another hair-brained scheme likely cooked up on the porcelain throne, but part of me is curious about how exactly they'd implement this train wreck.
Since Trump is relying on declarations of national emergencies for his tariffs, there's the question whether it's even legal given that Berman Amendments to the IEEPA[0] explicitly exempt "informational materials, including but not limited to, publications, *films*, posters, phonograph records, photographs, microfilms, microfiche, tapes, compact disks, CD ROMs, artworks, and news wire feeds" from the President's authority under IEEPA.[1]
Even if we set that aside and ignore the likely legal challenges, how would you actually implement them? It's not like a movie or TV episode "produced" overseas gets transmitted into the US each time somebody wants to watch it. It's a digital file, and you're really only sending it once. So when do you tariff the damn thing, how do you manage to actually do it since there's not exactly a literal port of entry for the internet, and what exactly do you value it at? The system isn't built to track and tariff info being uploaded to random servers, and making it work would require all sorts of new law.
Plus, what's the legal definition of "production" he wants to use? What constitutes foreign production? Can some of the producing just be done remotely? What if raw footage is uploaded instead and then it's edited here? Or a nearly finished copy that just needs something minor done to be considered ready? Hollywood accountants are in a league of their own. Put them in a room with lawyers and accountants whose focus is the creative eccentricities of tariff engineering--hello, chicken tax people[0]--and I shudder to imagine what they'd get up to.
We're only a few months in at this point, and I feel like I'm losing my mind.
I think the issue is less the cost to developers and more the cost to users. Were there more users, no doubt a larger number of indie developers would be able to justify the expense. Without those users--or at least a reliable promise of those users in the near future--it's tough to justify even dipping your toes into it. It's a chicken and egg problem that's fundamentally tied to cost as well as hardware limitations. Discomfort from the bulk and weight was my biggest sticking point even before the price, for example.
Plus, the hardware is just the initial starting point. Your initial outlay will quickly be eclipsed by the dev hours spent working on Vision versions of your app(s), and that's when the opportunity costs become particularly noticeable. Time spent on a Vision app that may have no real market for years is time you could be spending adding features, testing changes, fixing bugs, marketing, etc. Skipping on Vision Pro is really a no-brainer for most indie developers, at least for the foreseeable future.
Yes. That was my original point, just above the head of the branch where you responded. Could I have been more concise or more clear? Serious question, I am mildly retooling my prose style of late.
Ah, sorry about that. Any lack of clarity is on me; I had walked away for a bit before responding and ended up flattening the branch in my head by the time I started typing. You're fine :).
This is a bit longer than I would have wanted to spend writing about Adobe billing practices, but oh well.
Is it the most manipulative dark pattern in e-commerce? Hardly--there are plenty far more vicious--but it's still an attempt to prime a would-be subscriber to focus on the annual, billed monthly and play on their understanding of the word "monthly" by using it in both options.
"Annual, billed monthly" is set in smaller italicized type right under the actual price of US$59.99/mo on the main pricing page[0]. You've now been primed to focus on the $59.99 price. Only when you select a plan and a modal pops up do you see that there's a separate monthly option available from the annual, billed monthly option that's been helpfully pre-selected or a third annual, prepaid option.
The point is to quickly shepherd subscribers through the payment process. The user sees the $59.99 option they expected is pre-selected, so most hit continue and move on. If they look beyond the price in bold to the plan descriptions in smaller italics, well, there are literally decades of eye tracking studies showing users skim websites rather than carefully reading every single word. The price in bold draws in the eye, the word "monthly" is present so the user catches the word, and then they move on to the continue button.
Adobe could have easily labeled the plan Annual, billed in 12 installments or even Annual, billed in monthly installments to better differentiate the two options. They didn't for a reason. The word "monthly" comes with certain expectations. Using it for both the actual monthly plan and the default annual, billed monthly plan allows those expectations to bleed over to both.
While it mentions a fee for cancelling after 14 days, you'll find nary a mention of what that fee actually is until you track down a legal page[1] that isn't linked to any point during the payment process up until the sign-in prompt (I didn't bother creating a new account to look beyond that). At the very least, it's not present during the stage when you're still relatively uncommitted and somewhat more likely to notice any more onerous terms were they present.
Finally, there's an option for a 30-day free trial of Adobe Stock. I'd have sworn it was pre-selected a few years ago, but I may be mistaken on that. If it was, then at least that's a change for the better. Anyhow, did you notice how it's on a 30 day trial period whereas the normal plan has a 14 day cancellation window? Let those deadlines fall to the back of your mind for a week or two, and will you remember which is 14 days and which is 30? There was no reason why Adobe had to use 30 days for Stock or only 14 days for their other offerings. But it adds to the confusion, and that's the entire purpose of a dark pattern. Stock is also an "annual, billed monthly plan," but nowhere in the checkout process is it mentioned that Stock also has a large cancellation fee. That's hidden in a separate part of the Subscription Terms page.[1]
Adobe could easily just choose to settle for a straight-up monthly payment plan with no bullshit and completely sidestep recurring--but largely toothless, given the state of most alternatives to their software--criticism over their billing practices. They could eliminate the dark patterns and make their plan selection and payment process more transparent. They don't, presumably because those patterns generate more revenue than the lost goodwill they create is worth. That goodwill is diffused, and even if people grumble about it online, it generally doesn't rise to the level of leaving.
>but it's still an attempt to prime a would-be subscriber to focus on the annual, billed monthly and play on their understanding of the word "monthly" by using it in both options.
Do you think "$500 biweekly" car ads, or "$2000/month" apartment rentals are the same?
>"Annual, billed monthly" is set in smaller italicized type right under the actual price of US$59.99/mo on the main pricing page[0].
I might be sympathetic to this reasoning if this was a $2 coffee or something, but $60/month is nothing to be sneezed at, and I'd expect buyers to read the very legible text under the price tag. Otherwise, this makes as much sense as complaining about supermarket price tags that show "$4" in huge font, and "/lb" in small font, claiming that it misled buyers into thinking an entire package of ground beef costs $4, because the $4 price tag "primed" them or whatever.
>While it mentions a fee for cancelling after 14 days, you'll find nary a mention of what that fee actually is until you track down a legal page[1] that isn't linked to any point during the payment process up until the sign-in prompt (I didn't bother creating a new account to look beyond that). At the very least, it's not present during the stage when you're still relatively uncommitted and somewhat more likely to notice any more onerous terms were they present.
Okay but if you read most complaints, it's clear that they're not even aware that such early termination fee even existed. There's approximately zero people who were aware the termination fee existed, found it too hard to figure out what it actually was, but somehow still went with the "Annual, billed monthly" option.
>Finally, there's an option for a 30-day free trial of Adobe Stock. I'd have sworn it was pre-selected a few years ago, but I may be mistaken on that. If it was, then at least that's a change for the better. Anyhow, did you notice how it's on a 30 day trial period whereas the normal plan has a 14 day cancellation window? Let those deadlines fall to the back of your mind for a week or two, and will you remember which is 14 days and which is 30? There was no reason why Adobe had to use 30 days for Stock or only 14 days for their other offerings. But it adds to the confusion, and that's the entire purpose of a dark pattern. Stock is also an "annual, billed monthly plan," but nowhere in the checkout process is it mentioned that Stock also has a large cancellation fee. That's hidden in a separate part of the Subscription Terms page.[1]
This feels like grasping at straws. If we're going to invoke "people might get two numbers confused with each other", we might as well also invoke "people can't calculate dates properly, and therefore a 14 day cancellation window is misleading because they think 14 days = 2 weeks, and set up a cancellation reminder for the same day of the week 2 weeks afterwards, not realizing that would be just over 14 days and thus outside the window".
It isn't grasping at straws because confusing or misleading people is literally how dark patterns work.
> Do you think "$500 biweekly" car ads, or "$2000/month" apartment rentals are the same?
The rentals make it very clear what the contract period is and what the penalty for breaking early is. Those terms are also tightly regulated in most jurisdictions for exactly the reason that they are prone to abuse.
> I'd expect buyers to read the very legible text under the price tag.
Given that the text fails to provide details about the fee is this even a valid contract to begin with? On multiple levels there's clearly been no meeting of the minds.
> if you read most complaints, it's clear that they're not even aware that such early termination fee even existed.
Isn't that a strong case that it's an unfair practice?
>The rentals make it very clear what the contract period is and what the penalty for breaking early is.
On the billboard or in the multi-page rental agreement that they send for you to sign? How is this different from than the ToS/fine print on adobe's site?
>Given that the text fails to provide details about the fee is this even a valid contract to begin with?
It's probably buried in the fine print somewhere, which courts have generally held to be enforceable.
>Isn't that a strong case that it's an unfair practice?
No, the legal standard is "reasonable person", not whether there's enough people bamboozled by it to raise a ruckus on reddit or whatever.
I can only speak for myself here but I have never had an interaction with a new (to me) landlord where I was later surprised to discover what the rental period or early termination penalty was. Every one of them has gone out of their way to verbally specify the length of the term in addition to requiring me to initial it on the contract.
I have had plenty of other issues with borderline dishonest landlords but mutually understanding what was being agreed to up front was never one of them. The issues generally came later when they tried to get out of or add additional things without my consent.
> It's probably buried in the fine print somewhere, which courts have generally held to be enforceable.
People elsewhere in this comment section reported that they checked and claimed that it is not found anywhere directly linked from the sales page. You generally have to specify the terms of a contract up front, before it is signed.
> No, the legal standard is "reasonable person"
It isn't conclusive, but I think it makes for a strong case. The more people who are confused by it the stronger your argument that it is confusing to a "reasonable person" becomes.
> I might be sympathetic to this reasoning if this was a $2 coffee or something, but $60/month is nothing to be sneezed at, and I'd expect buyers to read the very legible text under the price tag.
In some things, expectations are made to be disappointed. This is one of those.
We know that people use all sorts of cognitive shortcuts to make processing their environments easier. It doesn't matter if you're smart, dumb, foolish, or perfectly average. It's just how our brains have evolved to function, and companies have been consulting with industrial and organizational psychologists for decades to help them optimize their marketing and business strategies to maximize the chances that those shortcuts play out in a way that breaks in their favor. Before I/O psychologists, companies tried to do the same by guess and trial and error...and they stumbled upon lots of strategies that were later confirmed by psychological experiments.
Cereal boxes marketed to children have cartoon characters whose eyes are drawn looking down so as to appear as if they're making eye contact with kids walking down the cereal aisle.[0] There are all sorts of "tricks" commonly used by salespeople selling things to sophisticated buyers who are capable of recognize them for what they are. Why did pharma reps take doctors to dinner and give them cheap pens and swag? Or consider the success of psychological pricing[1] and how those strategies somehow manage to be successful despite it being commonly accepted wisdom that odd prices (i.e. $1.99 instead of $2) is a marketing gimmick. We know it's a gimmick, and yet, it still has an impact on our buying behavior.
Yes, the text is there below it, but the whole point of a dark pattern is to manipulate a large enough percentage of buyers/users in a way that generates more revenue than is lost due to any frustration or annoyance created by the same patterns. Most people skim through websites, pluck out key words, and continue on. We can bemoan people for not reading the fine print, but that's not going to change the behavior.
As for the beef metaphor, per unit pricing can absolutely be used to trip up would-be buyers into buying a bit more than they planned. Not because the foolish shoppers don't know any better, but because mixed units usually require a bit more cognitive engagement. Grocery stores absolutely recognize that and benefit from it. On the other hand, you can't really sell beef in a way other than by weight, so it's the opportunity for abuse is much more limited.
> Okay but if you read most complaints, it's clear that they're not even aware that such early termination fee even existed. There's approximately zero people who were aware the termination fee existed, found it too hard to figure out what it actually was, but somehow still went with the "Annual, billed monthly" option.
Sure, because Adobe purposely hides information about the fee. That's one of the dark pattern at play. In the absence of that information, users will insert their own expectations to create meaning. If there's a fee, we'd expect it's probably a reasonable one (even if we have countless examples in our lives of how fees can be anything but reasonable). Does half the annual cost of a subscription seem reasonable to most people? Would that be most people's first guess? Probably not. I might not have been clear about this in my original comment, but there are multiple dark patterns at work here.
> This feels like grasping at straws. If we're going to invoke "people might get two numbers confused with each other",[...]
That particular dark pattern is less about people confusing two different numbers with each other when they're directly in front of them, so much as it is about giving you two different numbers to remember two weeks after you've made your decision and gone on with your life. Literally nobody on the planet is going to keep the free trial or cancellation period as a mental priority over the course of two weeks, so it becomes little more than a random thought at the back of your mind. At best, you might jot it down or set aside the receipt until closer to the deadline. The pattern's purpose is that, if you think of the cancellation/trial periods at all, the numbers will be easily conflated. Think about the times in your life when you've asked yourself something like did I see/do/hear [insert thing] last Monday or was it Tuesday? and weren't quite confident in your answer.
Dark patterns doesn't have to trip up all subscribers or even most of them. But if it trips up a some of them, well, Adobe isn't going to complain about the opportunity. Multiple, more subtle dark patterns together can work just as effectively as one particularly vicious one. They can even be preferable, in that they won't piss off your customers nearly as much, either on their own or as a whole.
A bit of common sense and understanding would go a long way to eliminating half the complaints you hear about HOAs.
If you know the tree is going to immediately start dying, you're just going to find the cheapest, least healthy sapling at the nursery. Had they let you wait until the tree is more likely to survive, there's a better chance you'd be willing to spend a bit more to buy an older/larger sapling that'll look better and provide more shade from the start. Plus, the temporary tree slowly dying would probably be less visually appealing than an empty spot for a few months.
There are reasons why we plant street trees: improved aesthetics, increased home value, shade along the street and sidewalks, traffic calming effects, etc. By ignoring the reason behind them and just focusing on checking the box, your HOA was just begging for some malicious compliance that undermined the benefits of the replacement tree.
I'd expect the original agreements that were put in place--both the ones with the subcontractors as well as the purchase agreements--are quite strict on what you can do with the plane. Trying to reverse engineer software (the policy was that no one gets access to the original source code for the F-35[0], at least back in 2009) is probably a no-go under those agreements.
The original article suggests that Ukraine may end up having to replace the electronic countermeasures hardware to get around this in the future, so I'd expect any attempts to "un-brick"/work around the lack of support will eventually be along those lines, even if it results in some performance degradation.
No matter how they approach this, it's going to be a horrifically difficult and expensive task.
> Trying to reverse engineer software (the policy was that no one gets access to the original source code for the F-35[0], at least back in 2009) is probably a no-go under those agreements.
the UK made access to the source code a condition of purchase, and the technology transfer agreement was signed
in a hypothetical scenario where the US federal government falls under the direct control of a russian asset, I imagine this would end up in our allies hands reasonably quickly
> I'd expect the original agreements that were put in place--both the ones with the subcontractors as well as the purchase agreements--are quite strict on what you can do with the plane. Trying to reverse engineer software (the policy was that no one gets access to the original source code for the F-35[0], at least back in 2009) is probably a no-go under those agreements.
We're talking about Europe being able to protect itself from a potential Russian invasion despite the US bricking their F35s, and your argument is that they'd have to bend or break an agreement?
I don't think that's a big hurdle, in that eventuality.
I'd be surprised if the algorithms have much say on when and where shorts show up in your feed versus just inserting them into specific spots in your feed that were determined by a whole lot of user testing to see what's most effective. There might be some logic to tweak it, but overall placement is probably fairly uniform across users.
reply