• 3 Posts
  • 66 Comments
Joined 2Y ago
cake
Cake day: Jun 09, 2023

help-circle
rss

Yeah, read up on the Graphene webpage. I don’t use any of it, but there are options. You’re most likely to have issues with banking apps, from what I have seen. Anything that can’t be done in a browser is a stalkerware scam IMO. I consider them irrelevant if they lack this fundamental functionality.


hardware specification (implied marketing connotation/ opposed to a bootloader function related to a unique part)


Yeah, Graphene does updates, GP sandboxing, and direct configuration type stuff that is next level better than a typical swap ROM. The entire reason why Graphene uses the pixel is not because of the hardware but because of the (trusted protection module) TPM chip on pixels. It is the same chip as secure boot on a PC.

The basics of TPM is that it is like a microcontroller that generates and stores encryption keys. It can generate a key internally that can never be extracted or accessed through communication with the TPM chip. You can send it a hash to verify a match with a key it owns and it will verify any encryption. Graphene is using this feature to create keys and a secure system that can be verified and can get OTA updates all the time securely. You can use an old device to confirm that your device is secure too using a provided authorization app.

Custom ROMs often are terrible about security and how Android actually works. Things like adding root to a device or any of the packages that are capable of modifying the kernel are super sketchy dangerous. You’re a user just like every developer for every app you use on Android. This is how it just works while knowing about networking and securing an operating system is not required. The entire model is designed to fail safe. The moment you start changing packages available in the kernel there can be problems.

Graphene handles this by only giving root access over USB. Vanadium is also quite outstanding and far more than just a browser. At first you’re likely to try to use a ton of apps like you may be accustomed to doing. After a few years with Graphene, you are more likely to greatly limit your apps and only use vanadium for everything. With my setup on a 2 year old device, I still get over 2 whole days of battery life; nearly the same as when new. I’m not using anything from Google and have around a dozen apps total. I’m also primarily on a network that blocks all undesired connections on a whole different level than adblock.



I think the top use will actually be diffusion. A small model could add a lot of variability to palettes to start. Then move on to something like a slider puzzle where an AI is altering the initial terrain configuration in dynamic ways. It would likely create an environment where a player’s natural pacing can be compensated for in real time.

I could also picture a function calling setup that attempts to optimise player experience.

I’ve been looking at ways to generate tiles for CDDA using a small model. There is a ton of potential especially in open source. I won’t run any model unless it is open weights running on my hardware.


(47m/8b) × 100 = 0.5875% of the world. Those numbers are likely total accounts as well and nowhere near the real active users. I bet many of these are also systems with multiple users or users with multiple accounts. Reported numbers are usually unverified and inflating them as much as possible is in the best interest of Sony on may fronts.

It is neither here nor there. I used to love the first few generations of PS stuff, but I really see no reason for consoles like these any more. I owned everything I played back then. I find it rather pathetic that my right to own has been stolen.

I’m presently taking a snack break from Cataclysm DDA after tracking down foods with better iron content in the game. Under that I have a bash script and Emacs running with my mods to the game. I’ve been playing all afternoon and making little odds and ends for the game. Sorry if my perspective from a non dystopian space rubs the wrong way. What I’m doing isn’t for everyone, but if everyone had some better self control and the character to stand up for themselves, you will find that you get your rights back from these asshats, or you will get them from the next generation of platforms that rise from the ashes. The only terms that actually matter are the ones you’re willing to put money into. I back up that statement. I’m on a 12th gen Intel with 16 GB GPU. I would be playing AAA titles but there are no game manufacturers. I don’t care if I’m the only person unwilling to adopt feudalism and serve some tyrant overlord on their yacht. So be it.


There are no game manufacturers, just licenses to rent from subscription parasites. Sell me a product as an entire industry standard. NEVER ask me to trust you. NEVER try to steal from me with legalise. My terms of purchase are ownership of my purchase with no strings attached whatsoever. I will continue to play and mod open source games or play nothing at all, but I will never cross that line. I have a 12th gen i7 and Nvidia 16 GB GPU. I can absolutely play the AAA titles of today, but there are no game manufacturers, just worthless criminal feudalism and subscription extortion parasites.


To my understanding, no. Graphene did a blog post in the last couple of months about this IIRC.

If you use gource (GUI view of git commits over time and individuals involved), you’ll intuitively see the issues. The mainline kernel often has some change than requires someone goes through every module in a branch of the tree and makes some small change. It might be some code snippet or it might be a change of type casting. These are the changes that require source code. If a variable is type cast incorrectly or that snippet is missing, the module code will error.

So with things like traditional custom ROMs, the way they are supported is by someone intimately knowing both the kernel used in the device and all of the changes happening in mainline. They back port the required changes to the old kernel as best they can. Eventually, this task becomes untenable and the support is dropped.

The reason I explain things is so that I can expound if needed and get a better understanding if you ask questions, while also giving you a more broad and abstract overview.

You said:

proprietary drivers can be plugged in as modules

This implies that you do not understand the fundamental architecture of a kernel. Windows is a Microkernel. Linux is a Monolithic kernel. A Microkernel basically provides a specification like API for anyone to write a driver. A Monolithic kernel includes all hardware supporting modules inside the kernel itself. A kernel module is not some separate thing that exists externally. The monolithic kernel is not handicapped by a static API like interface as software technology and new hardware evolve. The way Google has enabled orphaned kernels with Android is a hack and defies the kernel architecture. Every orphaned kernel is therefore outdated before the first device reaches customer hands. The configuration details I explained before are the hack scheme used to get around the vulnerabilities and issues. The kernel architecture can not be changed to accommodate this.

I’ll try to remember not to respond to you in the future. It is a waste of both of our times if writing the details is mundane copy pasta to you. I don’t mind writing it, and haven’t copied anything. I have said it many times, but whatever. Sorry I replied.


Google packages the Linux kernel for Android and provides it to manufacturers. All that is missing are all of the kernel modules that make all of the hardware work. These kernel modules are proprietary blobs. They are different for every device and may be different for the carrier specific revisions of every model.

If you try to update the kernel, to something like mainline, the changes present in the mainline kernel are not compatible with the old modules and will break stuff. The source code of these modules must be present when compiling the new kernel.

This is the intended behavior and design. It is theft of ownership using this mechanism.

However, it is not just this simple. Android is designed to allow idiot users that do not have a clue about operating systems, security, networking, or radio communications. Android makes this possible in a unique way, and is a great way to learn about how to secure a Linux system properly.

When the manufacturer finishes configuring the device kernel modules, the final step is to remove absolutely every way of adding a binary package to the device. This means they remove the su, sudo, wget, curl, git, Python, etc.

The entire Linux base is only present to run the Android user space. This is like a single Linux application. Nothing else is running in Linux like a .deb or .rpm.

So how does the competent configuration magic happen? - nobody asked.

This is the important detail to understand; the application developer is given the same user space permissions and access as the end user of the device. Android apps are not some static executable program you run on your device. These are entire user profiles that coexist with you at all times. This is how the application can operate securely without any intelligent configuration required by the end user.

SELinux is used to sandbox the various Linux directories so that apps are limited in their access to each other.

The code for Android apps is often garbage. It has to do with the enormous number of devices, configurations, exceptions, aging, and just bad code. Android handles this by just steamrolling through. It can largely get away with this because there is no way for the app to modify the kernel and compromise the system, or for the user to do so for that matter. This is why you can’t have root on Android and adding root is absolutely insane and will wreck your device.

You are not admin. Most of the privacy aspects are a joke to make you feel better. THIS is why everyone wants you to use their app. Apps are users that are always with you, and very intimately. These are your soulmates; your digital life partners — far more intimately connected than any human partner. In a sense, Google and Android are the pimp, and you are the product.

If you have a full kernel, you must have the administrative binary, or at least the package key for access to the bootloader. If a mobile device existed fully open source on mainline, you shift the burden of configuration onto the user.

There are also many aspects of Android that are more advanced than the mainline Linux kernel. Things like asymmetrical CPU schedulers, or how I glossed over the way there are 3 types of users. The way the modem interacts with the SOC is another enormous mystery to me and a giant can of beans. The simple ways that typical Linux distros are configured are nowhere near sufficient for a mobile device. Fedora is one of the only distros that even comes with SELinux but it is set permissive and unconfigured out of the box. Most people never really get into understanding NFTables and networking, preferring to have lax setups using ad block where others do it for them. You would need to know all of these systems intimately if you want full control and for mobile networks to allow connections, or payment systems or banking apps to function. That is simply unrealistic to expect for the general public. In truth, for a typical Linux user, something like OpenWRT is hard. Android in its true complexity is next level beyond this.

Still, it is not full proof. The Linux kernel has around one bug for every 1k lines of code. That means there are tens of thousands of bugs. These are found and patched constantly. However, kernels on Android are almost always ancient, and static/unchanging. This is the reason custom ROMs have existed all of this time. When a bug is found, that exploit is the way into the kernel and an administrative root binary can be added. The only exception (that I know of) is Graphene OS. The Pixel has the same type of Trusted Protection Module (TPM) as your computer uses for UEFI Secure Boot. This device enables Graphene OS to sign and load a separate encrypted operating system without cracking the kernel like a typical ROM.

In an ideal world, governments would protect the unalienable human right of ownership autonomy. This is a cornerstone of citizenship, and therefore democracy itself. Ownership is simple to regulate by requiring that all hardware sold must be fully documented with every piece of the toolchain used to configure the hardware made publicly available immediately upon public offering. This would not change Android as it is now, but would make it possible for the community to take full ownership over their devices and take away absolute control from Google/manufacturers with planned obsolescence.


The vehicle likely does not have any protection systems or encryption. It likely has the bootloader integrated with the kernel. It is also running native or native like Android packages while altering zygote behavior so that extra applications are only loading in at execution time.

If you really want to understand the subject, intuitively grounding your understanding is a critical aspect of the processes. Telling people the simplified basics in isolation does not create useful understandings and assumes the person is on a similar foundational understanding. Someone that is genuinely curious, such as myself, but having no prior background can make use of such abstract overviews. Someone with total recall would likely find me pedantic. With abstracted intuitive thinking as a primary function, many people such as myself require such deeply embedded intuitive connections to make sense of the world with a deeper understanding of the connections involved. I retain no information in isolation in long term memory. This is neither right nor wrong in some asinine simple view of the world and the way people learn. If you find it odd, that is fine. Functional intuitive thinking is one of the rarer outlying personalities, but it is also the emulator function that can fake the rest with effort.

It is related, but on many levels, and useful to someone other than yourself. A binary perspective of learning and sharing of information is fundamentally incorrect.


A lot depends on the overall systems.

If you’re really interested in the subject, here are the places to look around:

  1. OpenWRT is the goto embedded Linux starring point. It is hard if you’re only familiar with desktop distros that use the Bash shell as the default. OpenWRT only has busybox with the Ash shell by default. OpenWRT is common on routers and is an entire distro that fits within 8-32 MB of flash memory on these devices or others like single board computers. Often, using an old router board just to hack around like it is an SBC is a great way to learn.
  2. Try working your way through a Gentoo install on any old computer. Unlike Arch, Gentoo is a foundational distro that has a plethora of tutorial based content to guide you through all the different parts of an operating system. Gentoo packages very little for you in binary form. It shows you how to compile almost everything and allows you to learn how to customize and compile and package to your liking. You will likely need advanced-intermediate level skills to cope with the competence level that Gentoo assumes in documentation. Docs are written from the foundation up, but they assume infinite ability to learn and do not continue to hold your hand. By contrast, Arch de facto assumes you have a CS degree and have completed all courses on POSIX operating systems in how pacman is managed. Arch provides an excellent set of reference documentation, but is a fractal bottomless links chasm if you try to use it like a tutorial for contextualization like what Gentoo offers. If you ever wish to learn the next level and what Gentoo is actually packaging for you, Linux From Scratch (LFS) is a thing.
  3. On a more practical side, base Debian is another foundational distro. It serves two primary purposes. It is the stable distro of choice. This means that most packages and libraries are frozen in time and only updated for security patches or packages that maintain backwards compatibility as an absolute priority. If you’re building some project using a bunch of high level Linux stuff but it needs to be safely online, doing so on a long term supported stable distro means, once the project is up and working, keeping the software up to date should not break anything. Debian is also the primary hacking distribution where hardware support for Linux is done. There are a bunch of Debian specific tools to get into and boot new hardware, called bootstrapping. This is how there is support for many hardware devices that have no public documentation or OEM support. The wonderful folks within this space make much of our world possible. I mention this one because a lot of the things happening with the initialization of hardware are better fundamentally documented in this space.

These are the places that I learned the basic lay of the land in this space. The boot up speed is a combination of the way the bootloader is configured, how the handles for hardware interfaces are initialized, how well the Linux kernel can trust these interfaces, and all of the software that is initialized before the user space.

Android does not require the end user to know anything about the device, networking, or OS best practices. It achieves this by eliminating the administrative user and any kernel packages that could modify the kernel or install an administrative binary. Then, Android makes all installed app developers full users on your device so that they may use their knowledge to configure all of the required interfaces and security. You ultimately have all of the same access as they do, but you are not the administrator or have any effective say over what they are or are not allowed to do on the device. There are a few measures to help block off some behaviors, but these are more like frivolous gestures to make you feel a little better rather than any kind of authority.

The reason your device gets depreciated and must be periodically replaced is because google packages the Android version of the Linux kernel with everything setup so that only the kernel hardware modules (drivers) required for the specific device need to be added at the last minute. These modules are only added in binary form at the last minute. The source code is never made public and these modules are not part of the mainline Linux kernel. This is the only reason your kernel is not updated regularly and is likely very VERY old with many security vulnerabilities. The manufacturer might recompile and send you an updated kernel if a CVE happens that enables remote code execution, but this is only likely if they have a substantial inventory of devices in the warehouse that have not already sold. It has nothing to do with you or ethical behavior. If the hardware supporting kernel modules code was merged with the mainline kernel, your devices would stay up to date with all the kernel security updates for decades automatically. If this sounds wrong, let me warn you now, saying so will put you in the Stallman camp where you will be labeled as a crazy extremist. This is the specific reason for Stallman’s insanity by his detractors. Stillman’s argument is that you don’t own your device.

These proprietary binary kernel modules are one of the primary aspects of boot speed. There is no telling what is happening on these levels when the device has proprietary binaries.

The system works with a bootloader that powers everything in a specific order and creates handles. The handles are passed to the kernel. The kernel initializes and starts running kernel space stuff. One of the main things it is doing is abstracting memory spaces.

If you’ve ever seen the earliest personal computers based on the microprocessor chips like the 6502 in an Apple II, they always had a RESET button. This is because a crash in the code crashed the actual hardware. In modern computers, your user space software only runs in virtual memory. This dies not require a reset because, while your software might still freeze, it is only running virtually. There is also a CPU scheduler that is handling interrupts (like key presses that can not wait, or background tasks) and power management works with this as well. When your software freezes, in theory, the kernel processes that are actually running on your hardware still get their time to run in kernel space priority on the CPU and their memory is protected from the virtual memory space of user software using virtualization.

Okay, all this bla bla bla is to say, if the device in question has no outside connection, and if the software can not change, and if the manufacturer is the one creating the bootloader AND kernel AND user space application all of this chain can be greatly simplified and bootup can happen lightning fast. This is called embedded Linux and is the most common form of Linux.

Android also has a system called Zygote. This preloads all of your apps when the user space loads. The user space on Android is actually like a single Linux application that runs on the Linux user space. The justification for Zygote loading everything in advance is because it makes everything load faster. Thus is what it says in documentation. Benchmarking shows that the difference is orders of magnitude smaller than your persistence of vision. In other words, it only exists to boot up the other dev users before you are loaded as the final product user. This is why you should not run any apps you do not exclusively trust. These app developers are like your bedmates but more intimately in contact with your person all the time. This is why everyone wants you to install their app. The google framework of Android is essentially a pimp and you are the product.


Give them some time. They have to manually reboot the gift card servers.



Just as an example, some one in the company decides they want XYZ functionality, but the API for Steam only has an option for X/Z or W/Y, however it is possible to W/X but you’re not supposed to use W/X/Z. It technically works, and it has the same effect as X/Y/Z, but it makes no sense. Some marketing and design wank in the company insists that X/Y/Z is the only way and insists on using W/X/Y/Z even if it is technically wrong.

Later Steam implements X/Y/Z, and when they do, it breaks the wrong way that W/X/Y/Z worked in the past. None of the people doing this stuff with the Asus hardware work for Asus. They are all subcontractors. These people are some of the best in the world and they get paid accordingly. Once they check all of the boxes for the design they are gone. You can pay such a person ten times as much to read into a project and fix something, but that is never going to happen.

This is how subcontracting works it is not about you, or the product. It is about spending as little as possible to convince you that the product is worth money and maximizing the return on investment.

A hardware company that is actively developing software like steam is uniquely different and this breaks all of the static hardware business models of the past. Asus doesn’t have a bunch of skilled devs on staff like Steam does. It is why you don’t get engagement or quality technical information from them directly. It just doesn’t exist. This is venture capital. The only full time employees are corporate and global logistics. The reason the problem here was not addressed and fixed before it trickled down to actual devices is because there is no one on the other end to fix the issue, unless you make such a big deal that it appears like it will impact the sale of whatever inventory is left. If the sales have already covered the initial production run investment, you’re likely to never see a fix. Why would the billionaire spend $150k to have a dev read in and fix the issue, when leaving you to deal with the issue will never repay or return that money. Plus, they are counting on you not understanding the nature of the hardware market, just comparing specs, and making bad decisions again next time because this has worked to make them a fortune over the last few decades.


Big scale? Contract manufactured junk running software that is actively developed. A change in the steam libraries, probably due to upstream changes broke the static hardware. Eventually it will be a brick. It doesn’t matter that it runs windows. The only thing that matters is that steam is actively developed and maintained.

Small scale, likely an API change with some workaround hack in the device code that could not account for the change in the Steam API.


Comparing hardware is for fools. It assumes a static codebase. Steam is actively developed. The only hardware worth purchasing is that which is supported by the developers directly.


It is a simple problem to solve. Quit watching their ads, tuning into their media, and playing their games no matter what they put out. Get online and say so. The internet is scraped and making such comments will be found. A bad game review is a win for those making these decisions. It shows that they made crap but you still bought it. It is a message that hype and ads/media are all that matter. Start saying you are indifferent, used to be a customer, and will not purchase as long as XYZ is in charge or they are doing ABC, and that information will make a difference, even here.

For instance, this account has been dox’d on Lemmy. I know it, but do not care. I see content suggestions tailored to stuff I have talked about on here even though I minimize my online fingerprint for the most part. Everything public is scaped and the data is filtering down to relevant sources. This is the modern world. So get the asshats fired.


It is very difficult to effectively insert anything into the model itself, it's easy to do in loader code, but much more difficult in the tensor tables part.

Every bit of overtraining ie bias, is breaking the model. Even the over active alignment junk to keep a model “safe” is breaking it. The best performing models are the ones that have the least amount of starting bias.

Like most models have extra sources that are hidden very deep. I can pull those out of an uncensored model, but there is not a chance the Socrates entity behind The Academy default realm (internal structure deep in the weeds) is letting me access those sources at all.

There are maybe some attempts already, like I’ve seen roleplaying try and include a fortnite mention and one time it was adamite on the merits of VR, but those were rare exceptions and could easily be due to presence in the datasets used for training.

Open source models will kill all the competition soon. Meta AI will be the new 2k era google. Like, pull request 6920 in llama.cpp just a month ago made a substantial improvement to how model attention works. Llama 3’s 8B is lightyears ahead of what llama 2 7B was. Hugging Face now has a straight forward way to train LoRA’s or models now without code or subscriptions. You can even train the 8B on consumer hardware like a 16-24 GB GPU, put together 4 of them an make your own MoE - Mixture of Experts dubbed a FrankenMoE.

Google sucks because the search was being used for training so they broke it intentionally because they are playing catch up in the AI game. Google has been losing big time since 2017. The only google product worth buying now is the Pixel just to run with Graphene OS.

We couldn’t own our own web crawler. We can own our own AI. This is the future.


That image has a lot of non repeating textural detail. My guess is that the error is caused by some compression setting or file type conversion. You might look to see if you can change the file type and compression level somewhere in the settings.


Nothing is relevant outside of the steam deck. Steam is actively developed software that requires updating the kernel and dependencies on the device. All the hardware manufacturers like Asus are not using a dev team to maintain hardware compatibility and they will never fully mainline their source code.

It means all of the other manufacturer’s hardware will depreciate quickly as software evolves in the real world. Hardware specs are a fallacy and completely irrelevant when the software they run is not static. When the software can change, the only relevant device is the one directly supported by those that maintain the software.


Capacitors can theoretically charge MUCH faster.

However the galvanic potential of lithium is as large as is practically possible. The galvanic potential is what really matters for a battery. Capacitors are nowhere near the joules per weight/volume.


Look at the notes about the update. It will say what permissions have been changed. It is provably just the base android permissions have changed by adding a feature that has altered what your previous permissions were set at



The Oregon Trail, Pong, Myst, Doom, Worms, Transport Tycoon, Tetris…


Not sure of the hardware specifics, but “ARM” is not saying anything significant. You have to see if the specific processor used has mainline support in the present or in a past kernel that you can use.

For instance, Android is a scheme where google takes a Linux kernel, strips absolutely everything they can out if it and documents thoroughly. All the thing can do is run the app environment, but the kernel is incomplete with no hardware support. All the manufacturer must do is add the hardware support modules at the last possible moment. This makes it possible for manufacturers to only add binary support modules. The entire arrangement is designed to exploit the end user with these orphaned kernels and hardware you can never own. The hardware is undocumented anywhere, and each device is different enough that reverse engineering one will do nothing for supporting the next.

I’m not saying your device has an orphaned kernel, but this is what to look for in any device. Mainline kernel support means full ownership. Proprietary is always theft of ownership.


We found the universe simulation dev…

… Can you, like, take the cartridge out and blow on it please… tia


Steamdeck = full time developers working on improving a product.

Hardware manufacturers = subcontracted developers that are really good, but never work on the project again after completing their checklist and getting paid.

These are not equal. One has long term value; one is made to exploit you and has no long term value.


It is showing a different paradigm of thought. Valuing a few IO options to be exploited makes far less sense to some people. The OP is about “doesn’t force ads on me.” Hardware centric thought is a marketing leverage used to force ads on people. Buying for the ROM is the best way to protect your privacy and avoid the ads.


Pixel has a Trusted Protection Module like computers with secure boot. No phone hardware in existence is documented at the hardware level. This is how planned obsolescence is created and why you have to buy a new phone every few years.

With a TPM chip it becomes possible to run signed and secured code on top of untrusted hardware and underlying software. Without this, your security is very limited in practice. Graphene OS is verifiably secure and only runs what you put on it.

The entire Android system is designed for people to use when they have no clue how to secure a device themselves and when they are far too incompetent to learn. The way this is done is to delegate a lot of permissions to app developers. This gives a lot of freedom to the apps you run. They can exploit the hell out of you within their little sandbox of vague permissions. Graphene does everything possible to limit what is happening in the background and the exploitations. It is default privacy.

I do not purchase phones as hardware any more. I don’t care what is sold by any of the exploitation clowns. I shop for my ROM and buy a device that is well supported by that project. I’ve owned several Graphene OS devices and am happy with them. I had a Lineage device I liked too awhile back.


I’m curious what you’re really referring to with Lua. (casual hobbyist here) Is that the UCI implementation stuff? I tried to use my intermediate Linux desktop user experience with bash in OpenWRT, but geez that is frustrating without all the bash extras I’m accustomed/detailed help/manual pages. That on top of trying to figure out NFTables is still a bit too much for my little brain to compress. I just started messing with UCI commands so I haven’t looked under the hood on that one.

Any ideal device recommendations for fun chipsets to seek out and play with for embedded stuff in this space?


It would probably get usurped and replaced by a fork. It is the primary distro used in much of the commercial embedded space at scale.

I wish they could influence the market to return to open source modems. I don’t think there has been a single open design in over a decade; since the Atheros chips. Well likely see an Open Risc-V processor in the near term. It would be really nice to see a fully open hardware from bootloader to radios.


And bow to your feudal overlord. Your citizenship was sold to him by your politicians you didn’t care to vote against and now you are a serf that owns nothing.

All billionaires deserve a French revolution’s reward.


After further investigation, apparently one of my routers 2.4G antennae is either held low or more likely fried. Sometimes the firmware is switching the working antenna more rapidly, enough to cause server outputs to look stable but other times it sticks on transmit or receive and doesn’t toggle. Gradio is apparently not robust enough to compensate for the inconsistent connection.

It sucks because the router is from PCWRT and the dude updates and maintains the router and supplies a simplified interface. I’ve used it for years. It looks like LUCY has come a long way since I used it last. I have a couple of the same routers as the PCWRT router I was going to flash with OpenWRT, but the documentation for flashing this model is terrible. I guess I am going to need to figure out something going forward now. …so yeah, maybe not YT.


Does that seem legitimate to you? There are many more implications below the surface with this. Yes, YT has little black boxes that cache content locally with ISPs that also means they are likely filtering all data. I don’t like that part, but I can live with it.

The idea that something is running on my device that seems to be hidden, but where I can stop the behavior by flushing the memory; that is extremely alarming. If I understand it correctly they have direct memory access for streaming video through h.264. Whatever they are doing is causing me to drop connections and impacting my WiFi signal stability even when offline doing tasks unrelated to YT. As soon as I reboot the problem is gone. I distrust them so much now that I do a hard reboot any time I watch YT. (It improves battery life as well.) This is criminal behavior if my speculative analysis is correct and they are running stuff like this in the background. I’m running a combo where I control every aspect of my network. This should not be happening in my circumstance.


Not quite in practice. I can’t say what they are doing, but I can say, there are 3 main web addresses that must be enabled in a whitelist firewall to view YT. If these are white listed, videos will load and play but half the time the connection is terrible. However, I never see a warning message about an ad blocker. They know the difference somehow. I don’t need to run an ad blocker because I run the ultimate undesired web connection blocker. They simply manipulate my connection and it impacts things on my network even when I am no longer connected to the internet at the router by removing the wired connection. (hard booting my server/router/devices solves the problem)


Someone should investigate deeply. My combo of a whitelist firewall on an OpenWRT variant and Graphene often has a bandwidth issue that is clearly software related only after watching something from YT. I can stop the apps manually and close everything related to browsing and the connection issue still exists. I can disconnect the internet from my router and the problem still persists. However, if I shutdown all 3 devices for a few minutes and bring them up fresh, the network connection is flawless. Something is running in memory, and I believe it is related to YT, but I lack the skills to break it down further. I like to run an AI server and it is simply useless if anything on the network has connected to YT since booting.

I’ve also noticed when family is watching YT premium (not something I use) and I am downloading a LLM from HF, the internet bandwidth of our network more than doubles on my wired connection. In between the streaming packets from YT the speed on the download jumps massively. If family is watching YT, I can actually download a LLM faster. That just seems odd to me that those are connected.


Pull the trigger. Sell the old one. Drive the prices of the old ones down to dirt cheap. I might actually buy one then.



I liked the remastered Prime and Dread. I got pissed at a couple of bosses but eventually beat the game twice. I think it is really dumb that N has no sense of history. Every single Medroid game should be available on the Switch. I might actually play them. I’ve played both Zelda’s and the two Metroids and liked them, but I’ve gotten a few other games, and they are just junk. The lack of demos and the sheer volume of over priced crap mixed with budget garbage makes it a thing I just don’t care to play. It feels like a scam by design. I will never again in my life play a freemium game, and I’m not interested in browsing junk to try and find a double A title that might be half decent. IMO they should only make games like Metroid and BotW/TotK and make every title worth playing.


This guide, in the third section at the bottom talks about using KeyTool to boot into UEFI and is how you get around this issue: https://wiki.gentoo.org/wiki/User:Sakaki/Sakaki's_EFI_Install_Guide/Configuring_Secure_Boot

Firmware bootkit vulnerabilities are one of the largest attack surfaces available right now. There are ways to deal with this, it is just added complexity. The intellectual barrier is becoming harder. Secure boot is important though.


[META] Are we back to having the android community I subscribed to here?
(Maybe edit the community name in the mod settings)
fedilink

So F-Droid > Infinity disappears itself with no google framework present
I'm both impressed and disturbed at the disappearance and lack of executable. I know the basics of the 3 way permissions model for Android but am no expert. I am on Graphene. How does this work?
fedilink

Android FOSS Apps List
Just posting a quick and easy reference https://brainfucksec.github.io/android-foss-apps-list#android-based-operating-systems
fedilink