Hacker Newsnew | past | comments | ask | show | jobs | submit | cdesai's commentslogin

Google is usually pretty quick to upload source code to AOSP after release on Pixel.

Android 16 has been highly unusual though, with the only source code release done 3 months ago in June, when it was initially released.

https://android.googlesource.com/platform/frameworks/base/+r... - only two "16.0.0" hits here, both from June 10.


I remember fondly reading that (and about his work in general), which is why when I saw the video thumbnail I immediately had a feeling "wait no it can't be".

Thanks for the link!


How can they do that with HTTPS though?

HTTP sure they can happily MITM and redirect, but with HTTPS you need a valid cert.


Your browser shows a TLS warning saying that the certificate doesn't match. If you override it, it brings you to that page.

This is not a DNS block, the IPs are owned by Google, Italian ISPs are forced to forward the traffic of a blocked IP to AGCOM's servers.


DNS.


Connecting with https prevents any DNS poisoning, unless the ISP managed to get a fraudulently issued certificate or a MITM root CA installed on the end users' devices. Neither seem likely.


It's not poisoning, it's blocking.


The 24h timeline sounds very tight. I wonder how much they'll be able to stick to it.


Full title: ‘Everything LTS’ – Canonical will build distroless Docker images to customer spec that include upstream components not packaged in Ubuntu, and fix critical CVEs within 24 hours, supported on RHEL, Ubuntu, VMware or public cloud K8s for 12+ years.


It's a fork of the chromium update engine.

https://android.googlesource.com/platform/system/update_engi...

Many Android specific changes though.


> If we're speaking of FAKE_SIGNATURE.... No it doesn't? If implemented properly

We've always heavily restricted as well.

https://calyxos.org/docs/tech/microg-details/

> Really, please tell me in which threat model does using microg hinders security, maybe we can find a fix. So far, I've never heard any.

I keep asking the same to anyone bringing this up. We'd be happy to even submit patches to microG for any issues found and reported.


Unfortunately that is currently not supported since Android Auto is a proprietary app and needs system / OS level privileges to actually work.


Sigh, always.

The users have been banned, it's just that no mods were around at that time.

We strictly don't allow any GrapheneOS talk at all on our channels due to this drama. I don't know what else to do.

See: https://view.matrix.org/room/!aPqEsAdWuysydZNCic:matrix.org/...

Not the thing one wants to wake up to, but what can you do.

Disclosure: CalyxOS lead developer.


I just wanted to take a sec and say I've been using Calyx for eight or nine months now- sure, there was some pain that came in the first month from adjusting to a new phone OS (there always will be when being a Samsung lifer trying something new to me), but overall I've been very pleased with it. Thanks for all the work you and the team have put into it :).


You're claiming no mods were around when Nicolas Merrill was right there in the middle of the conversation? It's blatantly not true. Screenshot is here for everyone to see:

https://twitter.com/DanielMicay/status/1511639628637511681

You shouldn't lie about things that are so easily disproven. The main thing you disallow in your rooms are people defending GrapheneOS against your misinformation and libel. Those are the people who get quickly banned. You're frequently the ones engaging and spearheading this. You only ban people when it's not going your way and then you clean things up after the fact just as you're doing here. The fact remains that you have NOT banned the people openly involved in highly abusive behavior, and you're directly part of it yourselves too.

Nick is frequently one of the people directly involved in bullying and libel targeting me along with pushing blatant misinformation about GrapheneOS. The incredibly toxic behavior directed towards us comes from the top. Nick, you and Techlore have orchestrated this. You're directly responsible for the highly abusive behavior directed towards me and you're going to be held accountable for it whether you like it or not. You act as if you're trying to stop it but you're more focused on removing the messages of people countering vicious attacks on us than you are on stopping the abuse you've regularly engaged it and encouraged. It did not become what it is now without the direct support of the Calyx organization and CalyxOS. Everyone tied to the organization is tainted by it and it will follow them.

I have plenty more screenshots to post on Twitter if you folks would like showing extremely abusive behavior from Nick. I can show both you and him supporting the abusive behavior and raids towards us. Most of these attacks come directly from the top and are heavily based on the libel and misinformation from you, Nick and Henry. The legacy of your project will be your abusive behavior. It's how you're going to be remembered. It's not as if you're doing anything beyond marketing and misleading users beyond that.

Eventually you folks are going to pay the cost of your nasty character assassination campaign and misinformation war both to promote your project and to harm GrapheneOS. You don't even do remotely the same kind of work. From the start, all you've done is try to take advantage of an unfortunate takeover attempt on our project. The attempt at undermining us was happening even in your early days when we were helping you and telling people about your project.

This is never going to go away and your continued escalation over the past year and especially the past few months is not going to go unanswered. You think you can get away with it because all we've done is talk about what's happening. It's not going to remain that way. Any project, conference or organization where you're involved and who you work with inherits all of this baggage going forward until you make any real attempt at reversing this and repairing the harm that has been caused. It will follow you around for the rest of your life. You will always be the people who engaged in extremely abusive behavior towards someone which a dozen people in your room who you have not banned have openly said is aimed at trying to drive me to kill myself. You were openly against even banning Kiwi Farms. There is nothing more that needs to be said.


Geez, it's one message, there was more after it, when no mods were around. I can't speak on behalf of Nick of course.

I woke up, saw it, and banned those people. We don't allow people to do this for any project, ever. What else can even be done, there's thousands of people on the channel, and moderation is hard and time consuming.

People on the internet say things, you can't keep attributing it to us always.

Somebody joins our channel, your channel, posts on twitter, etc - how are we responsible for what they say anywhere else, we don't control their speech.

Learn how the internet works - this has been the crux of the problem all along, you attributing things to us, and then using that as justification of your behaviour doing exactly what you're accusing us of doing. All those threats :(

HN is not the place for this conversation either.


Nick and you are both openly involved in bullying and libel targeting me along with spreading misinformation about your product and our project to benefit yourselves. This has been a consistent behavior from both of you for a long time.

You frequently make false accusations against us, and that is a major part of your contribution to the libel and harassment targeting us. You fabricate stories and pretend as if you're victims of some indescribable toxicity. Debunking your claims and telling people about your abuse is not itself abuse or toxic.

Moderators across a bunch of different communities are increasingly noticing that every post about GrapheneOS is brigaded by people spreading the inaccurate talking points you have largely come up with yourselves.

You've invested heavily in character assassination and libel against me including contributing to extreme harassment and bullying perpetrated by core members of your community that you openly talk to on a daily basis. You're doing it right here, falsely claiming you folks haven't been extensively involved in it and denying what people can plainly see from the logs.

> Geez, it's one message, there was more after it, when no mods were around. I can't speak on behalf of Nick of course.

It's not one message. I don't know why you continue lying about this. It was hours of discussion where Nick was frequently involved, and where he openly encouraged and talked to people who were at the same time harassing us and raiding our rooms.

You only care about getting your community members to bring their high level of abusive behavior and toxicity to our rooms and platforms like this instead of yours. You're more than happy to allow dozens of people involved in actively harassing us, waging a misinformation war and spamming our rooms to be members of your community. You're more than happy to regularly chat with folks who have repeatedly told me to kill myself and engaged in severe harassment and libel. We have archives of evidence to prove it, and we're actively contacting other organizations and conferences to share that evidence. Persistent abusers like yourself and Nick do not belong in this industry. Again, this is the path you chose working with the people you did in such an unscrupulous way where you built your project on misinformation, libel and harassment.

We are not attributing the actions of other people to you. These are your actions. This is the path you chose and continued to double down on. You've built a highly toxic community engaged in these attacks across platforms. You've built your community with partnerships with highly abusive people like Techlore. You're involved in these attacks yourself, and part of that is pretending that you aren't and that we are somehow the aggressors for being targeted by you in this way and talking to our community about this.


That makes sense, the apps are downloaded from mirrors and it automatically falls back to another if one isn't reachable


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: