Well, of course it's getting rate limited behind a subscription. Someone has to pay for all the additional compute and storage required to datamine your conversations.
> changing it [the license] is allowed as long as the name is changed. But what if that's exactly what I want to do?
I don't have a Mac environment, but I have researched a bit for devex purposes, and I would go with the Colima project as a open source solution for containers on mac. Have you tried it?
The link redirects back to the blog index if your browser is configured in Spanish, because it forces to change the language to spanish and the article is not available in spanish. Here's an archived link:…
And some webmasters were pretty keen on interfering with the context menu and your shortcut keys in order to prevent you to see it (and failing).
Yeah, no. If it's not part of my job, and neither is my own company, it's not my problem.
Do you guys really think these obvious marketing comments will work here?
Funny. Some days ago, on the Firefox mover to github topic, people were wondering if issue trackers should also be distributed. Seems an interesting idea.
That's right. I was digging through the comments on the substack version of the post and he confirmed it: https://dynomight.substack.com/p/noise/comment/17817515
You set up another alerting system to watch the alerting system. Duh!
I learned how to use Autodesk animator on DOS when I was 7 years old. Then again, I have been a geek all my life.
If blasting other nations is your thing, then sure, why not?
Do change the default name of the SSID, but avoid choosing a new one that sounds cool, fun, or original. Take a look at the rest of networks on your area and choose an SSID name as similar as possible to the rest.…
It's explained on the official documentation: https://docs.docker.com/reference/dockerfile/#scope
> Technical writers: documentation by example is good only for newbies skimming through. People familiar with your product need a reference and exhaustive lists, not explanation for different fields spread over 10…
> Can anyone conjecture on what might account for the apparent change? Many companies that do not have business in countries known for their abundance of bad actors will block their IP ranges right away. Nowadays…
Weeell... There's a feature list with the following pending entry: > MacOS and Windows support (using QEMU)
Yeah, but that means all major browsers agreeing on a standard, and we all know how that goes.
Libraries shouldn't be reading environment variables, that responsibility should be only for the application.
Yes and no. These notices started last year, but back then targeted lower API levels, which is why OP might not have seen them until now. But it's true that the first notice was sent months before the time limit, so he…
"This question is locked and replying has been disabled."
...and it's already outdated. Docker compose versioning was deprecated a long time ago.
Someone will then come up with "Maintaina-bot-bot", so that we don't have to bother clicking that button. Programmers are lazy creatures.
Also, the install instructions suggest installing the python implementation of docker-compose, which has been deprecated in favour of the compose docker plugin.
> Surely there were non-"appified" versions available? Ironically, those are probably more expensive. Privacy has become a commodity.
Well, of course it's getting rate limited behind a subscription. Someone has to pay for all the additional compute and storage required to datamine your conversations.
> changing it [the license] is allowed as long as the name is changed. But what if that's exactly what I want to do?
I don't have a Mac environment, but I have researched a bit for devex purposes, and I would go with the Colima project as a open source solution for containers on mac. Have you tried it?
The link redirects back to the blog index if your browser is configured in Spanish, because it forces to change the language to spanish and the article is not available in spanish. Here's an archived link:…
And some webmasters were pretty keen on interfering with the context menu and your shortcut keys in order to prevent you to see it (and failing).
Yeah, no. If it's not part of my job, and neither is my own company, it's not my problem.
Do you guys really think these obvious marketing comments will work here?
Funny. Some days ago, on the Firefox mover to github topic, people were wondering if issue trackers should also be distributed. Seems an interesting idea.
That's right. I was digging through the comments on the substack version of the post and he confirmed it: https://dynomight.substack.com/p/noise/comment/17817515
You set up another alerting system to watch the alerting system. Duh!
I learned how to use Autodesk animator on DOS when I was 7 years old. Then again, I have been a geek all my life.
If blasting other nations is your thing, then sure, why not?
Do change the default name of the SSID, but avoid choosing a new one that sounds cool, fun, or original. Take a look at the rest of networks on your area and choose an SSID name as similar as possible to the rest.…
It's explained on the official documentation: https://docs.docker.com/reference/dockerfile/#scope
> Technical writers: documentation by example is good only for newbies skimming through. People familiar with your product need a reference and exhaustive lists, not explanation for different fields spread over 10…
> Can anyone conjecture on what might account for the apparent change? Many companies that do not have business in countries known for their abundance of bad actors will block their IP ranges right away. Nowadays…
Weeell... There's a feature list with the following pending entry: > MacOS and Windows support (using QEMU)
Yeah, but that means all major browsers agreeing on a standard, and we all know how that goes.
Libraries shouldn't be reading environment variables, that responsibility should be only for the application.
Yes and no. These notices started last year, but back then targeted lower API levels, which is why OP might not have seen them until now. But it's true that the first notice was sent months before the time limit, so he…
"This question is locked and replying has been disabled."
...and it's already outdated. Docker compose versioning was deprecated a long time ago.
Someone will then come up with "Maintaina-bot-bot", so that we don't have to bother clicking that button. Programmers are lazy creatures.
Also, the install instructions suggest installing the python implementation of docker-compose, which has been deprecated in favour of the compose docker plugin.
> Surely there were non-"appified" versions available? Ironically, those are probably more expensive. Privacy has become a commodity.