Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
strcat
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
34 ms
·
451.
▲
by
strcat
1y ago
See the response at https://news.ycombinator.com/item?id=44583672 .
452.
▲
by
strcat
1y ago
The posts were made from our project account based on the consensus of our team. It was written and reviewed by multiple people prior to posting it. We made it obvious we were talking about Ukraine while not explicitly saying it to avoid in
453.
▲
by
strcat
1y ago
> What we're talking about is the GrapheneOS account claiming someone was conscripted, and claiming that it's an "existential and defensive" war. Our lead developer was conscripted. > I assume this is basically tru
454.
▲
by
strcat
1y ago
It has nothing to do with Israel. See the response at https://news.ycombinator.com/item?id=44583672 .
455.
▲
by
strcat
1y ago
See the response at https://news.ycombinator.com/item?id=44583672 .
456.
▲
by
strcat
1y ago
See the response at https://news.ycombinator.com/item?id=44583672 .
457.
▲
by
strcat
1y ago
> I will follow their wishes and not specify the specific war or side, but this comment gives me all the information to figure it out. The primary goal of making it public was getting him diverted away from infantry to a role related to
458.
▲
by
strcat
1y ago
> Samsung Flagships and Iphones seem to have similar level of security engineering in them (Pixels use Samsung CPUs essentially) but aren't open to the required degree for third party roms. Samsung has devices providing all of the m
459.
▲
by
strcat
1y ago
GrapheneOS has no specific requirement for the Titan M2. It requires a secure element providing the standard AOSP secure element features which are provided by other devices such as recent Samsung Galaxy devices. Fairphone doesn't prov
460.
▲
by
strcat
1y ago
GrapheneOS has no specific requirement for the Titan M2. It requires a secure element providing the standard AOSP secure element features which are provided by other devices such as recent Samsung Galaxy devices. Fairphone doesn't prov
461.
▲
by
strcat
1y ago
> Doesn't the ASB get published at the same time as pixel updates? So by definition it's up to date. Android Security Bulletin are standalone backports of High and Critical severity security patches to older initial yearly rele
462.
▲
by
strcat
1y ago
Fairphone no secure element, no hardware memory tagging and lack the expected security patches. It's missing some of the other features too. Our list is about hardware requirements and firmware/driver requirements, not the AOSP po
463.
▲
by
strcat
1y ago
The vast majority of Android apps work on GrapheneOS. There are tap-to-pay apps including PayPal, Curve Pay and many European banking apps which work on GrapheneOS. > that is after installing the optional play services, reducing the priv
464.
▲
by
strcat
1y ago
GrapheneOS can also be purchased preinstalled on devices regardless of what you think about the web installer.
465.
▲
by
strcat
1y ago
GrapheneOS is sold preinstalled on devices. People do not have to install it themselves. It's also far easier to install than a desktop OS via https://grapheneos.org/install/web . The post from Purism is highly ina
466.
▲
by
strcat
1y ago
Apps have to choose to block using a non-stock OS and only a tiny minority of them do it. GrapheneOS bypasses it for many of them and we intend to get it fully resolved. Regulatory action is in progress for this in Europe already and it wil
467.
▲
by
strcat
1y ago
GrapheneOS can be purchased preinstalled on devices and https://grapheneos.org/install/web is far easier than installing a desktop OS.
468.
▲
by
strcat
1y ago
You wouldn't have this problem with a stock OS Android device either. It's worth noting that you're using an insecure end-of-life device and are missing a large number of High and Critical severity privacy/security patch
469.
▲
by
strcat
1y ago
No, Murena sells devices with /e/OS which is fork of LineageOS which drastically rolls back privacy and security compared to it. LineageOS itself rolls those back compared to the Android Open Source Project but not nearly as much
470.
▲
by
strcat
1y ago
If the web install guide only had to cover installing from macOS, ChromeOS and Android, it would be significantly simpler. Most of the complexity in the install guide is to work around issues with desktop Linux distributions. People do not
471.
▲
by
strcat
1y ago
Our web installer is more safer and easier to use than Google's web installer which doesn't include important checks or information. Making a fancy wizard interface instead of having it as buttons integrated into a page is more ae
472.
▲
by
strcat
1y ago
Including GPLv3 code within a GrapheneOS release would make GrapheneOS more restrictively licensed than the Android Open Source Project (AOSP). GrapheneOS is meant to be usable everywhere AOSP can be used. It's meant to permit making a
473.
▲
by
strcat
2y ago
You can see that we're on the latest 6.1.134 and 6.6.87 now because Greg KH caught up the Android GKI LTS branch to the kernel.org LTS branch. That will be included in our upcoming OS release in the next couple days. We ship GKI LTS up
474.
▲
by
strcat
2y ago
In general, we don't remove functionality. An exception is if something is explicitly insecure and has no reasonable use case. We removed support for instant apps, booting a Google signed GSI, adding new users while locked and pattern
475.
▲
by
strcat
2y ago
That can be done without root access and likely also without needing network ADB via device management.
476.
▲
by
strcat
2y ago
> You are right, it may have been a unusual bug that hardly occurs, but it definitely happened to me. This doesn't mean that it was a GrapheneOS issue. > I also agree that having a unlocked bootloader is a security risk It's
477.
▲
by
strcat
2y ago
Kernel drivers for all of the main Android hardware platforms are fully open source. It's the userspace libraries/services which tend to have a lot of code that's not open source. At least for Snapdragon, that's shared w
478.
▲
by
strcat
2y ago
> Do you also contribute your fixes back to the upstream projects like the upstream Linux kernel, AOSP or Google? We've made significant contributions to the Linux kernel, AOSP and Pixels in the past. We continue doing it to the ext
479.
▲
by
strcat
2y ago
> The bigger problem came from apps that threw null point exceptions on startup when probing for google play crap. > > The following failed for at least one week over a two month period: parkmobile, multiple ev charging networks, u
480.
▲
by
strcat
2y ago
Only providing the Pro mode in Pixel Camera on the Pro devices is one of the only ways they're artificially segmenting them via software. The AI model differences are largely based on real differences in available memory and that doesn
More ›