didn't the underlying API they built upon ramp up their pricing and effectively price them out?
like a precursor to reddit's own API pricing changes that made it hard for 3rd party clients to compete.
The saving grace with these API wrappers is that local models being a thing can still let them hedge against the underlying AI labs eating up their stack.
It appears the individual was unable to distinguish a display name from the actual email address (common phishing tactic of having something like [email protected] as the email display name while the actual email address is a random throwaway). [1]
Good reminder to use a password manager as well (as it would also catch the 'npnjs' typo squatted domain too).
Similar incident happened to the HIBP guy who mentioned ignoring the password manager safeguards due to being half asleep while on the plane.
Also keep in mind you can disable install scripts in npm from running (if you happen to not do your development in an isolated environment) via configuring your .npmrc with
> 2. They support premium domains, so you can be struck by lightning and randomly have the price of your domains dramatically jacked up (had to drop a domain due to this).
Do you have an example of this as it is against ICANN's rules IIRC.
The only instances I have seen about this were the posts here on HN when someone didn't read the registration price being at a discount compared to the renewal price thereafter.
If there is of course a legitimate instance of reclassification into a premium domain after the fact, you have a big case on your hands.
If the worst is a public mea culpa and following the agreements you should've done in the first place, that barely seems like a deterrent to infringe the license.
Might as well create a crawler bot on github and slurp up all the GPL/AGPL for your new AI-coding startup, iterate fast, make profit, then pay a pittance in legal fees and a small "We're sorry".
> and if the spirit of HN is to judge without facts - then I apologize.
Although snarky, I am sure you would appreciate if HN doesn't devolve into sensationalist titles such as: "PHP sucks" ad nauseam since there are plenty of social media networks that get flooded with titles like that already.
Just as we (the audience) in good faith read and judge based off of the merits of the article's content - one could also argue that an author should treat the audience with similar courtesy of not needing to:
> misleading (purposely, because it attracts interest)
Not saying this applies to this article since in my subjective view I didn't find the title misleading or egregious.
You might also be interested in seeing the recent edit history of titles on HN
> The titles are misleading (purposely, because it attracts interest)
I am neutral to this conversation but thought you might not want to justify this point as it is against the spirit of HN. Specifically in the guidelines:
> Otherwise please use the original title, unless it is misleading or linkbait; don't editorialize.
Which would give the submitter permission to change the title to something more substantive.
While I use and enjoy their other services, I would advice taking this incident into consideration about their registrar services that "prevents transfer-out of domains, sets to 'pendingdelete'"
Twitter says it's been working on it since last year.
But as for the whole "3 days before he bought the shares" - He's been accumulating for far longer than that and even the CEO of Twitter mentioned they were in talks with Elon about being on the board "in recent weeks" [1]
With that said, yes it may be manufactured coincidence mostly driven by the new CEO change and not by Elon buying shares
Nowadays when signing up for valid services, some don't let you opt-out of the marketing emails until much later in the flow; the worst offenders ignore your opting out options by including a new category of marketing-type emails every couple of months that you have to go in and untick.
Wouldn't that be classified as spammy ads from a valid message (when done using dark patterns with no one-click unsubscribe option)?
You can scroll directly to the bottom and see the final comparison table.
Here's a screenshot for your convenience [1]
I agree with you that I prefer to get straight to the point, but this pet-peeve tangent doesn't seem to be a productive discussion of the actual merits of the tooling.
like a precursor to reddit's own API pricing changes that made it hard for 3rd party clients to compete.
The saving grace with these API wrappers is that local models being a thing can still let them hedge against the underlying AI labs eating up their stack.