Readit News logoReadit News
_rami_ commented on At this SF grocery store, you can't leave unless you buy something   sfgate.com/food/article/s... · Posted by u/c420
_rami_ · 4 months ago
This is the default in some countries, e.g. Italy in major cities :D
_rami_ commented on Writing your own CUPS printer driver in 100 lines of Python (2018)   behind.pretix.eu/2018/01/... · Posted by u/todsacerdoti
Havoc · 10 months ago
Ideally don't buy a thermal printer at all. The paper usually contains BPA. You found one that says BPA free? Yep they switched to BPS. Also toxic and harmful to reproductive health.

If you absolutely must - use a European supplier - both are banned there for thermal paper.

_rami_ · 10 months ago
There's completely safe thermal paper in Germany by this company: https://www.oekobon.de/ There's a similar company in France, I forgot the name
_rami_ commented on Writing your own CUPS printer driver in 100 lines of Python (2018)   behind.pretix.eu/2018/01/... · Posted by u/todsacerdoti
_rami_ · 10 months ago
Author here. Funny this ended up here again!

These days, we don't use this any more. First, because we now use primarily original Boca printers and are allowed to use the official drivers, and second, because we do 99% of printing from Android devices, where we also handle the protocol conversion ourselves, but it's a lot simpler without CUPS. Still, was a fun ride doing this back then!

_rami_ commented on CAPTCHAs are over (in ticketing)   behind.pretix.eu/2025/05/... · Posted by u/pabs3
timshell · 10 months ago
I'm a founder in this space (www.roundtable.ai; YC S23)

Behavior is a big missing link. Many CAPTCHA services (including Google reCAPTCHA v3) claim to use behavioral analyses, but you can disprove this using Operator to fill out a form and see reCAPTCHA and other bot detection systems flag it as a human.

At Roundtable, we rely on first-order behavioral markers (keystroke, mouse, scroll, click) etc. When first-order are sufficiently spoofed, analyze higher-level cognitive traits (e.g. incongruent effect in Stroop)

_rami_ · 10 months ago
(Author here) Interesting! How do you differentiate between a bot and a screenreader user? Both won't move their mouse, scroll, etc but only send a single click event
_rami_ commented on CAPTCHAs are over (in ticketing)   behind.pretix.eu/2025/05/... · Posted by u/pabs3
jsnell · 10 months ago
> So what’s left?

If the profit per successful abuse event is $200, the author's suggestion of limits on credit card numbers or phone numbers won't work either. Those are only effective against scaled abuse up to something like $1 / event. Bank accounts would almost certainly be more robust, but that seems quite hard to implement outside of a handful of countries where the online auth ecosystem is built around banks.

With generic abuse background, but not knowing anything about the ticketing abuse ecosystem, is doing the sales on a first-come-first-serve basis an absolute necessity from a business perspective? There would be a lot more tools available if the problem was reframed from "decide instantly whether to sell this buyer a ticket" to "decide which 10k of these 100k intents of purchase received during the first 24h to sell the tickets to". And by more tools, I mean offline analysis and clustering, not just a lottery.

(You'd still want to combine that with strongly personalized tickets though. It'd be how you address for bots-as-a-service, not how you address buying tickets to resell.)

_rami_ · 10 months ago
(Author here) Anything else than first-come-first-served requires strong identity to avoid people trying to get better chances with many entries into the pool, thus falling into the "sacrificing privacy" category
_rami_ commented on CAPTCHAs are over (in ticketing)   behind.pretix.eu/2025/05/... · Posted by u/pabs3
frabcus · 10 months ago
The option that strikes me as missing, is making users pay a cost before they are randomly entered in a lottery for the ticket.

So, for example, everyone pays $0.01 on their credit card, or does a holding charge on their credit card, or registers their identity. All in a 5 minute (or 1 day!) window. And then after the window, tickets are randomly distributed amongst every card which so registered.

You could check multiple things - phone and card and Government ID if necessary (lowering the privacy).

This also feels fairer and less stressful - instead of a lottery based on your internet access, or ability to run lots of browsers at once.

This feels harder for scalpers to do to me, as they need more fake identities, but I'd be curious about the actual ratios when trying it. What goes wrong?

Another one I predict is that you can't buy digitally. For examples, the Lewes fireworks display you have to buy tickets in person in a bookshop in Lewes. Doesn't help if you make a digital ticketing system though!

_rami_ · 10 months ago
(Author here) Yes, every kind of lottery/raffle is a possible solution but only with strong identity verification to avoid double-entry and hence only with sacrificing privacy, as mentioned in the article.
_rami_ commented on Ask HN: Who is hiring? (October 2024)    · Posted by u/whoishiring
_rami_ · a year ago
pretix | Linux sysadmin | https://pretix.eu/about/de/job/ops | Heidelberg, Germany | Full Time | REMOTE (DE) | €57k+

u/_rami_

KarmaCake day100November 2, 2015View Original