Here's a random video I found explaining what deep drawing is (skipped past the intro boilerplate): https://youtu.be/O3Wx1HA3fns?t=35
4,238 karma · joined July 6, 2017
See https://news.ycombinator.com/user?id=i336_ for old comments. Unsure if accidentally-locked accounts can be recovered; made new account regardless.
Flutter apps don't scroll at 30/60fps on my aging Mate 20 Pro, but that website is fine for me in Chrome.
Maybe this is what the age of desktop AGI looks like.
The only measurable flaw I could find was the errant use of an opening quote (‘) in
> He huffed a laugh. "Lucky you." His gaze drifted to the stained-glass window, where rain blurred the world into watercolors. "I bombed my first audition. Hamlet, uni production. Forgot ‘to be or not to be,' panicked, and quoted Toy Story."
It's pretty amazing I can find no fault with the actual text. No grammar errors, I like the writing, it competes with the quality and engagingness of a large swath of written fiction (yikes), I wanna read the next chapter.
But I can't quite wrap my mind around the core concepts and internalize them into a mental model. It's too different from the simple world of imperative C or scripting languages I guess I call home. So I'm left watching das blinkenlights from the outside, as my attention span chokes on the layers of computer science incorporated into typical explanations. *shrug*
I'd be very interested if anyone knows of an ELI5-style alternate path I could walk to break each of the concepts down one at a time. (I ask because I think this is (currently) the kind of thing I think ChatGPT would struggle to present as effectively as a human.)
Functional GUI: M_LIN8 G800x600 > 800x600 @00000+100+Dch4
Functional DOS: M_TEXT T80x25 > 720x400 @00000+050-W
Broken GUI: M_VGA G400x600 > 400x600 @00000+200-Dch4
Broken DOS: M_TEXT T80x25 > 720x400 @00000+250-W
- Broken DOS and Broken GUI are 200 or 250, functional are 100 or 050. What's that address?
- Broken GUI is somehow in M_VGA mode instead of LIN8. How and why did it get like that, and is that related to why it somehow got into 400x600, horizontally half of 800x600 (??). (True "textmode" is actually 720x400, as seen in both DOS modes.)
I agree it was an engineering marvel, IMO only less impressive than the CPU implemented in JPEG instructions for Pegasus.
I would have been yelling at an Arduino (and possibly a shift register) wired to the 7-segment LEDs... (I don't do hardware :D but I would've been convinced it was necessary)
That sounds awesome but my brain can't follow today.
What did the setup look like here?
My brain's looking at a test motherboard, then at 86Box (which would presumably run on your main system), and I can't figure out how to connect the dots.
I wonder if people with such cards have inexplicable problems with certain payment systems?
Edit: just saw the sibling comment, was viewing an old copy of the page
I once read drh note that no-one had ever bought any copies of TH3. I'm not sure what that does or doesn't say.
But I would hope this is using TH3 in the development pipeline!
If it's a direct port, the branch coverage should be constructively similar so as to be just as effective a test as for the C version.
It's not random. It's a DOS .COM file encoded as printable 8-bit-clean ASCII. The whole point is that it's executable code.
I stopped watching from there so it's possible this was mentioned later in the video.
1. Say what you're about to say
2. Say it
3. Say what you just said
I read it a while back so unfortunately I don't have a source.
I was actually able to demonstrate the issue in person, and everyone was scratching their heads trying to figure out what was going on.
I decided to try factory resetting it as a hail mary... and instantaneously I got a perfectly functioning ADSL connection.
It would have been far less embarrassing for me to have thought to try that and make the effort at home. lol
If there is no black bar, you could get one of those long narrow LCDs off AliExpress, set up the driver, add it as an X display with the right positioning... and then drag the mpv window across that and the TV. Should work. Those little LCDs are just silly expensive though...
So the industry has basically just gone and reinvented the very premise Google built BeyondCorp to mitigate, starting back in 2009.
IIUC the baseline premise was to move away from "login to the VPN and you're inside the corporate network and you can access everything". It was incredibly convenient but a logistical nightmare in practice.
The BeyondCorp approach was to integrate authentication into each product so that the access control could be managed on a case by case basis.
Google standardised on OAuth across the board, and had a centralised login protocol/API with a WAF etc, but each product called out to this, and policy was decided by the calling application. This approach shines through to the whole Login with Google ideology.
Thinking about it, I wonder how much corporate/enterprise/even SOHO OAuth is effectively the inverse of this approach - login to eg Auth0 once and you immediately have access to all your apps.
That approach isn't technically broken, but it feels a bit like there's an antipattern here in the encouragement of centralised policy management. That just encourages everyone to think about "login once!" just like the old VPNs.
And it's just hilarious how everyone's just... wandered in this direction. First VPNs, then "centralised access bad", then BeyondCorp, then OAuth, then "login once!", and back to the beginning.
At least the web gives you the tools to setup siloed authentication per app. VPNs don't provide that level of slicing and dicing. So it's easier to fix, and merely a (complex) security design problem now.
What sector is the app in, what are some other interesting (non-identifying) aspects of the app that stand in contrast to revenue? Is that in ads, or does the app have in-app purchases et al?
It's really interesting to see the current "state of the art" in terms of the types of bots that get past the particular CAPTCHA implementation this site uses.
It's a very rudimentary type of CAPTCHA, the kind that anything developed within the past 5 years would probably get past with at least 30% accuracy (logarithmically skyrocketing to >90% within the past ~2 years).
So the post quality is somewhat distributed across a spectrum - on one end, dumb CAPTCHA OCR/processing <=> "slightly better than Markov chain model replication", and at the other end, clearly more sophisticated systems that more easily pass the CAPTCHA and generate more interesting posts.
What's curious is that 90% of the comments are rudimentary. There are very few interesting spam posts. I'm trying to figure out what to make of this.
I'm picturing some majority of utterly outdated spambot infra, still out there, scanning the Web for WordPress/XSS-level stuff, and finding success on blogs like these... and that these old bots are the only systems of their kind out there, because all the spammers collectively gave up with reCAPTCHA and CloudFlare protecting almost all meaningful concerns, with moderation following not too far behind.
Kind of makes sense.
But it's really depressing to compare these old clunky bots that are kind of cute (in a way) to the upgraded versions - the current-era tech, that get past moderation... and effectively pass the Turing test :'(
And that would presumably be evidence of however many doofuses trying to upload their entire music library to YouTube privately.
It both doesn't make sense - you're making a private collection - and also does; YouTube have a for-profit music streaming service.
I guess we're now entering an era where we don't just have to worry about *just* paperclip maximization, but also the dimension of "how many paperclips the humans are leaving in the training data when they walk away from the LLM" :/ - in this case, if you upload 1000 songs into a private playlist then fine, maybe penalize that. But for a single video? That's messed up.
https://en.wikipedia.org/wiki/Tandem_Computers: 1974 (50y) (semi-dead)
https://en.wikipedia.org/wiki/QNX: 1982 (42y)
https://en.wikipedia.org/wiki/VxWorks: 1987 (37y)
https://en.wikipedia.org/wiki/GNU_Hurd: 1990 (34y)
https://en.wikipedia.org/wiki/4690_Operating_System: 1993 (30y) (these run the self-service touchscreens at Costco's food section, IIUC)
It's surprisingly hard to query for "graph intersection between earliest first release date and most recent release date" :(