Live data from Hacker News

I built a receipt printer for GitHub issues

aschmelyun.com

161–170 of 178 posts

Re: I built a receipt printer for GitHub issues

#161

Earlier quoted context omitted.

There's still plenty of places that specifically require a scanned copy of documents, instead of the original digital one. The printing and scanning process essentially makes it blurry and that's exactly what they want. I wonder if there's any tool that can achieve the same effect.

> I wonder if there's any tool that can achieve the same effect. I wonder if that's sarcasm, because it obviously should be possible with a simple call to e.g. convert/imagemagick. Of course, people who do the printing/scaning would need a simplified GUI to use it. A quick search on $searchengine showed that e.g. win2pdf has an option to generate an image-only pdf. The market seems to be covered. Maybe there's room f…

There is a version - it's been posted on HN before: https://github.com/baicunko/scanyourpdf

Re: I built a receipt printer for GitHub issues

#162
post #12

There's something about a physical reference to information that you can't quite capture digitally. You can hand it to someone. You can use it as a prop to express your happiness or frustration. You can destroy. I know this was a fun project but I hope we can capture more physical interactions in the future, and not just in VR.

Sorry to be ‘that guy’ but it is also a little bit wasteful.

Premature optimisation considering supermarkets go through like 200 rolls of this stuff a week per till haha

If someone starts minting NFTs for issues I’m in your corner tho

Re: I built a receipt printer for GitHub issues

#163

> Wrapping up and next steps The only logical next step here is to get that metal spike thing, so you can stab closed issues on completion.

This is how I work! I write my tasks on slips of paper and stab them on to the spike when done. https://share.icloud.com/photos/0f3i7xv2QbOeofiM4atMtSCzA

That's a lovely system. I would definitely put my hand through the spike accidentally!

Re: I built a receipt printer for GitHub issues

#164

Earlier quoted context omitted.

I once worked at a job where one of the owners of the company, when asked to send a pdf copy of a document, would print out the document on the shared office copier/printer, then scan it back in using the same copier/printer and have it email him the pdf. Every single time he ever made a pdf of any file, even hundreds of pages, he would do this way.

There's still plenty of places that specifically require a scanned copy of documents, instead of the original digital one. The printing and scanning process essentially makes it blurry and that's exactly what they want. I wonder if there's any tool that can achieve the same effect.

When I experience this, they want a “real” signature made by hand with pen ink, but scanned and sent.

Although I keep a few signatures ready in Preview, these do not suffice. I need a tool that makes the signature look like it was created with a blue ink ballpoint.

Re: I built a receipt printer for GitHub issues

#167

> Wrapping up and next steps The only logical next step here is to get that metal spike thing, so you can stab closed issues on completion.

It's called a spindle.

No, I’m fairly sure the correct technical term is “metal spike thing”.

/s

Re: I built a receipt printer for GitHub issues

#168
I wrote some software with two other guys for a restaurant in Copenhagen. I did the backend for an automated seat allocation system, while other guys wrote a web app for browsing and ordering menu items. The restaurant insisted that the orders be printed as paper slips, while the guys had imagined a PC running the ticket system software (that the chefs would interact with). In the end they did exactly what the linked post describes (but for another ticket system — Zendesk IIRC): an RPi connected to a thermal ticket printer, using some open source library for converting from the ticket data fetched from the API to the format required by the printer.

Re: I built a receipt printer for GitHub issues

#169
post #138
post #67

You should get a camera and write an OCR scanner that automatically scans the receipts as they are printed, then pushes it into a DB so you can view all your issues via a simple web application, replete with tracking, reminders, and then an e-mail integration that e-mails the opener of the issue when you put a comment on the receipt that's printed and rescanned.

I know this is a joke, but Jaron Lanier actually proposes machines communicate through human (?) or VR (?) interfaces. Something like that. I spent 15 minutes searching the web and my library but couldn't find it. I read two books of his, it must be in "Dawn of the New Everything" or "You Are Not a Gadget". I'm fuzzy on the idea, but found it interesting enough that I remember it.

I once got a phone's speech-recognition system to recognize another's text-to-speech system, just to see how accurate they'd be. And I know one game that has a speech-recognition system to post in chat and then other players can use text-to-speech to read the chat aloud. Fun times.

Re: I built a receipt printer for GitHub issues

#170
This is cool and quirky, but if the core problem is really just “when you email me I might forget to reply” I’d first look at reducing noise, not adding signal. For all its weird preachy branding, the idea of inbox zero is a great for implicitly turning emails into todo items.
Post reply on HN