The issue stems from the fact that people believe prediction markets are gambling. Prediction markets are financial derivatives regulated by the CFTC. This definition is not something I am trying to defend, I am simply accepting the current legal definition to explain why funding your Kalshi account is not considered a cash advance. Gambling is not even allowed in my state, yet Kalshi is permitted. Legally, Kalshi is not gambling as of the current legislation. That is why, for the nth time, funding your Kalshi account is NOT considered a cash advance.

People should do a little bit of research before blindly downvoting, or maybe even try it for themselves.

Comments URL: https://news.ycombinator.com/item?id=48631319

Points: 3

# Comments: 0

This is not a realistic replay of what a common LLM might actually print out - it's entirely fabricated. But for the purpose of estimating the feel of tokens per second, I suppose it's good enough.

Comments URL: https://news.ycombinator.com/item?id=47810357

Points: 40

# Comments: 9

So if you typically use a file-backed DuckDB database in one process and want to quickly modify something in that database using the DuckDB CLI (like you might connect SequelPro or DBeaver to make changes to a DB while your main application is 'using' it), then it complains that it's locked by another process and doesn't let you connect to it at all.

This is unlike SQLite, which supports and handles this in a thread-safe manner out of the box. I know it's DuckDB's explicit design decision[0], but it would be amazing if DuckDB could behave more like SQLite when it comes to this sort of thing. DuckDB has incredible quality-of-life improvements with many extra types and functions supported, not to mention all the SQL dialect enhancements allowing you to type much more concise SQL (they call it "Friendly SQL"), which executes super efficiently too.

[0] https://duckdb.org/docs/current/connect/concurrency

I also think having a dropdown for the address search is somewhat expected these days, but is lacking here. That might be on purpose or due to a technical limitation, but just thought I'd mention.

Comments URL: https://news.ycombinator.com/item?id=47526503

Points: 6

# Comments: 2

Comments URL: https://news.ycombinator.com/item?id=47493857

Points: 30

# Comments: 11

It seems like there's a lot of personal information being asked for / thrown around... including a debit/credit card number?

Is there no better way to handle the bounty payment?

Your comments are more practical (and maybe aimed at a layman's use of Starlink) but I am talking about the theory of Starlink supposedly interrupting a perfectly-working connection in order to change your IP, which interrupts everything, by design of TCP/conntrack. Whether that operation is fatal or not due to retries or whatever else is not my point at all.

Also, ISPs at home don't randomly disconnect you to give you a new IP. They may give you a new IP when you disconnect and reconnect for other reasons, but they should never dump your connection on purpose just to give you a new IP for no reason. That's not good design at all, hence the question about how Starlink handles wanting to give you a new IP.

An interesting problem - I wonder what they truly do here. I suppose people expect interruptions with Starlink so doing an IP swap wouldn't be all that different to losing service due to obstruction for a few minutes.