24 karma · joined June 5, 2014
This will become a huge problem / is already a problem. Whats the right way to solve this? some sort of https like trust relationship for the whole QR code interation?
1. Traceability of Encrypted Content
2. Harsh Content Take Down and Data Sharing Timelines
3. User Directed Take Downs of Non-Consensual Sexually Explicit Content and Morphed/Impersonated Content
4. Social Media User Verification
5. Automated Filtering
6. Digital Media Regulation
Except point 3. Read each sentence with "Do not do" and see if it makes sense for internet.
jacquard has been discontinued. We want to thank all our loyal fans. We understand you may not agree with this decision, but we hope you'll come to love these alternatives as much as you loved jacquard.
Turns out people care only if there is an end user impact and doesn't really care about random anomalies.
And to build the capabilities required for measuring the impact + automating the workflow of the actual chaos tests is a lot of work
What I can't understand is -
If your logs are in ELK and metrics in prometheus/grafana - why do you need SSH access? Sounds like thats a good problem to solve
[1] - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/user-dat...
I think what worked for us in this case was using Jenkins shared library[1]. We provide a common template for the common stacks and expose only few configurable options. This would really help in maintaining sanity across the jenkins env and since you maintain the shared lib, you can control the dependencies.
[1] - https://jenkins.io/doc/book/pipeline/shared-libraries/
I have always felt this. When I joined my new workplace, I spent quite a lot of out of office hours on learning more in my field. To be honest, it really paid off. Studying after uni really matters.