jka

7 ms·

1.
paperplanes – throw and catch paper planes with people worldwide from your phone(paperplanes.world)
2 points by jka 4y ago|0 comments
2.
Progressive Web App Store(progressivewebapp.store)
12 points by jka 4y ago|1 comments
3.
by jka 4y ago
Quoting from a relevant wikipedia entry[1] to hopefully pre-emptively reduce some confusion: ''' In parliamentary procedure, the verb to table has the opposite meaning in the United States to the rest of the world: - In the
4.
by jka 4y ago
It's a shame that (if I remember correctly from the video?) the bug that allows this is restricted to single-player; if not, I suppose it'd be possible to start the "outer" map as a network game, and then use the second
5.
by jka 4y ago
There can be a good intellectual challenge in refactoring code like that to be both efficient and readable (although at some extremes, and depending on the programming language, perhaps there'll be conflict between those two goals). Al
6.
Beyond PEP 8 – Best practices for beautiful intelligible code [video] (2015)(youtube.com)
1 points by jka 4y ago|0 comments
7.
by jka 4y ago
Per-employee distribution might tell one story; per-manager distribution might tell another.
8.
by jka 4y ago
Offering an opinion: the tech industry is invested in the success of PyPI -- perhaps not always in a literal monetary sense, you're right, but certainly in an ecosystem sense.
9.
by jka 4y ago
Ok: you've provided two requirements that I agree with: - It should be possible to compare between two releases (I'd personally like to see a code diff, ideally with a complete path of the commits involved) - Providing a reputatio
10.
by jka 4y ago
Odd but serious question: could there be ways to distribute versioned software that doesn't require management of developer accounts (and the associated time-and-effort costs related to account takeovers)?
11.
by jka 4y ago
That's a very good point regarding operational cost of handling account takeovers. I'm not sure I have much useful commentary to add, but it does occur to me that a sufficiently-sized pool of software users could inspect changes (
12.
by jka 4y ago
Choosing to use FOSS software to build products/services has always involved an element of caveat emptor, and even with the best of intentions, mistakes and errors are introduced sometimes, as they can be into any commercial software.
13.
Apertium – a free/open-source machine translation platform(apertium.org)
4 points by jka 4y ago|0 comments
14.
by jka 4y ago
Trying to ignore any hype, lofty sci-fi ideas, or potential philosophical questions for a moment: roughly speaking, it sounds like this is a search engine, for use in a neat and thought-provoking use case. There's an architecture diagr
15.
Piltdown Man(en.wikipedia.org)
1 points by jka 4y ago|0 comments
16.
by jka 4y ago
Related to this, there's a really good talk by the founder of lichess that includes an overview of the cheating problem, and the techniques they use to detect and manage it. The relevant section of the video on YouTube is: https:&#x2F
17.
by jka 4y ago
I think I'd prefer a code review discussion where the file being modified is a CSV file listing everyone in the organization's roles, seniority levels, and compensation, and where anyone in the company (and perhaps at a later date
18.
by jka 4y ago
(see also 'Sam Vimes "Boots" theory of socioeconomic unfairness': https://en.wikipedia.org/wiki/Boots_theory )
19.
by jka 4y ago
It's generally not a model that has much supportive mindshare for the web currently, but it is possible to achieve tamper-prevention without requiring the content of communications to be encrypted. For example, most official Debian[1]
20.
by jka 4y ago
Digital experience ('DEX') issues reported by employees, from the original report: - 37% : Security/regulatory policies - 37% : IT overwhelmed by number of issues that need resolving - 35% : Lack of training for IT personnel
21.
by jka 4y ago
Worth mentioning that the experimental payments during this research were one-time-only. (a few descriptions[1][2][3] of Universal Basic Income seem to define it as including recurring/periodic payments) [1] - https://en.wik
22.
by jka 4y ago
Often I begin from the assumption that the marketplace -- for some reason -- wants to gather as much information about customers as possible, rather than to sell them minimal products that meet their requirements, and so: - Unless you'
23.
by jka 4y ago
Slightly-curious, slightly-unnerved, slightly-paranoid question here: Is there any chance that this code snippet was sampled from repositories that contained associated commentary/discussion, guiding GPT-3 to produce similar explanatio
24.
by jka 4y ago
Roughly speaking, yep - Common Crawl provides a sizable chunk of web data (420 TiB uncompressed, over 3 billion unique URLs, as of May 2022; historic statistics here[1]), and is updated on monthly basis. Not near-real-time, true, albeit re
25.
by jka 4y ago
A correction/clarification since writing the parent comment: publication of packages requires an authentication token, and does not require an interactive 2FA challenge. Generating a suitable token for package publication, however, do
26.
by jka 4y ago
Hrm, fair point. Although migrating 'backwards-compatibly' like that could leave a lot of people in the cold if-and-when a security update for the package is released (and we're talking about critical packages here, at least
27.
by jka 4y ago
Sure, accepted. That'd be a disruptive change, though, and I think that a better approach is possible. The suggestion regarding separation of (immutable) packages and policy in the article could provide some hints in that direction.
28.
by jka 4y ago
> You can always publish your creation on your website or wherever. What you're suggesting wouldn't solve the problem for critical packages, though; the effect would be similar to yesterday's package unpublish issue[1] (al
29.
HTTP Digest Header (integrity mechanism)(developer.mozilla.org)
2 points by jka 4y ago|0 comments
30.
by jka 4y ago
It seemed clearly-written and thought-provoking to me; the author doesn't claim that 2FA is a burden, either. Writing and distributing software should be straightforward so that everyone can participate. And consuming software should

More ›