jb0x168
I think the difference here is that apps getting uploaded to the app store have static analysis run on them looking for unauthorized calls. Still doesn't rule it out, but adds an extra check to the process.
Unless you have some secret kung-fu that makes your on-prem infrastructure hack-proof.
The issue with the cloud is scale.
I've spent way too long reconfiguring yubikeys to act as an OTP device so that they work over RDP.
(edit: reconfiguration is needed to capture the device ID/secret and get them registered to our MFA provider as an OTP token, I realize they do OTP OOB :) )
New Page Rule -> your.site/*.png (or jpg, gif, etc)
Cache Level: Everything
Edge Cache TTL: (some large value, an hour maybe)
This will make sure you don't serve any given image more than once per hour, and the rest of the requests will get served CF's edge cache.Our inability to empathize, or "put ourselves in someone else's shoes" is at the root of so many of our problems...
Inherent in the negative concept of slavery is the removal or limitation of self-determination. If the components don't have free will, this isn't an imposition.
However, in the larger context, there are very much thinking, feeling entities that are negatively impacted by the use of this terminology.
In contrast, it costs next to nothing to update the terminology to use similar terms that don't cause psychological harm to a significant portion of the populace.
I feel the same way about "denylist" versus "blocklist". "Denylist" is more precise, but I think "blocklist" would make for an easier transition.
The educational versions of minecraft (e.g. the raspi version) integrate python scripting directly.
Microsoft forked a "bedrock" version of minecraft that I'm not as familiar with and that has a different plugin ecosystem. The Java-based version still has all the same plugin capabilities it always has.
Based on my experience:
- Use the "Jira Agile" (formerly greenhopper) add-on so that you have sprint/kanban boards and reports to visualize planned and in-flight work. Enable the "Backlog View" for your boards to separate planned from in-progress work.
- Keep required fields to an absolute minimum (we only require Summary) so that you can quickly capture cards and flesh them out later.
- Avoid complex workflows - use the Software Simplified workflow if possible. Don't complicate it further without a really strong business case.
- Learn the keyboard shortcuts. C (create), E (edit), I (assign to self) "[" (hide sidebar) and "." (command palette) are your friends
- Confluence and Slack both have great integrations to let you publish and interact with your Jira issues
Those are just a few random thoughts on how we've kept Jira working for us and not against us.