lzo and zstd are both advertised as fast loseless compression algorithm, and are implemented in btrfs filesystem. This benchmark tries to figure out which one is ideal for personal linux desktop usage, by simulating some common files that I might store.

The code is modified from https://gist.github.com/atoponce/353f4b4520d95ad71d3896b8aa21e166

test files are stored on tmpfs (in memory), to avoid hard drive bottleneck

CPU: 13th Gen Intel i9-13900H (20) @ 5.200GHz

Content :

1. Create a Telegram Bot and get a Bot Token
2. Get Chat ID for a Private Chat
3. Get Chat ID for a Channel
4. Get Chat ID for a Group Chat
5. Get Chat ID for a Topic in a Group Chat

As a security professional, it is important to conduct a thorough reconnaissance. With the increasing use of APIs nowadays, it has become paramount to keep access tokens and other API-related secrets secure in order to prevent leaks. However, despite technological advances, human error remains a factor, and many developers still unknowingly hardcode their API secrets into source code and commit them to public repositories. GitHub, being a widely popular platform for public code repositories, may inadvertently host such leaked secrets. To help identify these vulnerabilities, I have created a comprehensive search list using powerful search syntax that enables the search of thousands of leaked keys and secrets in a single search.

(path:*.{File_extension1} OR path:*.{File_extension-N}) AND ({Keyname1} OR {Keyname-N}) AND (({Signature/pattern1} OR {Signature/pattern-N}) AND ({PlatformTag1} OR {PlatformTag-N}))

**1.

References:

• obsproject/obs-studio#12650
• https://obsproject.com/forum/threads/obs-version-32-0-0-removed-disable-shutdown-check.190590/

For Windows users looking to workaround this change, here's my setup consisting of two Task Scheduler tasks.

This is a collection of coding patterns I have learned to solve not only some of the most common problems, but the 14 patterns (yes, there are way more than 14, but the point here is taking 6 months of preparation and condensing it into a 30 minute read that would not take more than 1-2 weeks to master. I have found these problems and patterns to be the most useful in that the data structures and algorithms are used in many other problems and become familiar over time. Good luck!

Please feel free to comment if you got some value or find any errors!

Thanks!

• 1. Sliding Window

Applied rationality for a coding agent. Defensive epistemology: minimize false beliefs, catch errors early, avoid compounding mistakes.

This is correct for code, where:

• Reality has hard edges (the compiler doesn't care about your intent)
• Mistakes compound (a wrong assumption propagates through everything built on it)
• The cost of being wrong exceeds the cost of being slow