firefoxd

With the new wave of ads on mobile, the ones with the "next" button, I gave up. Instead I use the app to find videos and copy them to pipepipe.

Maybe the curated list can be exported to load on other apps.

This thread reminds me of the time I was trying to learn meteorjs and people ask me if it has html5 shims. I google it, then I get asked how does it handle state, and if it supports functional, i google... Does it hydrate the dom? What about shadow dom? Let me goo... Does it have hooks?

Anyway, I just learned what abliterated means and it might be obsolete by tomorrow.

Edit:

> An abliterated large language model (LLM) is an open-weight model modified to remove or dampen its built-in safety refusals without requiring full retraining or prompt jailbreaks.

Not to brag*, but that's what I've been doing since 2013 on my php blog [0]. It was actually the result of a hn warm hug of death. My CDN is just a separate webserver serving all static assets using nginx.

Both my css and js are dynamically minified and included in the html depending on which component is loaded on the page.

[0]: https://idiallo.com/blog/handling-1-million-web-request

* I am bragging

With php2shell going mainstream, to the point that random friends who happen to know I'm a programmer, consult me to understand the extent of it, I think they succeeded with their doomerism message.

When we find a bug, we patch it. When we find more bugs, we patch them as well. That's what happened here. Sam is telling us, "we found bugs, it's over" and the general public swallowed the frog.

I mean, there is the bbc interview where they invited a cyber security expert who said he didn't know php existed before the the news broke out. The general public doesn't see that gaff.

When we reach that fabled intelligence, the AIs will simply answer "No" to these kind of questions.

That's already happening. And we call it AI slop.

Not telling you this time, Mr. Bot

It's the content of the page, the raw html, that is replaced with a zipbomb. Example: https://example.com checks if you are a malicious bot, depending on the result, it will send you gzip html or gzipped bomb. So that can't be swapped or redirected to a CDN. The bots would simply ignore the redirect.

It worked fine... on a small scale But it's one thing to swat flies versus fighting swarm of yellow jackets. Serving a 1MB file a million times a day on a small digitalocean droplet is not feasible. Let's just say it didn't scale. And AI bots usually come with beefier machines, and recover faster after a bomb.

Last year, I wrote a post about how I use zipbombs to deal with bot traffic [0]. It went mega viral over the web, and I regret it. My server was completely overwhelmed with bot traffic. After months of dealing with it, I had to find a better strategy then keep my mouth shut.

[0]: https://news.ycombinator.com/item?id=43826798

Yes, we use zscaler. It even included the list of AI prompts I've written and in-app activities.

Once I had an issue where I had to request access to a 3rd party vendor URL from my work machine. IT was telling me that I already had access, and that I had accessed the URL several times. Weird, because I was getting a dns resolve error. To prove that he wasn't making it up, the IT guy shared his screen with me.

Ever since I saw his screen and the level of details in my activity log on the work machine, I don't even access example.com on their device anymore.

I'm sure this workers already has invasive tracking software on her work machines. Now the company was just trying to fire her without it counting as a layoff.

That was a perfect execution. I almost saw a Kojima Game by Hideo Kojima title. The only thing missing was the dialogue at the end of the credits, where Xero says that "Afghanistan is where the answer lives."

Couple months back I wrote [0]:

> “You have the right to remain silent. Everything you say, do, or generate on this device can and will be used against you… Would you like to create an account?”

[0]: https://idiallo.com/blog/the-right-to-remain-silent

Had something similar with my TV remote. It was helpful with a neighbor who loved to keep his volume annoyingly high.

https://news.ycombinator.com/item?id=46848415

Everyone finds their own use case acceptable. It's the way others use it that's terrible.

Ps: I'm very tired of the all lowercase flex.

People expect a binary response, is it AI generated yes or no. But it's more complicated than that. For example, if you see an emdash, it's probably AI generated. But it can also mean the author used it for fixing grammar or tenses. LLMs can't help but try to help. The same for it's not X, but Y. Sure it's a known pattern, but it's not like people don't use this trope all the time.

In my experience, Pangram is great for detecting an author who is trying to pass someone else's work as theirs, or if they are tackling a subject they have little to no knowledge in.

"We own the glass" that's what really stood out to me. I can still disconnect my TV from wifi. But what scares me is when every device comes with their own esim and cellular radio.

At this point, we can all just drop SEO [0]. We are writing content for a robot that hides the source of information.

[0]: https://news.ycombinator.com/item?id=49665572

I like the trunk analogy, the branches can only grow so much before the tip the entire tree over.

I usually use the example of a blue sky. Write that the sky is blue. That's it. Simple yet the temptations to paint the sky with clouds, trees, and emotions is hard to resist. Always come back to the writing, and endure that you clearly wrote that the sky is just blue.

This is really fascinating. Even the AI companies have incentives to reject AI generated content. It's like they want you to use AI for everything, but they don't want AI output fed back to them.

At work, right after an AI training, we were asked to use our "authentic" voice when writing mid year reviews.

The law is too slow. It's like a horse carriage in the age of twitter. Why can't they expedite for special cases? Not even defending Antropic or any company. Just that if a tweet can cause damage in seconds, the law shouldn't be too far behind.