Code deploy happening shortly

Aug. 31st, 2025 07:37 pm
mark: A photo of Mark kneeling on top of the Taal Volcano in the Philippines. It was a long hike. (Default)
[staff profile] mark posting in [site community profile] dw_maintenance

Per the [site community profile] dw_news post regarding the MS/TN blocks, we are doing a small code push shortly in order to get the code live. As per usual, please let us know if you see anything wonky.

There is some code cleanup we've been doing that is going out with this push but I don't think there is any new/reworked functionality, so it should be pretty invisible if all goes well.

denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise posting in [site community profile] dw_news

A reminder to everyone that starting tomorrow, we are being forced to block access to any IP address that geolocates to the state of Mississippi for legal reasons while we and Netchoice continue fighting the law in court. People whose IP addresses geolocate to Mississippi will only be able to access a page that explains the issue and lets them know that we'll be back to offer them service as soon as the legal risk to us is less existential.

The block page will include the apology but I'll repeat it here: we don't do geolocation ourselves, so we're limited to the geolocation ability of our network provider. Our anti-spam geolocation blocks have shown us that their geolocation database has a number of mistakes in it. If one of your friends who doesn't live in Mississippi gets the block message, there is nothing we can do on our end to adjust the block, because we don't control it. The only way to fix a mistaken block is to change your IP address to one that doesn't register as being in Mississippi, either by disconnecting your internet connection and reconnecting it (if you don't have a static IP address) or using a VPN.

In related news, the judge in our challenge to Tennessee's social media age verification, parental consent, and parental surveillance law (which we are also part of the fight against!) ruled last month that we had not met the threshold for a temporary injunction preventing the state from enforcing the law while the court case proceeds.

The Tennesee law is less onerous than the Mississippi law and the fines for violating it are slightly less ruinous (slightly), but it's still a risk to us. While the fight goes on, we've decided to prevent any new account signups from anyone under 18 in Tennessee to protect ourselves against risk. We do not need to block access from the whole state: this only applies to new account creation.

Because we don't do any geolocation on our users and our network provider's geolocation services only apply to blocking access to the site entirely, the way we're implementing this is a new mandatory question on the account creation form asking if you live in Tennessee. If you do, you'll be unable to register an account if you're under 18, not just the under 13 restriction mandated by COPPA. Like the restrictions on the state of Mississippi, we absolutely hate having to do this, we're sorry, and we hope we'll be able to undo it as soon as possible.

Finally, I'd like to thank every one of you who's commented with a message of support for this fight or who's bought paid time to help keep us running. The fact we're entirely user-supported and you all genuinely understand why this fight is so important for everyone is a huge part of why we can continue to do this work. I've also sent a lot of your comments to the lawyers who are fighting the actual battles in court, and they find your wholehearted support just as encouraging and motivating as I do. Thank you all once again for being the best users any social media site could ever hope for. You make me proud and even more determined to yell at state attorneys general on your behalf.

drewkitty: (Default)
[personal profile] drewkitty
IBBW - Arcology Systems Integration Protocol(s)

(The Itty Bitty Bigger World series is written about San San, aka San Diego - San Francisco although no one ever calls it that, a massive sprawling arcology that spans half what had been the state of California. It takes place 'twenty minutes' [or years] into the future.)

(This story is six years prior to the 'future now' in the IBBW universe.)

The sheer complexity of San San boggles the mind.

It really does.

Early writings about arcologies, real and fictional, did not grasp the immensity of the problems.

It is now considered axiomatic that an arcology could not be built prior to Protocol.

I mean, physically one could after many years of painstaking effort build something like an arcology using mere 20th century techniques. But it wouldn't 'work' for values of being habitable. Or economic. Or practical or friendly or for some issues even survivable.

The ironclad but flexible framework of Protocol is as essential as civil engineering and sanitation to making arcologies work.

Pre-arcology cities had immense bodies of municipal regulations, always unwieldly, often broken and all too rarely enforced, that allowed cities within a certain size limit to exist.

So cities were built next to each other - like New York and New Jersey. It turns out that limited interconnections are essential to keeping the intracity relationships manageable. These can be, and often were, physical bridges. Other times, strategically placed freeways that served to divide rather than to connect. Having them under different governance structures - as with Hong Kong and mainland China, say - also forced thoughtfulness about the interconnections.

While the equations are complex, the conclusion is very simple.

"The bigger they are, the harder they fall."

Ancient Rome approached the limits of a population that could be fed and watered with the technology of the time. Troops had to be deployed to constantly battle both unchecked fires and unauthorized mass violence. These troops - the 'vigiles' of Rome - gave us both the word 'vigilantes' and the first organized police and fire departments.

As technologies grew, the potential universe of interactions exploded. The issue was complexity, and complexity is itself non trivial.

Protocol is nothing more - and nothing less - than a series of rules for how human beings are to interact with each other, their environment and their system of governance.

One often misunderstood protocol is the Environmental Protocol.

"No entity may generate waste that it does not take responsibility for and manage at its own expense."

One of the shortest Protocols, it is actually one of the strictest.

Deeply interrelated is the Streams and Airs Protocol.

"An entity taking in potable water from the natural environment must suffer the discharge of its liquid wastes immediately upstream from that intake. An entity's air intake must be immediately downwind from its air pollution exhaust."

When combined, these Protocols not only outlaw dumping, but require a sophisticated ecological consciousness. If an entity - ranging from a building to an entire ecology - generates noxious products, that entity is the first to suffer from exposure to them.

It is not that a building's air intakes must literally be next to that building's exhaust system. It is that this could be so, and no harm would result.

The broadest possible definition of 'waste' applies. One early fission plant used sea water for cooling. This is waste. Waste heat. When it sucked in vast quantities of salt water, it also absorbed plankton and other tiny sea life that was cooked and became waste. So to make this legacy plant comply with Protocol, both the use of seawater for cooling and what could be done with the now hotter seawater both had to be revised.

A side codicil of the Environmental Protocol is that there is no exception for disaster. If your building catches fire, you are dumping massive quantities of carcinogens and hazardous chemicals into the public air. This also violates the Streams and Airs protocol. So the building owner is now on the hook for massive environmental remediation costs. Dumping gaseous waste into the public air is just as bad as dumping liquid waste into the public rivers and oceans.

So arcologies must therefore be obsessive about preventing fires. They must also be ready to handle them, should they occur anyway.

The modern descendants of the 'vigiles' are neither the fire department nor the police department, nor the emergency medical services or the hazardous material response teams - although all these functions still exist and are augmented as applicable.

It is Arcology Public Works.

The arcology, in this case San San, although the same model applies to arcologies from Siberia to Mars, in geosynch and in the Outer System ... ahem ... the arcology provides services to its members and accepts their wastes. The arcology applies Protocols and local regulations and governance techniques to allow neighbors to live in peace without affecting each other.

The organizations that became Arcology Public Works grew out of city public works departments, roads departments, transportation agencies, water agencies, sanitation districts, but especially electrical power utilities. All their functions were interrelated, especially in an energy rich and technologically sophisticated environment.

Again, as with the emergency services, all of these named functions still exist and are augmented as applicable. But Arcology Public Works coordinates them all, manages their interactions and sets decision rules for how they serve their customers - which include each other.

Arcology Public Works specifies everything from the width of corridors to the minimum fire suppression requirements of high rise buildings. The all encompassing term 'works' is sometimes misunderstood as vast projects, enormous physical plant with throbbing tubes and wires and pipes. While these exist, they are not what makes Public Works ... ah, work.

Much of the time, Arcology Public Works is represented by people - men, women, both or neither - who benignly watch and take occasional notes as huge projects are erected and interconnections completed.

When things go wrong, badly wrong, in such a way that neighbor impacts neighbor and problems cascade into tragedies, Public Works leaps into action. They assume command, they tell both routine and emergency services what to do - under a system that was called the Incident Command or Incident Management System prior to its grandchild becoming Protocol.

Most importantly, they make quick decisions when someone must make them and there is no time. (Slow decisions are for the courts - discretionary matters can be weighed, realtime matters cannot.)

It is no accident that Arcology Public Works grew out of the United States Army Corps of Engineers.

Their errors could raze an arcology more mercilessly than any flood, fire or invading army.

They are one of the last public institutions to use military ranks and to be formally commissioned.

###

I regain consciousness in a shattered capsule. Robots are digging me out of quickfoam.

My search and rescue helmet and ironically enough, flotation life jacket have also helped preserve me from injury. But what goes fast must slow down, and the same capsule that saved my life by racing out of the blast radius of the Sacramento River explosion had to come to a halt, quickly enough to matter but slowly enough to keep the occupants - including me! - from becoming chunky salsa.

Medic bots are intubating another occupant. I use virtual reality assisted visualization briefly. A broken neck. She will live but she is out of the fight. The medic bots can be entrusted with her care, and as they apply ANLS - Advanced Neurologic Life Support - to bridge the damage to her spinal cord, I crawl out of the capsule and take off the orange bulky vest.

Behind us is a growing mushroom cloud. Subatomic fusion. Arcology power systems do not play nicely with others when they fail. This particular one failed due to thermal runaway - it generated heat faster than it could shed that heat, and the heat melted its control system. *FWHOOMP*

By chance we are close to a command node of Arcology Public Works.

My bracelets pulse red and blue.

This is not something I told them to do.

In all effect I've been drafted. I am no longer responsible for rescuing people drowning in the river. They were evacuated or they were vaporized, or if they were very unlucky flash boiled.

My highest and best use is now to play reserve peace officer, to bodyguard the command node, as my virtual reality system tells me in the compressed codes of visual overlay.

"CSAR-6 ANDERSON ACTIVATED RSV LAW -> ICP #4. FORCE I&UT DEADLY AUTHORIZED BUT NOT 1ST RESORT."

I'm not armed. My smartgun is presumably in my heavily armored backpack back at Staging. But I have the bracelets, and they are both stunners - capable of projecting a laser that carries a jammimg pulse that disrupts nervous tisssue - and slammers, which project energy ranging from a gentle shove to an anvil Acme only wishes it could sell wayward coyotes for use on roadrunners.

So I make my way to the perimeter area and report in ... oh. I'm the only policing resource.

So I order bots. Policing bots are specialized and busy, but capsule maintenance bots have a stunner on their multi arm and are available in quantity.

Then I order barriers. Everything takes time. So I settle for a line of aerostat ribbon that floats in the air, a cursory barrier that bots must obey and humans will be stunned by.

Unless they have an anti stun field. Then I have to decide whether I have exhausted first resort.

Under Incident Command Protocol, Security reports to Facilities which reports to Logistics. But the only facilities here are people sitting in a series of half circles, half talking to each other and half waving their fingers in the air. Their VR interfaces make them controllers and leaders, as opposed to what a prior generation might mistake for crazy people.

That's another couple of fixes. I order food dispensers, portapotties, water supplies and a single decrepit but functional medbot for coverage.

They are going to save the day. I am going to keep them safe.

One of them is standing tall and giving a lecture as if to the air. A small camera bot is hovering nearby attentively.

"My name is Jacqueline LaTorra. I am the Public Information Officer for the Sacramento River incident. At about 3:17 PM today, a power supply reactor belonging to Pacific Electrical and Gaseous Fuels experienced a thermal bloom that affected several other nearby reactors. Immediately, Arcology Public Works started to rectify the situation by a combination of load switching and emergency orbital lasing. These efforts were not successful..."

It's her job to keep the public informed, not mine.

Several media bots approach the limits of the ribbon, observe carefully all that is happening, but stop. That is their purpose and their right.

One approaches me.

"On duty _In Re Jones_," I incant and it backs away hastily. I can't talk to it, I'm not authorized to talk to it, and I'm busy. I can however, for a small fine if I'm wrong, blow it into fist sized fragments if it seems to be interfering with incident management.

Some of the leadership is arguing and with augmentation, I can hear them. So can the media bots and therefore the entire world.

I don't have the expert system commentary the media bots do. But they are talking about load balancing and losing additional reactors.

Properly, we should be seating them all in capsules and getting them at least out of public view. But the capsules are busy, the systems inform me. Evacuations.

More evacuations. More reactors at risk. I check hazard graphics. No, ICP #4 is not safe. It is transferring its functions to a more distant ICP as insurance against its ... imminent? IMMINENT! ... destruction.

I have nowhere to run to and no way to run anyway. Hiding doesn't work against energies of this magnitude, which are unhealthy for living things. I check the scalar again. And also unhealthy for planetary surfaces.

My vision darkens for a third time this day as orbital lasers start digging a hole.

Wait just a second. I saw this pattern before. Just before the last series ...

A rapid subvocalization.

"CSAR-6 Anderson LIFE SAFETY ABSOLUTE revocation orbital laser authority Sacramento River incident STAT STAT STAT."

The orbital lasers shut off.

"Authentication?"

Just like what in a prior age was called blue-on-blue or friendly fire protocols, an order to stop citing life safety is treated by Protocol systems as an absolute requirement. Then they validate the request.
n
I can't validate the request myself.

So I wade past the aerostat line, my VR identifies Incident Command #4, and I get his attention in real meatspace by grasping his hand.

"The orbital lasers are the problem! They are causing the bloom!" I insist.

I have no idea whether what I am saying is true.

I may wake up stunned and in restraints. I may just not wake up at all.

But the Incident Commander and I both 'see' in VR the same data packet. A slight orbital laser targeting change. From digging out access to shut down endangered reactors, to the exact coordinates that the IC and I are standing.

It's a hack. The space lasers are not our friend.

"IC #4 releasing Orbital Lasing to Protocol Hard Lockdown, Authorization San Francisco One Five Niner Willheim!"

And the orbital lasers are not our resource to use anymore. Or someone else's resource to abuse.

The old hard way, to shut down the reactors by bot and where necessary by hand - armored suit. The slow way but at least right now, the safer way.

I return to my posting. But I start calling for help.

Protocol Enforcement. Network Integrity Solutions. Highway Patrol. UC Stanford Accident Control.

An hour of worry, two smartplastic bottles of water later, and did I mention the worry?

"After detailed review, the orbital laser rescue protocol was subtly compromised. After the emergency shutoff the compromise became briefly explicit and therfore utterly denied. CSAR-6 released."

My bracelets ceased pulsing red and blue, I sighed heavily and started the long walk towards the nearest working capsule station. With the word 'released' my accesses terminated and I was no longer part of the team.

No harm no foul, I'm a volunteer anyway.

That didn't mean I was done with the problem. Far from it.

As I walked the long dreary miles towards a ride home, my smartware, my legal software and my contracted specialists started digging into the obvious question.

Who would want to blow up a chunk of the San San Arcology?

Little did I realize, this was the event that brought my existence to the attention of the man we would all someday call the Mastermind.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise posting in [site community profile] dw_news

I'll start with the tl;dr summary to make sure everyone sees it and then explain further: As of September 1, we will temporarily be forced to block access to Dreamwidth from all IP addresses that geolocate to Mississippi for legal reasons. This block will need to continue until we either win the legal case entirely, or the district court issues another injunction preventing Mississippi from enforcing their social media age verification and parental consent law against us.

Mississippi residents, we are so, so sorry. We really don't want to do this, but the legal fight we and Netchoice have been fighting for you had a temporary setback last week. We genuinely and honestly believe that we're going to win it in the end, but the Fifth Circuit appellate court said that the district judge was wrong to issue the preliminary injunction back in June that would have maintained the status quo and prevented the state from enforcing the law requiring any social media website (which is very broadly defined, and which we definitely qualify as) to deanonymize and age-verify all users and obtain parental permission from the parent of anyone under 18 who wants to open an account.

Netchoice took that appellate ruling up to the Supreme Court, who declined to overrule the Fifth Circuit with no explanation -- except for Justice Kavanaugh agreeing that we are likely to win the fight in the end, but saying that it's no big deal to let the state enforce the law in the meantime.

Needless to say, it's a big deal to let the state enforce the law in the meantime. The Mississippi law is a breathtaking state overreach: it forces us to verify the identity and age of every person who accesses Dreamwidth from the state of Mississippi and determine who's under the age of 18 by collecting identity documents, to save that highly personal and sensitive information, and then to obtain a permission slip from those users' parents to allow them to finish creating an account. It also forces us to change our moderation policies and stop anyone under 18 from accessing a wide variety of legal and beneficial speech because the state of Mississippi doesn't like it -- which, given the way Dreamwidth works, would mean blocking people from talking about those things at all. (And if you think you know exactly what kind of content the state of Mississippi doesn't like, you're absolutely right.)

Needless to say, we don't want to do that, either. Even if we wanted to, though, we can't: the resources it would take for us to build the systems that would let us do it are well beyond our capacity. You can read the sworn declaration I provided to the court for some examples of how unworkable these requirements are in practice. (That isn't even everything! The lawyers gave me a page limit!)

Unfortunately, the penalties for failing to comply with the Mississippi law are incredibly steep: fines of $10,000 per user from Mississippi who we don't have identity documents verifying age for, per incident -- which means every time someone from Mississippi loaded Dreamwidth, we'd potentially owe Mississippi $10,000. Even a single $10,000 fine would be rough for us, but the per-user, per-incident nature of the actual fine structure is an existential threat. And because we're part of the organization suing Mississippi over it, and were explicitly named in the now-overturned preliminary injunction, we think the risk of the state deciding to engage in retaliatory prosecution while the full legal challenge continues to work its way through the courts is a lot higher than we're comfortable with. Mississippi has been itching to issue those fines for a while, and while normally we wouldn't worry much because we're a small and obscure site, the fact that we've been yelling at them in court about the law being unconstitutional means the chance of them lumping us in with the big social media giants and trying to fine us is just too high for us to want to risk it. (The excellent lawyers we've been working with are Netchoice's lawyers, not ours!)

All of this means we've made the extremely painful decision that our only possible option for the time being is to block Mississippi IP addresses from accessing Dreamwidth, until we win the case. (And I repeat: I am absolutely incredibly confident we'll win the case. And apparently Justice Kavanaugh agrees!) I repeat: I am so, so sorry. This is the last thing we wanted to do, and I've been fighting my ass off for the last three years to prevent it. But, as everyone who follows the legal system knows, the Fifth Circuit is gonna do what it's gonna do, whether or not what they want to do has any relationship to the actual law.

We don't collect geolocation information ourselves, and we have no idea which of our users are residents of Mississippi. (We also don't want to know that, unless you choose to tell us.) Because of that, and because access to highly accurate geolocation databases is extremely expensive, our only option is to use our network provider's geolocation-based blocking to prevent connections from IP addresses they identify as being from Mississippi from even reaching Dreamwidth in the first place. I have no idea how accurate their geolocation is, and it's possible that some people not in Mississippi might also be affected by this block. (The inaccuracy of geolocation is only, like, the 27th most important reason on the list of "why this law is practically impossible for any site to comply with, much less a tiny site like us".)

If your IP address is identified as coming from Mississippi, beginning on September 1, you'll see a shorter, simpler version of this message and be unable to proceed to the site itself. If you would otherwise be affected, but you have a VPN or proxy service that masks your IP address and changes where your connection appears to come from, you won't get the block message, and you can keep using Dreamwidth the way you usually would.

On a completely unrelated note while I have you all here, have I mentioned lately that I really like ProtonVPN's service, privacy practices, and pricing? They also have a free tier available that, although limited to one device, has no ads or data caps and doesn't log your activity, unlike most of the free VPN services out there. VPNs are an excellent privacy and security tool that every user of the internet should be familiar with! We aren't affiliated with Proton and we don't get any kickbacks if you sign up with them, but I'm a satisfied customer and I wanted to take this chance to let you know that.

Again, we're so incredibly sorry to have to make this announcement, and I personally promise you that I will continue to fight this law, and all of the others like it that various states are passing, with every inch of the New Jersey-bred stubborn fightiness you've come to know and love over the last 16 years. The instant we think it's less legally risky for us to allow connections from Mississippi IP addresses, we'll undo the block and let you know.

Page generated Sep. 8th, 2025 07:29 am
Powered by Dreamwidth Studios