•
I am pretty sure I bought from a seller using this (or something similar) on eBay. It sent me down a rabbit hole of reading about this type of scam that exploded earlier this year: https://www.uspsoig.gov/sites/default/files/reports/2026-04/25-072-3-r26.pdf Here's how it went down: https://www.ebay.com/fdbk/feedback_profile/theperfectpart Note that they’ve sold so much that even 1k neutral ratings are barely registering - they have “100% positive feedback” I bought a cheap tool from this seller on ebay. Tracking number was provided showing my town as the destination. About four days later, I get an unprompted ebay message from the seller: “I monitor all my shipments and sometimes there are problems so I’m proactively sending you a new one, here’s a new tracking number.” The original tracking number showed a message I’d never seen before “Item seized - counterfeit postage”. The new tracking number showed postage that had been bought back in January, but never entered the mailstream. Huh. I suspect that buys them time while they re-ship. I did eventually get the item after another tracking number was provided. My suspicion is that the seller uses counterfit USPS postage on 'x' number of packages to juice their margins. If you look at the neutral reviews, you can see a pattern — slow postage, lost package, had to replace, blah blah. Look at the positives — rave reviews at how fast things are arriving. Probably because the seller is “paying” for higher end postage via scamming the USPS. And only when they get caught by USPS do they need to re-ship an item. They must get away with it enough to make it worthwhile
••••••••
This article has some inconsistencies with what I experienced. For example, my label absolutely had tracking before being intercepted. In fact, it made it all the way to my city's distribution center. https://www.freightwaves.com/news/nullship-selling-counterfeit-postal-labels-freightwaves-investigation-finds#:~:text=%E2%80%9CCounterfeit%20shipping%20labels,not%20paid%20for.%E2%80%9D Here's the trajectory. Note that the final status has updated to no longer say "counterfeit" it's now just "postage assessment". ----- Delayed for postage assessment, Item in transit to destination August 13, 2026 5:44 AM Departed USPS Facility JERSEY CITY NJ DISTRIBUTION CENTER August 11, 2026 2:08 PM Delayed for postage assessment, held awaiting payment August 10, 2026 9:21 PM Arrived at USPS Facility JERSEY CITY NJ DISTRIBUTION CENTER August 10, 2026 4:53 PM In Transit to Next Facility August 10, 2026 6:24 AM In Transit to Next Facility August 9, 2026 7:13 PM Departed USPS Facility MYTOWN DISTRIBUTION CENTER August 9, 2026 8:18 AM Arrived at USPS Facility MYTOWN DISTRIBUTION CENTER August 9, 2026 1:28 AM Departed USPS Facility MYTOWN DISTRIBUTION CENTER August 8, 2026 10:30 AM Delayed for postage assessment, held awaiting payment August 7, 2026 6:29 PM In Transit to Next Facility August 7, 2026 9:14 AM Arrived at USPS Facility MYTOWN DISTRIBUTION CENTER August 7, 2026 7:17 AM In Transit to Next Facility August 6, 2026 7:04 AM In Transit to Next Facility August 5, 2026 5:53 PM Departed USPS Facility OPA LOCKA FL DISTRIBUTION CENTER August 5, 2026 4:46 AM Arrived at USPS Facility OPA LOCKA FL DISTRIBUTION CENTER August 4, 2026 2:33 PM
•••••••••••••••••••••••••••••••••••••••••••••••••••••••
If agentic coding isn't dramatically changing your productivity you're getting left behind. There's a clear difference between vibe coding and AI assisted software / systems engineering from how I think about things. With AI you can be massively more productive. I do a lot of things beyond code and this is what I've built in 2026 (quick snip from scc, it has proper excludes for node_modules and other pulled in deps that I didn't build) from ~code/ on my dev box: ─────────────────────────────────────────────────────────────────────────────── Language Files Lines Blanks Comments Code Complexity ─────────────────────────────────────────────────────────────────────────────── TypeScript 10,705 2,445,724 191,695 71,737 2,182,292 167,330 JSON 1,435 604,218 58 0 604,160 0 Rust 1,260 718,912 56,372 57,773 604,767 65,562 Markdown 1,087 162,160 36,375 0 125,785 0 SQL 1,046 129,795 6,142 7,389 116,264 1,344 Python 705 168,359 22,710 23,235 122,414 17,962 JavaScript 657 209,397 8,824 7,587 192,986 45,383 ─────────────────────────────────────────────────────────────────────────────── Total 19,009 4,903,248 353,289 186,252 4,363,707 326,094 ─────────────────────────────────────────────────────────────────────────────── Estimated Cost to Develop (organic) $179,262,721 Estimated Schedule Effort (organic) 98.79 months Estimated People Required (organic) 161.19 ─────────────────────────────────────────────────────────────────────────────── Processed 206,138,543 bytes, 206.139 megabytes (SI) ───────────────────────────────────────────────────────────────────────────────
•••••••••••••••••••••••••••••••
A healthy measure of my personal skepticism comes from the fact that GenAI represents the convergence of so many historically negative (and frankly idiotic) influences. - AI hype-mongers. We've dealt with these for decades in academia and industry, through countless boom/bust cycles. Yes, there's progress, but reality is boring and selective. - Tech Bros. NFTs? The MeTaVeRsE? The CEOs of OpenAI, Anthropic, Meta, and SpaceX have proven repeatedly to be dishonest grifters chasing all and only money. They're like the tobacco industry of laughably dishonest at this point (and consistently wrong). - Singularity grifters. The Kurzweil cultists flooding the ranks of lesswrong feel suddenly emboldened. They've been issuing batshit proclamations and navel gazing about AI alignment to anyone who will pay attention to them (and write them a check) for decades. It's no more connected to reality now than it was then. - The LinkedIn hivemind. If you aren't transforming your organization to meet the new GenAI future, your company is BEHIND and you are FAILING AS A LEADER. Be the one firing white collar workers, not the one being fired. Make sure you look good on paper with bullshit performative AI initiatives or your ass is dust. Oh, no ROI? No problem. Read my book on NAVIGATING THE ENTERPRISE AI TRANSFORMATION. It's skin-deep and filled with empty platitudes and clip art, but it will make you look like a big brave tech leader, just like Steve Jobs or Dario. - Investors. Yes, we're in a bubble. Yes, we've been in a bubble before. Yes, it's going to pop. Yes, that's going to be bad. Really bad, probably. Remember the financial crisis? Investors don't. And this time, there won't be a deep-pocketed government to bail anyone out, because debt is already sky-high and we're still recovering from COVID. So while I get there's something there, and I'm keeping abreast of it and extracting the best and leaving the worst, it is an exhaustingly negative experience.
••••••••••••••••••••••••••
The problem is that every facet they add to the analysis increases the complexity, making it harder to price risk - meaning they'll eagerly overprice [0] (based on "what if") with some idea that "the market" (ie nobody) will sort it out. This creates a race to the bottom against anything that might seem "weird", aka regular people just living their lives (while being put under a microscope), similar to how the ever growing housing bubble has painted most houses beige. Your bushes only seem like a reasonable example because you are looking at them in isolation - it was only a single issue you had to deal with, and something you seemingly wanted to deal with anyway. If they had instead blasted you with a litany of different issues, or a bush that you wanted to keep for sentimental reasons, or you simply didn't have the time/resources to create your own counter-documentation and operate their heavyweight bureaucracy, you'd be singing a much different tune. And while these things can happen anyway with regular in-person home inspections, the point is that increasing surveillance and unaccountable "AI" make it much easier to bury customers in a deluge of complexity making for even-less-competitive markets. (I would give a healthy list of examples of my own home being deficient in many ways an insurance inspector would call out yet are in the process of being managed, but I'm sure it would just invite a lot of "well ackshually that's dangerous and weird!" out of touch responses from people whose first instinct is to call someone rather than to fix something themselves) [0] Notice how they weren't going to raise your premiums by $30 a year or whatever, but outright cancel your policy - in other words a massive overweighting of the actual risk from some bushes growing into the house.
•••••••••••••••••••••••••••••••
The biggest early selling point of Tcl was Tk, as a relatively easy way to make good-enough GUI programs with open source on Unixen and the X Window System. Even much easier than the easier-to-use X toolkits like XView with C, and the alternatives only got more difficult from there. There were no Web frontends. Tcl itself was quite clever as what I'd actually call a string-based scripting language (contrast with Bourne/C-shell/etc. that preceded it on Unix). Originally, Tcl was among the handful of off-the-shelf extension languages . You write your big application in C or C++, and then you embed an interpreter for a higher-level extension language, for users or the original developer to add on functionality. The options at the time were usually a small Lisp/Scheme, Tcl, Python, or something entirely bespoke and probably quirky and half-butted. During early dotcoms, there was considerable interest in Tcl for backend work, and it also wouldn't have been the worst choice to put into the browser. Like Python, Tcl would've been more accessible and democratizing-the-Web than JavaScript, and there were already solid off-the-shelf designs and implementations. (Scheme would've appeared slightly more intimidating than Python or Tcl, and was more powerful, which I think was why Tim Berners-Lee preferred Python over Scheme as the people's programming language for various Web purpose. The semantics of the JavaScript we got was more a hurried toy Scheme, plus the simplest object model, and a more intimidating syntax that came from systems programming.)
••••••••••••••••••••••••••••••
I spent the weekend trying Deepseek 4 Pro on a Linux porting project and it led me down a complete rabbit hole where Linux wouldn't even boot by the end of the weekend. Waste of $120. Switched back to GPT 6 on Monday and Linux is booting again and I'm making progress. The only thing I've found Deepseek and Kimi good for are security tasks that GPT refuses to do. This is a summary of what Deepseek did and got wrong: Lost the proven baseline: changed kernel source, configuration, compiler, RAM geometry, MMC width, and peripherals together. Matching an upstream commit did not preserve local boot fixes, making failures difficult to isolate. Misidentified an image: a file labelled “r18-known-good” actually contained the r23 parent bootloader. Filename-based reasoning replaced verification of the artifact’s identity and provenance. Shipped inconsistent boot contracts: flash-16b’s loader read too few kernel blocks. Fresh2 changed the device tree without updating the loader’s expected length and CRC, creating deterministic rejection before normal Linux handoff. Patched binaries without maintaining reproducible source: loader constants diverged from source, a separately compiled cache-flush length remained stale, and assembly used an oversized stage-two slot. Their causal contribution to hangs was not established. Overstated diagnosis: claimed failures were definitively in U-Boot, blamed compiler or IPU changes without controlled isolation, converted noisy observations into confirmed hangs, and neglected persistent journals as an alternative explanation. Mistook compilation for integration: framebuffer registration was incomplete, timing success handling was inverted, BT.656 selection was unreachable, encoder overrides were missing, and audio lacked software clock configuration. Misread hardware evidence: asserted interrupt-free PMIC operation, assigned RF to the wrong SPI controller, confused regulator identifiers with register addresses, and described repeated encoder writes as unique registers. Overclaimed results: treated kernel/probe indications as userspace success, presented earlier discoveries as new progress, and omitted failed flashing attempts from the final narrative.
•••••••••••••••••••••••••••••••••••
F2P games can absolutely be made to exploit the same mechanics as real gambling, and are often designed to do so. But no matter what they do, they're just not as potent as real money gambling. The pull isn't the same when it's not done with real cash, they tend to be less ruthless and it seems that a smaller proportion of people is potentially susceptible to F2P addiction compared to real gambling. For the right people, they can be very wallet-draining but it doesn't seem many go into homelessness like with gambling. What's a "TV shopping network addiction"? I tried searching it, and I can only find isolated news articles from 5-15 years ago that report on it purely because of how unusual this is. Going to file this under 'people can get behaviorally addicted to anything', what a strange example. Do you even know anyone who has bought anything from a TV shopping network, let alone a 'significant number' that are left destitute? The reason why people disagree with you is because the hair-splitting between different types of addictions seems very pedantic. Clearly people think that gambling addiction is not even on the same scale of addiction than the other examples. If F2P games are cocaine, then gambling is heroin. There is a reason why gambling is taking over Western economies so rapidly, but not any of those other things - it's just too good at exploiting people's brains. So when gambling addiction is so potent that it goes off the chart compared to any of the dozens of other things that can be psychologically addictive, people aren't particularly interested in finding the exact point where it's too much for society to bear - they just know that gambling is far beyond that point.
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
 Top