wstuartcl

Umm based on the statute and elements of the crime they were charged with and found guilty of.

Whoever, while committing a robbery, is armed with a dangerous weapon or any article used or fashioned in a manner to lead the victim to reasonably believe it to be a dangerous weapon, or inflicts bodily harm upon another, is guilty of aggravated robbery in the first degree and may be sentenced to imprisonment for not more than 20 years or to payment of a fine of not more than $35,000, or both.

Or is your stance that a person committing robbery with a weapon and threatening to use it should instead be considered a hapless person that has not chosen to act in a way that is highly likely to cause great injury or death? Like a gun is "ok" and should not be considered as evidence of intent to commit harm during the act of robbery unless they shoot it?

Lol yeah, armed robbery is effectively the charge for someone that was totally willing to kill while robbing but due to circumstances did not need to. That should not be considered a light crime.

It would be mind blowing to me and completely unexpected if twitter was not already under many active settlements related to accessibility lawsuits each with their own ongoing obligations.

There are very few large entities that have not been impacted by ADA lawsuits at this point -- even ones that had accessibility as a core value before the lawsuits.

I believe just meta has encountered many dozens of ADA related lawsuits for everything from their use of disability information for ad targeting to web accessibility -- both government instantiated and civil cases.

I am fairly sure much of their accessibility work was instantiated by these lawsuits and settlements.

https://www.facebook.com/help/273947702950567

Having worked with many PR/Marketing/Media brand teams I do not know of one group that utilized twitter client in any of their workflows -- they all used a mix of third party clients for reading and other integrations/clients for posting and managing conversations and ad work. Sure much of the API surface area for latter still works but there was a goodly portion of impacted folks on these clients that were the same people that were on the same teams that impact ad spend and brand usage.

I also do not think Musk understands just who the primary userbase on many of these 3rd party apps were -- many of those pesky advertisers/brands that he seems to be both courting and at war with exclusively use api apps for tracking posting/responding and integrations.

The fact that Elon has disbanded the accessibility team at twitter probably already leads them into hot water related to this (It is not uncommon for orgs like twitter to be bound by multiple long term settlements related to accessibility suits that each have obligations of certain deliverables in this area.

If your friend truly does have issues navigating the site perhaps she may want to look to a legal remedy -- from all appearances that is really the only knob that seems to have any impact on Musk.

While I do get what you are saying VRChat shutdown is a pretty poor match to this scenario. the TOS for that always had a clear verboten against modifying the client and network traffic via 3rd party apps/patches.

In Twitters case, the API was shut down (with no warning) and then the TOS was updated to make the integrations verboten only well after there was a fairly huge backlash and late response of "clients were disabled that were violating api 'rules'" did not hold up against the actual rules in place.

I really do get the whole move fast and break things model, however this is Musk taking that model to mean put on blinders and run full speed while holding scissors in a crowded room with many walls -- consequences be damned.

While I agree that getting locked out is a clear risk of any business built against another company's platform I do think it is perfectly reasonable for someone whom has done so for 15+ years (and is part of an ecosystem that helped establish that third party) to be publicly upset for the mode and method for how this change happened at twitter. Its not just his frustrations being vented in this post but the impact to his users (which is well out of his control).

Twitter's actions of breaking the API for the largest 25 integrators with millions of users (by all indications) on purpose with 0 deprecation warning, 0 communication, 0 response the the break is garbage. Knowing that Musk is the agent of change and the one setting these actions in place he can take the heat.

at the end of the day I am done with twitter as it is, so its no skuff on my skin either way -- as far as I am concerned there is a clear path forward for the types of actions Musk has taken at twitter. It is just a matter of time.

I just wish companies would move these types of conversations/notifications off of twitter -- i'm done with that s-show.

Depending on the nature of the app a suitable easter egg may be that over time the outputs become randomly but subtly incorrect. Another technique is to canary mark outputs in some way (like a tell tale unique string in PDF/export outputs). In this way your sales team may be able to search for those outputs and put pressure on large orgs creating those files.

I think it will be interesting to see the next few years. There were quite a few orgs that jumped as the pricing was introduced, detachment from k8s etc that was a side effect, a bunch of new options in (free) market. Just from my perspective out of the orgs I know of that bought into the pricing, every one of them has active projects to get off in the next year.

Its even more amazing when you really sit down and think about all of the systems (many highly resistant to change like aircraft navigation systems) that all connect and utilize this service.

What appear like simple changes and proposals in the aerospace realm are extremely hard to execute and many times take decades (multiple) to come into play. Global services/systems are even harder.

Depending on your age and general personal history, in the past it was very common to see references and use of "the Ukraine" to talk about the region/area as well as the country (that mostly covers that geographical area). It could be remnants of your recollections popping up subconsciously.

In this case it really was meant to be projected as similar to "Have you seen the Bob document yet?"

if collisioncheck(v1,v2, distance) { // collision }

where you have defined an actually readable equivalent inside of collisioncheck would be my prerogative... I also agree paren matching failures should error, but your example is NOT why.

Both are still in use. For instance during your pilots tests either is considered an equivalent answer.

FAA and most all global air systems and services tend to use their own nomenclature for communicating to pilots -- I would read "equipment failure" as a term that pilots would use and understand as "a temporary or permanent failure of software or hardware in the system" and not read into it any additional common sense from other areas of expertise.

You could also go to a neurologist and have some tests run -- beyond general aging and its impacts on memory and reasoning there are other types of issues that can impact people much younger than expected.

That said, if you do not exercise you should really try for a few weeks. Where your body may have been able to coast with normal effort in the past as you get older you need to give it more focused work to get the same level of outcome. Beyond being good for your health exercise is known to have huge impacts on both mental state and acuity.

It is not that they are creating new laws, it's that the dev committed theft of services and fraud (existing well established laws) as he utilized the system with intent to receive free services that were directly forbidden in the grant from google.

Wonder what the lawyer costs would be should google go after the company that paid him to do the fraud for them?

Yes. Serving content crafted for spiders specifically is a blacklist waiting to happen.

It really varies from role to role -- staff engineers/principals/whatever nomenclature used can be just another manager/director or a pure dev with light mentorship/heavy resource for helping with hard dev problems and designs and anywhere in-between.

Also regarding nomenclature of the titles -- its all over the place in the wild some places call jr's "staff software engineer" sometimes its seniors or principals.

"probably" but not always. I have worked on a few projects that saved 70-90% of costs for AWS -- but these all were starting from a position of auto scaling out a ton of ec2 (on demand full cost instances) to batch process huge amounts of data. In both scenarios by optimizing the batching to align tasks to pack as much as possible into (just short of hour long) hour long windows and converting to a (wide list of ec2 types to avoid contention lockout) spot instances there was easy fodder for the improvement.

But yeah -- no one should see their bill change by that much without understanding exactly what was done to trigger it. Even in the best cases, there are always tradeoffs that must be known and accepted.

This is an outcome of what they have done in the warehouses to "optimize". Instead of requiring all of each vendor's items to exist in each warehouse they have commingled them (with what seems extremely little checks and balances). All items they accept for warehouse are tossed into the same bin location and any orders from any vendors for that item are pulled out of that random bin (instead of segmenting the vendors stock).

In this way when your order Acme Widget A from vendor X you could be randomly getting stock from vendor C's items (which are knock offs), Vendor "acme"'s items which are the actual company items or vendor Z's items which they have setup to toss back into their stock from returns with little if any checking).

This optimization provides warehouse "leveling" allowing Amazon to ship local products faster without needing to ensure each vendor splits tock or shipping via warehouse/warehouse but obviously builds in a huge carrot to game the system for vendors and makes it hard to have checks that identify the actual problem vendors.

I thought they announced no pi5 this year specifically.

Maybe the solution is to add anti-right to repair as a major indicative element to the monopoly legislations (ie if indicated it reduces the hurdle of the other elements that must be proven dramatically). Forcing repair lock in should be indicative of monopoly behavior.

Something needs to change where the perceived "cost" of building out repair lock in revenue is much higher than it currently is.

Wonder if it is a font license issue.

regarding frequent changes, in my experience keeping 5 or 6 Phoenix/Liveview apps up to date the pain I have seen with changes is far less than I have experienced with Rails, Django and even front end updates required to keep react and vue inline. All of that when Liveview is not even a 1.0 yet...

I do get that books and other rotting materials obviously fall behind quickly but have you seen hard uplifts to codebases to keep them up to date?

Snorted a little at this -- how can anyone forecast JS ecosystem 5 years out. =)

I think this is what takes time -- they have to build more than a circumstantial case that the crime was committed and as you said the suspect is not going to confess so they have a large hill to climb.

Flying to an island on his plane (even after everything we know about that has happened on that island residence) does not itself indicate any wrong doing -- they have to fond more evidence that links the threads together. If they charge or show their hands before they have enough it sets various clocks in motion that can harm the long term cases.

I have faith they are still working as many of these as they can looking for charges -- its only faith.