https://www.phoronix.com/news/Intel-iGPU-Avoid-Linux-5.19.12

Orange Site:

https://news.ycombinator.com/item?id=33092974

https://old.reddit.com/r/linux/comments/xw69t5/beware_kernel_51912_could_damage_intel_laptops/?sort=controversial

https://old.reddit.com/r/Fedora/comments/xvmm5f/intel_laptop_users_should_avoid_linux_51912_to/?sort=controversial

https://old.reddit.com/r/openSUSE/comments/xvnno4/intel_laptop_users_should_avoid_linux_51912_to/?sort=controversial

https://twitter.com/search?f=tweets&q=Linux+5.19.12&since=&until=&near=

Slashdot:

https://linux.slashdot.org/story/22/10/05/141248/intel-laptop-users-should-avoid-linux-51912-to-avoid-potentially-damaging-the-display

Intel Laptop Users Should Avoid Linux 5.19.12 To Avoid Potentially Damaging The Display

Intel laptop users running Linux are being advised to avoid running the latest Linux 5.19.12 stable kernel point release as it can potentially damage your display.

Intel Linux kernel engineer Ville Syrjäl posted today on the kernel mailing list: After looking at some logs we do end up with potentially bogus panel power sequencing delays, which may harm the LCD panel.

Greg, I recommend immediate revert of this stuff, and new stable release ASAP.

Greg Kroah-Hartman has immediately released Linux 5.19.13 with the problematic Intel graphics driver patches reverted.

If you do not have this problem with 5.19.12, there is no need to upgrade."

Discuss.

Orange Site:

https://news.ycombinator.com/item?id=33040873

Orange Site:

https://news.ycombinator.com/item?id=33003777

https://old.reddit.com/r/technology/comments/xlktl6/opiran_anonymous_hits_iranian_state_sites_hacks/?sort=controversial

Generated from TLDR This:

In the wake of the recent Iranian government crackdown on dissent after Mahsa Amini’s death, the international hacktivist group Anonymous has launched a new operation against the country’s online infrastructure.

It is worth noting that on September 16th, 2022, a 22-year-old Iranian woman named Mahsa Amini died in Tehran, Iran, under Police custody.

Amini was arrested for failure to follow government-mandated forms of the Hijab.

A Google search for the Center’s website shows it was hacked by Anonymous (1) – The deface page left by Anonymous plays a video containing content that shows a message of support to Iranians (2) – Screenshots 3 and 4 show what is inside the database Forensic center’s database. (

JUST IN: In response to a violent police crackdown of protestors and censoring communications, #Anonymous launched #OpIran and have now hacked over 100 Iranian websites, including several belonging to the Iranian government. #

However, it is clear that the group is determined to continue its fight against what it sees as an oppressive regime.

Generated by TLDR This:

Most of the companies participating in a four-day workweek pilot program in Britain said they had seen no loss of productivity during the experiment, and in some cases had seen a significant improvement, according to a survey of participants published on Wednesday.

Critics, however, worried about added costs and reduced competitiveness, especially when many European companies are already lagging rivals in other regions.

Jo Burns-Russell, the managing director at Amplitude Media, a marketing agency in Northampton, England, said the four-day workweek had been such a success that the 12-person company hoped to be able to make it permanent.

The result has been that the company is delivering the same volume of work and is still growing, even though half of the employees are off on Wednesdays and half on Fridays.

“It’s definitely been good for me in terms of making me not ping from thing to thing to thing all the time,” Ms. Burns-Russell said.

She has taken up painting as a hobby and feels calmer overall.

Could it be?

Thoughts? Discuss.

https://marsey.club/

https://github.com/pablouser1/ProxiTok

https://proxitok.herokuapp.com/

Archive.today is now under intense pressure to do the same because they still have a record of the thread that kicked off the whole campaign: https://archive.ph/uLpNt

lol that archive is like lawlz's imgur url

American wireless carriers are used to getting lawsuits — particularly T-Mobile, which has faced several lawsuits over the years, including in June this year for leaving Sprint 5G customers hanging following the heavily publicized merger. Well, the self-ascribed Un-carrier is gearing up for another legal battle, this time with AT&T, as the latter has made it clear it is unhappy over its competitor's recent marketing campaign alleging that AT&T and Verizon don't offer senior discounts unless they live in Florida.

a lawsuit filed with the US District Court in Sherman, Texas on September 6, AT&T alleges that T-Mobile's campaign is attempting to "deceive senior citizens" on purpose. The company then clarifies its stance on senior discounts, revealing that it provides discounted tariffs for seniors in all 50 states as long as they are members of the American Association of Retired Persons (AARP), Fierce Wireless reports.

T-Mobile's campaign was spearheaded by launching a marquee website, BannedSeniors.com, with information on how to switch carriers as well as how to create a virtual mailbox in Florida. The website even puts seniors in touch with Florida real estate agents if they are considering a move. Meanwhile, the AT&T website mentions the discounts currently available for AARP members, with the ability to save up to $10 per line per month on the Unlimited Premium plan. This is on top of the $50 waiver that AARP members get on upgrade and activation fees.

But it's T-Mobile's claim that 92% of American seniors "can’t get a wireless discount from Verizon or AT&T because they don’t live in Florida" that has appeared to have triggered the lawsuit by AT&T. The plaintiff counters that this is simply not the case so long as the customer is an AARP member — membership costs $12 for one year though overall costs are lower with longer-term packages.

Moreover, AARP membership is open to individuals aged 50 or older whereas T-Mobile's Essential 55+ — the specific plan that the carrier is trying to promote — only covers seniors aged 55 or up. Customers don't have to be with AARP, though, as anybody in the age group can get the plan which costs $40 per month for one line and $55 for the maximum of two lines.

AT&T is seeking damages in the form of compensation and attorney fees from T-Mobile while also trying to obtain any profits it accrued as a direct result of this campaign. The carrier is also requesting a jury trial and an immediate suspension of T-Mobile's senior discounts campaign. For its part, Verizon confirmed its discount limitations, saying that eligibility is limited to Florida seniors who are aged 55 or older.

orange site

• DOJ suit alleges Google’s exclusive deals lock out rivals

• Company says phone makers, browsers want its search engine

If the DOJ makes Google stop paying companies to be their default search engine and ends up killing Mozilla I'll c*m.

Kek at riceboys being hunted ; https://old.reddit.com/r/worldnews/comments/x2scvw/comment/imn1wvy/?sort=controversial

If I ain’t wrong booth coe of nvidea and amd are rice boys so majority in that field must be rice

lol

October 06, 2022 - Exclusion Deadline

October 06, 2022 - Objection Deadline

November 05, 2022 - Claim Deadline

November 17, 2022 9:00 am - Final Approval Hearing

Plaintiffs filed a class action complaint alleging that Snap Inc. (the “Defendant”) violated Illinois’ Biometric Information Privacy Act, 740 ILCS 14/1, et seq. (“BIPA”), based on Defendant allegedly collecting and storing biometric identifiers and/or biometric information (collectively, “biometric data”) through the use of the “Lenses” and “Filters” features offered by Snap without complying with BIPA’s requirements.

A Settlement has been reached in this case and affects the following persons:

All Illinois residents who used Lenses or Filters offered by Snap between November 17, 2015 and the present (the “Class Period”).

The Settlement, if approved, would provide $35,000,000 to pay all Settlement Payments to Settlement Class Members, the Service Award to the Class Representatives, the Fee Award, payment of Administrative Expenses, any federal, state, and/or local taxes of any kind (including any interest or penalties thereon) and any and all other fees, costs or expenses.

Your legal rights are affected whether you act or don't act. Read the notice carefully.

Already bricked a Pixel 6

With Android 13 out of Google's hands and onto developers who are modifying the operating system for their own purposes, it's going to be a tricky road ahead. There are a number of new features the version bump brings that need to be tested, but before they can do that, they'll need to make sure of one crucial thing and that's to install Android 13 on both system partitions of their Pixel device. One developer has found out what happens when things go awry without that second updated partition.

There are two concepts in Android at play here that go into what has happened: seamless updates and bootloader rollback protection.

The idea of A/B system partitions were first introduced with Android 7.1 Nougat in 2016 to enable seamless software updates to be installed on one partition while still allowing the device to be used with its current software on the other partition. After the installation completes, the user would then be able to reboot onto the updated partition immediately, saving considerable downtime from waiting for the software to install during the reboot process. It also leaves the other partition with the older version of the software.

As for the idea of rollback protection, Google will sometimes update a device's bootloader to prevent an older version of Android from being loaded onto a device — this is usually in response to known vulnerabilities. Indeed, with the Android 13 update for the Pixel 6, Pixel 6 Pro, and Pixel 6a devices, Google had indeed made it so that those phones would not boot if an Android 12 build were to be later installed on them.

One developer became the victim of a collision of these concepts. They were working with an Android Open Source Project build of Android 13 on their Pixel 6 when the device failed to boot.

It wouldn't have been such a catastrophic failure in most cases because the phone would immediately be able to turn to its functioning B partition and boot from there. But because the B partition was still on Android 12, the rollback protection feature kicked in and prevented the device from turning on. And with no known way to switch back and attempt another boot from the Android 13 partition, this Pixel is as good as bricked.

Who's most likely to come across this type of scenario? We think it'll be developers who shoot ADB or fastboot commands that could cause a sixth-gen Pixel running Android 13 — @flawedworlddev notes that the anti-rollback feature only kicks in after an initial successful boot on Android 13 — to crash and fail to boot from its A partition. We'd also say that there's a non-zero chance consumers might be vulnerable to this issue right now as some sort of freak app crash or system failure could trigger a boot failure, but the odds are vanishingly small and will disappear completely if they are successfully able to load a future software update.

But once the phone's gone, it's gone. Developers should make sure that both partitions on their Pixel devices get successful Android 13 installations before playing around with anything else.