whelchel

I've wondered this myself. I would love a version of reddit only with real people. I'd also love it if the anonymity was a gradient, and not a binary.

E.g. you could join a California based subreddit and verify you are a California resident, but not go further than that, etc., without cross-tying with other claims you've made about yourself in other forums/sub-reddits.

I've thought about using the various crypto-decentralized options here, such as Proof of Humanity or BrightID.

I'd be curious if you've made any progress here thinking about this, feel free to DM me via profile.

This is an amalgamation of ideas I’ve read and may be totally from elsewhere, but I think a good approach here would be to handle this more dynamically.

Every patent is taxed at some arbitrary rate - say 3% a year. The catch is the patent holder decides how much it’s worth. Low value means low tax. However, whatever value you pick is an open price for licensing by anyone else.

Ultimately, use it or lose it. If you don’t think it’s valuable and someone else does, the world still benefits.

Tune the tax percentage based on how much you want to hurt patent trolls vs impact on actual long term R&D

If you know, can you share names/links? Thanks!

Could a core common library that Chromium depends on update its license to block use in software that supports attestation, roughly?

If Google wants more control and closure of the web, they shouldn’t benefit as easily from its current openness.

I have a similar experience for personal life. I use this too - it's imperfect, but it's a nice balance of complexity and utility that doesn't get in the way once you set it up.

If helpful for others, my language

--

As a resident of [STATE], I'm writing to express my dismay at some very recent specific tax changes negatively impacting small businesses innovating in technology, as well as express my support for a recently introduced bill to unwind those changes (S.866 - American Innovation and Jobs Act).

As both a software engineer and entrepreneur, changing software development expenses to be exclusively treated as R&D expenses amortized over many years will harm our country's ability to create innovative companies on the frontier of technology, as smaller businesses that take up-front losses in exchange for growth and deferred income will be dramatically penalized and go out of business. Conversely, large companies with established revenue and credit will not be harmed, increasing their ability to reduce competition in the market. So many of America's great companies in the last decades have come from a small number of people working together on software and hardware, losing money up front to gain money in the future. If you cannot write off the up-front expenses as truly spent money with uncertain return, those businesses cannot start.

It's a lose-lose-lose - this change hurts the little guys, helps the incumbent big guys, and will reinforce competitive sclerosis relative to our geopolitical competitors.

I don't know what the exact right answer is, or if S.866 is it - but the current situation is certainly not correct. If we want America to be competitive and create high-paying modern jobs, we can't tax new companies to death before they have a chance to get started.

The Economist deliberately does not put bylines on the vast majority of content - it’s not sinister.

https://www.economist.com/the-economist-explains/2013/09/04/...

Love this idea! Clever to build up the repeated skills and software internally, and take cuts of the moat-margin other SaaS tools reap from switching costs.

Can anyone comment on how concerning this is? It doesn’t seem good. I was considering updating from 1Password4 to 7 and biting the bullet on the subscription model. Based on this case study it seems 7 is a security regression trade for UX improvements. Now, I’m considering Keepass or at least waiting to hear some responses from providers involved.

Also a fan. I'm also switching permanently to Firefox after this incident rather than use multiple browsers depending on the purpose.

There is some merit to that idea but I think you may be missing a few things. Often, parking is placed between a bike lane and the side walk. Bikes need to be able to cross lanes, often in cities, to make left turns. How can they do that when they're up on a curb to start, but additionally, with potential street parking in the way?

I think technically in many jurisdictions, bikes are to be treated as vehicles. Whether or not they're always treated that way is up for debate (and vice versa), but it may explain also partially why things were done that way.

Command line it seems

This is great! Bookmarked. Numbers are rattled off so quickly in foreign languages, and small syntax differences where the order is changed and really cause new learners to pause and miss the complete rest of the sentence etc.

This is a pretty solid article. I think the JIT learning idea is a strong one; his anecdote about the public speaking advice he received immediately after a speech that stuck to this day resonates. Sometimes the smallest bits of thoughts and advice like that make a huge difference simply because they arrived at the time when you were most receptive and "vulnerable" to hearing it. Though I think learning can be fun, I see the point the author is making. I wonder however, what's to be done when there is no one there for JIT help? That's when we push the frontier of human knowledge, and cultivating that is important as well. I couldn't help while reading this to find it analogous to compiled and interpreted languages, in more ways than one.

When it comes to changing things on HN, I think something like comment collapsing would be much more helpful than de-dup (as some of the other comments mention), though I know there are extensions that help out.