Some people have some bizarre obsession with having absolute and total control over the placement of every single last character in their document while simultaneously not caring about the fact that this placement is sometimes not reproducible and randomly becomes diseased.
My most memorable MS Word experiences are all the times I accidentally put my document into a weird state and didn't notice something was wrong until I've spent 3 more hours on it, at which point I was forced to re-create the document by copy pasting text into an earlier copy.
And the only reason I knew something was subtly wrong was because the weird VB extension I was required to use would stop working correctly. Basically this would happen when some random key element of the document had ended up with a very subtly different style. If I didn't have to worry about the VB extension breaking, I'd just have a document with some weird bug somewhere.
If I wanted a professional looking document, I would use some modern LaTeX variant maybe with Pandoc to generate most of it from something more restricted like Markdown.
If I wanted total control over the content of a page, I would use some kind of graphical publishing software with text and vector graphics.
I have zero idea what kind of Stockholm syndrome you must have to think that Microsoft Office (or any other similar WYSIWYG editor for that matter) is power user software.
It has lots of features, that's for sure. But the features form a Jenga tower. That makes it a toy.
FreeBSD and OpenBSD docs are great, but let's not say they're the pinnacle of docs. I like them a lot more than docs for the average Linux distribution. They're even more polished than Arch Linux wiki. But they still have room for improvement. And improving the Arch wiki is easier in my experience.
* Wiki-style "HOWTO"-based that helps you solve a particular problem (Arch and Gentoo wikis showcase this style well)
* Reference documentation that reminds you how you solved a problem (man pages are great examples here)
* Comprehensive documentation that truly documents the system, but can be a bit more obscure if you're not reading it "cover to cover" - textbook style (This is the older "original" software documentation type, which the BSD docs are an example of)
You are either talking about a license nobody is using (at least I've never heard of it) or misconstruing what the AGPL obligates you to do.
I am going to assume it's the latter.
If you in your house take an AGPL program, host it for yourself, and use it yourself, nothing in the AGPL obligates you to publish the source changes.
In fact, even if you take AGPL software and put it behind a paywall and modify it, the only people who the license mandates you to provide the source code for are the people paying.
The AGPL is basically the GPL with the definition of "user" broadened to include people interacting with the software over the network.
And the GPL, again, only requires you to provide the source code, upon request, to users. If you only distribute GPL software behind a paywall, you personally only need to give the source to people paying.
Although in both these cases, nothing stops the person receiving that source code from publishing it under its own terms.
Meanwhile the solution to this problem in the UK is to reaffirm that you are in fact guilty by default unless by happenstance you are determined not to be by an unfairly chosen panel of blind and deaf mice.
GrapheneOS currently doesn't ship Play Store or Services OOTB. They install as normal apps (albeit with GrapheneOS providing support code to make the fact that these things use/expose custom privileged APIs work correctly). I don't know if the Google TOS would prohibit that, at least I am not aware of any enforcement action against GrapheneOS in this regard. GrapheneOS also doesn't have Google's blessing, meaning some apps like Google Pay won't work on it. To get this, you need to apply to be an OEM.
Really Motorola doesn't need to sell a GOS phone. Motorola just need to sell a phone with the right hardware security features, open source/upstream their Android/Linux patches, and give users the ability to run GOS.
Hopefully they can then give you the option to buy one with GOS preinstalled, but even if they don't. It will be sufficient that it can run GOS.
Unlike Windows, nobody feels they're paying an inherent tax when buying a stock Android phone. I'm sure nobody will mind.
The hard part will be actually supporting the phone for long enough.
GOS is reliant on Google's open sourced Pixel android releases up to and including the 9 series. This is because GOS doesn't have the resources to handle that entire side of things. But I guess part of that is also that GOS doesn't have access to the necessary information to do that stuff properly either.
That's fair, this would still be a valuable development even if Motorola doesn't end up shipping devices with GrapheneOS preinstalled, but if they did I think there's a lot of potential for them to enter the mainstream. A device with GrapheneOS without any [major] caveats (like Play Integrity API, Google Pay not working) would be a game changer.
I can't see such a GrapheneOS existing without explicit Google support. And I don't think Google would support something like that unless they suddenly decided to actually not be evil again.
Google's hardware is just hardware. It is not locked down like the hardware of many other manufacturers. Moreover, it's the only such hardware which also allows you, the user, to lock it down for your own security. GrapheneOS is not just focused around avoiding Google, it's more accurately focused around security and user choice.
The goal is to give you the option to avoid needing to rely on Google's spying or services while not having to compromise on security.
None of these other solutions regularly get included in Celebrite's documentation as being an explicit benchmark of their software's ability to break into phones. And that's almost certainly due to the fact that unless you leverage hardware security features like what GrapheneOS (and stock Android on a Pixel, and iOS on an iPhone) utilises, you have no chance of going against any actual adversaries.
And I'm not just talking about state actors here, even drive-by opportunistic attacks are likelier on a random other phone running some other Android build.
So yeah, you are running Google hardware, that doesn't make you "googled". It's just a sad reflection on the reality of the hardware landscape. If you want the same security as what GrapheneOS offers, you will currently need to use a Pixel.
I'd be curious to see what comes out of their Motorola partnership though.
Why are we degoogling, for what purpose? I couldn't care less about giving them what likely amounts to ~10€ of margin per year on the hardware sale. What I care about is not giving them data which is worth a lot more than that, and to take back control over my device.
When you go with an alternative you lose superior privacy and security offered by GrapheneOS and you just end up leaking more data back to Google and other ad-tech companies than you would otherwise, negating any benefits several times over.
I think it’s very valid. I want to be hardware-independent, not only OS independent. I need graphene to work on a fairphone, jolla phone or whatever other alternatives there are. E/os can do that (to an extent), Graphene can’t for probably very good reason, but still: It‘s not an alternative then.
If you have something which contains pointers, you should have a destructor function for it, which itself should check if the pointer is not NULL before attempting to free any fields.
We are talking about C. A destructor function in C is a function that gets called when the library gets unloaded. No you shouldn't have a destructor function for it.
Imgur isn't blocked, they are blocking the UK. It has to do with their infractions regarding the GDPR. They blocked the UK to avoid getting fined any harder.
Google doesn't have any magic way to do instant notification that nobody else has access to. The only thing they have access to in this regard is disabling any battery optimisations without triggering warnings.
Notification and battery performance is on par with google's solution except when an android build does dumb things to prevent the background activity, in which case notification performance gets worse and battery draw gets worse (not sure why exactly, it's just a common issue in these regards).
Well, there is an advantage, if everything is using the one service then you only need to have one thing alive to check it, so each new app is "free" if you already have push enabled (assuming that push notifications are rare enough the activity isn't the cost), as where each app doing it themselves is going to cause more battery use, so it isn't directly equivalent.
However, it also isn't a big deal, at least in my experience, at least for ntfy.sh.
My most memorable MS Word experiences are all the times I accidentally put my document into a weird state and didn't notice something was wrong until I've spent 3 more hours on it, at which point I was forced to re-create the document by copy pasting text into an earlier copy.
And the only reason I knew something was subtly wrong was because the weird VB extension I was required to use would stop working correctly. Basically this would happen when some random key element of the document had ended up with a very subtly different style. If I didn't have to worry about the VB extension breaking, I'd just have a document with some weird bug somewhere.
If I wanted a professional looking document, I would use some modern LaTeX variant maybe with Pandoc to generate most of it from something more restricted like Markdown.
If I wanted total control over the content of a page, I would use some kind of graphical publishing software with text and vector graphics.
I have zero idea what kind of Stockholm syndrome you must have to think that Microsoft Office (or any other similar WYSIWYG editor for that matter) is power user software.
It has lots of features, that's for sure. But the features form a Jenga tower. That makes it a toy.
reply