dogecoinbase

I think we can all understand the ways in which embedded advertisement in LLMs will be fundamentally different than view-based advertisement.

If you'd be willing to scan/post those I'd love to see them!

Many registrars allow renewal of domain names without authentication (you're unable to change any of the domain settings, however) -- some just let you do it, others it's a process, e.g. https://www.namecheap.com/support/knowledgebase/article.aspx...

41 meters is the height of a 13-story building.

My favorite read on the subject: https://scottaaronson.blog/?p=2756

lmao you posted moments before me! Leaving mine for posterity but everyone upvote this one instead.

Satire is already ahead of you: https://theonion.com/protesters-urged-not-to-give-trump-admi...

it's irksome to see tptacek having his patio11 moment for sure.

They claim full open source but for several years they did not release the server.

Specifically, they didn't publish the source for their server-side from 20 April 2020 to 6 April 2021 [0] while they secretly added a cryptocurrency payment system to which Moxie was a paid technical advisor [1], which Moxie denied they were doing in January 2021 [2].

0: https://www.androidpolice.com/2021/04/06/it-looks-like-signa... (source was published shortly after the publication of that article)

1: https://news.ycombinator.com/item?id=26715013 (comment from founder of MobileCoin)

2: https://www.theverge.com/22249391/signal-app-abuse-messaging...

Unfortunately no. The entire point of DoH is to bypass the ability of the users to prevent browsers from providing browsing habits to their owners.

I simply park my car on top of papers that I want to keep in place -- one less paperweight to buy.

But great news, we're on HN, so maybe jgrahamc or eastdakota can show up and explain why it's totally normal and fine that their product prevents random people from reading about the causes of natural disasters.

They are, but it's self-inflicted: https://sfba.social/@sysop408/110639474671754723

Lest anyone doubt that Twitter was idiotic enough to release code that would cause a race condition and result in its own users executing a DDOS attack on it, here's the network console readout from Firefox showing all the network requests blasting away.

Glad to hear Moxie's out. As a reminder, Signal didn't publish the source for their server-side from 20 April 2020 to 6 April 2021 [0] while they secretly added a cryptocurrency payment system to which Moxie was a paid technical advisor [1], which Moxie denied they were doing in January 2021 [2].

0: https://www.androidpolice.com/2021/04/06/it-looks-like-signa... (source was published shortly after the publication of that article)

1: https://news.ycombinator.com/item?id=26715013 (comment from founder of MobileCoin)

2: https://www.theverge.com/22249391/signal-app-abuse-messaging...

If a computational process could not complete before the heat death of the universe, does it have an output?

The lesson, then, appears to be that size of privacy organization does not have a correlated effect on effectiveness.

As the old joke goes, there are 10 types of people in the world, those that understand binary... and nine others.

It's to prevent DNS-based ad blocking (e.g. Pi-hole).

This is exactly correct. You have to call them.

What are the uses?

Right, the issue is that it's not possible to set file retention for individual channels/conversations, so if you want to have long-term file retention in some places and brief in others, it can't be done (additionally (in my experience, at least), people tend to believe that setting message retention will also apply to files -- it's not called out in the interface/etc).

Bear in mind that at this time, and for many years, data retention policies simply do not apply to uploaded files in a given channel (IIRC it does apply to global retention, but I'm not totally sure of the current behavior). There's a sensitive channel with a short retention period in a Slack for a company I do some consulting for and every few months I remind the admins that images/PDFs/etc that are uploaded to the channel are not purged and they should manually do it... but there's still stuff in there from 2016 if I do a search in:#channel for Files.

after all, you can never protect against someone making an entirely new device that just happens to look like an iPhone.

The specific threat being protected against (leaving aside the increased safety of iPhone users by making the stolen parts market untenable) is your phone, that you recognize and use as your phone and which contains your confidential material and credentials, having internal components swapped out while unattended.

I don't have a specific alternative, but I think that if it's not possible to be effective in a role, one should decline it. It's possible to be an effective SWE while still writing (and hopefully also sometimes fixing) bugs.

Security is not easy, and the entire field is not negligent - the problem is massively asymmetrically stacked against security practitioners, enhanced by poisonous attitudes like the ones expressed here.

Is remaining in a role in which it's not possible to be effective negligent?

Normal service providers normally remove violent/hate sites as a matter of course, which makes it not news. Cloudflare has set themselves up as a sort of refuge of last resort, for [redacted] reasons. Fill in the blank yourself.

We dismantle the service providers that provide cover for the forums in which DDoS attacks are advertised and purchased, like Cloudflare themselves.

CF no longer deserves the benefit of the doubt. See e.g. https://news.ycombinator.com/reply?id=32705613

Additionally, incentives exist for him to report things he himself did while at Twitter, for example: https://twitter.com/igb/status/1562072030010191880

[Mudge and Sethi] deprioritized Twitter's kernel & OS upgrade and encryption at rest initiatives.

(from Ian Brown, who deserves his good reputation as much as anyone I've met)

This is literally the business model. The owner of an IP address is responsible for the content delivered from that IP address. Cloudflare would like to have it both ways -- they get to multiplex sites behind their network infrastructure and accept money for the service, but not be responsible for the content that they deliver, because it originally came from somewhere else.