2,041 karma · joined April 2, 2011
https://patents.google.com/patent/US8131597 https://patents.google.com/patent/US6199048
Context: https://www.paperspecs.com/caught-our-eye/beware-the-qr-code...
https://en.wikipedia.org/wiki/West_Fertilizer_Company_explos...
and the possibility of a shipment of fertilizer somehow getting caught in a fire ...
https://status.digitalocean.com/incidents/6wtmldty17g1
As big as this is, any chance a major hub/backbone went down?
Instead, there wasn't anything there that people already knew about/wanted. Consequently, there was no reason for people to want the platform. (i.e. Why do I want to pay for this new thing?!?)
Personally, I found Quibi's advertising so annoying and pointless that I would likely never be interested in looking past it to see what the platform was all about.
On the other hand, if they had started pushing shows/creators as an anchor for the platform (with something like an "only on Quibi ..." branding say) it might have been more interesting. I.e. make the platform secondary to the content, convince people they want the content, and that gives them a reason to look at the platform in the first place.
Basically, the consumers don't care about the platform itself so much as they care about what it provides them.
* We have a couple of all-sites channels that a restricted on who can post (in practice or effect for the smaller ones) that are subdivided by function.
* Use threads and switch to threaded conversations fast rather than in channel discussions.
* Keep team "business" and "social" channels separate even if they are effectively the same groups of people.
* If have a support channel, make sure to put what the resolution of the issue/conversation was in a summary comment at the end.
* If you're remote, jump to video/voice conferencing before you get to a 200+ comment thread ...
That's a few for starters.
(formatting)
https://gist.github.com/arlaneenalra/a3ea9cf2d3a57397bda14a7...
https://www.logitech.com/en-us/product/trackman-marble-busin...
I use one all the time with a utility that maps one of the little buttons to turn on mouse wheel emulation.
https://github.com/huggingface/pytorch-pretrained-BigGAN/blo...
When you look further down you find:
https://github.com/huggingface/pytorch-pretrained-BigGAN/blo...
And that's just a quick search for s3 in the repo. It would not surprise me in the least to discover a `from_pretrained` that points at one of the s3 resources being pulled. There's probably other stuff like that as well in the code that could be causing equally nasty heartache .. especially if non-persistent containers are involved....
(This is a WAG aka Wild A Guess)
EDIT: Dug a little more and found:
https://github.com/search?q=org%3Ahuggingface+s3&type=Code
Unless I'm mistaken here, there's a crap ton of code that could be downloading models at runtime ... Which seems significantly less than ideal ...
https://theconversation.com/how-we-discovered-three-poisonou...
It's very useful to have enough exposure to things to be able to tell generally what's going on and to know what you need to look up.
So yeah, PHP is still a thing.