Something tells me that with how passionate these guys are this was probably just a crunch to avoid the unacceptable result of the project falling behind, but isn’t sustainable. They’ll burn out if this is what they have to do every time, and they probably know that and tried to avoid it.
Depends on what your definition of winning is. If we reach a state where it is literally impossible to run your own software without heavy hardware modification, which would exclude 99.9% of users, that would be like big tech winning in my book. That’s why right to repair is important, and we probably also need laws to prevent OEMs from disallowing the use of alternate OS.
@akc3n@lemmy.ml another new OEM, this one using ARM cores: https://www.indiegogo.com/projects/liberux-nexx--3#/
Seems like they are also trying to find their place, they just backed off from a pretty expensive desktop replacement device to offer a more reasonable phone. Maybe an OS partnership would also help them since they are currently rolling their own Linux OS…
For those out of the loop: https://news.itsfoss.com/organic-maps-fork-comaps/
Wow this is big news, Comaps is the fork of Organic Maps: https://news.itsfoss.com/organic-maps-fork-comaps/
Let’s be careful to remember that there are different levels of effort and understanding required for different levels of security and privacy. GrapheneOS has taken the approach of offering harm reduction, with sane defaults and options that allow advanced users to take near-complete control over their device (within the limits of the Pixel hardware). This is obvious by their inclusion of the sandboxed Google Play Store as a major feature of the OS, as it is much better than the situation on Google’s Android. It is also not installed by default, forcing users to at least somewhat educate themselves in order to install it.
Accrescent is right in line with this philosophy, and is also not installed by default. Of course if your threat model (or desire) is to achieve the highest level of online anonymity and to have a completely FOSS system, you should not use it… of course you probably shouldn’t use FDroid either, in that case, and should build from source. However, you are clearly in a situation where your threat model does not require those lengths, and FDroid is more of a principled choice.
I think its pointlessly inflammatory to call Accrescent “dangerous” just because it allows for non-FOSS software. Now if you want to criticize whether or not it is fulfilling its stated goals, that is another story.
Ah I see. One thing I mentioned was that they seem to be iterating quickly on hardware; maybe it would be worth a discussion with them to see if they’d be interested in trying to design a device with compatible hardware, specifically in order to allow GrapheneOS as an alternate option. Maybe they’d be more likely to entertain that vs other older OEMs.
Have you guys reached out to Nothing? Looks like they run Android, and are a relatively new company (founded by the former OnePlus founder) that is just starting sales to the US. Maybe an angle GrapheneOS could take is to be an alternate OS install option, they are very focused on growth and attracting the privacy and security community might benefit them as they aim to squeeze out more ROI. They also seem to be cranking out new phone designs at a pretty good rate, so perhaps they could accommodate hardware requests, who knows? business@nothing.tech to inquire
CIA surveillance birds 😱
For accessing reddit behind a vpn there is a very reliable system of frontends. Here is the instance I use: https://redlib.freedit.eu/
https://github.com/jersou/mouse-actions
It’s recommended by the easystroke dev too: https://github.com/thjaeger/easystroke/wiki
The two have completely different goals, and SimpleX’s goal (anonymity) comes with difficulties such as not having typical “accounts”, which means no true simultaneous multi-device support.
GrapheneOS devs have a problem with this guy https://discuss.grapheneos.org/d/20165-response-to-dishonest-attacks-on-the-grapheneos-project-by-robert-braxman
This is great to see, and should definitely be front and center for new users! At first glance it seems to have good coverage of the things people run into when working with user profiles.
One thought: when I moved to GrapheneOS, I did not understand how it related to my threat model. I attempted to use multiple profiles, as this is a feature that many people who use GrapheneOS value. I had no concept of my real risk, and tried to segregated FOSS from non-FOSS, etc. This IS actually a bit difficult for the layperson vs stock Android. Things like notifications and app installation work differently at the end user level; e.g., use FDroid vs Google Play, no FCM notification functionality and having to manually configure a replacement.
However, the layperson, using a single profile and sandboxed google play, is already better off than any project out there from my understanding. For adoption, that’s what I would be advertising for GrapheneOS. It just needs a one page explanation of the simple features and advantages for the person coming fresh from stock Android, and avoid (on that page only) getting into the tools for more advanced threat models.
Vesktop is great. However, with the Discord IPO looming (https://www.ign.com/articles/discord-is-reportedly-exploring-an-ipo) it is definitely time to abandon ship.
So it looks like the protocol was audited, but I don’t know about the app or servers. https://www.pindrop.com/article/audit-signal-protocol-finds-secure-trustworthy/
Yeah why is the focus on him using chatGPT vs yet another mentally ill person getting killed by a cop…