Unbridled data collection is a requirement for a startup? Maybe in the US, pump-and-dump-startup schemes; I like to think other countries found companies that actually do something useful.
I mean Spotify has been one of the biggest driving forces in reducing music piracy, in part thanks to being more convenient.
On the other hand, they don't pay artists nearly enough so the flipside is that to the artists it doesn't actually make that much of a difference whether someone listens to them on Spotify or just pirates the music.
Really wonderful, sustainable businesses when the inevitable privacy legislation hits the books in the United States. Just great high quality revenue, wish I could get in on some of that
Despite what these “studies” say, the Amazon is NOT near a tipping point of destruction. In fact, it’s not even close.
These publications fail to disclose that these fires are seasonal and will continue to happen without man-interference.
These so-called protection of the Amazon is part of an agenda rich countries have to keep Brazil uncompetitive. How about we start rebuilding green space in Western Europe?
How about we start planting more trees in southern California?
The link is no not a peer-reviewed research in Nature, it is a "News Feature" written by "a science writer based in
Manaus, Brazil."
The cites for the tipping point are two editorials written by the same team of two researches in Science Advances, these are editorials, not research articles.
The research article claims that with a 40% deforestation the rain reduction will cause problems, but in the editorial they use hand waving to reduce that to 20%.
Yes, that's definitely the balance to maintain. Ease of entry, vs tooling to manage the project as it grows. The main reason I see it being an inhibition is due to the size of the HTML spec, and the number of pages that it will need.
I think this is why a lot of sites take markdown, then add their own extensions, like how there is "Github Markdown" among many other flavors. That's definitely one route, but I see something like ReStructuredText or Asciidoc as more mature and interoperable, while still being relatively easy to master in the same way as Markdown. Since they can both produce docbook output, vastly easing any migrations in the future by adhering to an industry standard.
It's not that easy. We have 60+k pages carried over from 15 years of organic evolution. It's unstructured and messy.
A move away from HTML to something "more popular syntax" (like Markdown) is NOT easy.
Talking about responsibility to society is hypocritical when you're paying lawyers to hide money away from medical care, schools, infrastructure and other tax funded sources in countries all over the world.
Tim seems like a person only interested in talking in points that smear his competition. Understandable from pure selfish business perspective, but the fact that he's trying to make a moral argument just leaves a bad taste in our mouth.
Can't answer that but on a related note, recent zsh fully supports true color. You could always use it in things like prompts with literal escape sequences but it'll also work for syntax highlighting etc and interpret colours in hex triplet form for you now.
No. The discussion here is about using JWT for sessions with web clients.
If you’re registering a dedicated client id and secret for each web client, they you’re doing something wrong. If you’re doing this and then also using JWT, then you’re doing something really bizarre, and still wrong.
Id/secret pairs can make lots of sense for integrating partner services with your API. They make no sense for web clients, where you should be authing a user and not a client.
Nowhere was I hostile. I answered your comments politely and clearly. You were arrogant and condescending but you apparently don't actually know what you're talking about.
Please do go find your tribe of condescending devs with fragile egos.
I bruteforce a password for your JWT-enabled app. Then I have a token. Copy the token from my browser ( usually just open Network tab at the inspector and copy the headers for the request ). Then I store the token at my server and make it execute a request to the app on intervals to prevent from expiring ( reissue ) the token.
