Readit NewsI can’t claim I’m the first one to think about this, but every time Ticketmaster shows up on HN I keep coming back to this idea:
Sell the tickets with regressive price based on time. Sales starts say 2 months before event, initial price is truly exorbitant, say one million dollars. Price decreases linearly down to zero (or true cost price). At any point, people can see current price and the seats left.
Now every potential spectator is playing a game of chicken: the more you wait, the lower the price, but also lower are the chances that you’ll have a ticket. That would capture precisely the maximum amount of dollars that each person is willing to pay for it.
This idea sounds extremely greedy, because it is, so I can’t fathom that no one ever pitched this in a Ticketmaster board meeting.
My idea, however, was a bit less greedy. Once you sold the last ticket, that would be your actual (and fair) price-per-ticket for the concert, and everyone would be refunded the difference. You’ll never know how low it will go, so you shouldn’t overpay and hope it will lower later. I’m pretty sure Ticketmaster will skip this last part if they decide to implement this.
There are multiple issues with my idea, it’s elitist, promotes financial risks on cohorts poorly capable to bear them, etc etc, but it will definitely fix the scalpers problem. Pick your poison.
The time at which scalpers buy tickets becomes irrelevant. They can resell tickets at arbitrary-high-price + margin because buyer know they will receive refund for the exceed amount, thus pay only (final price + scalper margin) for the ticket eventually.
Bonus: buy ticket from scalpers after price settled, you will get a determined price, no more guessing and find inner peace.
The problem for scalpers is that if they buy too many tickets, the final price may become too high to be attractive for real buyers.
sorz commented on Magma: A foundation model for multimodal AI agents microsoft.github.io/Magma... · Posted by u/SerCe
In the mug-scrubbing video, the person clearly pretends to wash the cup but does not seem to want to get their hands wet anyway. I'm curious as to when models can figure out that subtle thing.
sorz commented on Learn AutoHotKey by stealing my scripts hillelwayne.com/post/ahk-... · Posted by u/Tomte
I have swapped Caps Lock and Escape on my Linux personal laptop and I have grown used to it. So when I dual booted Windows on my machine, I used Powertoys[1] to achieve the same.
At work, I have no option to install Powertoys or Uncap[2] for that matter. AutoHotKey is the only way, but I'm unable to get it to work. I used this StackOverflow[3] answer, but with this, both Caps Lock and Escape send both of the keys. So I'm stuck occasionally messing up my Teams messages :)
[1]: https://github.com/microsoft/PowerToys [2]: https://github.com/susam/uncap [3]: https://stackoverflow.com/questions/38558376/how-to-map-caps...
Did you try scancode map registry[1]? I use it to swap Ctrl/CapsLock and it works well even with RDP softwares and run-as-admin apps which PowerToys couldn't handle.
[1] https://superuser.com/questions/550679/where-can-i-find-wind...
> Ignorant person here (sorry if I'm asking a dumb question), but given the larger population of China to Taiwan, why is that not the correct thing to do? Or is this "Traditional Chinese" a language spoken only in Taiwan?
They addressed this:
> NOTE: The Google Translate menu only says "Chinese (Traditional)". However, if you pick the option, you will see the language code reflected in the URL is zh-TW, which means "Traditional Chinese as being used in Taiwan". The alternative option for Google to fix this problem is to officially drop zh-TW support and switch to an appropriate language code instead, such as zh-Hant.
The whole post is on base on the fact that "TW" in their URL. But I think this is really just a internal implementation detail of Google Translate, which is not intended to display to users (e.g. complete hidden on their app). Everywhere on their UI shows "Chinese (Traditional)". That is what they try to communicate with users.
Sure, zh-TW is somewhat misleading. But they nor say that parameter is a ISO 639 or RFC 5646 conformed.
sorz commented on RWKV: Reinventing RNNs for the Transformer Era arxiv.org/abs/2305.13048... · Posted by u/ianbutler
I wish this was written with more care. None of the symbols are defined.
Worst of all, they use "channel dimension" in a sequence model. What even is a channel in a sequence of tokens? This happens as soon as you have a single person with CNN background on the team and it makes zero sense. What if you actually have channels in your data? What then?
They said the paper is still working in progress and will improve it.
sorz commented on ChatGPT outperforms crowd-workers for text-annotation tasks arxiv.org/abs/2303.15056... · Posted by u/georgehill
Is NLP a solved problem now?
Just watched a talk[0] about natural language understanding research in post-GPT-3 era. Old issues may has been solved, while new topics are coming to this area (quoted from the slides):
- Retrieval augmented in-context learning
- Better benchmarks
- Last mile for productive application
- Faithful, human-interoperable explanations
sorz commented on ChatGPT outperforms crowd-workers for text-annotation tasks arxiv.org/abs/2303.15056... · Posted by u/georgehill
Is NLP a solved problem now?
To the author, I wish you best of luck with this but be aware (if you aren't) this will attract all kind of bad and malicious users who want nothing more than a "clean" IP to funnel their badness through.
serveo.net [2] tried it 8 years ago, but when I wanted to use it I at some point I found it was no longer working, as I remember the author said there was too much abuse for him to maintain it as a free service
I ended up self-hosting sish https://docs.ssi.sh instead.
Even the the ones where you have to register like cloudflare tunnels and ngrok are full of malware, which is not a risk to you as a user but means they are often blocked.
Also a little rant, tailscale has their own one also called funnel. It has the benefit of being end-to-end encrypted (in theory) but the downside that you are announcing your service to the world through the certificate transparency logs. So your little dev project will have bots hammering on it (and trying to take your .git folder) within seconds from you activating the funnel. So make sure your little project is ready for the internet with auth and has nothing sensitive at guessable paths.
[2] https://news.ycombinator.com/item?id=14842951