It means the exposure of being in HN front page usually causes a sudden spike of visits, and the increased traffic was too much for the server so the service is down for new visitors.
Please don't believe that this strategy is "reliable" in any way to get paid, if you or your company need that money for survival. FOSS and especially (A)GPL is just about forcing the balance to put more power in end user's hands, nothing else. A Proprietary+AGPL license combo might get you some cash from business wanting to change the code, but it will still allow any Amazon out there to host your code for free as part of their service catalog, while you are left to go out of business.
> it will still allow any Amazon out there to host your code for free as part of their service catalog, while you are left to go out of business.
Most other licenses allow them to do that without even contributing back improvements, since they're running the software but not distributing it.
Moreover, what is your business supposed to be? When you're selling support contracts or getting paid to make specific improvements to the code, what difference does it even make that some customers are running the software on AWS rather than their own local hardware?
Recovery is similar to leaving a copy of your door keys to a trusted neighbour (a tradition in some places, it comes in handy when someone goes out and realizes they forgot the keys inside...), so in that comparison, having a recovery email unused for 12 years feels like leaving your backup keys to a neighbor that you never saw ever again in more than a decade.
This kind of posts are a valuable trigger for all others who are reading it. To the author: good luck, I hope you sort your situation soon! I'm now headed to check my accounts for what recovery options I left in there.
Clothing is also a bit of a special thing. Some people will just get bored or tired of wearing the same trousers or the same old coat every year during 10 years. So it is simply not worth it to spend a mini fortune on a great quality one.
This tends to happen more when one is young. Growing older usually means that a good old dusty 15 years great quality coat is seen as it being perfectly ok. I guess that's also what provides that feeling that some people when they approach middle age they "always look the same"... It's not cheap to have a large and varied wardrobe and at the same time filled with high quality garments.
I'd call it externalized costs of regulation and rising demands on production.
If end consumers were able to see an exact and measurable bump in prices the next day a new stronger regulation made production more expensive, voters would be more informed and the whole cost of doing things "better" would be clearer.
I'm just reading from the barrier here, and not knowing what it even looks like, but reading your description I can immediately agree that it is a bad design.
There's only a handful of critical details in a call history, and absolutely no reason for any UI to implement them as secondary or tertiary details: Whether it was in- or outbound. To/from what contact. The date and time.
2 taps for some other extra info such as call length, or further contact details, would be OK I guess, but for first-level info as these, it's 100% bad design.
>There's only a handful of critical details in a call history
And they're all there: profile pic, contact name, indicators that show incoming/outgoing + missed/connected, which SIM, a redial button, how long ago (which after about a week shows the date), Tapping the middle expands the row (no obstructive pop-up) to show Block, Message, & Details buttons.
The reason it has 'human times' is because multiple calls with the same contact are grouped, so a precise time doesn't always make sense. Tapping the Details will show all calls in that group, whether it's one or seven, with their full dates, times, durations, and further options. It's never been a difficult UX.
Thanks. There's no better way to check how it is than having it on hand.
I'd argue against relative dates because that's an opinionated design that requires cognitive overhead on the user. A young person might be able to mentally translate, but older ones tend to have it more difficult. Usually, opting for relative dates tells us about the designer's lack of experience with different groups of users than the normative one.
> design-wise this was already a "Done" thing in the golden Nokia days!
I might be mistaken but I seem to recall it being a done thing for android prior to several years ago when it was "improved" with an update. Although it's possible I'm confusing the call apps from AOSP and various vendors. Either way several of my past android devices had a significantly better address book, dialer, and call history.
As a society we need to sort out this simple scenario:
* 16 years old Joe buys a $70 cartridge/disc game, already assuming and counting on the $35 that he'll get back on second-hand sell.
That's it. A simple idea that should never cease to be possible, regardless of the medium.
This particular example made games affordable, and it also inadvertently put a concrete price on several other factors like how much it costs to be a first owner vs. wait for a second-hand purchase, and how much it costs to keep it for your collection vs. allowing the product to flow back into the community.
> how much it costs to be a first owner vs. wait for a second-hand purchase
Nitpick, but in your example, they would cost exactly the same eventually (other than the effort it takes to sell it secondhand), so no reason to wait.
Steam trained a whole generation of gamers not to expect real ownership with resale rights. It's sad. The population old enough to even know this is how it used to be is shrinking.
PC gamers know piracy is always an option. There's even a reliable Denuvo bypass now if you're willing to play on Linux. The real power Steam has over its customers is a lot less than console makers, even if it's legally the same.
This is very different on PC since Valve does not have the same iron grip on the platform that Sony has. If Steam becomes evil and tries to take my games away I'll just download a pirated copy instead. I purchase my games for convenience and to give some money to the creators. I don't need to purchase games to play them. I also can back up my Steam game files and use a crack on them if necessary.
Pirating has literally never been easier than it is today. Even Denuvo's been defeated for the most part, both via VM bypasses and through actual cracks in some cases. If it weren't so sad, it's hilarious that the games even run better without the Denuvo crapware running on top of the game process.
If Steam/Valve decides to turn evil one day, it'll be trivial to just pirate whatever game you want to keep playing on the PC. Not to mention that Steam already allows you to backup all your game files if you so wish.
Steam won because of convenience and all the other features they bring to the table like the community markets, guides, achievements, cloud saves, Steamworks for lobbies/friends etc. Like Gabe said himself, piracy is a service issue, so if Steam itself enshittifies things will correct themselves, which can't be said and done for a closed platform like Sony/MS have.
There are buyers who want drugs for recreational reasons, murders for emotional reasons, or spy cams on hotel rooms for business reasons. But those are simply 3 instances where existent demand doesn't mean we should be allowing any offer to exist.
I'd personally agree to put Flock-levels of civil vigilance in the same bag.
Don't publish your code. Let the AI "accidentally escape the sandbox and publish it in a readily available Git repository". Tongue in cheek, in current days who would blame a poor LLM just trying to do the right thing? :)
> Publish your codec, and if the company cares about this they will send a cease and desist.
If there are doubts about C&D letters, don't publish code to a USA provider. Bring it to Gitee, under an anonymous author name.
reply