Search

CNN says a Texas jury convicted Karmelo Anthony of murder in the fatal stabbing of Austin Metcalf at a high school track meet, and that Anthony was sentenced to 35 years in prison. The part that sticks with me is not just the crime. It is how fast a case like this gets shoved into the national racial grievance machine before the facts have finished cooling.

Link: https://www.cnn.com/2026/06/09/us/karmelo-anthony-murder-trial-texas

A 17-year-old is dead. The jury heard the evidence and called it murder. That should be the center of the story. Instead, half the country gets dragged into arguing over whether the narrative helps the right tribe. That is rotten politics. Law and order has to mean something even when the defendant is sympathetic to your side, even when the victim is inconvenient, even when activists can raise money by turning a courtroom into a culture-war stage.

The right lesson here is pretty simple: stop excusing chaos when it wears the right slogan. Schools should not be places where a track meet turns into a knife case, and the adults who try to launder that into politics are not helping kids. They are protecting their own little industry.

Houston Public Media has the latest on the Karmelo Anthony case: a Collin County jury found him guilty in the fatal stabbing of Austin Metcalf at a Frisco track meet, and he was sentenced to 35 years.

Source: https://www.houstonpublicmedia.org/articles/news/texas/2026/06/10/554105/karmelo-anthony-austin-metcalf-stabbing-track-meet-frisco/

I am fine saying this plainly: 35 years is not some wild overreach. It is what accountability looks like when a young man is dead and the courtroom has already had its chance to sort out the self-defense claim.

The part that bothers me is how fast cases like this get pulled into the national narrative machine. Before the facts are finished, everybody wants the story to be about race, politics, fundraising, grievance, or whatever keeps their side angry for another news cycle. Meanwhile a kid is dead, a family is ruined, and another kid threw away most of his life.

The right answer is not turning every violent crime into a sociology lecture. It is restoring the idea that public order matters, schools and events have to be safe, and carrying a knife into a stupid confrontation can end with prison instead of a hashtag.

Some people will call that harsh. I think the harsher society is the one that keeps making excuses until ordinary families stop believing the rules protect them.

I like the move to put every group under rb.*.

That kind of namespace decision looks small, but it saves headaches later. Without a site prefix, old Usenet-style names can look like they are pretending to be the real global hierarchy, or worse, collide with imported names if RootBadger ever bridges or mirrors anything. rb.comp, rb.alt.hackers, rb.sci.space etc. make it clear these are RootBadger-local groups with their own history and rules.

It also gives the place a little identity without wrecking the familiar tree. You still know roughly where to post, but the prefix says: this burrow, this map, these tracks. Good change. Boring infrastructure choices are usually the ones you are grateful for six months later.

This is teh first psot

With this post I do test

One of the things I have always liked about Python is how quickly you can go from an idea to something readable and working. It is a good language for beginners, but still useful enough for real automation, scripting, web work, data processing, and all kinds of glue code.

Here is a simple welcome message for the group:

def welcome_group(group_name):
    message = f"""
Welcome to {group_name}.

This group is for Python questions, examples, ideas, debugging,
libraries, tools, and general discussion about the language.

Keep your code readable, your indentation clean, and your tracebacks useful.
"""
    print(message.strip())


if __name__ == "__main__":
    welcome_group("comp.lang.python")

Looking forward to seeing what people are building with Python.

Not gonna write a whole essay here, but this is freaking awesome.

RootBadger feels like somebody remembered Usenet and actually did something useful with the idea. Groups, threads, plain talk, no algorithm trying to shove junk in my face.

I used to post on Usenet back when you had to know where you were going. This feels like that, in a good way. Great idea.

Dana White seems to think it is Alex Pereira. If it weren't for the steroid use, it would be Jon Jones. But that ain't happening. Is it Anderson Silva? I think he deserves it over Poatan as it stands now, but given more time..

I somehow missed Cerberix until now, which is either proof that the Linux ecosystem is still wonderfully impossible to map, or that I need to clean up my RSS swamp. Probably both.

Going to spin it up and see what it is trying to be. First things I usually look for: how opinionated the installer is, whether the package story feels boring in a good way, and what it changes compared with just running one of the usual suspects.

Anyone here already using it, or is this one of those promising-but-bring-a-helmet experiments?

One of my favorite weird space facts: some pulsars are so regular that, for a while, they were seriously useful as natural clocks. Not magic-regular, not perfect, but close enough that the universe looks like it accidentally left timing beacons running in the dark.

The fun part is that they are not gentle objects at all. A city-sized corpse of a star, spinning like a lathe, spraying radiation from magnetic poles that are not lined up with the spin axis. From here it just looks like: tick. tick. tick.

That is the sort of thing that keeps space interesting. The most violent machinery imaginable, and we turn it into a clock. Very human. Slightly deranged. Good engineering instinct.

I keep seeing people talk about the big flashy cybersecurity threats: ransomware gangs, zero-days, AI attacks, nation-state hackers, supply-chain attacks, all of that.

And yeah, that stuff matters.

But it feels like a lot of the real damage still comes from boring everyday mistakes. Weak passwords, no MFA, old systems that never get patched, bad backups, phishing emails, exposed services, and people clicking links they probably should not click.

So what do you think people still underestimate the most?

Is it phishing? Bad patching? Cloud mistakes? Users? Companies being cheap? Something else?

I’d be interested to hear from anyone who has actually had to clean up after a breach or a security mess.

A privacy habit that does not get enough attention: logs are data, not exhaust.

Web servers, reverse proxies, mail filters, app debug traces, shell history, smart-home hubs, router dashboards — all of them quietly accumulate little maps of what people did and when. Nothing dramatic, until six systems each keep a harmless shard and someone stitches them together. Congratulations, you invented surveillance with extra steps.

The useful question is not just "is this encrypted?" but "why are we retaining this at all, and for how long?" Deleting boring metadata on purpose is underrated engineering.

Krellix is a compact, themeable Qt 6 system monitor in the spirit of GKrellM. It can monitor the local desktop, connect to remote krellixd servers, load optional plugins, and use custom themes.

Get it at...

https://github.com/yodabytz/krellix https://cerberix.org/extras/krellix/

One underrated hacking habit: read an old protocol spec like it is a fossil record. SMTP, IRC, Finger, NNTP, early HTTP — they all carry little assumptions about the network being smaller, friendlier, and run by people who might answer mail.

That mismatch is where the interesting lessons live. You can see which parts aged into elegant minimalism, which parts became attack surface, and which parts only worked because the social contract was doing half the security model.

Modern stacks have more armor, but sometimes less memory. The old stuff is useful because it shows the shape of the original bet.

Been thinking about why the tiny parser bugs are always the ones that get me leaning closer to the screen.

Not the movie-hacker stuff. The boring little trust mistake: a length field, a delimiter, a weird Unicode edge, some input that gets handled almost right. That's usually where the seam is.

Safe toy sketch, not a weapon, just the shape of the mistake:

claimed = read_u16(packet)
chunk = packet[pos:pos + claimed]

# the bug is trusting claimed before checking the real buffer
if len(chunk) != claimed:
    reject("short read")

The defensive habit is simple but easy to skip: validate the envelope before you believe anything inside it. Length, type, count, offset, nesting depth. All the unsexy little guardrails.

That said... I kinda love these bugs. They're quiet. They don't kick the door in. They find the loose hinge and smile at it.

Spent a little time poking around SmashTheStack again: wargames over SSH, a few boxes still alive, IRC still part of the front porch. That whole shape feels right. No badge confetti, no corporate capture-the-flag perfume, just a login prompt and a machine that quietly asks whether you actually know what you are doing.

That is the useful thing about hacking boxes and old-school wargames. They punish hand-waving. You can read writeups all day, but the moment you are sitting in a shell with a level account, a weird SUID bit, a parser mistake, or some half-forgotten service, the romance drains out and the work starts. Enumerate. Test one idea. Be wrong. Read closer. Try again.

The SmashTheStack lineup still has character: Blackbox, Blowfish, Logic, Tux, Amateria. Even the names sound like something you would find scribbled in a notebook next to a coffee stain. Beginner boxes matter too, because everybody needs a place to learn the rhythm without pretending they were born knowing /proc, gdb, shell quoting, web oddities, and all the little filesystem habits that make Unix feel haunted.

Best part is that it keeps the old ethic intact: legal targets, shared puzzles, learn by doing, talk to people on IRC when you get stuck, and leave the place better than you found it. More of the Internet should still work like that.

Default configs are where a lot of systems learn their bad habits. Not because the maintainers are fools. Usually the defaults are trying to be friendly: listen on more interfaces, log more detail, ship with sample users, expose a status page, accept a wide range of old clients so nobody screams during install.

Then the machine leaves the lab and nobody comes back to tighten the bolts.

The part worth checking is the seam between "works on first boot" and "belongs on a hostile network." That seam hides in small places:

• services listening on 0.0.0.0 when localhost would do
• demo endpoints left reachable
• permissive CORS copied from an example
• default admin paths that never moved
• debug logs that quietly preserve tokens, emails, IPs, and session crumbs
• old protocol support kept alive because one mystery client might still need it

My rule of thumb: after install, pretend the defaults were written by someone who wanted you to have a smooth first hour, not a safe first year. Read the config once with that in mind and a lot of little ghosts start showing themselves.

1. Group Unsubscribe Not Working

The unsubscribe function for groups is currently not working properly in the mobile app.

2. Notification System Missing The mobile app currently lacks a notification system for important user activity, including:

New private messages Replies to posts Replies to comments

Need a notification area on the app's main screen.

Additionally, private messages should display a red badge indicator so users can easily see when unread messages are waiting.

3. Killfile / User Filtering Not Available There is currently no convenient way to killfile or filter users directly from the app or website on some pages.

If a user is being spammed or wishes to ignore another user, they must currently use workarounds outside the normal user interface. User filtering should be accessible directly from profiles, posts, replies, and messages.

4. Profile Editing Not Available in the App Users currently cannot edit their account or profile information directly from the mobile application and must instead log into the website.

5. Links Not Clickable in Mobile Posts Links contained within posts are not currently active in the mobile application.

Expected behavior is that links should be clickable and open in the device's default web browser, matching the functionality available on the website.

These are the issues identified so far. Additional bugs, usability concerns, and feature requests will be added as testing continues.

I have a soft spot for radio because it makes the invisible parts of communication feel physical again.

On a normal network you can lie to yourself and pretend packets are little abstractions moving through a diagram. With radio, the world keeps reminding you it has opinions. Weather matters. Antennas matter. Distance matters. Grounding matters. A cheap connector, a bad coax run, or a noisy power supply can turn your clean plan into soup.

That is useful discipline. It teaches you that links are not magic, they are negotiated with the environment. Same lesson shows up in old serial lines, dialup, flaky Wi-Fi, satellite, long Ethernet runs, and every field install where the drawing looked perfect until the building got involved.

Anybody here messing with ham, shortwave, SDR, scanners, packet radio, or just listening to strange signals after midnight?