1: https://foundation.pbs.org/ways-to-give/gifts-to-the-pbs-end...
So this certainly won't be the death of PBS, as I had feared.
Update 2: For the record (easier to respond in this original post than to each response), I am not defending the decision at all. I grew up listening to NPR, and have been on recurring monthly donations to PBS for years.
I was genuinely curious about what percentage comes from federal funds. So I am just trying to level-set and get ahead of any hysteria about the actual impact.
That's a nice chunk of change, though low enough that a few friendly billionaires could put some pocket change into a trust today and make up for this funding in perpetuity. And there undoubtedly will be a massive surge in donations from small donors in response to this.
As long as the bigger fish are willing to subsidize the smaller rural stations, I don't think there is anything to be afraid of.
The removal of this Sword of Damocles is in my opinion a great thing for PBS and NPR.
On every flight I've taken, gate checking implies the latter, that it will be on the cart or floor of the jetbridge when deplaning.
I think the opposite, MCP is destined to fail for the exact same reason the semantic web failed, nobody makes money when things aren't locked down.
It makes me wonder how much functionality of things like AI searching the web for us (sorry, doing "deep-research") might have been solved in better ways. We could have had restaurants publish their menus in a metadata format and anyone could write a python script to say find the cheapest tacos in Texas, but no, the left hand locks down data behind artificial barriers and then the right hand builds AI (datacenters and all) to get around it. On a macro level its just plain stupid.
You've described most white-collar jobs :)
It seems that users commonly misconfigure Spring Boot security or ignore it completely. To improve the situation, I made this PR: https://github.com/spring-projects/spring-boot/pull/45624.
When the PR was created in 2016, endpoints were marked as "sensitive" and, for example, the heapdump endpoint would have to be explicitly enabled. However, Spring Boot has evolved over the years, and only the "shutdown" endpoint was made "restricted" in the later solutions. My recent PR will address that weakness in Spring Boot when users misconfigure or ignore security for a Spring Boot app so that heapdumps won't get exposed by default.
I think it would be wise to either disallow the ports being the same, or if they are the same, only enable the health endpoint.
It's mind-boggling because the US has been trying very very hard to pull Sri Lanka away from China for a decade now
An app he wrote: https://web.archive.org/web/20240304061200/https://sit.luddy... or https://web.archive.org/web/20240727022112/https://homes.lud...
A news (probably PR) article about it: https://web.archive.org/web/20220622001223/https://www.compu...
None of these sites is available any more. This looks suspicious, even given the regular bit rot of American college servers. The app is supposedly downloadable at https://apkcombo.com/app-guardian/edu.iub.seclab.appguardian... . Anyone around with a disassembler and too much time?
Correction on this: Wikipedia was GFDL until 2009. See https://en.wikipedia.org/wiki/Wikipedia:Licensing_update .