Speculation for fun: I always thought popular apps can use private apis or are handled in a special way by the OS itself. If yes, perhaps this is related.
Then again I found no source for that - and some certificate rollover seems more likely.
It’s a completely opposite scenario for me, I accidentally shipped a pixel art game.
It’s actually a game about nonograms. My first attempts at pixel art were bad but it didn’t matter that much, the focus was elsewhere anyway. With time the art improved; far from perfect but it’s still one of the things I like most about that game.
So I guess: practice, room for failure, achievable goals and time.
Oh no, that one has proper pixel art. Mine just has pretty puzzles (nonograms that turn into pixel art images when solved) and an occasional pixel art level. I plan to add more levels like this later.
That page addresses tort liability, not liability for driving infractions or crimes. Liability for damages when a company does it is more settled of a situation.
It still isn't quite as clear who or if anyone is liable when traffic laws are broken:
Sounds like the tickets should be at least more expensive than the cost of equivalent QA (and if not, self driving companies might offload QA to the police).
However, I skip permashortlinks - I try to keep my regular links relevant and short. Also, I like seeing full links, they can often indicate what content awaits there - vs short links, which are more opaque.
That's one more benefit of this workflow: it can be adjusted to fit one's personal preferences. I suppose others might prefer short links or maybe at some point I'll change my mind; with POSSE making these kind of changes is easy.
Yeah, I’m happy to just call permashortlinks a bad idea, seldom warranted historically and roughly never now. The article offers no explanation about why to use permashortlinks—what looks to be “a few reasons why” is actually a few reasons why to link to the original (rather than copying and pasting the contents), nothing to do with the permashortlink practice.
https://indieweb.org/permashortlink does give a few reasons, but they’re bunk. “More reliable in email”? Not meaningfully so. “Quicker to recall / copy due to size”? Not typically a concern. Maybe a nice-to-have, but you can consider adjusting your URL style, then it can be even better. “Less effort to manually enter”? Repeat of the previous point.
And it doesn’t address the problems of the permashortlink. Cost. Diluting across different domains. Having something different to maintain and remember.
Don’t do separate permashortlinks. Just fix your regular links to not be bad.
> Desk Reject Comments: The paper is desk rejected, because the reciprocal reviewer nominated for this paper ([OpenReview ID redacted]) has violated the LLM reviewing policy. The reviewer was required to follow Policy A (no LLMs), but we have found a strong evidence that LLM was used in the preparation of at least one of their reviews. This is a breach of peer-review ethics and grounds for desk rejection. (...)
Anecdote, I like wired headphones for important online calls. I use earpods[1], I started using them back when they came with a phone, I'm happy that it's still possible to buy replacements. I like having a reliable wired connection that works and disconnects predictably.
I guess a lot of that is nostalgia. My laptop model no longer has a webcam cover or a physical network switch; connecting and disconnecting the trrs[2] cable reminds me of these.
But some of that is still practical needs. I have AirPods and Bose wireless headphones, both praised for reliable connections. Every now and then they take a bit longer to connect or the volume changes unpredictably, or they need to be charged, etc - when wired headphones just work.
I very much appreciate it when people use wired headphones with a decent mic for calls. Speech clarity is just so much better even with Earpods compared to tws earplugs.
Nonograms! I built Nonodle[1], a daily nonogram puzzle game and I’m adding an option to access these puzzles from Nonoverse[2], my iOS nonogram app.
There is an API, and it’s a straightforward task, but one thing led to another and I’m also improving the app UI. The update will take some time but I hope it will only be better.
I think in this case the name alone is not enough to suspect a replacement; perhaps it’s just a similar product in the same domain (_mono_space visual editors).
Then again I found no source for that - and some certificate rollover seems more likely.
reply