It's an Atlassian Statuspage style oddity, the title is too long for a single line and it's put an ellipsis and linebreak. But the ellipsis has overwritten the end of the content on the first line. Full title shows on the home page.
The entire post is clearly LLM generated. I get that a person clearly put together some thoughts, but prompting an LLM to 'turn this into a blog post' is the kind of low effort content I thought was not appropriate for HN.
At least bringing up the underlying method (restrict to contributors) has spawned the discussion about how that's probably a bad idea on the security side.
It's definitely a fake bait post, what they're describing isn't even possible in the way they said. The post and the OP comment replies even look LLM generated as well. They somehow have a good reason why every legitimate suggestion can't work.
The account was commenting on the satirical sysadmin subreddit yesterday, so they know what makes a engaging story.
LiveKit Cloud uses virtual compute and networking across multiple (USA based) cloud providers. DigitalOcean, Google and Oracle at minimum. They each have servers all of the world of course, but the controlling entity(s) parent companies are all based in the USA.
Latency shouldn’t be a problem, it's handled by a global CDN.
Proton including that part about geopolitical instability implies that Meet is does not fall under the USA's CLOUD Act - that would be wrong. The metadata of any Meet call could be handed to USA authorities, for example the participants date & time, source IP and useragent of each member. The call itself should be E2E encrypted.
Proton Meet relies entirely on LiveKit Cloud to run https://proton.me/meet/privacy-policy which uses virtual compute and networking with DigitalOcean, Google and Oracle.
I don't any signs that it's a bot, or that the comment was LLM generated. It's pretty safe to assume they made an alt to make that comment, as they didn't want to take a negative opinion towards a conservative author on their main. i.e. trying to avoid controversy.
I didn't immediately see a red flag that would make me discount all of their work. It's clear what the author's general opinions are. They're entitled to them of course.
I've had Windows Server VMs soft crash and hard crash on Azure. Some soft-lock and a restart via Azure gets them back. Some times the only fix has been to power off / deprovision - then power on again (i.e. a restart didn't fix it). It's not common, but I've encountered it multiple times. These are with operating systems that were created in Azure from their images.
OpenAI were already logging all the chats, it's just that if the end-user decided to delete their chat history - they would respect that at the time and also delete it server side (apparently). The court order mandated them keep the chat content even if the end-user wanted it deleted.
They were required to change the way their systems worked, to no longer respect a user's chat deletion request. That means a non-chat-logging company can of course be forced to change the way their system works, to instead log chats.
In the same way Apple can not only be forced to hand over back-doored access to UK users iCloud data (when Apple also hold a copy of the keys), they can also be forced to change the way their OS works to prevent the scenario where Apple don't hold the keys (preventing Advanced Data Protection from being enabled). The USA could force the same thing via the CLOUD Act.
I think we're expecting too much from an LLM generated article from a user that has been spending a lot of time spamming their content across multiple platforms and websites.
They mean to send an email in advance, with a message ID that would later be used in the target email. First email gets ignored, moved to spam, or not read yet. Then the target email gets sent with the predicable message ID, and gets bounced.
Comments on issues use the format
<[OrgName]/[RepoName]/issues/[IssueNumber]/[CommentID]@github.com>
A mitigation to this would be to take the combination of message ID and the sending domain and use that as the unique value, because message ID is not guaranteed to actually contain a domain label that's owned by the sender.
For example SendGrid's message IDs are <[RandomValue]@geopod-ismtpd-[Integer]>.
I don't think they're advising anyone create both a CNAME and TXT at the same label - but it certainly looks like that from the weird screenshot at step 5 (which doesn't match the text).
I think it's mistakenly a mish-mash of two different guides, one for 'how to use a CNAME to point to a third party DMARC service entirely' and one for 'how to host the DMARC record yourself' (irrespective of where the RUA goes).
It's an incredibly complex topic, and I do feel for people who are now seeing a massive disruption to the existing ways to monetise their own work (they should be able to live comfortably).
It's quite ironic that they used an LLM to write or at least entirely re-format their post, when their topic is about the impact these systems have on the ongoing sustainability of the humans behind the work.
I personally don't use LLMs and generative models, I find their output way too untrustworthy and their practice of mining the data of others unsettling. Not that anything on the internet can be inherently trusted anyway.