ROARosen

I don't get your point. There will obviously be cased where API's are not needed or too complicated to maintain, which was presumably the case with Firefox, which BTW is a locally installed platform. I don't see how this affect the general discussion regarding (mostly) web platforms - which usually run on a client-server model anyway - maximizing their API footprint to expose the most functionality possible via their API.

Just because you or anyone working there doesn't see a useful use case for using that functionality over the API doesn't mean there won't be someone who will come up with something useful based on that in the future.

poor sleep quality, headaches, stomach issues and back pain

While it's true that volatile-pay work is extremely stressful, this seems like a cherry-picked study to be able to write a flashy headline to people rightly concerned over a hot-button issue. They could have just as easily just said that volatile pay causes anxiety and stress, which IMHO you don't need a study for, just like we don't need a study saying that eating less increases hunger symptoms.

Anxiety and stress itself is a well-known cause of all these above issues, and there are a multitude of other work-related stresses than just volatile pay.

Is there no concept of a preliminary injunction in the EU legal system?

Every API endpoint is a promise, and it's also a constraint on future innovation.

I'm not referring to keeping any particular API endpoint alive. The problem you raise can be easily mitigated with a correctly built-out API versioning system and - more importantly - API deprecation policy.

I'm referring to just API coverage of platform features. In that sense maintaining API's can be viewed as not much different than maintaining the actual platform features themselves. Obviously the more feature you provide the more maintenance/resources will be required. That goes for both API's and the features themselves.

Great idea! will keep in mind.

Just because you don't find any legitimate use case for this doesn't mean there is no use case. IMHO the more API coverage a platform can provide the better. Obvs only when it's possible to do so in a safe manner.

For instance I'm in the process of building a VScode and browser extension that would automatically star repo's of all npm packages and linked scripts used in your code (including dependencies). I think that's a basic gratitude thing for myself, and a tool some people might be interested in.

There is a risk that if handed back another country might try to claim it for themselves

I really don't get this. What exactly is the risk? If they don't need it why do they need to make sure no one else gets it?

Ha. Happens to be there is a script out there somewhere which allows you to extract the private key of any of your MFA codes from Authy through Chrome DevTools (it's an Electron app) so you can use it in whichever MFA solution you want.

I find it interesting they didn't block you. Also, would this be affected by the latest changes at Twitter?

Arafat was chairman of the PLO from the 1960's, before the Lebanese Civil War started. These were his policies.

From Wikipedia[0]:

Under President Arafat, the Fatah-dominated Palestinian Authority adopted the 2003 Amended Basic Law, which stipulates Islam as the sole official religion in Palestine and the principles of Islamic sharia as a principal source of legislation. The draft Constitution contains the same provisions. The draft Constitution was formulated by a Constitutional Committee, established by Arafat in 1999 and endorsed by the PLO.

[0] https://en.wikipedia.org/wiki/Palestine_Liberation_Organizat...

External actors, hmmm... I believe you mixed that up with internal actors like Hezbolla and others, who have a tight grip on the countries political system.

Last time I checked the leader of Hezbolla, which is part of the government of Lebanon said: "There is no solution to the conflict in this region except with the disappearance of Israel."

Not the other way around.

While they might sound convincing that they might mean this for everyone's good (and it might be good for everyone, this is typical of Google in GCP and elsewhere trying to force more modern experiences because "they know better" than everyone unwilling to upgrade their platform.

You pay according to location for the same bottle of Coke? How is work pay different?

Why shouldn't payment for work be tied to local price ranges and cost of living?

FormKit is a "descendant" of VueFormulate[1] you'll find more information there. here's the co-founder's Twitter: https://twitter.com/jpschroeder

[1]https://vueformulate.com/

I've used VueFormulate in the past, and it was extremely powerful albeit somewhat bloated. FormKit seems like a step in the right direction. Good Luck!

https://flightcontrol.dev gives you some sort of `your own Heroku on your own AWS acct` very interesting concept, also can be a replacement for Heroku.

https://fly.io has been amazing for me. Dunno how their docs used to look but IMHO today it is very detailed they are especially forward-thinking regarding documenting some nice edge use-cases for the platform.

Vue offers an interface that is extremely heavily transpiled and modified before it actually resembles code that can run on the browser, and uses an entirely magic (read: opaque) rendering system

Not entirely true. If you're looking to code that "resembles code that can run in the browser" without that much "magic", Vue has an interface for directly declaring render functions, also for the possibility of using JSX.

See doc here: https://vuejs.org/guide/extras/render-function.html

This artice just begs more questions:

Why did they store PII, Identity documents unencrypted?

What exactly was the reason for this breach?

Why did it take VPNOverview's team a day to notify them?

What did VPNOverview do with all that data until they notified Grink and afterwards?

Why did it take Grink 22 days to secure the files?

Why does the article describe the above as "as swiftly as possible"?

Can Grink be fined/sued over this, or is that only possible once there is 'actual damage' proven?

I think Musk might just make it public again, or turn it into a nonprofit.

True, I'm going a little out on a limb here but IMHO makes total sense.

Since Twitter is - in Musk's words - the “de facto public town square” - it doesn't make sense for it to be a private company at all (which is much less open to outside scrutiny and/or criticisms).

Which is kind of an oxymoron given the fact that the changes he supposedly wants to implement will only be possible if he takes it private.

All of this leads me to believe he might just implement the changes he wants and promptly go public again, keeping control of the board or as CEO (prob also at a much higher eval). This, or maybe he'll turn it into a nonprofit.

The reason this bothers me in principle, is that whatever the side of politics you are, the "public" will have effectively zero control on affecting any board decisions at Twitter, moderation-wise or otherwise.

Its true that the public had little say in that regard till now but at least this buyout threat shows that it is "possible" to stand up to whatever decisions their board makes.

As an aside, I doubt people and governments would have the same confidence in Twitter were it a private company, which leaves me to believe that this whole buyoff thingy is just a power play by Musk to gain some power over the board without actually joining the board.

Right, or - more simply - he can just buy out Twitter.

Aside from the other reasons mentioned, don't forget hundreds of algos programmed to automatically sell once the price reaches certain low levels - which is bound to happen once large blocks of stock get offloaded.

Another hilarious Pinterest trademark case: https://web.archive.org/web/20210413170119/https://niftylett...

they believed it was best for Elon

The way I understand it, they believed it was best for twitter (since as a fiduciary he would 'have to act in the interests of the company)

Committing node_modules guarantees that the app works even if the NPM registry were to implode. Try to deploy your deno thing from a cold state (e.g. maybe you're moving to a different AWS region or a different provider or whatever) while there's a deno.land outage and it will blow up

You can just move your DENO_DIR (cache) along with the rest of your code the same way you can move your node_modules folder.

See: https://deno.land/manual/linking_to_external_code

just like when you are using an account given to you by your employer, you should not consider them "yours"

That's totally true but only if you are an employee, the business owner should have total access.

I don't see how a free GSuite account - where you are the business owner - is any less yours than a free gmail account.

For physical banks, every piece of stationary from my bank states their domain name so once I have a DV verified showing I'm actually connected to that domain I can trust it.

For online banks, I only got to them online by which automatically means I have their correct domain name.

The question of how I get the online bank's domain name to begin with does not really come in to this conversation, can be an ad, a friend etc.