They are correct. It only means more work for future devices, makes the initial port to a device slower. But then, once things have been figured out. It becomes just as fast and reliable as it was (unless what I said earlier: Google setting things in a very different way in a major update (for example, moving to Fushia, which has been abandoned)
I agree, but it’s more complicated than that: They have removed the device tree for pixel devices from AOSP and using the device tree of the basic virtual phone in android studio instead. That brings the pixel 10 family (as well as future android pixel devices) to the same level as many other phonemaker’s devices as far as making roms is concerned. So not all hardware will be documented, many drivers will need to be rebuilt. The pixel line up to the 9a is not affected because older device trees can be used (until Google wants to mod the way drivers load or add API’s).
It’s Thunderbird… Of course they release the code! How would it even exist without releasing the code?
BTW: K-9 is also Thunderbird.
Pixel 10 are set get quite powerful GPUs with raytracing etc
Google is starting to use DRM on all it’s videos so that only the official youtube clients on devices and big browser brands can play them. It also kills all the systems like invidious.
I mean the chips cores being 100% Designed by AI using Alphachip (which has been open sourced by Google) or other AI only chip designing tools instead of using off the shelf ARM or RISC cores.
I don’t know how they spent so much time with Samsung, especially since TSMC is accostumed to using alphachip for the dimensity line, the same AI chip designing tool Google uses for it’s NPU’s. Iwonder what it could mean for the future of chip design, is the ARM architecture about to be rendered irelevant by AI.
It’s not fdroid that doesn’t make it easy to insyall apps that are open source but not FOSS, it’s the licence of the non gpl open source softwarebthat usualy bans modifying, building and redistributing the code. It’s not foss, it’s just viewable source.
Because in the main repo of fdroid, the apps code is quickly eyed then packaged by the fdroid team from source (plus a quick virus scan. Google only does reputation check and use virus total (their android anti-virus and anti malware software), yes, the same virus total you can access as an app or webpage.
You know, games can be great tabletop too, strategic, tactical, RPG, it’s all there + you get to meet people you wouldn’t have met IRL because, like online gaming, it unites people from different walks of life. Great friendships are regularly made around gaming boards and those friends don’t need software to talk too. Yes I know, some games require figurine armies but you can always find someone who’ll be happy to lend you an army for a game and there are whole second hand armies sold.
Paid builds. You get Access to the source code but you can either build yourself or pay a small amount to have a packaged built and updated whenever.
I also like the twice a year nag screen thunderbird or Wikipedia uses (KDE was right to start doing it too, in my books).
I don’t believe a small donate button in the “about” section of the settings screen is of any use.
https://m.slashdot.org/story/336593
https://www.hardenedbsd.org/~shawn/DEFCON-25-Ilja-van-Sprundel-BSD-Kern-Vulns.pdf
I doubt it changed much ant it sounds logical too.
Or morally better than breaking TOS, use a FOOS alternative like Jellyfin.
Pcloud will probably go this way.
Sms was from a time communications weren’t done over IP, RCS or iMessage use the IP protocol, RCS could be implemented by the telcos but isn’t because , unlike SMS, it can also be implemented by anyone with a server with a connection to the internet but as RCS is an open GSMA telecom standard, it is implemented within all modem chips by phone makers, even Apple has a Qualcomm modem chip with RCS management included. I reckon it needs a few extra features in the basic standard such as E2E encryption, chatbot capabilities, malware and spoofing protection, maybe Google could help there as they have introduced those into their Message app and could disclose their code, but they are obviously trying hard to create a walled garden too… The solution could come from Meta as they seem pretty keen to advance on open communications (Threads interoperability with Mastodon is a demonstration of that policy)
Android users get to use the default messages app, with the whole e2e encryption, reactions, full sized photos etc… SMS is used for advertisements, and sending messages to iphone users… SMS is only used by old people for 2fa as 2fa apps usualy have superior security and are now systematically prefered by companies.
Both iphone users and android users need to download an extra app if they want E2E, full graphic images and videos, reactions etc…
Just as people aren’t content with iWork and usually download Office because it works the same and can be read with the same formatting everywhere.
I’ve got another gripe with the bluetooth stack on android: there is no order of device to send telephony to. I never want to listen to music or answer the phone calls on my smartwatch whenever the car or the earbuds are switched off. But i still want to be able to pick up an emergency call from it whenever both are not connected. Puting in a priority order, within which the phone would be, could allow me to make and pick calls from any devices while automatically switching to the phone when the two other forementioned devices switch off.
They couldn’t make a Limited Edition Ultra Premium Pro Design, so they went with the cheaper stuff.
The question, as always is which sony/canon DSLR they used to actually take the photos.
Sorry realme but on that specific point: there has been too much gaslighting from big and small manufacturers. I’ll wait until the reviews are out.
RMS warned of this a bit over 20 years ago. This is why you should get Free and Open source software and not Open Source Software. Preferably with a GPL licence which allows you to download, run, read the code, modify it and share it. Open source can mean you only have the right to read the code and signal to the dev code you’ve saw that could have been better or errors you saw.