i336_

I completely understand how what I wrote could come across this way now I reread it. I guess today is one of those days I'm not able to articulate what I'm thinking (happens a lot sadly).

While the black bar is not a "banned topic" or anything, bringing it up tends to produce heated disagreements, and at the worst possible time too (since the conversation ends up in the thread of someone who's no longer with us).

Devolving into meta flamewars is quite disrespectful, and creates extra work for the moderators as as well.

I suggested opening a dedicated thread the last time it was brought up, and that's here: https://news.ycombinator.com/item?id=14119519

Here's the last time the black bar was discussed in a thread it was used. You'll need showdead turned on to see all the offtopic discussion. https://news.ycombinator.com/item?id=14118290

I login to $app with my password. $app bounces me to SMS. I then go back to $app with the SMS code.

So I needed my password with $app and the code from the SMS.

Ah, that's what I was missing. Thanks.

Are there any hacks that can convince macOS (or the older versions of OS X described in this article) not to treat the display as HiDPI? Yeah, I realize the machine will abruptly feel like it needs a magnifying glass to use, but in a pinch (laptop on lap <2ft from eyes) it might work for some (insert standard disclaimers here about eyes being non-replaceable and needing to last the distance).

Also.

The late-2015 21″ iMac is ~$1.5k+, and "has a multi-core Geekbench score of 5623."

Then the late-2011 17″ MacBook Pro which is ~$1.3k checks in with a "9240 Geekbench score".

Is there some datapoint I'm missing here?

Sure, it has a text format, but it's the equivalent of Lispified Java bytecode. (https://developer.mozilla.org/en-US/docs/WebAssembly/Underst... (uninformative but current), http://loyc.net/2016/lesv3-and-wasm.html (2016, from when wasm wasn't finalized, but has some good concrete examples that look like the wasm in the first link))

With this being said, it may actually be easier to figure out wasm than frameworkified JS since you can apply IDA-style reversing to it.

Open question: what existing tools and research are good at inferring the high-level behavior of stack machines? Eg, research papers, or (preferably open source) tools for reversing eg Java code. I want links I can throw at Ph.Ds.

In a nice bit of timing, HN Replies (my HN notifier) grabbed the comment before it was deleted! It was interesting, so I'm anonymously adding it below:

--

> I have seen first hand a large VoIP carrier reach out to an ITSP because one of their end subscribers was scanning the 710 number space either manually or not. And it was within a few minutes after the scan started. This type of activity (and others too) will set off all kinds of alarms at phone providers.

The other two comments I see in this subthread are practical and pragmatic, but I also agree with your view as well. I would far prefer to pay the fees and have all transactions processed via the blockchain.

Although at the end of the day, pragmatism makes money...

Are you saying there's more than one 710 number? [Just Y/N]

  data:text/html,
  <style>img { opacity: 0.5; position: fixed; left: 0; top: 0 }</style>
  <body><img src="https://www.cl.cam.ac.uk/~fms27/vck/share1.gif">
  <img src="https://www.cl.cam.ac.uk/~fms27/vck/share2.gif">

I think the reason the images loaded was because I was on a data: URI? Or am I misinterpreting CORS?

After 200-400 suspended tabs open and a browser chewing molasses, I tend to export all URLs to a list for One Day In The Magical Future™, kill my session and restart.

So yeah, I'm very interested to find out what rule system you use - is this bespoke, or using standard email client features?

Also, what email client do you use? I've been trying to find a medium between "old computer becomes unusable after >10 tabs are open" and "fast, native information-presentation applications (like terminals) are text-only and don't support images" for 15+ years.

I use Gmail's basic HTML mode 99% of the time. It... I can't say I like it. I want something that doesn't use Qt and GTK+, because I perceive more lag with applications that use these toolkits than I did with lightweight WinAPI apps I ran on Win98/Win2K machines with half the hardware capability.

Regarding the numbers here, I'd say there are multiple thousands, possibly 5 figures. The top article about Apple refusing to publicly backdoor the iPhone (https://news.ycombinator.com/item?id=11116274) got 5667 points. And sometimes my comments will attract a reply chain but not get upvoted, which shows that some proportion of people doesn't upvote here.

How did that happen?

Releasing this even without abstracted integration sounds reasonable to me - this is a system you built primarily for internal use, and you're engineering strictly atop AWS.

If the community wants support for other providers, someone else can come along and re-integrate with another provider, and maybe see if/where it's possible to collaborate with you guys on small changes that allow for easy maintenance for everyone.

Unrelated, but are there any phone keyboards that interpret a hard press as uppercase and a soft press as lowercase?

(Relative to your average tap force)

It felt like I'd just hand cranked a CSS animation. Kinda steampunk.

Note that I'm not dissing the author here. They appreciate the feedback they've gotten, which means they're receptive, and that's honestly a very large percentage of "this'll work out okay," which in this case means that this project will iterate until it nails something new, or the author will go join one of the other hashing efforts out there.

The idea is not to conceptualize an imaginary person, but to lower the hesitancy of "but there's noone there". Trying it in an empty house may be helpful.

I found myself pacing after a mildly stressful event a few years ago, and the practice stuck as a way to help myself wind down. I'm not actually sure when I started talking to myself too, I think it was around that point. I do both on a virtually daily basis, it's how I figure many things out.

Opens new tab

Sound of typing

https://meta.stackexchange.com/questions/296990/what-are-the...

I've been thinking along the same lines for a very long time. Thanks for the inspiration to finally ask!

I'm honestly not sure.

THIS IS A CROSSPOST FROM TO A REDDIT THREAD, REPLY THERE

With that out of the way: I strongly suspect that the reason this is happening is that the person in question thinks Bitcoin is about to tank.

So they're getting out of the market.

So, I'm curious. What's a decent, low-drama/no-fuss broker I should be few issues with? Reason is obvious. :P

I'm completely ignorant of Bitcoin features I might like; I'll primarily want to export to USD (in the US), and maybe AUD (in .au).

That gives me hope, as someone who wants to do low-frequency data analysis that's only possible via multiple queries.

- Office IT maintenance all hate printers

- I'm sure you've gaped at the control software that came with the little $40 inkjet you bought (or had to use) at some point

- Even the creator of MINIX cited "buggy printer drivers" as his rationale behind prferring nanokernel architecture (all drivers run in userspace) instead of monolithic approach (all drivers run in ring 0; printer driver sits next to crypto keyring).

So. Printers are terrible.

Remember Brinks' fireproof safes that were absolutely rock-solid but were running fully unpatched WinXP and had a USB port on the side of the keypad for "security updates"? Hackable with a keyboard stuffer that looked like a flash drive. https://news.ycombinator.com/item?id=9961024

I remember reading (somewhere) a conclusion that went along the lines of, Brinks are awesome at making safes - and this safe was truly amazing - but they weren't a software company, to a profound extent.

It's clear to me that printer companies are similarly really, really bad at software design too.

So, reverse-engineering the firmware to figure out what things printers are doing use probably wouldn't be all too difficult.

The printer companies were told to write the code, not write it perfectly and make it impossible to unravel as well.

Of course, if anyone actually take a crack at this (excuse the pun) that'll make things change a bit, but printer firmware is probably at the "open sesame in a big way" stage right now, and the printer industry is huge and slow to change, which suggests reverse engineering could remain trivial for a little while, even with publishing.

The person who wrote the list in the article mentions (at https://news.ycombinator.com/item?id=14502425, in this thread) that there is a second generation of this technology that doesn't produce microscopically-visible dots.

Perhaps the use of all available colors is involved.