Gamer gunman Ryan Louis Mosqueda references Call of Duty: Black Ops 2 in attack on Texas border patrol agents. Is this a predictive programming psy-op and we get cyberattacks and drone assassinations? Or is it just a mentally I'll hispanic millennial larping?
the-sun.com/news/14648938/ryan…

European News Outlets Continue Misrepresenting GrapheneOS Project


GrapheneOS is currently under a state sponsored attack attempting to misrepresent it as being for criminals, which we covered a bit at grapheneos.social/@GrapheneOS/…. These poorly researched, biased and inaccurate news stories have led to more harassment towards our community and team.

These attacks are taking a multi pronged approach including pushing existing fabricated stories and harassment towards our team. We'd appreciate if our community was more active than usual in debunking misinformation and attacks on our team. It's a very abnormal wave of attacks.



European authoritarians and their enablers in the media are misrepresenting GrapheneOS and even Pixel phones as if they're something for criminals. GrapheneOS is opposed to the mass surveillance police state these people want to impose on everyone.

xatakandroid.com/sociedad/cada…


GrapheneOS AOSP 16 To Reach Stable Channel Within Few Days


GrapheneOS based on Android 16 has been through extensive public Alpha/Beta testing and should reach our Stable channel today. We'll continue fixing various upstream Android 16 regressions such as the back button issue impacting the stock Pixel OS we fixed in our latest release.

July Android Security Bulletin will likely be published today. We obtained early access to the signed partner preview and confirmed no additional patches were required, so we set the 2025-07-01 patch level last month after we backported Pixel 2025-06-05 driver/firmware patches.

Tomorrow will likely be the first monthly update of Android 16 with a new Android Open Source Project and Pixel stock OS release. We won't need to backport Pixel driver/firmware patches since we're on Android 16 and can simply incorporate and ship the monthly update within hours.

It can be extraordinarily difficult to backport driver/firmware patches due to dependencies on the new major release. We were only able to backport everything required for the 2025-06-05 security patch level because Android 15 QPR2 is much closer to Android 16 than Android 15.

After our Android 16 port was completed yesterday, we started fixing an Android tapjacking vulnerability disclosed last month:

taptrap.click/

We have a fix implemented and it will be included in our next release, likely with the monthly Android 16 update tomorrow.

This vulnerability was disclosed to Google in October 2024 and Android still hasn't fixed it. Security researchers should report vulnerabilities to GrapheneOS in addition to Google. This now joins our many other GrapheneOS exclusive fixes for serious Android vulnerabilities.

We've decided to make another release today with our fix for the Android tapjacking vulnerability because we need to fix a DisplayPort alternate mode regression specific to 8th generation Pixels which doesn't impact 9th generation Pixels.

They shouldve bounced trumps big beaitiful pork fuck check :pig_poop_balls2: but they didnt. Strap in he signed himself a 5 trillion dollar blank check and it cleared hope u got silver and gold
zerohedge.com/economics/trade-…

Against Imperial Memory: The “Long War” on Iran libya360.wordpress.com/2025/07…

Which memo did i miss?

Isn't #Netanyahu, PM of #Israel, on an #Interpol #UN #TheHague kinda wanted list?

How can he visit the #USA, without getting arrested?

As a German - yeah, i'm pulling that card (also, I didn't do it, i'm a millennial) - there shouldn't be "only following ze orders" - how is this guy not in custody, yet?

Did the UN/TheHague/Interpol lift their warrant - why?

(I mean, #Putin doesn't travel [much] internationally - imagine why!)

in reply to Multi Purr Puss

🧵 2/n NO, this is not a rhetorical question - i'm NOT an influencer - i am 1 of millions, amongst a #demos, which needs to figure stuff out, in order to sculpt a beautiful #democracy!

I guess, #TheHague would be the most reasonable entity to lodge an inquiry..

..unless someone can notify me of a reliable #news post, outlet..

This entry was edited (1 month ago)

Written by Lucy Thompson, APXS Collaborator and Senior Research Scientist at the University of New Brunswick, CanadaEarth planning date: Wednesday, July 2, 2025As we traverse the boxwork terrain, we are encountering a series of more resistant ridges/bedrock patches, and areas that are more rubbly and tend to form lower relief polygonal or trough-like features. We […]

Is NOBARA really better than FEDORA? benchmarks, experience, apps, controllers...


Download Safing's Portmaster and take control of your network traffic: safing.io

Grab a brand new laptop or desktop running Linux: tuxedocomputers.com/en#

👏 SUPPORT THE CHANNEL:
Get access to a weekly podcast, vote on the next topics I cover, and get your name in the credits:

YouTube: youtube.com/@thelinuxexp/join
Patreon: patreon.com/thelinuxexperiment
Liberapay: liberapay.com/TheLinuxExperime…

Or, you can donate whatever you want: paypal.me/thelinuxexp

👕 GET TLE MERCH
Support the channel AND get cool new gear: the-linux-experiment.creator-s…

🎙️ LINUX AND OPEN SOURCE NEWS PODCAST:
Listen to the latest Linux and open source news, with more in depth coverage, and ad-free! podcast.thelinuxexp.com

🏆 FOLLOW ME ELSEWHERE:
Website: thelinuxexp.com
Mastodon: mastodon.social/web/@thelinuxE…
Pixelfed: pixelfed.social/TLENick
Twitter : twitter.com/thelinuxEXP
PeerTube: tilvids.com/c/thelinuxexperime…

This video is distributed under the Creative Commons Share Alike license.

#nobara #fedora #linux

00:00 Intro
00:38 Sponsor: Secure and monitor your internet connection with Safing
01:36 What changes does Nobara bring?
03:56 Post-Install experience
06:12 Default layout and look
07:28 Gaming Performance comparison
10:20 Package manager & repos
10:54 Controller support
11:24 Davinci Resolve install comparison
13:03 Is Nobara Better than Fedora?
15:17 Sponsor: Get a PC that runs Linux perfectly, from Tuxedo
16:15 Support the channel

Nobara is created by Glorious Eggroll, the creator of Proton GE, which is a more up to date version of Proton to run your games through Steam. Nobara takes Fedora, and adds the Wine dependencies, Steam, all necessary codecs for video playback, 3rd party drivers, like their own packages for the Nvidia drivers, which need a separate repo on Fedora, and a LOT of fixes to various packages.

So, let's compare the post-install process for Nobara and Fedora.
Nobara gives you a welcome app that's actually useful, and will offer to download codecs needed for video decoding and encoding. You can also install drivers there, like the nvidia or amdgpu pro drivers.

It’s not a HUGE timesaver, if I'm honest. Maybe something like 5 minutes after the install.

You can also change the layout and accent colors straight from the welcome app, with layouts based on Windows, Windows 11, macOS, GNOME, GNOME 2, or Unity.

The default experience on Nobara on the "official" version uses a heavily modified GNOME. You get a taskbar, windows style, with Dash 2 panel, and the Arc Menu GNOME extension, for a more traditional menu. You have the APpIndicators as well for notification tray icons, you get BLur My Shell, for blurred translucent elements here and there, you get desktop icons, accent colors that can also be applied to GTK3 and flatpak apps, Pop Shell, for the auto tiling capabilities, and Wireless HID to display the battery level of controllers, keyboards and mice in the battery indicator. Window buttons also include minimize and maximize here.

The laptop uses a 12th gen i7 12700H, with 16 gigs of RAM, and an RTX 3060, and everything runs from an SSD.

With shadow of the tomb raider, running the game at the native 1440p resolution, on high details, Nobara got 87 FPS on average, with a minimum of 72, and a maximum of 144.

On Fedora, using the same settings, and resolution, I got 83 FPS, with a minimum of 67.

Running Horizon Zero Dawn, at 1440p, on high details, Nobara got an average of 64 FPS, with a min FPS of 22, and a max of 161, with a score of 11591.

Fedora got an average of 63 FPS at the exact same settings, with a score of 11281, a high of 159 and a low of 21.

And in Total War Warhammer 3, at 1440p, on medium settings and ultra unit size, Nobara reached 71.6 FPS on average, with highs up to 86 and lows down to 58. Fedora, with the same settings, got 69 FPS, nice, with a max of 84 and a low of 59.

Nobara comes with its own graphical package manager, on top of GNOME Software. This thing show everything that is installed, or the available updates. It lets you install flatpak packages, and it has a graphical repo manager.

Just to see if there was any difference between distros, I also tried to connect various bluetooth controllers, namely an XBox Series controller, and a PS5 dualsense.

On Fedora all controllers connected immediately, and worked as intended, without any noticeable input latency. On Nobara, same experience.

On Nobara, installing resolve didn't require anything specific. All the dependencies were already there, the nvidia drivers they package are perfectly good for it. You download it, you run the installer, and it works. Nobara even uses the cuda drivers, which has never been necessary for me on Fedora, I just install the cuda related libraries from the repos, or rpmfusion.

This entry was edited (3 weeks ago)

The attack occurred at a Border Patrol office in McAllen, Texas.

kayleighmcenany.saferead.org/l…
The Western Journal
Border Patrol Agents Ambushed by Active Shooter in Texas

A shooter armed dressed in tactical gear opened fire on Border Patrol agents as they arrived at a facility in McAllen, Texas, on Monday.

We've lived in this house for 4 years. Since we moved in Wife has wanted a screen door on the front. I have told her several times that it wasn't made for one and the jamb wasn't thick enough. She would say, so fix it. Like it was nothing. The boy was home for the long weekend so on Saturday he took me in his truck to get everything I needed. Sunday, I reframed the front door and put on a storm door. A painter is coming next week to paint the new framing. 1/2
This entry was edited (1 month ago)

Democratic Lawmakers Disturbed as Their Own Voters Demand Violence: ‘There Needs to Be Blood’

thegatewaypundit.com/2025/07/d…

The FBI Claims Epstein Didn’t Have a “Client List” – But What About The Speed Dial List of Names in Epstein’s Bedroom Uncovered by O’Keefe Media Group? (VIDEO)

thegatewaypundit.com/2025/07/f…

What the 17th BRICS Summit Declaration Says and Omits orinocotribune.com/what-the-17…

Brazil is doing a terrible thing on their treatment of former President Jair Bolsonaro. I have watched, as has the World, as they have done nothing but come after him, day after day, night after night, month after month, year after year! He is not guilty of anything, except having fought for THE PEOPLE. I have gotten to know Jair Bolsonaro, and he was a strong Leader, who truly loved his Country — Also, a very tough negotiator on TRADE. His Election was very close and now, he is leading in the Polls. This is nothing more, or less, than an attack on a Political Opponent — Something I know much about! It happened to me, times 10, and now our Country is the “HOTTEST” in the World! The Great People of Brazil will not stand for what they are doing to their former President. I’ll be watching the WITCH HUNT of Jair Bolsonaro, his family, and thousands of his supporters, very closely. The only Trial that should be happening is a Trial by the Voters of Brazil — It’s called an Election. LEAVE BOLSONARO ALONE!

relentless_eduardo reshared this.

GrapheneOS version 2025070600 released


Tags:
  • 2025070600 (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Pixel 8, Pixel 8 Pro, Pixel 8a, Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold, Pixel 9a, emulator, generic, other targets)

Changes since the 2025070500 release:

  • backport fix for back button regression in Android 16 from Android 16 QPR1 Beta 2.1
  • Pixel 8, Pixel 8 Pro, Pixel 8a: restore using asymmetric MTE mode for userspace instead of the default asynchronous mode
  • add back switching to using the Natural display color mode by default
  • migrate more device support to adevtool and remove more unused configuration
  • improve per-device integration for USB-C port control and pogo pins control to make maintenance easier
  • adevtool: remove obsolete overlay handling implementation
  • remove Circle to Search feature declaration
  • enable Runtime Resource Overlay (RRO) enforcement

GrapheneOS version 2025070500 released


Tags:
  • 2025070500 (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Pixel 8, Pixel 8 Pro, Pixel 8a, Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold, Pixel 9a, emulator, generic, other targets)

Changes since the 2025070301 release:

  • partially revert upstream changes in Android 16 breaking parts of the lockscreen layout including the date and media info
  • Pixel 8 Pro, Pixel 9 Pro, Pixel 9 Pro XL: add back feature declaration for Pixel Thermometer support lost in our Android 16 device port migration which prevented fresh installs of the app
  • Terminal (virtual machine management app): disable VM console feature since it isn't supported by the stable release of Android 16 outside of debug builds and trying to use it breaks installing the new images (the feature can be enabled once the core OS supports it in production builds)
  • update Pixel HAL compatibility matrix version numbers for Android 16
  • add lockscreen synchronization failsafe to protect against unknown vulnerabilities
  • improve code quality and add unit tests for our strict CVE-2024-50089 protection
  • kernel (6.6): update to latest GKI LTS branch revision including update to 6.6.94
  • fix port of our 2-factor fingerprint authentication tests to Android 16

No big deal just the CDC casually hiding a vaccine link to autism.... +1000% increase in autism
rumble.com/v6vkg15-covid-vacci…

reshared this

Source: libsoftiktok

DISGUSTING. Adult men wearing thongs in Berlin performed s*xually explicit dances in front of CHILDREN at a pole dance event in Berlin, Germany.

The event reportedly had children's tickets available for purchase. One of the performers responded to backlash saying "no child was traumatized."

This is child grooming.

h/t @DrBuzzzzz

[Video embedded in original tweet]

Original tweet : xcancel.com/libsoftiktok/statu…

GrapheneOS Based On AOSP 16 Now Available In Beta Channel For Testing


GrapheneOS based on Android 16 is now available in our Beta channel. There are 2 main known issues which will be fixed in the next release: lockscreen date and media info are not properly displayed due to an upstream AOSP bug and Pixel Thermometer doesn't appear in our App Store.

Last month, we provided the 2025-06-01 Android/Pixel security patch level early in the month before the stock OS release as preparation and then backported Android 16 firmware and kernel/userspace driver patches to provide the 2025-06-05 Android and then Pixel patch levels.

Our 2025062700 release raised the overall patch level to 2025-07-01 since we got early access to it with a verifiable signature and know we already provide the patches. We usually do an early Android Security Bulletin release before the stock OS but it was done for July in June.

Android Security Bulletins are backports of High/Critical severity patches to older Android. Starting this month, the initial release of Android 16 is one of those older releases. It's split into AOSP userspace patches (YYYY-MM-01) and driver/firmware/Linux patches (YYYY-MM-05)

YYYY-MM-05 patch level has a device-specific portion with more driver/firmware patches. For Pixels, it's the Pixel Update Bulletin. Most Pixel Update Bulletin patches aren't specific to Pixels but the Android Security Bulletin doesn't cover Samsung cellular, Broadcom Wi-Fi, etc.

Pixel Update Bulletin patches are what we had to backport to Android 15 QPR2:

source.android.com/docs/securi…

These were for firmware/drivers/services for Samsung cellular (including the Radio Interface Layer), Broadcom/Qualcomm Wi-Fi/Bluetooth, NVT touchscreen, fingerprint and TPU.

The only part truly specific to Pixels was the TPU patch. Bear that in mind when you look at those Pixel Update Bulletins. Other devices are meant to have their own bulletins covering the same things if they use those components and also further patches. It's fully up to OEMs.

Android Security Bulletin (ASB) is published on the first Monday of the month unless it's a US/Google holiday in which case it gets pushed ahead a day or two. The Android release for the month is a separate thing from the ASB backports, usually published the day after the ASB.

ASB is likely July 7 and the Android OS release is likely July 8. Our aim is to have Android 16 in our Stable channel prior to July 8 so we can ship the initial monthly update to Android 16 instead of needing to backport Pixel Update Bulletin patches which could be infeasible.

Each month, Android has a new stable OS release. It's a monthly, quarterly or yearly release. Quarterly and yearly releases move along the development branch about the same amount and have a similar amount of changes. Those have months of public Developer Previews / Betas first.

Pixels ship the latest monthly, quarterly and yearly release each month. Non-Pixels ship an initial yearly Android release and then only Android Security Bulletin backports until they ship the next yearly release. ASB backports are a subset of the AOSP patches, not all of them.

GrapheneOS needs to follow the stable releases in order to provide the full AOSP privacy/security patches. It also needs to keep up with them in order to ship Pixel driver/firmware patches which are made for the latest stable release, but we'd still need to do this on non-Pixels.

GrapheneOS version 2025070301 released


Tags:
  • 2025070301 (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Pixel 8, Pixel 8 Pro, Pixel 8a, Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold, Pixel 9a, emulator, generic, other targets)

Changes since the 2025070300 release:

  • fix upstream Android 16 issue causing very large Binder transactions due to the size scaling based on the number of apps installed across all users including base OS apps
  • reduce virtual memory reserved for Binder buffers back to 1MiB now that we have a direct fix for the upstream issue causing more to be required and using a larger virtual memory reservation size appears to have a small chance of failing
  • revert our fix for a screenshot process crash that's now fixed upstream in Android 16

GrapheneOS Foundation Discusses Non-Standard Per-app Permissions


Android regularly adds and splits permissions for new API levels. Legacy apps are handled by treating them as requesting the permission to provide a toggle for it. For example, Android 13 converted the existing toggle for disabling notifications for an app into a new POST_NOTIFICATIONS permission.

The Android Open Source Project has infrastructure for this since it's a regular part of the app sandbox and permission model improving. We add Network and Sensors permission toggles in GrapheneOS where Network is based on the existing low-level INTERNET permission and Sensors is entirely new.

Nearly all apps are unaware of these non-standard permissions just as they're unaware of new permissions added by Android before they get upgraded. Therefore, we enable them by default for compatibility but provide the ability for users to disable them at install time like the standard permissions.

For Network, apps request INTERNET, so we provide a toggle for rejecting that request in the initial app install dialog. If it's added in an upgrade, it's disabled by default. For Sensors, apps don't request it so we handle it similarly to how Android handled POST_NOTIFICATIONS for existing apps.

When Network is disabled, we act as if the network is down for compatibility. We won't run network-dependent jobs, various APIs will report it as down and we give errors matching it being down. When Sensors is disabled, sensors not covered by standard permissions give zeroed data and no events.

For usability, apps trying to use those sensors when Sensors is disabled will trigger a notification from the OS which can be disabled on a per-app basis. This informs users about what's going on so they'll know the app is either doing something sketchy or that it may actually require it.

F-Droid has an incorrect approach to installing apps which wrongly warns users about the standard Android POST_NOTIFICATIONS permission, our OTHER_SENSORS permission and previous Android permission additions/splits. They wrongly blamed GrapheneOS and didn't fix it:

archive.ph/MtB2J

They're now realizing that it happens with standard Android permissions added / split in new releases. Their approach to installing apps has been incorrect in multiple ways for many years and this is one of them. Their approach to listing which permissions are used by apps is also very incorrect.

F-Droid has a long history of denying issues including covering up serious security flaws. In some cases they eventually ship a fix but still deny it. It's a major factor in why F-Droid is not a safe or trustworthy source of apps due to major security issues not being acknowledged or addressed.

Multiple of the F-Droid developers wrongly blaming their app bug on GrapheneOS in that issue are Calyx contractors. They prioritize attacking GrapheneOS with inaccurate claims and fabricated stories about our team over fixing a bug in their app impacting both GrapheneOS and non-GrapheneOS users.

We've repeatedly brought up F-Droid not properly listing permissions or checking for them. Their understanding of Android's permission model is wrong. The way they list permissions misleads and misinforms users. It's one of many major F-Droid flaws they consistently don't acknowledge or fix.

Due to F-Droid deliberately causing friction and annoyances for GrapheneOS users, we'll be implementing a feature similar to our sandboxed Google Play compatibility layer for it. We'll can resolve deliberate issues created for GrapheneOS users ourselves as we did with Revolut.

Melbourne Metro Tunnel Update

Its looking great but the tunnel between Flinders St and Town Hall is way too narrow, it will be super annoying to transfer trains there, that is one area where they should not have skimped

youtube.com/watch?v=qa8AZTFzoC…

Iran: Israeli ‘terrorist’ strikes lethal blow to diplomacy, NPT presstv.ir/Detail/2025/07/06/7…

Monika Talks About Her Brother Alfred Schafer Being Arrested in Germany on July 7, 2025


This is from The Sane Asylum #340 Based Monday - 07JewLie25 on 07-Jul-25-12:00:33: ftjmedia.com/video/.theSYWfGSn…
This entry was edited (1 month ago)

USGS coastal observing camera in Nuvuk, Alaska, today. Image credit US Geological Survey / Pacific Coastal and Marine Science Center. Learn more at usgs.gov/programs/cmhrp/scienc… and usgs.gov/centers/pcmsc/science… and #interpretation #geology #usgs #publiclands #photography #landscapephotography #arctic #arcticocean #waves #alaska #research #live #sediment #color #ocean

Tried to flash new #Libreboot binary with (proper) text-mode instead of corebootfb-mode.

And suddenly found that my #ch341a programmer is dead :dragnshock: It was in the antistatic pouch in the shelf for half of the year and now it can't read/write/erase my #SPI chip on the #Thinkpad X220. It even can't be detected by OS.

Are CH341A programmers really so unreliable that they are dying without any visible reasons? :dragnsad: