HN user

Syrup-tan

278 karma

Feel free to reach me at ~ syrup+hn at denpa dot moe

Posts11
Comments45
View on HN

Euhh, I'm not sure I understand your use-case, but e-ink displays aren't especially "cheap", or such. They take a noticeable amount of time to update the display, so doing things like typing, or viewing output from top(1) would be less than ideal. (This seems to get better with firmware, and being "smart" about which places of the screen get updated, generally)

The appeal, at least to me, is that they can display information with little energy cost. For example you could have it monitor the system's health and have it update every half an hour, showing graphs and such, and it would be able to do that for a very long time with a smallish battery.

It's a service, of sorts, for registered users to know if any of their friends are in the vicinity, and if they are safe.

It also allows users to mark themselves as "safe" if they were in the affected area.

I'm unsure why this is downvoted.

I think he is saying that users can't be tracked between page-loads using this method, or your risk sending multiple users the same token. (which is true, at least with this implementation)

The time they spend on the website, latency, etc can all be used to add to a fingerprint, but there isn't something magic that makes this accurate, especially without JavaScript.

Edit: please don't mind me ghostposting kthx

Here's a simple modification to get the random number between 1 and 10

    [:div
     [:p "Hit Run to get a random number:"]
     [:h1 (+ 1 (Math.floor (* 10 (rand))))]]
If you weren't previously familiar with the syntax I figured this might help.

I can't help but feel that I'm doing this right now.

Hmmm, I wonder if it's possible to come to this realization just by thinking about it, and not having to hit rock bottom.

HMMM

Depends on what you meant by "Payload" in the first comment. I assumed it to mean "a bunch of bytes", so you could have just used URL parameters, which don't have a standardised maximum length, but you can generally rely up to about 2,000[0] or so. If that wasn't enough, you could split up the requests like the other comments said[1], or go full hack-mode and use the cookies[2]. (using a Set-Cookie response header to clear them after the request was made)

Edit: Of course this isn't recommended, but I think the time wasted trying to convince the (seemingly terrible) manager could have been better spent.

[0] http://www.boutell.com/newfaq/misc/urllength.html

[1] https://news.ycombinator.com/item?id=10649995

[2] https://news.ycombinator.com/item?id=10650110

Off-topic; regarding your attitude: The pricing of different services can be considered part of the living cost of an area, and is one of the many trade-offs you make when you choose to (not) move to/from an area.

For example: Europe might have better access to internet, however I'm not a fan of their policies, so I can choose to pay a bit more for internet in Canada, and deal with the lock-in.

It's silly to consider someone an idiot based off a single trade-off that they make. (Considering them an idiot based on many trade-offs is a different story)

I think it'd be cute to keep the absolute coordinate system, however create a simple web app which lets you point and click where you want it the brush go. For the Z coordinate, you could have a meter which goes up and down from 0-60 while you hold the mouse, and registers when you let go. (similar to many mini-game mechanics)

It could be done with the current Twitch stream in maybe 2-3 hours of dev work, thanks to Twitch using IRC for the chat backend.

Edit: s/coordinate system/absolute coordinate system/ s/but/however/

Meta: Finally, a comment that isn't hung up on the scrolling behaviour, or the price of the mining power. It's notable the rsync.net has similar, terrible web behaviour, but we seem to have sane discussions about it's service.

On topic: I think the neat part of 21 is that it seems to be a step forward in realising microtransactions, in a decentralised manner. Right now the only way around microtransactions is having a centralised pool, where you e.g. put $5/month in, and it pays services out of that pool. The problem with paying services directly is the base fees associated with transactions (for CC, it's around $0.15 + 3%, through Stripe).

With JavaScript enabled on GitHub, the separate links highlight different sections of the code.

If you start with if check 1 (such as in w.sh), a refactor-er would have to s/elif/if on check 2 and s/if/elif on check 1 if he wants to swap their order. By having all of the checks start with elif (such as in w2.sh), the refactor-er can change the order of the checks without having to modify them, making cleaner diffs.

I assume there are multiple steps you have to take in order to reach that performance, ie having to put it into ``Ludicrous mode'', then forcing the pedal to the floor. I assume it isn't something that could happen easily on accident.

It's also notable that Paul Walker wasn't driving when he died.