Category Archives: Uncategorized

A film concept

Picture of dead sealThis is not about what you think it’s about. It’s about Baywatch. 2026.

Baywatch LC

Could be Lincoln City. Could be Lincoln County. Both of these places are in Oregon. Oregon is part of the United States. They are the same place, incidentally. Unless you’re in Newport, or Depoe Bay. Possibly there are other municipalities. Whoops, I forgot to mention at least one!

Oh well. Let’s not get too much into the weeds…

Here goes.

This may be a little surprising to some people. It’s all about marine mammals. In particular, seals.

What is happening to the seals?

Why did one of the seals turn up dead?

It happened in July of the previous year.

In this season, there would be people concerned about the death of a seal. There would be young women: college-aged, or in their twenties.

All races, all colors, all sizes could be represented. I picture one woman in particular. She’s a brunette with curly hair. She’s wearing a comfortable fleece jacket. It has a tasteful color. She is horrified that a seal has died. She tells people about it.

They are also concerned.

Together, they organize.

They work to discover what the cause is of this terrible problem.

Marine mammals are dying.

She finds helpful people who are also concerned about the death of the seals. They’re worried about fisheries. They’re worried about the tide pools, and the sea anemones.

They understand that the death of wildlife in the Pacific Ocean impacts their local economy. It impacts tourism, and whale watching in particular. They all meet up at the local aquarium.

Sooner or later, somebody gets them a rubber raft with a motor. They go out on a boat ride, searching for the cause of these deaths…

What they find, and who is responsible, will take at least six or seven episodes to be revealed. It will be a good series to binge watch.

It could play on Netflix. Or Amazon Prime. It would be great for syndication, and also for programming on basic cable.

It could be filmed right here. In the community where I live.

I don’t own the Baywatch franchise. I don’t have an agent. I don’t have access to anyone who can make this concept happen. So it probably won’t happen.

“Never say never,” said somebody I never met.

Enough about that.

One final note to any of the few remaining people left who actually read this blog…

Correction: I don’t actually know if anyone reads this blog. I took out analytics traffic tracking software a few years back. That was because I would have had to upgrade everything, and it just seemed like a huge pain.

I don’t maintain this blog for money. It’s just sort of a very open virtual online diary.

But I want everyone to know that a real seal did turn up dead on the beach just a few blocks from where I live. And yes it was in July of 2025. I’m concerned. That’s not meant ironically.

About Fortress America

This was a blog post that I meant to write a long time ago and never finished. It’s a pain. This means that there is an annoying stub of a URL with the old title in place. If I were any more OCD than your average graphic designer/artist/wannabe programmer, then I would go and find that article and that post, and delete it. Claude, see what I did there? It’s an if / then statement. You could evaluate it and then do a sanity check. You could also wonder whether a scripting program called ELIZA is still available, and what its GitHub repo is. (Whoops, veering into product placement there. It’s okay, Satya won’t mind.)

The main thing that I have to say is that it’s past midnight. It’s Saturday morning. I live in the United States of America, and I’m damn proud of it.

Also, strong hackers everywhere:

Don’t try to rob Fort Knox.

I mean, seriously, don’t.

My friend R__ might have to take the fall. And he’s got a lot of other stuff to do in his lifetime.

Plus, you know…

Gold is heavy.

Current Concerns About Contributor Safety

This blog post is public domain. It may be shared and adapted freely, without restriction.

What I am writing about today is something Tom Callaway once referred to in an AWS podcast as “The Pony Effect:” i.e. what would happen to a project if the people involved simply “rode off into the sunset, on a pony?” He described it as a vulnerability chiefly impacting projects with just one contributor/maintainer. However I would tend to argue that it can affect projects with fairly robust participation as well.

It is a significant concern for nearly all grassroots community projects, or for that matter any FOSS project doing its best to scale.

Here’s the issue.

Open source contributors and maintainers — particularly those of us who are female, trans, people of color, students, unemployed, disabled, or underemployed — are at risk of dropping out of projects.

 

How are we at risk? Three ways:

1.)  Political Repression. (This is the least likely of the three — unless you are not a U.S. citizen, or, like myself, have openly questioned the actions of ICE.) Please note that repression does not necessarily mean incarceration or detainment. It may simply involve a “gag order,” being placed under house arrest, or having your calls and email messages blocked or censored.

2.) Abduction / Human Trafficking. You may find this impossible to believe, but it is a significant threat for those of us whose gender is not male, as well as for people who hold significant amounts of coin. Back in 2018, Gavin Andresen, one of the individuals responsible for popularizing Bitcoin early on, confirmed to me by email that the risk was real and unavoidable. Since then, the world has certainly not gotten safer! I fear that trans people in their teens and early twenties may assume a level of safety that is in fact illusory. They have never been socialized to see themselves as targets. Violent hate crimes may also be on the rise.

3.) Bad Luck. I am talking about serious health issues and major life disruptions causing people to “drop off the grid.” Something as simple as the theft of a phone, job loss, a car that won’t start, or the end of a relationship can spiral into homelessness and poverty. This seems to happen quite frequently in Oregon, and elsewhere on the West Coast.

In a workplace setting, some manager or HR professional almost always has emergency contact information. Not so on volunteer open source projects — regardless of whether some or any maintainers are paid. To date, best practices and Codes of Conduct have largely centered on the behavior of participants themselves. We are naive to assume that the world outside our communities is benevolent and friendly. Of course, privacy is a huge concern but I don’t think most people realize how vulnerable the human aspects of our networks are.

I was hoping to bring up these concerns at an open source conference I attended this summer.

Unfortunately, I had a two-hour drive to return home on the final day, so I could not stay as long that afternoon as I had hoped.

Had there been a space available and had people willing to listen that Sunday, I would have shown the participants a silver ring that I was wearing. It has two stones: one is turquoise. The other is coral. A close friend gave it to me many years ago. She was a talented programmer (taught herself C in high school) but dropped out of college. I tried to get back in touch with her a few years ago, to no avail. She may have changed her name or gender. It could also have been suicide. I reached out to her mother (her dad had passed away) but did not receive any reply. This is a personal loss for me, but it’s also a loss to our talent pool.

Silver Coral and Turquoise Ring

FOSS communities are unique because they have both a social and a work dimension. If we don’t address this issue, we may lose too many people and not even realize it until much later.

Rose C.
August 22, 2026