Nope, that is false. The language of the bill only requires filing if tax is owed. There will be a handful of folks on the cusp who will need to calculate their AGI to determine their state tax liability but everyone else knows offhand if they need to file.

The language is "Individuals not owing tax under this chapter are not required to file a return..."

It's a bad take.

i'd encourage reading it ahead of gifting (and i'd encourage grabbing it from archive.org or something, since it's 141 years old) because not all 10 yearolds are going to receive it the same way

as an aside, i checked and it takes four taps (with an thumb highlight thown in ) to define it from my phone.

I don't see the "humiliated" part. GOG definitely is picking a tiny fight and taking a principled stance but there's no indication Blizzard even cares, is there?

but also see: https://news.ycombinator.com/item?id=16986377

if I'm running the bridges local-to-the-client (I am, on my McBook) it's not meaningfully any less e2ee. encryption happens in the matrix client (running on the laptop), the encrypted message is sent to the homeserver on localhost, the bridge (on localhost) grabs the encrypted message and decrypts it, then the bridge re-encrypts it and sends it to Whatsapp (or wherever). the content of the message is as secure over the wire with this approach as using first-party apps directly

if one hosts their own bridges they're person-in-the-middling themselves and should take all the necessary precautions. if they're using beeper's hosted options they have to delegate read/write ability to beeper (though I think the signal and imessage bridges might be device-local), and beeper is clear about that.

there's an implicit analogue between comments and submissions. i suspect low karma users use the only tools at their disposal for both

I do, I didn't, but I understand why it happens. my HN account is 14 years old, I read comments frequently, comment rarely, upvote occasionally, and flag very very rarely.

I don't downvote because can't, I don't have enough karma yet. so, even if people who can't yet downvote don't know the full effects of flagging it's _literally_ their only option to indicate their belief something doesn't belong on the front page.

that said, the tags are kinda steep.

the tags are pre-paying for the webapp in general (vs only knownplus) but i'd prefer tags be a convenient shortcut instead of a cost of entry. that is, figure out whatever the appropriate price is for the web app and charge that (this seems like it'd lend itself well to freemium, 2 plants for free, up to n $12/yr, up to n $??/yr).

i have 43 pots of indoor plants and many of those have two to four distinct species in them. so that'd be $135 to add a single tag to each pot vs ~$15? to buy a bunch of NFC stickers

the tags also mean it's a $25 experiment to see if i even like the product (i might not really be the target market, but soil/light/water ranges and requirements being a tap away is pretty cool). i've currently got a bunch of different colored glass blobs i use to help remind me of watering targets but i'll usually do a quick search when it comes time to repot and mix up new potting soil mixes

that said, I have to echo some of the other folks here: this tool is not useful for determining the risk to my dog.

problems: - items known to be not-toxic are listed as toxic (water?) -items known to be toxic are not weighed higher than non-toxic items in search - items with dosage dependent toxicity don't expose that toxicity (onions are toxic, my dog would need to eat several raw onions to have any toxicity) - items known to be extremely toxic in low dosages (like xylitol) aren't present - the toxic component of dishes aren't listed

it should be able to carry a 0.5 m^3 cube and 70kg. maybe optimize for low cost and the ability to roll over some sporadic large cobble?

5 days without a human response is not great but it's not _awful_. Neither of the tagged reviewers have public commits in the last week, they may (hopefully are) both on vacation and enjoying some of the summer.

I've had open-source PRs wait for a couple months before people were able to take a look, stuff happens, people have things come up and people have competing priorities.

I really want to point out the timeline here:

  - drive-by PR was opened Sunday 8/6 at 8AM PT
  - CLA was agreed to Sunday 8/6 at 8:30AM PT
  - two... maintainers? were pinged Sunday 8/6 at 11:11AM PT
  - grumpy missive about Microsoft was written Friday 8/11 and posted to HN at 10:25AM PT

I honestly (not hyperbolicly) don't see how a phone not having a 3.5mm jack is relevant to the headphones _having_ a 3.5mm jack