I cannot count how many times CSV "format" has caused problems for me..
In my country the decimal separator is comma, instead of punctuation.
This causes problems when importing and exporting with this "format".
Just few weeks ago I had fun times working with API returning CSV in unknown encoding. Hopefully they will never make changes (you cannot always trust headers). Ah and i do love when CSV is missing headers and someone adds data into middle.
Of course some of these issues can be avoided by doing the things "right". Sadly you cannot trust this in real life. People write ugly structures in JSON, but at least you can validate results..
I have same way of estimating tutorials and similar content. There are quite many people posting videos without real understanding what they are teaching..
I am an engineer/developer and practically work solo in many projects.
Last year I started using the Docker at work. Before docker, all services were installed manually on physical/VM server machines.
Getting my head around Docker took some time, but I feel that it was time well spent.
I started with composes, but moved to docker swarm (single node) for having configs/secrets. Currently I manage everything with the Portainer, that allows me to control all the swarms and services with relatively easy way.
After the working stack is created and tested on the development server, installing it Into one or multiple production servers is quite easy. Depending of the case ugrading services is relatively safe as you can rollback to previous images if you or someone else messed up.
The nicest thing for me, is that all dependencies are inside the image. No need to worry about conflicting versions or setting up same thing multiple times. Sadly you still need to be aware of any security related issues that might exist within the image and maintain them. But this same issue does exist outside of Docker as well.
However, if you don't understand or think what you are doing, it is still possible to screw yourself in many ways. But I feel that this is always possible in our field, no matter what tools you are using.
While the Docker is not a silver bullet, it has made my life a bit less stressful. And I think it is important to understand what you're setting up and how you are doing it. Personally I would not want to go back to my old workflow.
Ps.
Sadly the swarm is deemed by many to be dead. It is relatively easy to manage by a single person and I am not getting the same feeling from alternative solutions, such as Kubernetes.
Everything is subjective.
The users who are voting now are not same people as the users who bought first models.
I have OnePlus3 as my main phone and I am still quite happily using it. However, as the manufacturer has changed their target audience, my next phone is not going to be oneplus.
Sad thing, it is pretty hard to find a decent phone which does not have crap pre-installed.
This happens to me a lot. I need to have access to keyboard for being able to type some older password. Same thing with pin codes.. Funny how brain works.
I noticed this yesterday and now I am wondering what to do.
Especially when more and more videos are getting flagged.
ID is out of the question, credit card seems more plausible. However, i wonder what happens when you give the number. I don't want that it sticks after validation...
The only possibility is to get out of Youtube (and other walled gardens) as soon as possible. Talk to your favorite content producers about Peertube, maybe setup an instance with some friends if you're sure you can handle that for the coming decade and not close down in 6 months time.
Both viewers and producers are heavily dissatisfied with Youtube. Time to move on.
If you allow adult videos without age verification you'll get shut down.
YouTube actually allowing adult videos is not something to diss. The fact that they need age verification is the price for it, the alternative is removing all those videos.
According to google ID cards are deleted after age has been proven, but for some reason they might keep credit card information.
>Important: If you enter your credit card info for age verification, Google will retain this data as necessary to meet legal and regulatory requirements.
Must be because of audit laws relating to processing credit cards.
Long time ago I remember reading about some service, that allows using single use credit cards. Last year I was looking for it, as many services cannot ne trusted with this information. But I could nothing like it. Maybe I was just dreaming...
Getting a legit card like that could be possible, but I don't think its worth of hassle and possible costs. Some companies practically throw these cards on you, but usually there is a catch.
My capital one card has virtual cards, and I’ve seen it other places. The only issue is that it’s done by a browser add on that has incredibly high permissions. I handle it by using a separate Firefox profile for the rare occasions I need to use them. I start Firefox with that profile, use it, then go back into my normal profile.
It's not about the limit, but about the tying of identity. If you enter a CC number, Google will then be able to know exactly who viewed the video. If you use youtube-dl, or even ad-blocking, who knows if that violates some T&C, and they could then shut down all accounts connected to you...
That's naive, they will eventually block those kind of virtual cards just like they block virtual phone numbers. The point is to tie the account to a real identity.
For years I have called my APIs "HTTP API" as they usually do not follow the abstract definition of the REST. And because I've seen so many APIs being called REST that barely follow any definition of a sane API.
The whole term is used by people as synonym for an API by management and by developers who never took closer look of the definition/paper.
I think that the situation is bit like in OOP, TDD and many other things that cause flame wars. When something good ideas come up, people tend to be religious about it. Instead of taking good ideas and utilize them for better solutions, we take things to extreme and fight about tiniest things.