Re #teaxyz, they finally posted this on their discord 2 hours ago
It remains a crypto pump and dump scam, and will not do anything positive for the funding of free and open source software.
Re #teaxyz, they finally posted this on their discord 2 hours ago
It remains a crypto pump and dump scam, and will not do anything positive for the funding of free and open source software.
If anyone was curious how the pair of pkgx and tea scams synergize.
I'm on the tea discord and what kind of cult is this? There are dozens of pages of this.
Tea memes... this one seems a little on point for the current AI-github-PR-spam activity
Actually posted by the actual scammers. wtf? https://twitter.com/teaprotocol/status/1727039946014507394
@mhoye all of which is not to say it's bad. yt-dlp supporting json output has been useful to me for example
@mhoye also unix programs often don't have output limited to utf8. so json can quite complicate situations involving eg non-unicode filenames and other things that people don't want to think about but that still exist
@mhoye maybe this kind of thing is par for the course in json use in webdev, IDK
@mhoye Once a program has started emitting json, it's now locked into doing that in future versions in a compatible way.
My approach has been that all json output be self-describing. Ie, a given (sub)command's json output always has the same objects with the same fields in all circumstances.
(Except for the one subcommand that I messed up and its output was not self-describing and now I'm stuck with it.)
This has all felt nontrivial to me. Worth it tho.
@mhoye example of me fucking up in a way that broke a downstream consumer
@mhoye so I've supported this (in git-annex) since before the spec existed. I do have a few thoughts.
Without a json schema for a particular program's output, it's hard to know if the objects you're seeing are the only ones it emits. Maybe there is a field that goes missing sometimes, or a different object that is emitted on error.
unix tools generally avoid this problem by having simple and self-descriptive output. json moves the goalposts some.
#FOSDEM legal devroom had a fun question
14 years from 2038 and #raspberrypi users are running 32 bit userlands by default on their 64 bit boards, without being aware of it.
youtube deleted their RSS feeds, but rsshub can generate RSS feeds using the youtube API
this is fine
#sourdough #pizza baked on hot coals in my wood stove at 900F because I'm still snowed in.
Subbed some (spanish) choriso for pepperoni, which works well.
This ISDN retrospective reminded me that I was paying $300/month in 1996 for internet via ISDN .. the ISP didn't seem to properly support 128 kbps so that was for 64 kbps.
@liw possibly relevant to your interests: After I got sqop working in my test suite, I ran that test case in a loop, and found it hung 1% or so of the time.
Due to a missing close-on-exec of the send side of the password pipe, which caused sqop to inherit both sides of the pipe sometimes and block reading the password since it was holding the pipe open.
I don't think this is a bug in sqop really, but interestingly, gpg appears to avoid the same behavior when run in the same way.
Stateless openpgp allows --with-password=@FD:42 to fail if there happens to be a file named @ FD:42
How is this a good idea? Now I'm gonna have to make an empty directory and run the command in that directory to prevent foot shooting accidents. This is a disaster waiting to happen for all programs using SOP.
An inspiring talk at #37c3 included this graphic. It shows how 500 developers each making 10 small optimisations of 1 cpu-second that happen 20 times a day for each of 1.5 million users, can save power equivalent to 30,000 two-person households.
Another form of that is, if you have 100 thousand users of your software, and make a 1 cpu-second optimisation that will occur 50 times a day, then you can save the power of a single two-person household.
https://events.ccc.de/congress/2023/hub/en/event/software_licensing_for_a_circular_economy/
Morning chai and haskell
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.