rustc

That's how you get this feature: https://wiki.php.net/rfc/deprecate-bareword-strings.

tldr: undefined constants were treated as a string (+ a warning), so `$x = FOO` was `$x = "FOO"` + a warning if `FOO` was not a defined constant. Thankfully this feature was removed in PHP 8.

> what's next?

Removing existing Docker images? Seems unlikely.

It's still risky if you pay unless you have a contract guaranteeing what the renewal price would be.

> OR they acknowledge that it's almost impossible to build a website without some form of tracking

Why would it be almost impossible to "build a website" without tracking?

Another weird idea: make this kind of tracking illegal. Why would anyone willingly agree to be tracked?

Or just ban this kind of data collection. Is there any reason anyone would willingly click "Accept" when a website asks to share your data with 500+ partner sites?

Does any host provide more compensation than refund for downtime?

What is the right way to make ripgrep behave closer to `git grep`? Plain `rg` ignores files inside hidden folders like `.github`, `rg --hidden` will search `.github` but also search inside `.git`. I currently have this alias that I don't remember where I found: `rg --hidden --glob '!*/.git/*'`. Is there a better way?

I would prefer a solution that works from outside git repos, so no piping `git ls-files` into rg.

But will the "big fine" be more than the money LinkedIn will make by doing this?

It would disallow private forks of WordPress (require them to share the modifications) but I don't know whether WPEngine and other hosts have any private modifications or they all use stock WordPress.

Have you thought about licensing future additions to WordPress under AGPL? I believe it can be done [1]. This will disallow private forks and require companies to publish any changes they make.

[1]: https://opensource.stackexchange.com/questions/12276/how-to-...

> If your bank calls you, hang up and log in or call their support number yourself.

And don't trust the number you see on Google. Google is known to show scammers' phone numbers in featured snippets or in their new "AI Mode". Click on the link and make sure it's the correct site before trusting the number.

The notifications are not real time. You can rack up a significant bill before they are triggered.

And what if they don't say "no problem"? Like the Netlify case where they at first offered a reduced bill (which was still a lot) before the post got viral and the CEO stepped in.

> Included in Always Free Tier

> 1 TB of data

Someone can rent a 1Gbps server for cheap (under $50 on OVH) and pull 330TB in a month from your site. That's about $30k of egress on AWS if you don't do anything to stop it.

> If you put your information freely on the web, you should have minimal expectations on who uses it and how.

Does this only apply to "information" or should we treat all open source code as public domain?

> If you want your content to be free, you release it and have no issues with AI. If you want to make money of your content, add a paywall.

What about licenses like CC-BY-NC (Creative Commons - Non Commercial)?

This is like `curl | bash` but you automatically execute the code on every webpage you visit with full access to your browser.

> Malicious actors can hide instructions in websites, emails, and documents that trick AI into taking harmful actions without your knowledge, including:

> * Accessing your accounts or files

> * Sharing your private information

> * Making purchases on your behalf

> * Taking actions you never intended

This should really be at the top of the page and not one full screen below the "Try" button.

Since when does PayPal Honey replace ads on websites?

> PayPal Honey is a browser extension that automatically finds and applies coupon codes at checkout with a single click.

There are many APIs that scrape Google but I don't know of any search engine that scrapes and rebrands Google results. Kagi.com pays Google for search results. Either Kagi has a better deal than SERP apis (I doubt) or this is not legal.

> Should curl be considered a bot too? What's the difference?

Perplexity definitely does:

    $ curl -sI https://www.perplexity.ai | head -1
    HTTP/2 403

> Crawling and scraping is legal. If your web server serves the content without authentication, it's legal to receive it, even if it's an automated process.

> If you want to gatekeep your content, use authentication.

Are there no limits on what you use the content for? I can start my own search engine that just scrapes Google results?

It's ironic Perplexity itself blocks crawlers:

    $ curl -sI https://www.perplexity.ai | head -1
    HTTP/2 403

Edit: trying to fake a browser user agent with curl also doesn't work, they're using a more sophisticated method to detect crawlers.

And now you spend the same time verifying/reviewing AI output?

> did they not make it clear to their customers that letting the Nonsense Generator have root was a bad idea?

No, the opposite (from replit.com home page):

> The safest place for vibe coding

> Vibe coding makes software creation accessible to everyone, entirely through natural language. Whether it’s personal software for yourself and family, a new business coming to life, or internal tools at your workplace, Replit is the best place for anybody to build.

> I recently made a user script that tries to highlight LLM generated text

How does that work?

> Ha, nice find! I'm the Adriaan in adriaan.com. I'm testing some new script features that might improve deliverability. It's not sending any personal data. I use another domain to have the least effect of ad-blockers.

You are sending the user agent, path, referrer, a session id + the IP (which is automatically sent) to your personal server and also using a different domain to track users who have ad blockers installed. Even Google Analytics does not use random domain names to track adblock users (yet).

> If you publish a model that doesn't follow these rules

The rules require tracking outputs, which open-weight models cannot do. So I'm wondering if open-weight models have separate rules or this effectively bans releasing such models.

How would this apply to open-weight models? The creators of the models cannot know who is using the model and for what.