A gmail expat, I've been over at posteo for about a decade. Couldn't imagine a reason to go back for my personal account.

I've used gmail for corpo email since, but I don't have a choice there.

Always has been.

> The [Save Our Bacon] Act would stop any state or locality from regulating the sale of meat based on how it’s produced in another state.

Interesting to think about this adjacent to the current availability of mifespristone by mail debate. They're not identical, but to what extent do the laws of one state impact the lives of those who reside in another?

Seems contrary to their supposed "states rights" philosophy.

Yeah, that's kinda where I am. States (for now) have the right to regulate what's for sale on their shelves.

This is a case where "the customer is always right" applies. CA and others have passed legislation for what kind of pork they will buy. IA is not compelled by those laws to fill those orders and doesn't have to rebuild out a new supply chain.

They may need to retool some of it if they want to capture these clear market demands, but again... nobody is compelling them.

From what I can tell, the message is

When you discover an exploit, only communicate with source (and pray they respond) or get sued. Seems like the position is customers and stakeholders shouldn't be allowed access to this information.

Seems similar to what Microsoft is doing lately:

https://www.cpomagazine.com/cyber-security/microsoft-doubles...

That's actually very common even with respected bug bounty programs. Communicating exploits to anyone else (let alone the general public) will at the very least make you ineligible for rewards.

IMO if you're participating in a BB program, you should abide by he rules set forth by the program.

If you're not, then you don't have to.

I mean, you could just turn on WebGL or use an approved, secure, agent to access the web. If you have nothing to hide, then you have nothing to fear.

Idk, if bots ate hammering your server then setup rate limits. If you have content that you don't want others to have access to, don't serve it with a webserver.

I used to just start giving any IP downloading way too much a redirect to multi-tb NASA images. This was a long time ago but it was surprisingly how many would follow redirects and never time out. Wouldn't see a request again for hours and then its right back to downloading a new part of the sky.

Those images also used to crash all the early GUI irc and chat clients that showed inline images without size checks...

How do you know it followed the redirect and downloaded the image?

Because it didn't come back for hours.

How were you tracking each IP address's data usage? Did you parse the logs every request? Store usage in a database? At the application or webserver level?

Webalayzer! I'm not sure there were really any other options at the time other than writing your own. Parsed the apache logs and gave you pretty detailed results and you could see the usage (in kb, which tells you how long ago this was!) broken down by date and IP.

Once you added a redirect rule for the IP to apache you'd just check your log and see the IP that was hitting you every couple of minutes poofed for a good few hours.

Now that's a name I've not heard in a long time.

That's nuts. I suppose you had Webalayzer on a minutely cron job. It might have been drawing more resources than Apache itself!

This. What even is the point of blocking scapers if Google consumes your content anyway and serves it as an AI answer?

These are sad times we're living as far as openness of the web goes. People would have less of a scraping problem if their websites didn't ship with 20MB of JS.

> What even is the point of blocking scapers if Google consumes your content anyway and serves it as an AI answer?

Google bot is generally fairly well behaved, but this is not the case for all scrapers and it can cause significant traffic (and expense).

There is something to be said for "one way indexes."

Imagine you run a company register for a local government. You want to let people look up companies by their registration number (which they must disclose in all communications to you) to see if they're legit and whether any warnings have been raised against them. You don't want unscrupulous marketers to just be able to `SELECT * FROM companies WHERE type='nail_salon' AND city='london'`.

If you aren't super strict about scraping, some shadowy business in Neverland, completely unconcerned with following your laws, will build that database.

> Imagine you run a company register for a local government.

Is this data not public for some reason? I think it will not hurt if there are multiple copies spread between public offices and private companies. What really hurts is a private company hammering your webserver for their own profit. They should get their own copy.

If the purpose of the index is to allow people to lookup registration and warnings, probably just serve the list. This is public information and doesn't need to be gated. CSV header could be:

Reg_no, status, no_warnings_last_12m

I have blocked several Asian countries because their IP ranges kept sending stupid scrapers that repeatedly downloaded the same image with a made-up query, bursting through the basic cache setup. Now a billion or so people can't acces my server.

Rate limits didn't work because they kept rotating IP addresses.

I'm pretty sure Turnstyle would allow more people through than my current solution, but this was quick and easy. I expect to have to ban more ASNs from other countries in the future but the worst bots are now gone.

Rate limits don’t work if bots rotate IPs from residential blocks on every request.

I would LOVE to be able to use rate limits (well actually, since I'm dealing with fraud not scraping, I'd ban the IP).

I can't, because every request comes from a new IP!!!

MS hates him! Find out this one trick they don't want you to know!

$ sudo pacman -S libreoffice

Why do Americans have to worry about the packaging of Japanese snack products? S&P is up 10.5% YTD

>Why do Americans have to worry about the packaging of Japanese snack products?

We don't but we worry about similar issues caused by the same root cause.

Big complex data model with ambiguous query patterns? Postgres

Small, well defined, data model with known query patterns? Bespoke model

There probably is a place for sqlite and my project space so far hasn't yet well-aligned with it.

Probably going to get some winces for this but I do everything with flat files. Maybe my data aren't massive enough, but I mean I can do the relational thing by just having these metadata in some column, and returning rows that contain my desired information in these columns. Even if the file were too big to fit into memory one could just subset chunks of it and chew through. All this can be done with no dependencies, just base libraries of a lot of languages.

IMO flat files is a cromulent solution for a subset of the entire database space. "Everything" is too broad for me but different strokes for different folks. Happy dataing.

I don't think I've got a push notification in awhile. Few months ago I switched to Lineageos and started using the web browser instead of apps. It's peaceful.

I still get notifications (SMS, email, calendar, etc) but nothing pushed

In the US, median homeowner tenure is about 12 years. If the local price-to-rent ratio is high, (greater NYC metro for example) then you may have to stay 20 years to come out ahead financially. In a case like that, renting can be a very attractive strategy for building wealth.

It's more complicated than that. If you sell-to-buy then the tenure only affects the costs related to the purchase itself. I suspect many homeowners live in a house they own for much more than 20 years. I've owned since 2007, but my mean tenure is less than 12 years since I moved.