But what happens if you don't use that stuff for a long time. You are in hospital when the bill needs to get paid. Your credit card gets stolen and the number needs to changed. Whatever personal crisis that you are not able to take care of life as usual for some weeks. They will just delete your data before you are back in business.
Does anyone know how long it takes, how many warning mails will come? I have very little data in AWS, but I more or less constantly feeling it might happen to me. Maybe not because of such big crisis, but just the simple fact that my bank will reject the automatic payment requiring a PSD2 second factor and I miss the email...
Well, the article did not say whether the unaudited access was possible in the opposite order after boot. First ask without reference and get it without audit log. Then ask without any limitation and get an audit log entry.
Did Copilot just keep a buffer/copy/context of what it had before in the sequence described. I guess that would go without log entry for any program. So what did MS change or fix? Producing extra audit log entries from user space?
Why would anybody open a bug report?
(Even/odd confusion of number of negations maybe:) )
I guess it became clear from other comments that disabling JavaScript causes the problem. An experimental fix exists for that.
My only contribution to node-grpc fixed missing quotes, but only because that produced real crashes.
In my current company nobody cares. It can be seen in the whole code quality. Full of smaller and bigger bugs as well as horrible hacks. It can be seen whether coders look twice or more at their own stuff before putting it to review or not, just trying to avoid ridicolous comments. It's a whole attitude. I write good code in a messy source base is unlikely to work in practice.
That said, I have submitted cleanup commits to open source projects only in the same MR with a real code change I wanted to make and only in vincinity of that change.
IMO a list of recent commits would be more useful as a landing page, or maybe even just the readme. When checking out a new project, I'm interested in what it does, not in its folder structure when its LICENSE.md was last modified.
That said, it's a bit like QWERTY. Maybe a bit weird, but it eases quick orientation on a new keyboard or repo if everyone uses the same layout.
Myself I shot slides from 1977 to 2001. Was not a big fan of Kodakchrome colors, preferred Fujichrome. And they were also cheaper, relevant for a student budget. After working with one of the first camera phones I have not bought any roll of film, even if in hindsight 100 KB VGA pictures were somewhat limiting... Now I mostly avoid taking photos because I won't have enough time in my life to keep them organized and watch them...
It was a nice programming exercise. Wouldn't be suprised if even back then something like that already existed and the whole effort just demonstrated a lack of insight of what is readily available.
Probably the code still exists on some backup I should not have. Have not looked back and don't know... The company who owned the rights has gone out of business.
Edit: After typing this it came to my mind a colleague of mine wrote yet another init in the same company. Mine had no dependencies except libc and not many features. The new one was built around libevent, probably a bit more advanced.