Aseprite is source available nowadays, not open source. Libresprite was then forked off of the last commit of Aseprite before the license was changed from the GPL.
Give it a month and the partnership will be in shambles after the GrapheneOS social account makes vague unverifiable accusations of alleged Motorola employees sending death threats to GrapheneOS contributors while praising other custom ROMs.
> @hide This method is prone to abuse and should probably not be in the API. If we ever do make it part of the API, we might want to rename it to something less funny like runUnsafe().
I assume that's the "The Monkey" testing tool for the original Mac that's mentioned in the footnotes in the Androids book. Supposedly goes back to the infinite monkey theorem that makes monkeys act as a metaphor for randomness, and it was also mentioned that one of the developers of Android had used the same kind of monkey testing for WebTV and Palm OS.
Yeah that's where the concept of the blink tag originates, the now deprecated HTML tag. But what's covered in the blog post refers specifically to a hidden (and AFAIK undocumented) blink tag that exists in the Android XML layout view system, which is an independent thing from the system WebView browser (that I assume probably still contains some code for blink tags, but that wouldn't be a surprising discovery). I don't know if there are any other built-in tags in Android views that really map to HTML tags otherwise.
oops, no idea why the link I put there didn't work. Just corrected it, ended up linking to the page about the book on Chet Haase's website instead: https://www.chethaase.com/androids
That would be quite fun, especially if you would have some thing that checks the DISALLOW_FUN policy. While doing a quick search on GitHub while reading the blog post to see if any Android apps with available source code were using it, all that came up were repositories containing code for the system Settings app locking away the version easter egg based on it. You might become the first third-party to use it!
Indeed. There is such an immense amount of media that is produced from decade to decade that nobody can ever know everything and understand "all" the references. Things that may seem like "things everyone know about" vary wildly between location and year ranges, and in the recent decades with the Internet there are just so many subcultures that all could be classified as "nerdy" but which lack a lot of overlap.
I suppose I'm too young to have watched Star Trek when it was really popular (and have all sorts of other blind spots when it comes to TV shows and other media even for people my age), but I've definitively heard about it. And I know some other references to it like Spock and the Vulcan salute, but the Tricorder had completely missed me until now.
Also, with something like GRAVITY_DEATH_STAR_I I could pretty easily tell it was a reference to something fictional (in that case Star Wars) since there is obviously no celestial body with that name. But with the Tricorder I was looking to actually make sure it's not some kind of actually real but vestigial hardware sensor thing that Android might have supported in the 00s, tangentially related to the Tricorder that was on Star Trek. I have certainly witnessed stranger coincidences.
Like Android still has functionality in the API for supporting trackballs, which I know used to be on some really early Android phones. So if that had been among the list as "there's this joke input device called a 'trackball' in the API, implying there are phones with a big physical ball you can roll around to move a cursor on the screen", that would be quite silly. Because it was a real and used thing in the past, even though nowadays it's more of a legacy feature (though might be a bad example as I assume you can connect input devices over USB or Bluetooth that may be treated as a trackball by Android).
reply