
#BlackTechTwitter | CEO of @Greenfire_io | Building @Greeneryfinance, worlds first cryptocurrency bookkeeping and accounting wallet | après cela, le déluge
New York, USA
Joined February 2013
- Tweets15K
- Following5.1K
- Followers1.2K
- Likes63.7K
coreydesir(.eth/.tez) retweeted
If you want to be ahead of your time, make sure your reading is centuries behind
coreydesir(.eth/.tez) retweeted
I’m in love with this sentence:
“The ones who made it look easy, did the hard part in private.”
coreydesir(.eth/.tez) retweeted
"If your wages only allow you to eat and sleep, it's not a job; in the past, that was called slavery."
- George Orwell
100% not true: Linux didnt catch on because companies with massive budgets didnt dedicate resources to porting their applications to the platform.
KDE and Gnome look and function roughly the same now as they did 20 years ago, what has changed is driver support and @WineHQ
A lot of people forgot that the main reason people were historically switching from Windows to Linux is because Linux is free. It was never about merit.
Now Linux desktop is better than Windows, but only because Windows got so much worse. This was never the case before.
Linux desktop was always built on layers of duct tape and prayers, and required a lot of niche knowledge to keep operational, and somehow people pretend that it's not.
27
coreydesir(.eth/.tez) retweeted
I’m no longer afraid of losing people. I’m afraid of giving the wrong people access to me again.
coreydesir(.eth/.tez) retweeted
“You will lose friends, you will lose lovers, You will lose comfort, but if in losing them, You find yourself, you have gained more than Kings.”
- Marcus Aurelius
coreydesir(.eth/.tez) retweeted
18 LINUX STORAGE AND FILESYSTEM CONCEPTS EVERY LINUX ENGINEER SHOULD MASTER
1. Linux Filesystem Hierarchy (FHS) → Understand the Linux directory structure, including `/`, `/etc`, `/var`, `/home`, `/usr`, `/tmp`, and `/boot`.
2. Disk Partitioning → Learn how to create, modify, and manage disk partitions using `fdisk`, `parted`, and `gdisk`.
3. Filesystem Types → Understand filesystem formats such as ext4, XFS, Btrfs, ZFS, FAT32, and NTFS.
4. Filesystem Creation → Use `mkfs`, `mkfs.ext4`, and `mkfs.xfs` to create filesystems on storage devices.
5. Mounting and Unmounting → Use `mount`, `umount`, and `/etc/fstab` to attach and configure filesystems.
6. Disk Usage Analysis → Use `df`, `du`, and `ncdu` to monitor disk space and identify storage consumption.
7. Logical Volume Management (LVM) → Master physical volumes, volume groups, and logical volumes using `pvcreate`, `vgcreate`, and `lvcreate`.
8. RAID Storage Management → Understand RAID 0, RAID 1, RAID 5, RAID 6, and RAID 10 for redundancy and performance.
9. Swap Space Management → Configure and monitor swap partitions and swap files using `swapon`, `swapoff`, and `free`.
10. File Permissions and Ownership → Manage filesystem access using `chmod`, `chown`, `chgrp`, and Linux permission bits.
11. Inodes and Hard Links → Understand inodes, hard links, symbolic links, and how Linux tracks filesystem objects using `ln` and `stat`.
12. Filesystem Integrity and Repair → Diagnose and repair filesystem problems using `fsck`, `e2fsck`, and filesystem-specific utilities.
13. Disk Quotas → Configure user and group storage limits to prevent excessive disk consumption.
14. Block Devices and Device Management → Understand `/dev`, block devices, device identifiers, and tools such as `lsblk`, `blkid`, and `udevadm`.
15. Filesystem Caching and Buffering → Understand page cache, buffer cache, writeback, and how Linux optimizes disk I/O.
16. Disk I/O Performance Monitoring → Use `iostat`, `iotop`, `iotune`, and `fio` to investigate storage performance and bottlenecks.
17. Network and Distributed Filesystems → Understand NFS, SMB/CIFS, SSHFS, and how remote storage is mounted and accessed.
18. Storage Backup, Snapshots and Recovery → Master `rsync`, `dd`, filesystem snapshots, Btrfs subvolumes, and recovery strategies to protect critical data.
Pro Tip: Master storage management by understanding how Linux organizes, allocates, mounts, monitors, protects, and recovers data. Always back up important data before performing destructive disk operations.
Grab Linux Systems Engineering Handbook:
codewithdhanian.gumroad.com/…
coreydesir(.eth/.tez) retweeted
I’m in love with this sentence:
“The best math you can learn is how to calculate the future cost of current decisions.”
coreydesir(.eth/.tez) retweeted
FFMPEG had one of the most valid crash outs in infosec history IMO. There's a huge elephant in the room when it comes to the fact that cybersecurity is extremely unbalanced. You have like 1,000 people pointing at problems for every 1 person fixing them.
Vulnerability research is extremely important, but it's become somewhat of a marketing stunt. First with fuzzers, and now with LLMs. It's a lot of "look what my new toy can do" rather than earnest attempts at actually fixing security problem.
What Google did to open source developers was especially egregious. They're a $3.6 trillion dollar company, who spent billions upon billions of dollars building a bot that points at problems really really fast, then they just dumped them all on a bunch of unpaid open source project maintainers to fix.
Then because of Google's 90 day disclosure policy, the maintainers have 90 days to fix the issues. After 90 days, Google goes public with the issues, making their project look bad if the vulnerability is yet to be fixed, and also potentially harming users if it gets exploited.
The 90 day policy was intended to give developers a reasonable amount of time to fix issues, while also applying some pressure with the threat of disclosure. Otherwise, you do get a bunch of goober ass vendors that will just ignore all security issues reported to them, then act completely surprised when their software gets hacked.
But when you're a small team, non-profit, or a solo developer, and you have a trillion dollar company's AI just blasting you with infinite problems to fix (each coming with a 90 countdown & a threat), that becomes extremely untenable. They're essentially inadvertently blackmailing developers into becoming unpaid interns.
Then on top of that, Google profits unimaginable amounts of money from the use of open source code. They use FFMPEG's code extensively across several highly-profitable products, meanwhile FFMPEG's developers work for free. There's no reason Google couldn't have donated money, engineers, AI tokens, or something towards fixing the problems. They can more than afford it.
I don't think Google has any malicious intent at all, it's just that the whole incentive structure behind vulnerability research is completely whack. All the glory goes to people who find issues, not those who fix them, so there's not a whole lot of interest in helping with fixes. Some vulnerability researchers will submit fixes with their reports, but most don't.
Honestly, in 2026 cybersecurity basically just feels like the equivalent of 50,000 people following the housecleaner around yelling "you missed a spot". Abysmally little effort has gone into anything outside of pointing out vulnerabilities.
coreydesir(.eth/.tez) retweeted
WATCH - Did Mansa Musa's wealth accidentally set off European colonialism?
coreydesir(.eth/.tez) retweeted
- 1 hr of linux
- 1 hr of networking
- 1 hr of database
do this straight for 6 months and you'll be better than 90% of the infrastructure engineers
coreydesir(.eth/.tez) retweeted
This is the best breakdown I’ve seen of how America 🇺🇸 has been destabilizing the Caribbean then be mad when Caribbean people go to America
There was no such nationwide effort to secure Black Churches after Dylan Roof went into Emanuel African Methodist Episcopal Church in Charleston, South Carolina and murdered 9 people after praying with them.
White supremacist nonsense...
If you want them to give up their Uranium, enriched or otherwise, PAY THEM!!!
Anything else is theft and unserious demands
Any credible nuclear deal must include Iran’s binding commitment to:
1) Full recovery of all 9,000+ kg of enriched uranium (including 440 kg of HEU) by the U.S., IAEA, or an international team.
2) Destruction of the stocks or access limited strictly to civilian nuclear fuel rods.
3) Permanent ban on uranium enrichment and plutonium reprocessing.
4) Full, permanent dismantlement/export/destruction of enrichment and reprocessing infrastructure, centrifuges, and manufacturing capabilities.
5) Complete, accurate declaration of the entire program, including past weaponization work, plus verified termination and IAEA verification of completeness.
6) Full restoration of IAEA access with “anywhere, anytime” inspections (including at military sites) and access to people, equipment, and documents.
NB: Any deal involving sanctions relief and removal of the blockade will undercut efforts to help the Iranian people overthrow their oppressors and contain Tehran's regional malign actions.
fdd.org/analysis/6-essential…
37
When it was the other set of people, there was a senate hearing and three university deans resigned...
You know what, nevermind...
Ole Miss student says she feels unsafe to be on campus with white people, fearing worst case scenarios
What's her worst case scenario, you ask?
"Calling me slurs to my Ring camera"
1
39





















