I get questions from people who read my posts and sometimes I answer them in a post. This is one of those times.

...

Someone read my "war room" post and picked up on the part where I spent several weeks trying to get to the bottom of what turned out to be "kill -9 -1" nuking the world on a bunch of FB machines. They asked how I keep track of things during that time, what my working memory is, and is it paper, text files, IRC messages, or just remembering things.

The answer is: back when I used to do that kind of thing, I found it very useful to have a "MMDD" (hey, I'm in the US, so just pretend it's the back half of an 8601 number... you'll see why...) directory, and inside of it, I'd have some short names for whatever I was dealing with that day.

That means today would be 0629, and then something inside of it might be "fbar" or "rsw" or "webi" or something. It was just something to keep all of the crap together and yet away from other things I was doing that day, while also distinguishing it from other times I might've done a "fbar" or "webi" or whatever project, if that makes sense.

These would just live off my home directory, and yes, it would fill up with crap, but I'd batch them up when a year ended. I'd take 01xx through 12xx and move them into "2013" when 2014 began, for instance. So, as you can see, they *are* ISO-8601 dates, sorta, but it's ~/YYYY/MMDD/foobar once it's old, and it's merely ~/MMDD/foobar until then. This is a balancing act between speed and having my homedir fill up with tons of ancient crap.

Any time I needed scratch space for output from things, that's what I used. That might be the output from a bunch of sweeps over the fleet to look for anomalies. Let's say I ran a command that sshed into a few hundred thousand hosts to look for common items in the logs. The stdout/stderr from that would probably be there so I could hit it up multiple times without asking the job runner system for another copy. It's a lot faster that way.

But in terms of troubleshooting things and dealing with permutations, it's hard to beat paper, and I usually end up with some kind of "lab notebook" at any job I work. I can think of examples of those going back over 20 years. The only problem is that the stuff in them really properly belongs to the company so I don't tend to have them after the fact. A great many pages of context have gone in the shredders over time, and not because I didn't ask. I've asked if anyone wanted them, and the answer has always been no.

There were also the internal posts about things, and then running commentary on IRC channels, but those tend to be useful after the fact, or for getting help from other people. My own state-keeping tends to stay on something close at hand and (usually) physically tangible.

As for those <date>/<term> directories, some of them turned out to be rather handy after the fact. A lot of times, something would happen, and then time would pass, and it would break *again* in exactly the same way, and I could think "didn't we deal with these people already?", dig around, find something from six months earlier, and go "AHA!". Now armed with the date, I could pull up the right posts, IRC logs, group messages, graphs, or whatever else.

Considering how much random crap I dealt with in any given day during my time "in the barrel" (kids, ask your parents), that was the only way to make any sense of it later. Without stuff like that, by the end of the week, I'd have no idea what I had been doing on Monday or Tuesday. That's how bad the load got at points.

...

Someone else wrote in and asked if I could do something to improve the overflow calculator thing I hacked up last week. It wasn't particularly usable on mobile, and that's definitely true. I wrote it on a laptop and paid exactly zero attention to what it would look like on a weirdly small screen that's usually taller than it is wide.

It was a fair point, so I took a whack at making it suck slightly less. It's probably still terrible, but in the specific case of me holding my phone upright, it looks halfway usable now. You're no longer forced into "flyspeck-3" mode with the fonts, at least.

CSS is such a mess.

...

I occasionally hear that the site is unreachable from one spot or another. This almost certainly comes down to IP filtering on my part. Perhaps you've read about the influx of web weasels who are scraping the living shit out of everything remotely URL-shaped they can get their hands on. My stuff is certainly in that space, and they show up here regularly.

Besides that, there are also a number of networks which send nothing but straight-up abusive traffic. This is where you look at the logs and see stuff like them using every single IP address in a (v4) /24 to scan for random webshit vulnerabilities. It's like, nice job, fucko, but I don't run PHP here. Anyway, that's pretty solid evidence that a given network is not worth hearing from ever again, and so into the filter it goes.

A whole lot of this happens automatically just based on whatever traffic is sent this way first. Send bad traffic and meet the bit bucket. I don't even find about most of it since it's constant and utterly uninteresting.

Then there are the people who run feed readers which don't play nicely. As previously described, they will get a handful of chances to slow down with 429s, and then if the web server feels like those aren't having an effect, it'll just ignore the traffic for however long it feels like. Again, I'm also not in the loop on this sort of thing. It's all automatic.

Finally, there is a new rub. I taught myself how to ingest BGP data, and so can now trivially go from an IP address to the autonomous system number of whoever's advertising it, including overlapping advertisements (like a /24 out of a bigger /20). Then I wrote something that will dump out an entire AS, and it's not hard to imagine what I do with that.

Enough bad behavior from a host -> filter the host.

Enough bad hosts in a netblock -> filter the netblock.

Enough bad netblocks in an AS -> filter the AS. Think of it as an "AS death penalty", if you like.

As long as clueless network operators continue to let abusive customers bounce around thousands of dynamic IP addresses with not so much as a hint of SWIP data, those entire net blocks will find themselves unable to get to large swaths of the net. That's just how it is, and it's nothing new. Send crap, meet /dev/null.

Dealing with what the web has become is exhausting.

I've long had a list of "magic numbers" which show up in a bunch of places, and even made a post about it back in November of 2020. You ever wonder about certain permutations, like 497 days, or 19.6 years, or 5184 hours, and what they actually mean?

I've been doing that stuff by hand in a calculator and finally decided to just do it in Javascript and put it online for anyone to try.

So, here's my latest waste of CPU cycles:

My rollover calculator.

I still haven't figured out the Crucial SSD 5184 hour thing, so it's not in there. 5124 hours, sure, I can understand that one, but 5184? 60 more?

Anyway, have fun while the world burns.

rsync is one of those tools which is rather useful. It saves you from spending the time and effort on copying data which you already have. It's the backbone of many a mirror site, and it also gets used for any number of backup solutions.

There's just one problem: in the name of efficiency, it can miss certain changes. rsync normally looks at the size and modification time of a candidate file, and if they are the same at both ends, that's the end of any consideration. It won't get any further attention and it moves on to something else.

"So what", you might think. "All files change at least their mtime when someone writes to them. That's the whole point of a mtime."

And yet... I'm writing this post, and here we are.

The keen-eyed observers out there are probably already thinking "ooh, bit rot" and other things where one of the files has actually become corrupted while "at rest" for whatever reason. Those observers are right! That's totally a problem that you have to worry about, especially if you're using SSDs to hold your bits and those SSDs aren't always being powered.

But no, this is something you have to worry about *beyond* that. This is about a "sneak path" that you probably didn't consider. I didn't.

Here, let's run a little experiment. If you have a x86_64 Debian box that's relatively current and you've been backing up the whole thing via rsync for a year or two, go do something for me.

Go run your favorite file-hasher tool on /usr/lib/x86_64-linux-gnu/libfribidi.so.0.4.0 for me. Give it a sha256sum or whatever, or even md5sum if you're feeling brash. Then note the modification time on the file.

Now mount one of your backups and do the same thing on the version of the file that's on the backup device. See anything ... odd? Unusual?

Identical mtimes, identical sizes... and different hashes, right? I spotted this on a bunch of my machines after going "hmmm..." about the whole SSD-data-loss thing.

Clearly, something unusual happened somewhere, and it's been escaping the notice of your rsync runs ever since. I haven't gone digging into the package history for this thing to find out just when and where it happened, and (more importantly) how. It's rather unusual.

If you're freaking out right now, there is some hope. rsync has both -I and -c which promise to not use the quick method and instead will run a checksum on the files. It's slower so you won't want to do this normally, but it's not a bad idea to add this to the mix of things that you do every so many rotations.

I should point out that the first time you do a forced-checksum run, --dry-run will let you see the changes before it blows anything away, so you can make the call as to which version is the right one! In theory, your *source* files can get corrupted, and if you just copy one of those across, you have now corrupted your backup.

Isn't entropy FUN?

At the start of 2023, I wrote a post talking about why I still had an "old-school cert" on my https site. Well, things have shifted, and it's time to talk about why.

I've been aware of the ACME protocol for a while. I have tech notes going back as far as 2018, and every time I looked at it, I recoiled in horror. The whole thing amounts to "throw in every little bit of webshit tech that we can", and it makes for a real problem to try to implement this in a safe and thorough way.

Many of the existing clients are also scary code, and I was not about to run any of them on my machines. They haven't earned the right to run with privileges for my private keys and/or ability to frob the web server (as root!) with their careless ways.

That meant I was stuck: unwilling to bring myself to deal with the protocol while simultaneously unwilling to budge on allowing the cruft code of existing projects into my life.

Well, time passed, and I managed to crack some of my own barriers. It wasn't by using the other projects, though. I started ripping into them to figure out just how the spec really worked, and started biting off really really small pieces of the problem. It took a particular forcing function to get me off my butt and into motion.

About six months ago, I realized that it was probably time to get away from Gandi as a registrar and also SSL provider (reseller). They had been eaten by private equity some years before, and the rot has been setting in. Their "no bullshit" tagline is gone, and their prices have been creeping up. I happened to renew my domains for multiple years and have been insulated for a while, but it was going to be a problem in 2025.

Giving them the "yeet" was no big deal, but the damn rbtb certificate was going to be a problem. Was I going to start paying even more for the stupid thing every year, or was I going to finally suck it up and deal with ACME?

That still left the problem of overcoming my inherent disgust for the entire protocol and having to deal with all of these encodings they force upon you. My first steps towards the solution involved writing really small and stupid utility functions and libraries that would come in handy later. I'm talking about wrapping jansson (a C library that handles JSON) so that it made sense in my C++ world and I could import JSON (something I use as little as possible). That kind of thing.

This also meant going down some dead-ends, like noticing that libraries existed which would allegedly create certain things (like a JWK) for you, and then realizing that they were not going to make my life any easier. I'd poke at it, reach my limit, and then swear and walk away for another couple of days.

This went on for some time. I have a series of notes where I'd grab a piece of the problem, wrangle it around for a while, get grossed out, and then set it down and go do something else. This just kept happening but I slowly made progress with small pieces that would Do Stuff, and then they'd connect to each other, and so on like this.

One positive development during all of this was discovering this "pebble" test server I could run on an isolated fake system. It would act as an ACME server and would let me harass it with my feeble attempts at implementing a client instead of bothering the real CAs. Even "staging" servers deserve better treatment than active development, after all.

And, well, after a whole lot of mangling and dead-ends and rewrites and other terrible crap, I had an awful little tool that would take a CSR, do all of the idiot dances and would plop out a certificate. I pointed it at Let's Encrypt staging, and it worked. Then I pointed it at their prod site, and _that_ worked. So I did it for the real thing ([www.]rachelbythebay.com), and *that* worked, and I dropped it into place.

Thus, for the past couple of weeks, if you've been hitting the https version of my site, you've been doing it across the new setup.

Now, I took notes about this, and I wanted to share some of my original off-the-cuff thoughts about implementing this for anyone who's similarly broken in the head and wants to see how bad it can be. I will note that I wrote this based on the first thing that worked, and it does not necessarily reflect the implementation I'm on a few weeks later.

...

Make an RSA key for your web site. Then make a CSR for it, setting the CN and adding a matching altname as an extension. No other fields matter. Nobody looks at those, anyway, and none of them will influence your final certificate no matter how prosaic or precise you get in there.

Make an RSA key of 4096 bits. Call it your personal key.

Write something that'll read a CSR. It needs to extract the CN and the SANs - the DNS: ones, at least. Ensure there's actually a CN [*] and actually SANs, and that the CN occurs within the SANs. So, yes, you have to have at least one SAN.

[* - I now know you can run with just SANs. I did not at the time.]

Write something that'll do a HTTP GET to <directory URL> which is given to you by the ACME service operator. It then needs to parse the body as JSON (or die) and extract some strings from the top-level object: "newNonce", "newAccount" and "newOrder" at the very least.

Write something that'll read an RSA key file on disk. It needs to extract the publicExponent (probably 65537, but you never know...) and the modulus. Make it read your personal key from earlier.

If you end up using "openssl rsa -in foo -noout -text" to do this, the modulus is a bunch of printed hex digits, like "00:ff:11:ab:cd:ef:22:33". It hard-wraps the output and also indents the lines, so you get to clean all of that up first.

Skip the first 00 for some inexplicable reason. Take the other bytes of the modulus and turn them into the actual character values, so a literal 0xff, 0x11, 0xab, 0xcd and so on down the line in the same order you find them in the file. Hang on to these values for later.

Write something that'll turn an ordinary integer into its equivalent big-endian bag of bytes, but don't pad it out to any particular alignment. You need to take that "65537" from your publicExponent and turn it into the equivalent bytes, so 0x01, 0x00, 0x01. Yes, it's a number you just turned back into a binary representation.

Write something that will do base64 *style* encoding, but not quite. The last two characters in the encoding set are usually + and /, but that won't do for webshit, so you need to make it use - and _ instead.

Take that publicExponent (65537), pump it through your big-endian bag-of-bytes encoder to get 0x01 0x00 0x01, then put it through your "base64web" encoder to get "AQAB".

Start a new JSON object. Add a string called "e" and set it to the output of the above step. So, yes, instead of saying that "e" equals "65537", you're saying that "e" equals "AQAB". Aren't you glad you did those extra steps?

Add another string called "kty" and set it to "RSA".

Add another string called "n" and set it to the "base64web" version of your modulus bag-of-bytes from earlier.

Take this JSON object and make it into a sorted compact string representation. This means it goes "e, kty, n" and it also has all of the usual padding (spaces) squished out. Call this a JWK string and save it for later.

Create a second JSON object. Add a boolean to it named "termsOfServiceAgreed" that's set to true. (Guess you'd better agree...)

Look up the URL for "newNonce" from the directory JSON you got earlier.

Make a HTTP HEAD request to that URL. Dig around in the headers (not the body, since there is no body on a HEAD) until you find "Replay-Nonce". Extract the value of that header. Hang onto it for later.

Look up the URL for "newAccount" from that directory JSON for before.

Create a third JSON object. Add a string to it called "url". Set it to that (newAccount) URL. Add a string called "alg". Set it to "RS256". Add a string called "nonce" and set it to the value from the *header* in that last HTTP HEAD request.

Add an object to this third object called "jwk". Within it, add "e", "kty" and "n" in a manner that matches what you did earlier (you know, from the "JWK string" you're still holding for later).

Dump this third JSON object to a sorted compact string representation. Call it "protected".

Dump the second JSON object to a sorted compact string representation. Call it "payload".

Create a string where you literally concatenate those two prior strings, such that it's the value of protected, then an actual period (as in 0x2e, a full stop, whatever), then the value of payload.

Write something that'll create a SHA256 digest of an arbitrary string and will sign it with an arbitrary RSA key (like "openssl dgst -sha256 -sign <key>"). The key in question is your personal key.

Pump that "<protected>.<payload>" string through the digest function. Then run it through your "base64web" encoder. Call this the signature.

Create a fourth JSON object. Add a string called "protected" and set it to whatever you built a few steps earlier. Add another string called "payload" and set it likewise. Then add one called "signature" and set it, too.

Take this fourth JSON object and dump it to a sorted compact string representation. Call this your post body.

Make a HTTP POST request to the "newAccount" URL from the directory. Set the content-type to "application/jose+json". Set the post data to the post body string from the previous step.

Dig around in the headers of the response, looking for one named "Location". Don't follow it like a redirection. Why would you ever follow a Location header in a HTTP header, right? Nope, that's your user account's identifier! Yes, you are a URL now. Hang on to that URL for later.

You now have an account.

You still have much to do.

...

That's about where I stopped writing my take on the protocol.

Again, my program no longer works quite like this, but this is where it started after having observed a bunch of other stuff that already existed.

So far, we have (at least): RSA keys, SHA256 digests, RSA signing, base64 but not really base64, string concatenation, JSON inside JSON, Location headers used as identities instead of a target with a 301 response, HEAD requests to get a single value buried as a header, making one request (nonce) to make ANY OTHER request, and there's more to come.

We haven't even scratched the surface of creating an order, dealing with authorizations and challenges, the whole "key thumbprint" thing, what actually goes into those TXT records, and all of that other fun stuff.

...

Random side note: while looking at existing ACME clients, I found that at least one of them screws up their encoding of the publicExponent and ends up interpreting it as hex instead of decimal. That is, instead of 65537, aka 0x10001, it reads it as 0x65537, aka 415031!

Somehow, this anomaly exists and apparently doesn't break anything? I haven't actually run the client in question, but I imagine people are using it since it's in apt.

...

This complexity must be job security for somebody. Maybe multiple somebodies.

During the Apollo flights to the Moon, the astronauts observed the spacecraft's orientation on a special instrument called the FDAI (Flight Director / Attitude Indicator). This instrument showed the spacecraft's attitude—its orientation—by rotating a ball. This ball was nicknamed the "8-ball" because it was black (albeit only on one side). The instrument also acted as a flight director, using three yellow needles to indicate how the astronauts should maneuver the spacecraft. Three more pointers showed how fast the spacecraft was rotating.

Since the spacecraft rotates along three axes (roll, pitch, and yaw), the ball also rotates along three axes. It's not obvious how the ball can rotate to an arbitrary orientation while remaining attached. In this article, I look inside an FDAI from Apollo that was repurposed for a Space Shuttle simulator1 and explain how it operates. (Spoiler: the ball mechanism is firmly attached at the "equator" and rotates in two axes. What you see is two hollow shells around the ball mechanism that spin around the third axis.)

The FDAI in Apollo

For the missions to the Moon, the Lunar Module had two FDAIs, as shown below: one on the left for the Commander (Neil Armstrong in Apollo 11) and one on the right for the Lunar Module Pilot (Buzz Aldrin in Apollo 11). With their size and central positions, the FDAIs dominate the instrument panel, a sign of their importance. (The Command Module for Apollo also had two FDAIs, but with a different design; I won't discuss them here.2)

Each Lunar Module FDAI could display inputs from multiple sources, selected by switches on the panel.3 The ball could display attitude from either the Inertial Measurement Unit or from the backup Abort Guidance System, selected by the "ATTITUDE MON" toggle switch next to either FDAI. The pitch attitude could also be supplied by an electromechanical unit called ORDEAL (Orbital Rate Display Earth And Lunar) that simulates a circular orbit. The error indications came from the Apollo Guidance Computer, the Abort Guidance System, the landing radar, or the rendezvous radar (controlled by the "RATE/ERROR MON" switches). The pitch, roll, and yaw rate displays were driven by the Rate Gyro Assembly (RGA). The rate indications were scaled by a switch below the FDAI, selecting 25°/sec or 5°/sec.

The FDAI mechanism

The ball inside the indicator shows rotation around three axes. I'll first explain these axes in the context of an aircraft, since the axes of a spacecraft are more arbitrary.4 The roll axis indicates the aircraft's angle if it rolls side-to-side along its axis of flight, raising one wing and lowering the other. Thus, the indicator shows the tilt of the horizon as the aircraft rolls. The pitch axis indicates the aircraft's angle if it pitches up or down, with the indicator showing the horizon moving down or up in response. Finally, the yaw axis indicates the compass direction that the aircraft is heading, changing as the aircraft turns left or right. (A typical aircraft attitude indicator omits yaw.)

I'll illustrate how the FDAI rotates the ball in three axes, using an orange as an example. Imagine pinching the horizontal axis between two fingers with your arm extended. Rotating your arm will roll the ball counter-clockwise or clockwise (red arrow). In the FDAI, this rotation is accomplished by a motor turning the frame that holds the ball. For pitch, the ball rotates forward or backward around the horizontal axis (yellow arrow). The FDAI has a motor inside the ball to produce this rotation. Yaw is a bit more difficult to envision: imagine hemisphere-shaped shells attached to the top and bottom shafts. When a motor rotates these shells (green arrow), the hemispheres will rotate, even though the ball mechanism (the orange) remains stationary.

The diagram below shows the mechanism inside the FDAI. The indicator uses three motors to move the ball. The roll motor is attached to the FDAI's frame, while the pitch and yaw motors are inside the ball. The roll motor rotates the roll gimbal through gears, causing the ball to rotate clockwise or counterclockwise. The roll gimbal is attached to the ball mechanism at two points along the "equator"; these two points define the pitch axis. Numerous wires on the roll gimbal enter the ball along the pitch axis. The roll control transformer provides position feedback, as will be explained below.

Removing the hemispherical shells reveals the mechanism inside the ball. When the roll gimbal is rotated, this mechanism rotates with it. The pitch motor causes the ball mechanism to rotate around the pitch axis. The yaw motor and control transformer are not visible in this photo; they are behind the pitch components, oriented perpendicularly. The yaw motor turns the vertical shaft, with the two hemisphere shells attached to the top and bottom of the shaft. Thus, the yaw motor rotates the ball shells around the yaw axis, while the mechanism itself remains stationary. The control transformers for pitch and yaw provide position feedback.

Why doesn't the wiring get tangled up as the ball rotates? The solution is two sets of slip rings to implement the electrical connections. The photo below shows the first slip ring assembly, which handles rotation around the roll axis. These slip rings connect the stationary part of the FDAI to the rotating roll gimbal. The vertical metal brushes are stationary; there are 23 pairs of brushes, one for each connection to the ball mechanism. Each pair of brushes contacts one metal ring on the striped shaft, maintaining contact as the shaft rotates. Inside the shaft, 23 wires connect the circular metal contacts to the roll gimbal.

A second set of slip rings inside the ball handles rotation around the pitch axis. These rings provide the electrical connection between the wiring on the roll gimbal and the ball mechanism. The yaw axis does not use slip rings since only the hemisphere shells rotate around the yaw axis; no wires are involved.

Synchros and the servo loop

In this section, I'll explain how the FDAI is controlled by synchros and servo loops. In the 1950s and 1960s, the standard technique for transmitting a rotational signal electrically was through a synchro. Synchros were used for everything from rotating an instrument indicator in avionics to rotating the gun on a navy battleship. A synchro produces an output that depends on the shaft's rotational position, and transmits this output signal on three wires. If you connect these wires to a second synchro, you can use the first synchro to control the second one: the shaft of the second synchro will rotate to the same angle as the first shaft. Thus, synchros are a convenient way to send a control signal electrically.

The photo below shows a typical synchro, with the input shaft on the top and five wires at the bottom: two for power and three for the output.

Internally, the synchro has a rotating winding called the rotor that is driven with 400 Hz AC. Three fixed stator windings provide the three AC output signals. As the shaft rotates, the voltages of the output signals change, indicating the angle. (A synchro resembles a transformer with three variable secondary windings.) If two connected synchros have different angles, the magnetic fields create a torque that rotates the shafts into alignment.

The downside of synchros is that they don't produce a lot of torque. The solution is to use a more powerful motor, controlled by the synchro and a feedback loop called a servo loop. The servo loop drives the motor in the appropriate direction to eliminate the error between the desired position and the current position.

The diagram below shows how the servo loop is constructed from a combination of electronics and mechanical components. The goal is to rotate the output shaft to an angle that exactly matches the input angle, specified by the three synchro wires. The control transformer compares the input angle and the output shaft position, producing an error signal. The amplifier uses this error signal to drive the motor in the appropriate direction until the error signal drops to zero. To improve the dynamic response of the servo loop, the tachometer signal is used as a negative feedback voltage. The feedback slows the motor as the system gets closer to the right position, so the motor doesn't overshoot the position and oscillate. (This is sort of like a PID controller.)

A control transformer is similar to a synchro in appearance and construction, but the rotating shaft operates as an input, not the output. In a control transformer, the three stator windings receive the inputs and the rotor winding provides the error output. If the rotor angle of the synchro transmitter and control transformer are the same, the signals cancel out and there is no error voltage. But as the difference between the two shaft angles increases, the rotor winding produces an error signal. The phase of the error signal indicates the direction of the error.

In the FDAI, the motor is a special motor/tachometer, a device that was often used in avionics servo loops. This motor is more complicated than a regular electric motor. The motor is powered by 115 volts AC at 400 hertz, but this won't spin the motor on its own. The motor also has two low-voltage control windings. Energizing the control windings with the proper phase causes the motor to spin in one direction or the other. The motor/tachometer unit also contains a tachometer to measure its speed for the feedback loop. The tachometer is driven by another 115-volt AC winding and generates a low-voltage AC signal that is proportional to the motor's rotational speed.

The photo above shows a motor/tachometer with the rotor removed. The unit has many wires because of its multiple windings. The rotor has two drums. The drum on the left, with the spiral stripes, is for the motor. This drum is a "squirrel-cage rotor", which spins due to induced currents. (There are no electrical connections to the rotor; the drums interact with the windings through magnetic fields.) The drum on the right is the tachometer rotor; it induces a signal in the output winding proportional to the speed due to eddy currents. The tachometer signal is at 400 Hz like the driving signal, either in phase or 180º out of phase, depending on the direction of rotation. For more information on how a motor/tachometer works, see my teardown.

The amplifiers

The FDAI has three servo loops—one for each axis—and each servo loop has a separate control transformer, motor, and amplifier. The photo below shows one of the three amplifier boards. The construction is unusual and somewhat chaotic, with some components stacked on top of others to save space. Some of the component leads are long and protected with clear plastic sleeves.5 The cylindrical pulse transformer in the middle has five colorful wires coming out of it. At the left are the two transistors that drive the motor's control windings, with two capacitors between them. The transistors are mounted on a heat sink that is screwed down to the case of the amplifier assembly for cooling. Each amplifier is connected to the FDAI through seven wires with pins that plug into the sockets on the right of the board.6

The function of the board is to amplify the error signal so the motor rotates in the appropriate direction. The amplifier also uses the tachometer output from the motor unit to slow the motor as the error signal decreases, preventing overshoot. The inputs to the amplifier are 400 hertz AC signals, with the magnitude indicating the amount of error or speed and the phase indicating the direction. The two outputs from the amplifier drive the two control windings of the motor, determining which direction the motor rotates.

The schematic for the amplifier board is below. 7 The two transistors on the left amplify the error and tachometer signals, driving the pulse transformer. The outputs of the pulse transformer will have opposite phases, driving the output transistors for opposite halves of the 400 Hz cycle. This activates the motor control winding, causing the motor to spin in the desired direction.8

History of the FDAI

Bill Lear, born in 1902, was a prolific inventor with over 150 patents, creating everything from the 8-track tape to the Learjet, the iconic private plane of the 1960s. He created multiple companies in the 1920s as well as inventing one of the first car radios for Motorola before starting Lear Avionics, a company that specialized in aerospace instruments.9 Lear produced innovative aircraft instruments and flight control systems such as the F-5 automatic pilot, which received a trophy as the "greatest aviation achievement in America" for 1950.

Bill Lear went on to solve an indicator problem for the Air Force: the supersonic F-102 Delta Dagger interceptor (1953) could climb at steep angles, but existing attitude indicators could not handle nearly vertical flight. Lear developed a remote two-gyro platform that drove the cockpit indicator while avoiding "gimbal lock" during vertical flight. For the experimental X-15 rocket-powered aircraft (1959), Lear improved this indicator to handle three axes: roll, pitch, and yaw.

Meanwhile, the Siegler Corporation started in 1950 to manufacture space heaters for homes. A few years later, Siegler was acquired by John Brooks, an entrepreneur who was enthusiastic about acquisitions. In 1961, Lear Avionics became his latest acquisition, and the merged company was called Lear Siegler Incorporated, often known as LSI. (Older programmers may know Lear Siegler through the ADM-3A, an inexpensive video display terminal from 1976 that housed the display and keyboard in a stylish white case.)

The X-15's attitude indicator became the basis of the indicator for the F-4 fighter plane (the ARU/11-A). Then, after "a minimum of modification", the attitude-director indicator was used in the Gemini space program. In total, Lear Siegler provided 11 instruments in the Gemini instrument panel, with the attitude director the most important. Next, Gemini's indicator was modified to become the FDAI (flight director-attitude indicator) in the Lunar Module for Apollo.10 Lear Siegler provided numerous components for the Apollo program, from a directional gyro for the Lunar Rover to the electroluminescent display for the Apollo Guidance Computer's Display/Keyboard (DSKY).

In 1974, Lear Siegler obtained a contract to develop the Attitude-Director Indicator (ADI) for the Space Shuttle, producing a dozen ADI units for the Space Shuttle. However, by this time, Lear Siegler was losing enthusiasm for low-volume space avionics. The Instrument Division president said that "the business that we were in was an engineering business and engineers love a challenge." However, manufacturing refused to deal with the special procedures required for space manufacturing, so the Shuttle units were built by the engineering department. Lear Siegler didn't bid on later Space Shuttle avionics and the Shuttle ADI became its last space product. In the early 2000s, the Space Shuttle's instruments were upgraded to a "glass cockpit" with 11 flat-panel displays known as the Multi-function Electronic Display System (MEDS). The MEDS was produced by Lear Siegler's long-term competitor, Honeywell.

Getting back to Bill Lear, he wanted to manufacture aircraft, not just aircraft instruments, so he created the Learjet, the first mass-produced business jet. The first Learjet flew in 1963, with over 3000 eventually delivered. In the early 1970s, Lear designed a steam turbine automobile engine. Rather than water, the turbine used a secret fluorinated hydrocarbon called "Learium". Lear had visions of thousands of low-pollution "Learmobiles", but the engine failed to catch on. Lear had been on the verge of bankruptcy in the 1960s; one of his VPs explained that "the great creative minds can't be bothered with withholding taxes and investment credits and all this crap". But by the time of his death in 1978, Lear had a fortune estimated at $75 million.

Comparing the ARU/11-A and the FDAI

Looking inside our FDAI sheds more details on the evolution of Lear Siegler's attitude directors. The photo below compares the Apollo FDAI (top) to the earlier ARU/11-A used in the F-4 aircraft (bottom). While the basic mechanism and the electronic amplifiers are the same between the two indicators, there are also substantial changes.

The biggest difference between the ARU-11/A indicator and the FDAI is that the electronics for the ARU-11/A are in a separate module that was plugged into the back of the indicator, while the FDAI includes the electronics internally, with boards mounted on the instrument frame. Specifically, the ARU-11/A has a separate unit containing a multi-winding transformer, a power supply board, and three amplifier boards (one for each axis), while the FDAI contains these components internally. The amplifier boards in the ARU-11/A and the FDAI are identical, constructed from germanium transistors rather than silicon.11 The unusual 11-pin transformers are also the same. However, the power supply boards are different, probably because the boards also contain scaling resistors that vary between the units.12 The power supply boards are also different shapes to fit the available space.

The ball assemblies of the ARU/11-A and the FDAI are almost the same, with the same motor assemblies and slip ring mechanism. The gearing has minor changes. In particular, the FDAI has two plastic gears, while the ARU/11-A uses exclusively metal gears.

The ARU/11-A has a patented pitch trim feature that was mostly—but not entirely—removed from the Apollo FDAI. The motivation for this feature is that an aircraft in level flight will be pitched up a few degrees, the "angle of attack". It is desirable for the attitude indicator to show the aircraft as horizontal, so a pitch trim knob allows the angle of attack to be canceled out on the display. The problem is that if you fly your fighter plane vertically, you want the indicator to show precisely vertical flight, rather than applying the pitch trim adjustment. The solution in the ARU-11/A is a special 8-zone potentiometer on the pitch axis that will apply the pitch trim adjustment in level flight but not in vertical flight, while providing a smooth transition between the regions. This special potentiometer is mounted inside the ball of the ARU-11/A. However, this pitch trim adjustment is meaningless for a spacecraft, so it is not implemented in the Apollo or Space Shuttle instruments. Surprisingly, the shell of the potentiometer still exists in our FDAI, but without the potentiometer itself or the wiring. Perhaps it remained to preserve the balance of the ball. In the photo below, the cylindrical potentiometer shell is indicated by an arrow. Note the holes in the front of the shell; in the ARU-11/A, the potentiometer's wiring terminals protrude through these holes, but in the FDAI, the holes are covered with tape.

Finally, the mounting of the ball hemispheres is slightly different. The ARU/11-A uses four screws at the pole of each hemisphere. Our FDAI, however, uses a single screw at each pole; the screw is tightened with a Bristol Key, causing the shaft to expand and hold the hemisphere in place.

To summarize, the Apollo FDAI occupies a middle ground: while it isn't simply a repurposed ARU-11/A, neither is it a complete redesign. Instead, it preserves the old design where possible, while stripping out undesired features such as pitch trim. The separate amplifier and mechanical units of the ARU/11-A were combined to form the larger FDAI.

Differences from Apollo

The FDAI that we examined is a special unit: it was originally built for Apollo but was repurposed for a Space Shuttle simulator. Our FDAI is labeled Model 4068F, which is a Lunar Module part number. Moreover, the FDAI is internally stamped with the date "Apr. 22 1968", over a year before the first Moon landing.

However, a closer look shows that several key components were modified to make the Apollo FDAI work in the Shuttle Simulator.14 The Apollo FDAI (and the Shuttle ADI) used resolvers as inputs to control the ball, while our FDAI uses synchros. (Resolvers and synchros are similar, except resolvers use sine and cosine inputs, 90° apart, on two wire pairs, while synchros use three inputs, 120° apart, on three wires.) NASA must have replaced the three resolver control transformers in the FDAI with synchro control transformers for use in the simulator.

The Apollo FDAI used electroluminescent lighting for the display, while ours uses eight small incandescent bulbs. The metal case of our FDAI has a Dymo embossed tape label "INCANDESCENT LIGHTING", alerting users to the change from Apollo's illumination. Our FDAI also contains a step-down transformer to convert the 115 VAC input into 5 VAC to power the bulbs, while the Shuttle powered its ADI illumination directly from 5 volts.

The dial of our FDAI was repainted to match the dial of the Shuttle FDAI. The Apollo FDAI had red bands on the left and right of the dial. A close examination of our dial shows that black paint was carefully applied over the red paint, but a few specks of red paint are still visible (below). Moreover, the edges of the lines and the lozenge show slight unevenness from the repainting. Second, the Apollo FDAI had the text "ROLL RATE", "PITCH RATE", and "YAW RATE" in white next to the needle scales. In our FDAI, this text has been hidden by black paint to match the Shuttle display.13 Third, the Apollo LM FDAI had a crosshair in the center of the instrument, while our FDAI has a white U-shaped indicator, the same as the Shuttle (and the Command Module's FDAI). Finally, the ball of the Apollo FDAI has red circular regions at the poles to warn of orientations that can cause gimbal lock. Our FDAI (like the Shuttle) does not have these circles. We couldn't see any evidence that these regions were repainted, so we suspect that our FDAI has Shuttle hemispheres on the ball.

Our FDAI has also been modified electrically. Small green connectors (Micro-D MDB1) have been added between the slip rings and the motors, as well as on the gimbal arm. We think these connectors were added post-Apollo, since they are attached somewhat sloppily with glue and don't look flight-worthy. Perhaps these connectors were added to make disassembly and modification easier. Moreover, our FDAI has an elapsed time indicator, also mounted with glue.

The back of our FDAI is completely different from Apollo. First, the connector's pinout is completely different. Second, each of the six indicator needles has a mechanical adjustment as well as a trimpot (details). Finally, each of the three axes has an adjustment potentiometer.

The Shuttle's ADI (Attitude Director Indicator)

Each Space Shuttle had three ADIs (Attitude Director Indicators), which were very similar to the Apollo FDAI, despite the name change. The photo below shows the two octagonal ADIs in the forward flight deck, one on the left in front of the Commander, and one on the right in front of the Pilot. The aft flight deck station had a third ADI.15

Our FDAI appears to have been significantly modified for use in the Shuttle simulator, as described above. However, it is much closer to the Apollo FDAI than the ADI used in the Shuttle, as I'll show in this section. My hypothesis is that the simulator was built before the Shuttle's ADI was created, so the Apollo FDAI was pressed into service.

The Shuttle's ADI was much more complicated electrically than the Apollo FDAI and our FDAI, providing improved functionality.16 For instance, while the Apollo FDAI had a simple "OFF" indicator flag to show that the indicator had lost power, the Shuttle's ADI had extensive error detection. It contained voltage level monitors to check its five power supplies. (The Shuttle ADI used three DC power sources and two AC power sources, compared to the single AC supply for Apollo.) The Shuttle's ADI also monitored the ball servos to detect position errors. Finally, it received an external "Data OK" signal. If a fault was detected by any of these monitors, the "OFF" flag was deployed to indicate that the ADI could not be trusted.

The Shuttle's ADI had six needles, the same as Apollo, but the Shuttle used feedback to make the positions more accurate. Specifically, each Shuttle needle had a feedback sensor, a Linear Variable Differential Transformer (LVDT) that generates a voltage based on the needle position. The LVDT output drove a servo feedback loop to ensure that the needle was in the exact desired position. In the Apollo FDAI, on the other hand, the needle input voltage drove a galvanometer, swinging the needle proportionally, but there was no closed loop to ensure accuracy.

I assume that the Shuttle's ADI had integrated circuit electronics to implement this new functionality, considerably more modern than the germanium transistors in the Apollo FDAI. The Shuttle probably used the same mechanical structures to rotate the ball, but I can't confirm that.

Conclusions

The FDAI was a critical instrument in Apollo, indicating the orientation of the spacecraft in three axes. It wasn't obvious to me how the "8-ball" can rotate in three axes while still being securely connected to the instrument. The trick is that most of the mechanism rotates in two axes, while hollow hemispherical shells provide the third rotational axis.

The FDAI has an interesting evolutionary history, from the experimental X-15 rocket plane and the F-4 fighter to the Gemini, Apollo, and Space Shuttle flights. Our FDAI has an unusual position in this history: since it was modified from Apollo to function in a Space Shuttle simulator, it shows aspects of both Apollo and the Space Shuttle indicators. It would be interesting to compare the design of a Shuttle ADI to the Apollo FDAI, but I haven't been able to find interior photos of a Shuttle ADI (or of an unmodified Apollo FDAI).17

You can see a brief video of the FDAI in motion here. For more, follow me on Bluesky (@righto.com), Mastodon (@kenshirriff@oldbytes.space), or RSS. (I've given up on Twitter.) I worked on this project with CuriousMarc, Mike Stewart, and Eric Schlapfer, so expect a video at some point. Thanks to Richard for providing the FDAI. I wrote about the F-4 fighter plane's attitude indicator here.

Notes and references

# Introduction

After thinking about BusKill product that triggers a command once the USB cord disconnects, I have been thinking at a simple alternative.

=> https://www.buskill.in BusKill official project website

When using a laptop connected to power most of the time, you may want it to power off once it gets disconnected, this can be really useful if you use it in a public area like a bar or a train.  The idea is to protect the laptop if it gets stolen while in use and unlocked.

Here is how to proceed on Linux, using a trigger on an udev rule looking for a change in the power_supply subsystem.

For OpenBSD users, it is possible to use apmd as I explained in this article:

=> https://dataswamp.org/~solene/2024-02-20-rarely-known-openbsd-features.html#_apmd_daemon_hooks => Rarely known OpenBSD features: apmd daemon hooks

In the example, the script will just power off the machine, it is up to you to do whatever you want like destroy the LUKS master key or trigger the coffee machine :D

# Setup

Create a file `/etc/udev/rules.d/disconnect.rules`, you can name it how you want as long as it ends with `.rules`:

```
SUBSYSTEM=="power_supply", ENV{POWER_SUPPLY_ONLINE}=="0", ENV{POWER_SUPPLY_TYPE}=="Mains", RUN+="/usr/local/bin/power_supply_off"
```

Create a file `/usr/local/bin/power_supply_off` that will be executed when you unplug the laptop:

```
#!/bin/sh
echo "Going off because power supply got disconnected" | systemd-cat
systemctl poweroff
```

This simple script will add an entry in journald before triggering the system shutdown.

Mark this script executable with:
```
chmod +x /usr/local/bin/power_supply_off
```

Reload udev rules using the following commands:

```
udevadm control --reload-rules
udevadm trigger
```

# Testing

If you unplug your laptop power, it should power off, you should find an entry in the logs.

If nothing happens, looks at systemd logs to see if something is wrong in udev, like a syntax error in the file you created or an incorrect path for the script.

# Script ideas

Depending on your needs, here is a list of actions the script could do, from gentle to hardcore:

* Lock user sessions
* Hibernate
* Proper shutdown
* Instant power off (through sysrq)
* Destroy LUKS master key to make LUKS volume unrecoverable + Instant power off

# Conclusion

While BusKill is an effective / unusual product that is certainly useful for a niche, protecting a running laptop against thieves is an extra layer when being outside.

Obviously, this use case works only when the laptop is connected to power.

Today, we’re looking at two case studies in how to respond when reactionaries appear in your free software community.

Exhibit A

It is a technical decision.

The technical reason is that the security team does not have the bandwidth to provide lifecycle maintenance for multiple X server implementations. Part of the reason for moving X from main to community was to reduce the burden on the security team for long-term maintenance of X. Additionally, nobody so far on the security team has expressed any interest in collaborating with xxxxxx on security concerns.

We have a working relationship with Freedesktop already, while we would have to start from the beginning with xxxxxx.

Why does nobody on the security team have any interest in collaboration with xxxxxx? Well, speaking for myself only here – when I looked at their official chat linked in their README, I was immediately greeted with alt-right propaganda rather than tactically useful information about xxxxxx development. At least for me, I don’t have any interest in filtering through hyperbolic political discussions to find out about CVEs and other relevant data for managing the security lifecycle of X.

Without relevant security data products from xxxxxx, as well as a professionally-behaving security contact, it is unlikely for xxxxxx to gain traction in any serious distribution, because X is literally one of the more complex stacks of software for a security team to manage already.

At the same time, I sympathize with the need to keep X alive and in good shape, and agree that there hasn’t been much movement from freedesktop in maintaining X in the past few years. There are many desktop environments which will never get ported to Wayland and we do need a viable solution to keep those desktop environments working.

I know the person who wrote this, and I know that she’s a smart cookie, and therefore I know that she probably understood at a glance that the community behind this “project” literally wants to lynch her. In response, she takes the high road, avoids confronting the truth directly, and gives the trolls a bunch of talking points to latch on for counter-arguments. Leaves plenty of room for them to bog everyone down in concern trolling and provides ample material to fuel their attention-driven hate machine.

There’s room for improvement here.

Exhibit B

Concise, speaks the truth, answers ridiculous proposals with ridicule, does not afford the aforementioned reactionary dipshits an opportunity to propose a counter-argument. A+.

Extra credit for the follow-up:

The requirement for a passing grade in this class is a polite but summary dismissal, but additional credit is awarded for anyone who does not indulge far-right agitators as if they were equal partners in maintaining a sense of professional decorum.

If you are a community leader in FOSS, you are not obligated to waste your time coming up with a long-winded technical answer to keep nazis out of your community. They want you to argue with them and give them attention and feed them material for their reactionary blog or whatever. Don’t fall into their trap. Do not answer bad faith with good faith. This is a skill you need to learn in order to be an effective community leader.

If you see nazis 👏👏 you ban nazis 👏👏 — it’s as simple as that.

The name of the project is censored not because it’s particularly hard for you to find, but because all they really want is attention, and you and me are going to do each other a solid by not giving them any of that directly.

To preclude the sorts of reply guys who are going to insist on name-dropping the project and having a thread about the underlying drama in the comments, the short introduction is as follows:

For a few years now, a handful of reactionary trolls have been stoking division in the community by driving a wedge between X11 and Wayland users, pushing a conspiracy theory that paints RedHat as the DEI boogeyman of FOSS and assigning reactionary values to X11 and woke (pejorative) values to Wayland. Recently, reactionary opportunists “forked” Xorg, replaced all of the literature with political manifestos and dog-whistles, then used it as a platform to start shit with downstream Linux distros by petitioning for inclusion and sending concern trolls to waste everyone’s time.

The project itself is of little consequence; they serve our purposes today by providing us with case-studies in dealing with reactionary idiots starting shit in your community.

Tech workers have long resisted the suggestion that we should be organized into unions. The topic is consistently met with a cold reception by tech workers when it is raised, and no big tech workforce is meaningfully organized. This is a fatal mistake – and I don’t mean “fatal” in the figurative sense. Tech workers, it’s time for you to unionize, and strike, or you and your loved ones are literally going to die.

In this article I will justify this statement and show that it is clearly not hyperbolic. I will explain exactly what you need to do, and how organized labor can and will save your life.

Hey – if you want to get involved in labor organizing in the tech sector you should consider joining the new unitelabor.dev forum. Adding a head’s up here in case you don’t make it to the end of this very long blog post.

The imperative to organize is your economic self-interest

Before I talk about the threats to your life and liberty that you must confront through organized labor, let me re-iterate the economic position for unionizing your workplace. It is important to revisit this now, because the power politics of the tech sector has been rapidly changing over the past few years, and those changes are not in your favor.

The tech industry bourgeoisie has been waging a prolonged war on labor for at least a decade. Far from mounting any kind of resistance, most of tech labor doesn’t even understand that this is happening to them. Your boss is obsessed with making you powerless and replaceable. You may not realize how much leverage you have over your boss, but your boss certainly does – and has been doing everything in their power to undermine you before you wizen up. Don’t let yourself believe you’re a part of their club – if your income depends on your salary, you are part of the working class.

Payroll – that’s you – is the single biggest expense for every tech company. When tech capitalists look at their balance sheet and start thinking of strategies for increasing profits, they see an awful lot of pesky zeroes stacked up next to the line item for payroll and benefits. Long-term, what’s their best play?

It starts with funneling cash and influence into educating a bigger, cheaper generation of compsci graduates to flood the labor market – “everyone can code”. Think about strategic investments in cheap(ish), broadly available courses, online schools and coding “bootcamps” – dangling your high salary as the carrot in front of wannabe coders fleeing dwindling prospects in other industries, certain that the carrot won’t be nearly as big when they all eventually step into a crowded labor market.

The next step is rolling, industry-wide mass layoffs – often obscured under the guise of “stack ranking” or some similar nonsense. Big tech has been callously cutting jobs everywhere, leaving workers out in the cold in batches of thousands or tens of thousands. If you don’t count yourself among them yet, maybe you will soon. What are your prospects for re-hire going to look like if this looming recession materializes in the next few years?

Consider what’s happening now – why do you think tech is driving AI mandates down from the top? Have you been ordered to use an LLM assistant to “help” with your programming? Have you even thought about why the executives would push this crap on you? You’re “training” your replacement. Do you really think that, if LLMs really are going to change the way we code, they aren’t going to change the way we’re paid for it? Do you think your boss doesn’t see AI as a chance to take $100M off of their payroll expenses?

Aren’t you worried you could get laid off and this junior compsci grad or an H1B takes your place for half your salary? You should be – it’s happening everywhere. What are you going to do about it? Resent the younger generation of programmers just entering the tech workforce? Or the immigrant whose family pooled their resources to send them abroad to study and work? Or maybe you weren’t laid off yet, and you fancy yourself better than the poor saps down the hall who were. Don’t be a sucker – your enemy isn’t in the cubicle next to you, or on the other side of the open office. Your enemy has an office with a door on it.

Listen: a tech union isn’t just about negotiating higher wages and benefits, although that’s definitely on the table. It’s about protecting yourself, and your colleagues, from the relentless campaign against labor that the tech leadership is waging against us. And more than that, it’s about seizing some of the awesome, society-bending power of the tech giants. Look around you and see what destructive ends this power is being applied to. You have your hands at the levers of this power if only you rise together with your peers and make demands.

And if you don’t, you are responsible for what’s going to happen next.

The imperative to organize is existential

If global warming is limited to 2°C, here’s what Palo Alto looks like in 2100:¹

Limiting warming to 2° C requires us to cut global emissions in half by 2030 – in 5 years – but emissions haven’t even peaked yet. Present-day climate policies are only expected to limit warming to 2.5° to 2.9° C by 2100.² Here’s Palo Alto in 75 years if we stay our current course:

Here’s the Gulf of Mexico in 75 years:

This is what will happen if things don’t improve. Things aren’t improving – they’re getting worse. The US elected an anti-science president who backed out of the Paris agreement, for a start. Your boss is pouring all of our freshwater into datacenters to train these fucking LLMs and expanding into this exciting new market with millions of tons of emissions as the price of investment. Cryptocurrencies still account for a full 1% of global emissions. Datacenters as a whole account for 2%. That’s on us – tech workers. That is our fucking responsibility.

Climate change is accelerating, and faster than we thought, and the rich and powerful are making it happen faster. Climate catastrophe is not in the far future, it’s not our children or our children’s children, it’s us, it’s already happening. You and I will live to see dozens of global catastrophes playing out in our lifetimes, with horrifying results. Even if we started a revolution tomorrow and overthrew the ruling class and implemented aggressive climate policies right now we will still watch tens or hundreds of millions die.

Let’s say you are comfortably living outside of these blue areas, and you’ll be sitting pretty when Louisiana or Bruges or Fiji are flooded. Well, 13 million Americans are expected to have to migrate out of flooded areas – and 216 million globally³ – within 25 to 30 years. That’s just from the direct causes of climate change – as many as 1 billion could be displaced if we account for the ensuing global conflict and civil unrest.⁴ What do you think will happen to non-coastal cities and states when 4% of the American population is forced to flee their homes? You think you won’t be affected by that? What happens when anywhere from 2.5% to 12% of the Earth’s population becomes refugees?

What are you going to eat? Climate change is going to impact fresh water supplies and reduce the world’s agriculturally productive land. Livestock is expected to be reduced by 7-10% in just 25 years.⁵ Food prices will skyrocket and people will starve. 7% of all species on Earth may already be extinct because of human activities.⁶ You think that’s not going to affect you?

The overwhelming majority of the population supports climate action.⁷ The reason it’s not happening is because, under capitalism, capital is power, and the few have it and the many don’t. We live in a global plutocracy.

The plutocracy has an answer to climate change: fascism. When 12% of the world’s population is knocking at the doors of the global north, their answer will be concentration camps and mass murder. They are already working on it today. When the problem is capitalism, the capitalists will go to any lengths necessary to preserve the institutions that give them power – they always have. They have no moral compass or reason besides profit, wealth, and power. The 1% will burn and pillage and murder the 99% without blinking.

They are already murdering us. 1.2 million Americans are rationing their insulin.⁸ The healthcare industry, organized around the profit motive, murders 68,000 Americans per year.⁹ To the Europeans among my readership, don’t get too comfortable, because I assure you that our leaders are working on destroying our healthcare systems, too.

Someone you love will be laid off, get sick, and die because they can’t afford healthcare. Someone you know, probably many people that you know, will be killed by climate change. It might be someone you love. It might be you.

When you do get laid off mid-recession, your employer replaces you and three of your peers with a fresh bootcamp “graduate” and a GitHub Copilot subscription, and all of the companies you might apply to have done the same… how long can you keep paying rent? What about your friends and family, those who don’t have a cushy tech job or tech worker prospects, what happens when they get laid off or automated away or just priced out of the cost of living? Homelessness is at an all time high and it’s only going to get higher. Being homeless takes 30 years off of your life expectancy.¹⁰ In the United States, there are 28 vacant homes for every homeless person.¹¹

Capitalism is going to murder the people you love. Capitalism is going to murder you.

We need a different answer to the crises that we face. Fortunately, the working class can offer a better solution – one with a long history of success.

Organizing is the only answer and it will work

The rich are literally going to kill you and everyone you know and love just because it will make them richer. Because it is making them richer.

Do you want to do something about any of the real, urgent problems you face? Do you want to make meaningful, rapid progress on climate change, take the catastrophic consequences we are already guaranteed to face in stride, and keep your friends and family safe?

Well, tough shit – you can’t. Don’t tell me you’ll refuse the work, or that it’ll get done anyway without you, or that you can just find another job. They’ll replace you, you won’t find another job, and the world will still burn. You can’t vote your way to a solution, either: elections don’t matter, your vote doesn’t matter, and your voice is worthless to politicians.¹² Martin Gilens and Benjamin Page demonstrated this most clearly in their 2014 study, “Testing Theories of American Politics: Elites, Interest Groups, and Average Citizens”.¹³

Gilens and Page plotted a line chart which shows us the relationship between the odds of a policy proposal being adopted (Y axis) charted against public support for the policy (X axis). If policy adoption was entirely driven by public opinion, we would expect a 45° line (Y=X), where broad public support guarantees adoption and broad public opposition prevents adoption. We could also substitute “public opinion” for the opinions of different subsets of the public to see their relative impact on policy. Here’s what they got:

For most of us, we get a flat line: Y, policy adoption, is completely unrelated to X, public support. Our opinion has no influence whatsoever on policy adoption. Public condemnation or widespread support has the same effect on a policy proposal, i.e. none. But for the wealthy, it’s a different story entirely. I’ve never seen it stated so plainly and clearly: the only thing that matters is money, wealth, and capital. Money is power, and the rich have it and you don’t.

Nevertheless, you must solve these problems. You must participate in finding and implementing solutions. You will be fucked if you don’t. But it is an unassailable fact that you can’t solve these problems, because you have no power – at least, not alone.

Together, we do have power. In fact, we can fuck with those bastards’ money and they will step in line if, and only if, we organize. It is the only solution, and it will work.

The ultra-rich possess no morals or ideology or passion or reason. They align with fascists because the fascists promise what they want, namely tax cuts, subsidies, favorable regulation, and cracking the skulls of socialists against the pavement. The rich hoard and pillage and murder with abandon for one reason and one reason only: it’s profitable. The rich always do what makes them richer, and only what makes them richer. Consequently, you need to make this a losing strategy. You need to make it more profitable to do what you want. To control the rich, you must threaten the only thing they care about.

Strikes are so costly for companies that they will do anything to prevent them – and if they fail to prevent them, then shareholders will pressure them to capitulate if only to stop the hemorrhaging of profit. This threat is so powerful that it doesn’t have to stop at negotiating your salary and benefits. You could demand your employer participate in boycotting Israel. You could demand that your employer stops anti-social lobbying efforts, or even adopts a pro-social lobbying program. You could demand that your CEO cannot support causes that threaten the lives and dignity of their queer or PoC employees. You could demand that they don’t bend the knee to fascists. If you get them where it hurts – their wallet – they will fall in line. They are more afraid of you than we are afraid of them. They are terrified of us, and it’s time we used that to our advantage.

We know it works because it has always worked. In 2023, United Auto Workers went on strike and most workers won a 25% raise. In February, teachers in Los Angeles went on strike for just 8 days and secured a 19% raise. Nurses in Oregon won a 22% raise, better working schedules, and more this year – and Hawaiian nurses secured an agreement to improve worker/patient ratios in September. Tech workers could take a page out of the Writer’s Guild’s book – in 2023 they secured a prohibition against the use of their work to train AI models and the use of AI to suppress their wages.

Organized labor is powerful and consistently gets concessions from the rich and powerful in a way that no other strategy has ever been able to. It works, and we have a moral obligation to do it. Unions gets results.

How to organize step by step

I will give you a step-by-step plan for exactly what you need to do to start moving the needle here. The process is as follows:

1. Building solidarity and community with your peers
2. Understanding your rights and how to organize safely
3. Establishing the consensus to unionize, and do it
4. Promoting solidarity with across tech workplaces and labor as a whole

Remember that you will not have to do this alone – in fact, that’s the whole point. Step one is building community with your colleagues. Get to know them personally, establish new friendships and grow the friendships you already have. Learn about each other’s wants, needs, passions, and so on, and find ways to support each other. If someone takes a sick day, organize someone to check on them and make them dinner or pick up their kids from school. Organize a board game night at your home with your colleagues, outside of work hours. Make it a regular event!

Talk to your colleagues about work, and your workplace. Tell each other about your salaries and benefits. When you get a raise, don’t be shy, tell your colleagues how much you got and how you negotiated it. Speak positively about each other at performance reviews and save critical feedback for their ears only. Offer each other advice about how to approach their boss to get their needs met, and be each other’s advocate.

Talk about the power you have to work together to accomplish bigger things. Talk about the advantage of collective action. It can start small – perhaps your team collectively refuses to incorporate LLMs into your workflow. Soon enough you and your colleagues will be thinking about unionizing.

Disclaimer: Knowledge about specific processes and legal considerations in this article is US-specific. Your local laws are likely similar, but you should research the differences with your colleagues.

The process of organizing a union in the US is explained step-by-step at workcenter.gov. More detailed resources, including access to union organizers in your neighborhood, are available from the American Federation of Labor and Congress of Industrial Organizations (AFL-CIO). But your biggest resources will be people already organizing in the tech sector: in particular you should consult CODE-CWA, which works with tech workers to provide mentoring and resources on organizing tech workplaces – and has already helped several tech workplaces organize their unions and start making a difference. They’ve got your back.

This is a good time to make sure that you and your colleagues understand your rights. First of all, you would be wise to pool your resources and hire the attention of a lawyer specializing in labor – consult your local bar association to find one (it’s easy, just google it and they’ll have a web thing). Definitely reach out to AFL-CIO and CODE-CWA to meet experienced union organizers who can help you.

You cannot be lawfully fired or punished for discussing unions, workplace conditions, or your compensation and benefits, with your colleagues. You cannot be punished for distributing literature in support of your cause, especially if you do it off-site (even just outside of the front door). Be careful not to make careless remarks about your boss’s appearance, complain about the quality of your company’s products, make disparaging comments about clients or customers, etc – don’t give them an easy excuse. Hold meetings and discussions outside of work if necessary, and perform your duties as you normally would while organizing.

Once you start getting serious about organizing, your boss will start to work against you, but know that they cannot stop you. Nevertheless, you and/or some of your colleagues may run the risk of unlawful retaliation or termination for organizing – this is why you should have a lawyer on retainer. This is also why it’s important to establish systems of mutual aid, so that if one of your colleagues gets into trouble you can lean on each other to keep supporting your families. And, importantly, remember that HR works for the company, not for you. HR are the front lines that are going to execute the unionbusting mandates from above.

Once you have a consensus among your colleagues to organize – which you will know because they will have signed union cards – you can approach your employer to ask them to voluntarily recognize the union. If they agree to opening an organized dialogue amicably, you do so. If not, you will reach out to the National Labor Relations Board (NLRB) to organize a vote to unionize. Only organize a vote that you know you will win. Once your workplace votes to unionize, your employer is obligated to negotiate with you in good faith. Start making collective decisions about what you want from your employer and bring them to the table.

In this process, you will have established a relationship with more experienced union organizers who will continue to help you with conducting your union’s affairs and start getting results. The next step is to make yourself available for this purpose to the next tech workplace that wants to unionize: to share what you’ve learned and support the rest of the industry in solidarity. Talk to your friends across the industry and build solidarity and power in mass.

Prepare for the general strike on May 1st, 2028

The call has gone out: on Labor Day, 2028 – just under three years from now – there will be a general strike in the United States. The United Auto Workers union, one of the largest in the United States, has arranged for their collective bargaining agreements to end on this date, and has called for other unions to do the same across all industries. The American Federation of Teachers and its 1.2 million members are on board, and other unions are sure to follow. Your new union should be among them.

This is how we collectively challenge not just our own employers, but our political institutions as a whole. This is how we turn this nightmare around.

A mass strike is a difficult thing to organize. It is certain to be met with large-scale, coordinated, and well-funded propaganda and retaliation from the business and political spheres. Moreover, a mass strike depends on careful planning and mass mutual aid. We need to be prepared to support each other to get it done, and to plan and organize seriously. When you and your colleagues get organized, discuss this strike amongst yourselves and be prepared to join in solidarity with the rest of the 99% around the country and the world at large.

To commit yourselves to participate or get involved in the planning of the grassroots movement, see generalstrikeus.com.

Join unitelabor.dev

I’ve set up a Discourse instance for discussion, organizing, Q&A, and solidarity among tech workers at unitelabor.dev. Please check it out!

If you have any questions or feedback on this article, please post about it there.

Unionize or die

You must organize, and you must start now, or the worst will come to pass. Fight like your life depends on it, beause it does. It has never been more urgent. The tech industry needs to stop fucking around and get organized.

We are powerful together. We can change things, and we must. Spread the word, in your workplace and with your friends and online. On the latter, be ready to fight just to speak – especially in our online spaces owned and controlled by the rich (ahem – YCombinator, Reddit, Twitter – etc). But fight all the same, and don’t stop fighting until we’re done.

We can do it, together.

Resources

Tech-specific:

• unitelabor.dev (new)
• Tech Workers Coalition (Global)
• CODE-CWA (US)
• UTAW (UK)
• Prospect (UK)
• Alphabet Workers Union (Google)

General:

• Industrial Workers of the World (Global)
• International Confederation of Labor (Global)
• AFL-CIO (US)
• workcenter.gov (US)
• generalstrikeus.com (US)
• Emergency Workplace Organizing Committee (US)
• Labor Notes (US)
• Organize Now! (UK)

Send me more resources to add here!

My spouse and I are on vacation in Japan, spending half our time seeing the sights and the other half working remotely and enjoying the experience of living in a different place for a while. To get here, we flew on British Airways from London to Tokyo, and I entertained myself on the long flight by browsing the interactive flight map on the back of my neighbor’s seat and trying to figure out how the poor developer who implemented this map solved the thorny problems that displaying a world map implies.

I began my survey by poking through the whole interface of this little in-seat entertainment system¹ to see if I can find out anything about who made it or how it works – I was particularly curious to find a screen listing open source licenses that such such devices often disclose. To my dismay I found nothing at all – no information about who made it or what’s inside. I imagine that there must be some open source software in that thing, but I didn’t find any licenses or copyright statements.

When I turned my attention to the map itself, I did find one copyright statement, the only one I could find in the whole UI. If you zoom in enough, it switches from a satellite view to a street view showing the OpenStreetMap copyright line:

Given that British Airways is the proud flag carrier of the United Kingdom I assume that this is indeed the only off-the-shelf copyrighted material included in this display, and everything else was developed in-house without relying on any open source software that might require a disclosure of license and copyright details. For similar reasons I am going to assume that all of the borders shown in this map are reflective of the official opinion of British Airways on various international disputes.

As I briefly mentioned a moment ago, this map has two views: satellite photography and a very basic street view. Your plane and its route are shown in real-time, and you can touch the screen to pan and zoom the map anywhere you like. You can also rotate the map and change the angle in “3D” if you have enough patience to use complex multitouch gestures on the cheapest touch panel they could find.

The street view is very sparse and only appears when you’re pretty far zoomed in, so it was mostly useless for this investigation. The satellite map, thankfully, includes labels: cities, country names, points of interest, and, importantly, national borders. The latter are very faint, however. Here’s an illustrative example:

We also have our first peek at a border dispute here: look closely between the “Georgia” and “Caucasus Mountains” labels. This ever-so-faint dotted line shows what I believe is the Russian-occupied territory of South Ossetia in Georgia. Disputes implicating Russia are not universally denoted as such – I took a peek at the border with Ukraine and found that Ukraine is shown as whole and undisputed, with its (undotted) border showing Donetsk, Luhansk, and Crimea entirely within Ukraine’s borders.

Of course, I didn’t start at Russian border disputes when I went looking for trouble. I went directly to Palestine. Or rather, I went to Israel, because Palestine doesn’t exist on this map:

I squinted and looked very closely at the screen and I’m fairly certain that both the West Bank and Gaza are outlined in these dotted lines using the borders defined by the 1949 armistice. If you zoom in a bit more to the street view, you can see labels like “West Bank” and the “Area A”, “Area B” labels of the Oslo Accords:

Given that this is British Airways, part of me was surprised not to see the whole area simply labelled Mandatory Palestine, but it is interesting to know that British Airways officially supports the Oslo Accords.

Heading south, let’s take a look at the situation in Sudan:

This one is interesting – three areas within South Sudan’s claimed borders are disputed, and the map only shows two with these dotted lines. The border dispute with Sudan in the northeast is resolved in South Sudan’s favor. Another case where BA takes a stand is Guyana, which has an ongoing dispute with Venezuela – but the map only shows Guyana’s claim, albeit with a dotted line, rather than the usual approach of drawing both claims with dotted lines.

Next, I turned my attention to Taiwan:

The cities of Taipei and Kaohsiung are labelled, but the island as a whole was not labelled “Taiwan”. I zoomed and panned and 3D-zoomed the map all over the place but was unable to get a “Taiwan” label to appear. I also zoomed into the OSM-provided street map and panned that around but couldn’t find “Taiwan” anywhere, either.

The last picture I took is of the Kashmir area:

I find these faint borders difficult to interpret and I admit to not being very familiar with this conflict, but perhaps someone in the know with the patience to look more closely will email me their understanding of the official British Airways position on the Kashmir conflict (here’s the full sized picture).

Here are some other details I noted as I browsed the map:

• The Hala’ib Triangle and Bir Tawil are shown with dotted lines
• The Gulf of Mexico is labelled as such
• Antarctica has no labelled borders or settlements

After this thrilling survey of the official political positions of British Airways, I spent the rest of the flight reading books or trying to sleep.

Hi nerds, I'm back from Systems Distributed! I'd heartily recommend it, wildest conference I've been to in years. I have a lot of work to catch up on, so this will be a short newsletter.

In an earlier version of my talk, I had a gag about unit tests. First I showed the test f([1,2,3]) == 3, then said that this was satisfied by f(l) = 3, f(l) = l[-1], f(l) = len(l), f(l) = (129*l[0]-34*l[1]-617)*l[2] - 443*l[0] + 1148*l[1] - 182. Then I progressively rule them out one by one with more unit tests, except the last polynomial which stubbornly passes every single test.

If you're given some function of f(x: int, y: int, …): int and a set of unit tests asserting specific inputs give specific outputs, then you can find a polynomial that passes every single unit test.

To find the gag, and as SMT practice, I wrote a Python program that finds a polynomial that passes a test suite meant for max. It's hardcoded for three parameters and only finds 2nd-order polynomials but I think it could be generalized with enough effort.

The code

Full code here, breakdown below.

from z3 import *  # type: ignore
s1, s2 = Solver(), Solver()

Z3 is just the particular SMT solver we use, as it has good language bindings and a lot of affordances.

As part of learning SMT I wanted to do this two ways. First by putting the polynomial "outside" of the SMT solver in a python function, second by doing it "natively" in Z3. I created two solvers so I could test both versions in one run.

a0, a, b, c, d, e, f = Consts('a0 a b c d e f', IntSort())
x, y, z = Ints('x y z')
t = "a*x+b*y+c*z+d*x*y+e*x*z+f*y*z+a0"

Both Const('x', IntSort()) and Int('x') do the exact same thing, the latter being syntactic sugar for the former. I did not know this when I wrote the program.

To keep the two versions in sync I represented the equation as a string, which I later eval. This is one of the rare cases where eval is a good idea, to help us experiment more quickly while learning. The polynomial is a "2nd-order polynomial", even though it doesn't have x^2 terms, as it has xy and xz terms.

lambdamax = lambda x, y, z: eval(t)

z3max = Function('z3max', IntSort(), IntSort(), IntSort(),  IntSort())
s1.add(ForAll([x, y, z], z3max(x, y, z) == eval(t)))

lambdamax is pretty straightforward: create a lambda with three parameters and eval the string. The string "a*x" then becomes the python expression a*x, a is an SMT symbol, while the x SMT symbol is shadowed by the lambda parameter. To reiterate, a terrible idea in practice, but a good way to learn faster.

z3max function is a little more complex. Function takes an identifier string and N "sorts" (roughly the same as programming types). The first N-1 sorts define the parameters of the function, while the last becomes the output. So here I assign the string identifier "z3max" to be a function with signature (int, int, int) -> int.

I can load the function into the model by specifying constraints on what z3max could be. This could either be a strict input/output, as will be done later, or a ForAll over all possible inputs. Here I just use that directly to say "for all inputs, the function should match this polynomial." But I could do more complicated constraints, like commutativity (f(x, y) == f(y, x)) or monotonicity (Implies(x < y, f(x) <= f(y))).

Note ForAll takes a list of z3 symbols to quantify over. That's the only reason we need to define x, y, z in the first place. The lambda version doesn't need them.

inputs = [(1,2,3), (4, 2, 2), (1, 1, 1), (3, 5, 4)]

for g in inputs:
    s1.add(z3max(*g) == max(*g))
    s2.add(lambdamax(*g) == max(*g))

This sets up the joke: adding constraints to each solver that the polynomial it finds must, for a fixed list of triplets, return the max of each triplet.

for s, func in [(s1, z3max), (s2, lambdamax)]:
    if s.check() == sat:
        m = s.model()
        for x, y, z in inputs:
            print(f"max([{x}, {y}, {z}]) =", m.evaluate(func(x, y, z)))
        print(f"max([x, y, z]) = {m[a]}x + {m[b]}y",
            f"+ {m[c]}z +", # linebreaks added for newsletter rendering
            f"{m[d]}xy + {m[e]}xz + {m[f]}yz + {m[a0]}\n")

Output:

max([1, 2, 3]) = 3
# etc
max([x, y, z]) = -133x + 130y + -10z + -2xy + 62xz + -46yz + 0

max([1, 2, 3]) = 3
# etc
max([x, y, z]) = -17x + 16y + 0z + 0xy + 8xz + -6yz + 0

I find that z3max (top) consistently finds larger coefficients than lambdamax does. I don't know why.

Practical Applications

Test-Driven Development recommends a strict "red-green refactor" cycle. Write a new failing test, make the new test pass, then go back and refactor. Well, the easiest way to make the new test pass would be to paste in a new polynomial, so that's what you should be doing. You can even do this all automatically: have a script read the set of test cases, pass them to the solver, and write the new polynomial to your code file. All you need to do is write the tests!

Pedagogical Notes

Writing the script took me a couple of hours. I'm sure an LLM could have whipped it all up in five minutes but I really want to learn SMT and LLMs may decrease learning retention.¹ Z3 documentation is not... great for non-academics, though, and most other SMT solvers have even worse docs. One useful trick I use regularly is to use Github code search to find code using the same APIs and study how that works. Turns out reading API-heavy code is a lot easier than writing it!

Anyway, I'm very, very slowly feeling like I'm getting the basics on how to use SMT. I don't have any practical use cases yet, but I wanted to learn this skill for a while and glad I finally did.

No newsletter next week

I’ll be speaking at Systems Distributed. My talk isn't close to done yet, which is why this newsletter is both late and short.

Solving LinkedIn Queens in SMT

The article Modern SAT solvers: fast, neat and underused claims that SAT solvers¹ are "criminally underused by the industry". A while back on the newsletter I asked "why": how come they're so powerful and yet nobody uses them? Many experts responded saying the reason is that encoding SAT kinda sucked and they rather prefer using tools that compile to SAT.

I was reminded of this when I read Ryan Berger's post on solving “LinkedIn Queens” as a SAT problem.

A quick overview of Queens. You’re presented with an NxN grid divided into N regions, and have to place N queens so that there is exactly one queen in each row, column, and region. While queens can be on the same diagonal, they cannot be adjacently diagonal.

(Important note: Linkedin “Queens” is a variation on the puzzle game Star Battle, which is the same except the number of stars you place in each row/column/region varies per puzzle, and is usually two. This is also why 'queens' don’t capture like chess queens.)

Ryan solved this by writing Queens as a SAT problem, expressing properties like "there is exactly one queen in row 3" as a large number of boolean clauses. Go read his post, it's pretty cool. What leapt out to me was that he used CVC5, an SMT solver.² SMT solvers are "higher-level" than SAT, capable of handling more data types than just boolean variables. It's a lot easier to solve the problem at the SMT level than at the SAT level. To show this, I whipped up a short demo of solving the same problem in Z3 (via the Python API).

Full code here, which you can compare to Ryan's SAT solution here. I didn't do a whole lot of cleanup on it (again, time crunch!), but short explanation below.

The code

from z3 import * # type: ignore
from itertools import combinations, chain, product
solver = Solver()
size = 9 # N

Initial setup and modules. size is the number of rows/columns/regions in the board, which I'll call N below.

# queens[n] = col of queen on row n
# by construction, not on same row
queens = IntVector('q', size) 

SAT represents the queen positions via N² booleans: q_00 means that a Queen is on row 0 and column 0, !q_05 means a queen isn't on row 0 col 5, etc. In SMT we can instead encode it as N integers: q_0 = 5 means that the queen on row 0 is positioned at column 5. This immediately enforces one class of constraints for us: we don't need any constraints saying "exactly one queen per row", because that's embedded in the definition of queens!

(Incidentally, using 0-based indexing for the board was a mistake on my part, it makes correctly encoding the regions later really painful.)

To actually make the variables [q_0, q_1, …], we use the Z3 affordance IntVector(str, n) for making n variables at once.

solver.add([And(0 <= i, i < size) for i in queens])
# not on same column
solver.add(Distinct(queens))

First we constrain all the integers to [0, N), then use the incredibly handy Distinct constraint to force all the integers to have different values. This guarantees at most one queen per column, which by the pigeonhole principle means there is exactly one queen per column.

# not diagonally adjacent
for i in range(size-1):
    q1, q2 = queens[i], queens[i+1]
    solver.add(Abs(q1 - q2) != 1)

One of the rules is that queens can't be adjacent. We already know that they can't be horizontally or vertically adjacent via other constraints, which leaves the diagonals. We only need to add constraints that, for each queen, there is no queen in the lower-left or lower-right corner, aka q_3 != q_2 ± 1. We don't need to check the top corners because if q_1 is in the upper-left corner of q_2, then q_2 is in the lower-right corner of q_1!

That covers everything except the "one queen per region" constraint. But the regions are the tricky part, which we should expect because we vary the difficulty of queens games by varying the regions.

regions = {
        "purple": [(0, 0), (0, 1), (0, 2), (0, 3), (0, 4), (0, 5), (0, 6), (0, 7), (0, 8),
                   (1, 0), (2, 0), (3, 0), (4, 0), (5, 0), (6, 0), (7, 0), (8, 0),
                   (1, 1), (8, 1)],
        "red": [(1, 2), (2, 2), (2, 1), (3, 1), (4, 1), (5, 1), (6, 1), (6, 2), (7, 1), (7, 2), (8, 2), (8, 3),],
        # you get the picture
        }

# Some checking code left out, see below

The region has to be manually coded in, which is a huge pain.

(In the link, some validation code follows. Since it breaks up explaining the model I put it in the next section.)

for r in regions.values():
    solver.add(Or(
        *[queens[row] == col for (row, col) in r]
        ))

Finally we have the region constraint. The easiest way I found to say "there is exactly one queen in each region" is to say "there is a queen in region 1 and a queen in region 2 and a queen in region 3" etc." Then to say "there is a queen in region purple" I wrote "q_0 = 0 OR q_0 = 1 OR … OR q_1 = 0 etc."

Why iterate over every position in the region instead of doing something like (0, q[0]) in r? I tried that but it's not an expression that Z3 supports.

if solver.check() == sat:
    m = solver.model()
    print([(l, m[l]) for l in queens])

Finally, we solve and print the positions. Running this gives me:

[(q__0, 0), (q__1, 5), (q__2, 8), 
 (q__3, 2), (q__4, 7), (q__5, 4), 
 (q__6, 1), (q__7, 3), (q__8, 6)]

Which is the correct solution to the queens puzzle. I didn't benchmark the solution times, but I imagine it's considerably slower than a raw SAT solver. Glucose is really, really fast.

But even so, solving the problem with SMT was a lot easier than solving it with SAT. That satisfies me as an explanation for why people prefer it to SAT.

Sanity checks

One bit I glossed over earlier was the sanity checking code. I knew for sure that I was going to make a mistake encoding the region, and the solver wasn't going to provide useful information abut what I did wrong. In cases like these, I like adding small tests and checks to catch mistakes early, because the solver certainly isn't going to catch them!

all_squares = set(product(range(size), repeat=2))
def test_i_set_up_problem_right():
    assert all_squares == set(chain.from_iterable(regions.values()))

    for r1, r2 in combinations(regions.values(), 2):
        assert not set(r1) & set(r2), set(r1) & set(r2)

The first check was a quick test that I didn't leave any squares out, or accidentally put the same square in both regions. Converting the values into sets makes both checks a lot easier. Honestly I don't know why I didn't just use sets from the start, sets are great.

def render_regions():
    colormap = ["purple",  "red", "brown", "white", "green", "yellow", "orange", "blue", "pink"]
    board = [[0 for _ in range(size)] for _ in range(size)] 
    for (row, col) in all_squares:
        for color, region in regions.items():
            if (row, col) in region:
                board[row][col] = colormap.index(color)+1

    for row in board:
        print("".join(map(str, row)))

render_regions()

The second check is something that prints out the regions. It produces something like this:

111111111
112333999
122439999
124437799
124666779
124467799
122467899
122555889
112258899

I can compare this to the picture of the board to make sure I got it right. I guess a more advanced solution would be to print emoji squares like 🟥 instead.

Neither check is quality code but it's throwaway and it gets the job done so eh.

Update for the Internet

This was sent as a weekly newsletter, which is usually on topics like software history, formal methods, unusual technologies, and the theory of software engineering. You can subscribe here.

New Logic for Programmers Release

v0.10 is now available! This is a minor release, mostly focused on logic-based refactoring, with new material on set types and testing refactors are correct. See the full release notes at the changelog page. Due to conference pressure v0.11 will also likely be a minor release.

AI is a gamechanger for TLA+ users

TLA+ is a specification language to model and debug distributed systems. While very powerful, it's also hard for programmers to learn, and there's always questions of connecting specifications with actual code.

That's why The Coming AI Revolution in Distributed Systems caught my interest. In the post, Cheng Huang claims that Azure successfully used LLMs to examine an existing codebase, derive a TLA+ spec, and find a production bug in that spec. "After a decade of manually crafting TLA+ specifications", he wrote, "I must acknowledge that this AI-generated specification rivals human work".

This inspired me to experiment with LLMs in TLA+ myself. My goals are a little less ambitious than Cheng's: I wanted to see how LLMs could help junior specifiers write TLA+, rather than handling the entire spec automatically. Details on what did and didn't work below, but my takeaway is that LLMs are an immense specification force multiplier.

All tests were done with a standard VSCode Copilot subscription, writing Claude 3.7 in Agent mode. Other LLMs or IDEs may be more or less effective, etc.

Things Claude was good at

Fixing syntax errors

TLA+ uses a very different syntax than mainstream programming languages, meaning beginners make a lot of mistakes where they do a "programming syntax" instead of TLA+ syntax:

NotThree(x) = \* should be ==, not =
    x != 3 \* should be #, not !=

The problem is that the TLA+ syntax checker, SANY, is 30 years old and doesn't provide good information. Here's what it says for that snippet:

Was expecting "==== or more Module body"
Encountered "NotThree" at line 6, column 1

That only isolates one error and doesn't tell us what the problem is, only where it is. Experienced TLA+ users get "error eyes" and can quickly see what the problem is, but beginners really struggle with this.

The TLA+ foundation has made LLM integration a priority, so the VSCode extension naturally supports several agents actions. One of these is running SANY, meaning an agent can get an error, fix it, get another error, fix it, etc. Provided the above sample and asked to make it work, Claude successfully fixed both errors. It also fixed many errors in a larger spec, as well as figure out why PlusCal specs weren't compiling to TLA+.

This by itself is already enough to make LLMs a worthwhile tool, as it fixes one of the biggest barriers to entry.

Understanding error traces

When TLA+ finds a violated property, it outputs the sequence of steps that leads to the error. This starts in plaintext, and VSCode parses it into an interactive table:

Learning to read these error traces is a skill in itself. You have to understand what's happening in each step and how it relates back to the actually broken property. It takes a long time for people to learn how to do this well.

Claude was successful here, too, accurately reading 20+ step error traces and giving a high-level explanation of what went wrong. It also could condense error traces: if ten steps of the error trace could be condensed into a one-sentence summary (which can happen if you're modeling a lot of process internals) Claude would do it.

I did have issues here with doing this in agent mode: while the extension does provide a "run model checker" command, the agent would regularly ignore this and prefer to run a terminal command instead. This would be fine except that the LLM consistently hallucinated invalid commands. I had to amend every prompt with "run the model checker via vscode, do not use a terminal command". You can skip this if you're willing to copy and paste the error trace into the prompt.

As with syntax checking, if this was the only thing LLMs could effectively do, that would already be enough¹ to earn a strong recommend. Even as a TLA+ expert I expect I'll be using this trick regularly.

Boilerplate tasks

TLA+ has a lot of boilerplate. One of the most notorious examples is UNCHANGED rules. Specifications are extremely precise — so precise that you have to specify what variables don't change in every step. This takes the form of an UNCHANGED clause at the end of relevant actions:

RemoveObjectFromStore(srv, o, s) ==
  /\ o \in stored[s]
  /\ stored' = [stored EXCEPT ![s] = @ \ {o}]
  /\ UNCHANGED <<capacity, log, objectsize, pc>>

Writing this is really annoying. Updating these whenever you change an action, or add a new variable to the spec, is doubly so. Syntax checking and error analysis are important for beginners, but this is what I wanted for myself. I took a spec and prompted Claude

Add UNCHANGED <> for each variable not changed in an action.

And it worked! It successfully updated the UNCHANGED in every action.

(Note, though, that it was a "well-behaved" spec in this regard: only one "action" happened at a time. In TLA+ you can have two actions happen simultaneously, that each update half of the variables, meaning neither of them should have an UNCHANGED clause. I haven't tested how Claude handles that!)

That's the most obvious win, but Claude was good at handling other tedious work, too. Some examples include updating vars (the conventional collection of all state variables), lifting a hard-coded value into a model parameter, and changing data formats. Most impressive to me, though, was rewriting a spec designed for one process to instead handle multiple processes. This means taking all of the process variables, which originally have types like Int, converting them to types like [Process -> Int], and then updating the uses of all of those variables in the spec. It didn't account for race conditions in the new concurrent behavior, but it was an excellent scaffold to do more work.

Writing properties from an informal description

You have to be pretty precise with your intended property description but it handles converting that precise description into TLA+'s formalized syntax, which is something beginners often struggle with.

Things it is less good at

Generating model config files

To model check TLA+, you need both a specification (.tla) and a model config file (.cfg), which have separate syntaxes. Asking the agent to generate the second often lead to it using TLA+ syntax. It automatically fixed this after getting parsing errors, though.

Fixing specs

Whenever the ran model checking and discovered a bug, it would naturally propose a change to either the invalid property or the spec. Sometimes the changes were good, other times the changes were not physically realizable. For example, if it found that a bug was due to a race condition between processes, it would often suggest fixing it by saying race conditions were okay. I mean yes, if you say bugs are okay, then the spec finds that bugs are okay! Or it would alternatively suggest adding a constraint to the spec saying that race conditions don't happen. But that's a huge mistake in specification, because race conditions happen if we don't have coordination. We need to specify the mechanism that is supposed to prevent them.

Finding properties of the spec

After seeing how capable it was at translating my properties to TLA+, I started prompting Claude to come up with properties on its own. Unfortunately, almost everything I got back was either trivial, uninteresting, or too coupled to implementation details. I haven't tested if it would work better to ask it for "properties that may be violated".

Generating code from specs

I have to be specific here: Claude could sometimes convert Python into a passable spec, an vice versa. It wasn't good at recognizing abstraction. For example, TLA+ specifications often represent sequential operations with a state variable, commonly called pc. If modeling code that nonatomically retrieves a counter value and increments it, we'd have one action that requires pc = "Get" and sets the new value to "Inc", then another that requires it be "Inc" and sets it to "Done".

I found that Claude would try to somehow convert pc into part of the Python program's state, rather than recognize it as a TLA+ abstraction. On the other side, when converting python code to TLA+ it would often try to translate things like sleep into some part of the spec, not recognizing that it is abstractable into a distinct action. I didn't test other possible misconceptions, like converting randomness to nondeterminism.

For the record, when converting TLA+ to Python Claude tended to make simulators of the spec, rather than possible production code implementing the spec. I really wasn't expecting otherwise though.

Unexplored Applications

Things I haven't explored thoroughly but could possibly be effective, based on what I know about TLA+ and AI:

Writing Java Overrides

Most TLA+ operators are resolved via TLA+ interpreters, but you can also implement them in "native" Java. This lets you escape the standard language semantics and add capabilities like executing programs during model-checking or dynamically constrain the depth of the searched state space. There's a lot of cool things I think would be possible with overrides. The problem is there's only a handful of people in the world who know how to write them. But that handful have written quite a few overrides and I think there's enough there for Claude to work with.

Writing specs, given a reference mechanism

In all my experiments, the LLM only had my prompts and the occasional Python script as information. That makes me suspect that some of its problems with writing and fixing specs come down to not having a system model. Maybe it wouldn't suggest fixes like "these processes never race" if it had a design doc saying that the processes can't coordinate.

(Could a Sufficiently Powerful LLM derive some TLA+ specification from a design document?)

Connecting specs and code

This is the holy grail of TLA+: taking a codebase and showing it correctly implements a spec. Currently the best ways to do this are by either using TLA+ to generate a test suite, or by taking logged production traces and matching them to TLA+ behaviors. This blog post discusses both. While I've seen a lot of academic research into these approaches there are no industry-ready tools. So if you want trace validation you have to do a lot of manual labour tailored to your specific product.

If LLMs could do some of this work for us then that'd really amplify the usefulness of TLA+ to many companies.

Thoughts

Right now, agents seem good at the tedious and routine parts of TLA+ and worse at the strategic and abstraction parts. But, since the routine parts are often a huge barrier to beginners, this means that LLMs have the potential to make TLA+ far, far more accessible than it previously was.

I have mixed thoughts on this. As an advocate, this is incredible. I want more people using formal specifications because I believe it leads to cheaper, safer, more reliable software. Anything that gets people comfortable with specs is great for our industry. As a professional TLA+ consultant, I'm worried that this obsoletes me. Most of my income comes from training and coaching, which companies will have far less demand of now. Then again, maybe this an opportunity to pitch "agentic TLA+ training" to companies!

Anyway, if you're interested in TLA+, there has never been a better time to try it. I mean it, these tools handle so much of the hard part now. I've got a free book available online, as does the inventor of TLA+. I like this guide too. Happy modeling!

Systems Distributed

I'll be speaking at Systems Distributed next month! The talk is brand new and will aim to showcase some of the formal methods mental models that would be useful in mainstream software development. It has added some extra stress on my schedule, though, so expect the next two monthly releases of Logic for Programmers to be mostly minor changes.

What does "Undecidable" mean, anyway

Last week I read Against Curry-Howard Mysticism, which is a solid article I recommend reading. But this newsletter is actually about one comment:

I like to see posts like this because I often feel like I can’t tell the difference between BS and a point I’m missing. Can we get one for questions like “Isn’t XYZ (Undecidable|NP-Complete|PSPACE-Complete)?”

I've already written one of these for NP-complete, so let's do one for "undecidable". Step one is to pull a technical definition from the book Automata and Computability:

A property P of strings is said to be decidable if ... there is a total Turing machine that accepts input strings that have property P and rejects those that do not. (pg 220)

Step two is to translate the technical computer science definition into more conventional programmer terms. Warning, because this is a newsletter and not a blog post, I might be a little sloppy with terms.

Machines and Decision Problems

In automata theory, all inputs to a "program" are strings of characters, and all outputs are "true" or "false". A program "accepts" a string if it outputs "true", and "rejects" if it outputs "false". You can think of this as automata studying all pure functions of type f :: string -> boolean. Problems solvable by finding such an f are called "decision problems".

This covers more than you'd think, because we can bootstrap more powerful functions from these. First, as anyone who's programmed in bash knows, strings can represent any other data. Second, we can fake non-boolean outputs by instead checking if a certain computation gives a certain result. For example, I can reframe the function add(x, y) = x + y as a decision problem like this:

IS_SUM(str) {
    x, y, z = split(str, "#")
    return x + y == z
}

Then because IS_SUM("2#3#5") returns true, we know 2 + 3 == 5, while IS_SUM("2#3#6") is false. Since we can bootstrap parameters out of strings, I'll just say it's IS_SUM(x, y, z) going forward.

A big part of automata theory is studying different models of computation with different strengths. One of the weakest is called "DFA". I won't go into any details about what DFA actually can do, but the important thing is that it can't solve IS_SUM. That is, if you give me a DFA that takes inputs of form x#y#z, I can always find an input where the DFA returns true when x + y != z, or an input which returns false when x + y == z.

It's really important to keep this model of "solve" in mind: a program solves a problem if it correctly returns true on all true inputs and correctly returns false on all false inputs.

(total) Turing Machines

A Turing Machine (TM) is a particular type of computation model. It's important for two reasons:

1. By the Church-Turing thesis, a Turing Machine is the "upper bound" of how powerful (physically realizable) computational models can get. This means that if an actual real-world programming language can solve a particular decision problem, so can a TM. Conversely, if the TM can't solve it, neither can the programming language.¹

2. It's possible to write a Turing machine that takes a textual representation of another Turing machine as input, and then simulates that Turing machine as part of its computations.

Property (1) means that we can move between different computational models of equal strength, proving things about one to learn things about another. That's why I'm able to write IS_SUM in a pseudocode instead of writing it in terms of the TM computational model (and why I was able to use split for convenience).

Property (2) does several interesting things. First of all, it makes it possible to compose Turing machines. Here's how I can roughly ask if a given number is the sum of two primes, with "just" addition and boolean functions:

IS_SUM_TWO_PRIMES(z):
    x := 1
    y := 1
    loop {
        if x > z {return false}
        if IS_PRIME(x) {
            if IS_PRIME(y) {
                if IS_SUM(x, y, z) {
                    return true;
                }
            }
        }
        y := y + 1
        if y > x {
            x := x + 1
            y := 0
        }
    }

Notice that without the if x > z {return false}, the program would loop forever on z=2. A TM that always halts for all inputs is called total.

Property (2) also makes "Turing machines" a possible input to functions, meaning that we can now make decision problems about the behavior of Turing machines. For example, "does the TM M either accept or reject x within ten steps?"²

IS_DONE_IN_TEN_STEPS(M, x) {
    for (i = 0; i < 10; i++) {
        `simulate M(x) for one step`
        if(`M accepted or rejected`) {
            return true
        }
    }
    return false
}

Decidability and Undecidability

Now we have all of the pieces to understand our original definition:

A property P of strings is said to be decidable if ... there is a total Turing machine that accepts input strings that have property P and rejects those that do not. (220)

Let IS_P be the decision problem "Does the input satisfy P"? Then IS_P is decidable if it can be solved by a Turing machine, ie, I can provide some IS_P(x) machine that always accepts if x has property P, and always rejects if x doesn't have property P. If I can't do that, then IS_P is undecidable.

IS_SUM(x, y, z) and IS_DONE_IN_TEN_STEPS(M, x) are decidable properties. Is IS_SUM_TWO_PRIMES(z) decidable? Some analysis shows that our corresponding program will either find a solution, or have x>z and return false. So yes, it is decidable.

Notice there's an asymmetry here. To prove some property is decidable, I need just to need to find one program that correctly solves it. To prove some property is undecidable, I need to show that any possible program, no matter what it is, doesn't solve it.

So with that asymmetry in mind, do are there any undecidable problems? Yes, quite a lot. Recall that Turing machines can accept encodings of other TMs as input, meaning we can write a TM that checks properties of Turing machines. And, by Rice's Theorem, almost every nontrivial semantic³ property of Turing machines is undecidable. The conventional way to prove this is to first find a single undecidable property H, and then use that to bootstrap undecidability of other properties.

The canonical and most famous example of an undecidable problem is the Halting problem: "does machine M halt on input i?" It's pretty easy to prove undecidable, and easy to use it to bootstrap other undecidability properties. But again, any nontrivial property is undecidable. Checking a TM is total is undecidable. Checking a TM accepts any inputs is undecidable. Checking a TM solves IS_SUM is undecidable. Etc etc etc.

What this doesn't mean in practice

I often see the halting problem misconstrued as "it's impossible to tell if a program will halt before running it." This is wrong. The halting problem says that we cannot create an algorithm that, when applied to an arbitrary program, tells us whether the program will halt or not. It is absolutely possible to tell if many programs will halt or not. It's possible to find entire subcategories of programs that are guaranteed to halt. It's possible to say "a program constructed following constraints XYZ is guaranteed to halt."

The actual consequence of undecidability is more subtle. If we want to know if a program has property P, undecidability tells us

1. We will have to spend time and mental effort to determine if it has P
2. We may not be successful.

This is subtle because we're so used to living in a world where everything's undecidable that we don't really consider what the counterfactual would be like. In such a world there might be no need for Rust, because "does this C program guarantee memory-safety" is a decidable property. The entire field of formal verification could be unnecessary, as we could just check properties of arbitrary programs directly. We could automatically check if a change in a program preserves all existing behavior. Lots of famous math problems could be solved overnight.

(This to me is a strong "intuitive" argument for why the halting problem is undecidable: a halt detector can be trivially repurposed as a program optimizer / theorem-prover / bcrypt cracker / chess engine. It's too powerful, so we should expect it to be impossible.)

But because we don't live in that world, all of those things are hard problems that take effort and ingenuity to solve, and even then we often fail.

Update for the Internet

This was sent as a weekly newsletter, which is usually on topics like software history, formal methods, unusual technologies, and the theory of software engineering. You can subscribe here.

Planner programming is a programming technique where you solve problems by providing a goal and actions, and letting the planner find actions that reach the goal. In a previous edition of Logic for Programmers, I demonstrated how this worked by solving the 24 puzzle with planning. For reasons discussed here I replaced that example with something more practical (orchestrating deployments), but left the code online for posterity.

Recently I saw a family member try and fail to vibe code a tool that would find all valid 24 puzzles, and realized I could adapt the puzzle solver to also be a puzzle generator. First I'll explain the puzzle rules, then the original solver, then the generator.¹ For a much longer intro to planning, see here.

The rules of 24

You're given four numbers and have to find some elementary equation (+-*/+groupings) that uses all four numbers and results in 24. Each number must be used exactly once, but do not need to be used in the starting puzzle order. Some examples:

• [6, 6, 6, 6] -> 6+6+6+6=24
• [1, 1, 6, 6] -> (6+6)*(1+1)=24
• [4, 4, 4, 5] -> 4*(5+4/4)=24

Some setups are impossible, like [1, 1, 1, 1]. Others are possible only with non-elementary operations, like [1, 5, 5, 324] (which requires exponentiation).

The solver

We will use the Picat, the only language that I know has a built-in planner module. The current state of our plan with be represented by a single list with all of the numbers.

import planner, math.
import cp.

action(S0, S1, Action, Cost) ?=>
  member(X, S0)
  , S0 := delete(S0, X) % , is `and`
  , member(Y, S0)
  , S0 := delete(S0, Y)
  , (
      A = $(X + Y) 
    ; A = $(X - Y)
    ; A = $(X * Y)
    ; A = $(X / Y), Y > 0
    )
    , S1 = S0 ++ [apply(A)]
  , Action = A
  , Cost = 1
  .

This is our "action", and it works in three steps:

1. Nondeterministically pull two different values out of the input, deleting them
2. Nondeterministically pick one of the basic operations
3. The new state is the remaining elements, appended with that operation applied to our two picks.

Let's walk through this with [1, 6, 1, 7]. There are four choices for X and three four Y. If the planner chooses X=6 and Y=7, A = $(6 + 7). This is an uncomputed term in the same way lisps might use quotation. We can resolve the computation with apply, as in the line S1 = S0 ++ [apply(A)].

final([N]) =>
  N =:= 24. % handle floating point

Our final goal is just a list where the only element is 24. This has to be a little floating point-sensitive to handle floating point divison, done by =:=.

main =>
  Start = [1, 5, 5, 6]
  , best_plan(Start, 4, Plan)
  , printf("%w %w%n", Start, Plan)
  .

For main, we just find the best plan with the maximum cost of 4 and print it. When run from the command line, picat automatically executes whatever is in main.

$ picat 24.pi
[1,5,5,6] [1 + 5,5 * 6,30 - 6]

I don't want to spoil any more 24 puzzles, so let's stop showing the plan:

main =>
- , printf("%w %w%n", Start, Plan)
+ , printf("%w%n", Start)

Generating puzzles

Picat provides a find_all(X, p(X)) function, which ruturns all X for which p(X) is true. In theory, we could write find_all(S, best_plan(S, 4, _). In practice, there are an infinite number of valid puzzles, so we need to bound S somewhat. We also don't want to find any redundant puzzles, such as [6, 6, 6, 4] and [4, 6, 6, 6].

We can solve both issues by writing a helper valid24(S), which will check that S a sorted list of integers within some bounds, like 1..8, and also has a valid solution.

valid24(Start) =>
  Start = new_list(4)
  , Start :: 1..8 % every value in 1..8
  , increasing(Start) % sorted ascending
  , solve(Start) % turn into values
  , best_plan(Start, 4, Plan)
  .

This leans on Picat's constraint solving features to automatically find bounded sorted lists, which is why we need the solve step.² Now we can just loop through all of the values in find_all to get all solutions:

main =>
  foreach([S] in find_all(
    [Start],
    valid24(Start)))
    printf("%w%n", S)
  end.

$ picat 24.pi

[1,1,1,8]
[1,1,2,6]
[1,1,2,7]
[1,1,2,8]
# etc

Finding hard puzzles

Last Friday I realized I could do something more interesting with this. Once I have found a plan, I can apply further constraints to the plan, for example to find problems that can be solved with division:

valid24(Start, Plan) =>
  Start = new_list(4)
  , Start :: 1..8
  , increasing(Start)
  , solve(Start)
  , best_plan(Start, 4, Plan)
+ , member($(_ / _), Plan)
  .

In playing with this, though, I noticed something weird: there are some solutions that appear if I sort up but not down. For example, [3,3,4,5] appears in the solution set, but [5, 4, 3, 3] doesn't appear if I replace increasing with decreasing.

As far as I can tell, this is because Picat only finds one best plan, and [5, 4, 3, 3] has two solutions: 4*(5-3/3) and 3*(5+4)-3. best_plan is a deterministic operator, so Picat commits to the first best plan it finds. So if it finds 3*(5+4)-3 first, it sees that the solution doesn't contain a division, throws [5, 4, 3, 3] away as a candidate, and moves on to the next puzzle.

There's a couple ways we can fix this. We could replace best_plan with best_plan_nondet, which can backtrack to find new plans (at the cost of an enormous number of duplicates). Or we could modify our final to only accept plans with a division:

% Hypothetical change
final([N]) =>
+ member($(_ / _), current_plan()),
  N =:= 24.

My favorite "fix" is to ask another question entirely. While I was looking for puzzles that can be solved with division, what I actually want is puzzles that must be solved with division. What if I rejected any puzzle that has a solution without division?

+ plan_with_no_div(S, P) => best_plan_nondet(S, 4, P), not member($(_ / _), P).

valid24(Start, Plan) =>
  Start = new_list(4)
  , Start :: 1..8
  , increasing(Start)
  , solve(Start)
  , best_plan(Start, 4, Plan)
- , member($(_ / _), Plan)
+ , not plan_with_no_div(Start, _)
  .

The new line's a bit tricky. plan_with_div nondeterministically finds a plan, and then fails if the plan contains a division.³ Since I used best_plan_nondet, it can backtrack from there and find a new plan. This means plan_with_no_div only fails if not such plan exists. And in valid24, we only succeed if plan_with_no_div fails, guaranteeing that the only existing plans use division. Since this doesn't depend on the plan found via best_plan, it doesn't matter how the values in Start are arranged, this will not miss any valid puzzles.

Aside for my logic book readers

The new clause is equivalent to !(some p: Plan(p) && !(div in p)). Applying the simplifications we learned:

1. !(some p: Plan(p) && !(div in p)) (init)
2. all p: !(plan(p) && !(div in p)) (all/some duality)
3. all p: !plan(p) || div in p) (De Morgan's law)
4. all p: plan(p) => div in p (implication definition)

Which more obviously means "if P is a valid plan, then it contains a division".

Back to finding hard puzzles

Anyway, with not plan_with_no_div, we are filtering puzzles on the set of possible solutions, not just specific solutions. And this gives me an idea: what if we find puzzles that have only one solution?

different_plan(S, P) => best_plan_nondet(S, 4, P2), P2 != P.

valid24(Start, Plan) =>
+ , not different_plan(Start, Plan)

I tried this from 1..8 and got:

[1,2,7,7]
[1,3,4,6]
[1,6,6,8]
[3,3,8,8]

These happen to be some of the hardest 24 puzzles known, though not all of them. Note this is assuming that (X + Y) and (Y + X) are different solutions. If we say they're the same (by appending writing A = $(X + Y), X <= Y in our action) then we got a lot more puzzles, many of which are considered "easy". Other "hard" things we can look for include plans that require fractions:

plan_with_no_fractions(S, P) => 
  best_plan_nondet(S, 4, P)
  , not(
    member(X, P),
    round(apply(X)) =\= X
  ).

% insert `not plan...` in valid24 as usual

Finally, we could try seeing if a negative number is required:

plan_with_no_negatives(S, P) => 
  best_plan_nondet(S, 4, P)
  , not(
    member(X, P),
    apply(X) < 0
  ).

Interestingly this one returns no solutions, so you are never required to construct a negative number as part of a standard 24 puzzle.

You're walking down the street and need to pass someone going the opposite way. You take a step left, but they're thinking the same thing and take a step to their right, aka your left. You're still blocking each other. Then you take a step to the right, and they take a step to their left, and you're back to where you started. I've heard this called "walkwarding"

Let's model this in TLA+. TLA+ is a formal methods tool for finding bugs in complex software designs, most often involving concurrency. Two people trying to get past each other just also happens to be a concurrent system. A gentler introduction to TLA+'s capabilities is here, an in-depth guide teaching the language is here.

The spec

---- MODULE walkward ----
EXTENDS Integers

VARIABLES pos
vars == <<pos>>

Double equals defines a new operator, single equals is an equality check. <<pos>> is a sequence, aka array.

you == "you"
me == "me"
People == {you, me}

MaxPlace == 4

left == 0
right == 1

I've gotten into the habit of assigning string "symbols" to operators so that the compiler complains if I misspelled something. left and right are numbers so we can shift position with right - pos.

direction == [you |-> 1, me |-> -1]
goal == [you |-> MaxPlace, me |-> 1]

Init ==
  \* left-right, forward-backward
  pos = [you |-> [lr |-> left, fb |-> 1], me |-> [lr |-> left, fb |-> MaxPlace]]

direction, goal, and pos are "records", or hash tables with string keys. I can get my left-right position with pos.me.lr or pos["me"]["lr"] (or pos[me].lr, as me == "me").

Juke(person) ==
  pos' = [pos EXCEPT ![person].lr = right - @]

TLA+ breaks the world into a sequence of steps. In each step, pos is the value of pos in the current step and pos' is the value in the next step. The main outcome of this semantics is that we "assign" a new value to pos by declaring pos' equal to something. But the semantics also open up lots of cool tricks, like swapping two values with x' = y /\ y' = x.

TLA+ is a little weird about updating functions. To set f[x] = 3, you gotta write f' = [f EXCEPT ![x] = 3]. To make things a little easier, the rhs of a function update can contain @ for the old value. ![me].lr = right - @ is the same as right - pos[me].lr, so it swaps left and right.

("Juke" comes from here)

Move(person) ==
  LET new_pos == [pos[person] EXCEPT !.fb = @ + direction[person]]
  IN
    /\ pos[person].fb # goal[person]
    /\ \A p \in People: pos[p] # new_pos
    /\ pos' = [pos EXCEPT ![person] = new_pos]

The EXCEPT syntax can be used in regular definitions, too. This lets someone move one step in their goal direction unless they are at the goal or someone is already in that space. /\ means "and".

Next ==
  \E p \in People:
    \/ Move(p)
    \/ Juke(p)

I really like how TLA+ represents concurrency: "In each step, there is a person who either moves or jukes." It can take a few uses to really wrap your head around but it can express extraordinarily complicated distributed systems.

Spec == Init /\ [][Next]_vars

Liveness == <>(pos[me].fb = goal[me])
====

Spec is our specification: we start at Init and take a Next step every step.

Liveness is the generic term for "something good is guaranteed to happen", see here for more. <> means "eventually", so Liveness means "eventually my forward-backward position will be my goal". I could extend it to "both of us eventually reach out goal" but I think this is good enough for a demo.

Checking the spec

Four years ago, everybody in TLA+ used the toolbox. Now the community has collectively shifted over to using the VSCode extension.¹ VSCode requires we write a configuration file, which I will call walkward.cfg.

SPECIFICATION Spec
PROPERTY Liveness

I then check the model with the VSCode command TLA+: Check model with TLC. Unsurprisingly, it finds an error:

The reason it fails is "stuttering": I can get one step away from my goal and then just stop moving forever. We say the spec is unfair: it does not guarantee that if progress is always possible, progress will be made. If I want the spec to always make progress, I have to make some of the steps weakly fair.

+ Fairness == WF_vars(Next)

- Spec == Init /\ [][Next]_vars
+ Spec == Init /\ [][Next]_vars /\ Fairness

Now the spec is weakly fair, so someone will always do something. New error:

\* First six steps cut
7: <Move("me")>
pos = [you |-> [lr |-> 0, fb |-> 4], me |-> [lr |-> 1, fb |-> 2]]
8: <Juke("me")>
pos = [you |-> [lr |-> 0, fb |-> 4], me |-> [lr |-> 0, fb |-> 2]]
9: <Juke("me")> (back to state 7)

In this failure, I've successfully gotten past you, and then spend the rest of my life endlessly juking back and forth. The Next step keeps happening, so weak fairness is satisfied. What I actually want is for both my Move and my Juke to both be weakly fair independently of each other.

- Fairness == WF_vars(Next)
+ Fairness == WF_vars(Move(me)) /\ WF_vars(Juke(me))

If my liveness property also specified that you reached your goal, I could instead write \A p \in People: WF_vars(Move(p)) etc. I could also swap the \A with a \E to mean at least one of us is guaranteed to have fair actions, but not necessarily both of us.

New error:

3: <Move("me")>
pos = [you |-> [lr |-> 0, fb |-> 2], me |-> [lr |-> 0, fb |-> 3]]
4: <Juke("you")>
pos = [you |-> [lr |-> 1, fb |-> 2], me |-> [lr |-> 0, fb |-> 3]]
5: <Juke("me")>
pos = [you |-> [lr |-> 1, fb |-> 2], me |-> [lr |-> 1, fb |-> 3]]
6: <Juke("me")>
pos = [you |-> [lr |-> 1, fb |-> 2], me |-> [lr |-> 0, fb |-> 3]]
7: <Juke("you")> (back to state 3)

Now we're getting somewhere! This is the original walkwarding situation we wanted to capture. We're in each others way, then you juke, but before either of us can move you juke, then we both juke back. We can repeat this forever, trapped in a social hell.

Wait, but doesn't WF(Move(me)) guarantee I will eventually move? Yes, but only if a move is permanently available. In this case, it's not permanently available, because every couple of steps it's made temporarily unavailable.

How do I fix this? I can't add a rule saying that we only juke if we're blocked, because the whole point of walkwarding is that we're not coordinated. In the real world, walkwarding can go on for agonizing seconds. What I can do instead is say that Liveness holds as long as Move is strongly fair. Unlike weak fairness, strong fairness guarantees something happens if it keeps becoming possible, even with interruptions.

Liveness == 
+  SF_vars(Move(me)) => 
    <>(pos[me].fb = goal[me])

This makes the spec pass. Even if we weave back and forth for five minutes, as long as we eventually pass each other, I will reach my goal. Note we could also by making Move in Fairness strongly fair, which is preferable if we have a lot of different liveness properties to check.

A small exercise for the reader

There is a presumed invariant that is violated. Identify what it is, write it as a property in TLA+, and show the spec violates it. Then fix it.

Answer (in rot13): Gur vainevnag vf "ab gjb crbcyr ner va gur rknpg fnzr ybpngvba". Zbir thnenagrrf guvf ohg Whxr qbrf abg.

More TLA+ Exercises

I've started work on an exercises repo. There's only a handful of specific problems now but I'm planning on adding more over the summer.

I started writing this early last week but Real Life Stuff happened and now you're getting the first-draft late this week. Warning, unedited thoughts ahead!

New Logic for Programmers release!

v0.9 is out! This is a big release, with a new cover design, several rewritten chapters, online code samples and much more. See the full release notes at the changelog page, and get the book here!

Write the cleverest code you possibly can

There are millions of articles online about how programmers should not write "clever" code, and instead write simple, maintainable code that everybody understands. Sometimes the example of "clever" code looks like this (src):

# Python

p=n=1
exec("p*=n*n;n+=1;"*~-int(input()))
print(p%n)

This is code-golfing, the sport of writing the most concise code possible. Obviously you shouldn't run this in production for the same reason you shouldn't eat dinner off a Rembrandt.

Other times the example looks like this:

def is_prime(x):
    if x == 1:
        return False
    return all([x%n != 0 for n in range(2, x)])

This is "clever" because it uses a single list comprehension, as opposed to a "simple" for loop. Yes, "list comprehensions are too clever" is something I've read in one of these articles.

I've also talked to people who think that datatypes besides lists and hashmaps are too clever to use, that most optimizations are too clever to bother with, and even that functions and classes are too clever and code should be a linear script.¹. Clever code is anything using features or domain concepts we don't understand. Something that seems unbearably clever to me might be utterly mundane for you, and vice versa.

How do we make something utterly mundane? By using it and working at the boundaries of our skills. Almost everything I'm "good at" comes from banging my head against it more than is healthy. That suggests a really good reason to write clever code: it's an excellent form of purposeful practice. Writing clever code forces us to code outside of our comfort zone, developing our skills as software engineers.

Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you [will get excellent debugging practice at exactly the right level required to push your skills as a software engineer] — Brian Kernighan, probably

There are other benefits, too, but first let's kill the elephant in the room:²

Don't commit clever code

I am proposing writing clever code as a means of practice. Being at work is a job with coworkers who will not appreciate if your code is too clever. Similarly, don't use too many innovative technologies. Don't put anything in production you are uncomfortable with.

We can still responsibly write clever code at work, though:

1. Solve a problem in both a simple and a clever way, and then only commit the simple way. This works well for small scale problems where trying the "clever way" only takes a few minutes.
2. Write our personal tools cleverly. I'm a big believer of the idea that most programmers would benefit from writing more scripts and support code customized to their particular work environment. This is a great place to practice new techniques, languages, etc.
3. If clever code is absolutely the best way to solve a problem, then commit it with extensive documentation explaining how it works and why it's preferable to simpler solutions. Bonus: this potentially helps the whole team upskill.

Writing clever code...

...teaches simple solutions

Usually, code that's called too clever composes several powerful features together — the "not a single list comprehension or function" people are the exception. Josh Comeau's "don't write clever code" article gives this example of "too clever":

const extractDataFromResponse = (response) => {
  const [Component, props] = response;

  const resultsEntries = Object.entries({ Component, props });
  const assignIfValueTruthy = (o, [k, v]) => (v
    ? { ...o, [k]: v }
    : o
  );

  return resultsEntries.reduce(assignIfValueTruthy, {});
}

What makes this "clever"? I count eight language features composed together: entries, argument unpacking, implicit objects, splats, ternaries, higher-order functions, and reductions. Would code that used only one or two of these features still be "clever"? I don't think so. These features exist for a reason, and oftentimes they make code simpler than not using them.

We can, of course, learn these features one at a time. Writing the clever version (but not committing it) gives us practice with all eight at once and also with how they compose together. That knowledge comes in handy when we want to apply a single one of the ideas.

I've recently had to do a bit of pandas for a project. Whenever I have to do a new analysis, I try to write it as a single chain of transformations, and then as a more balanced set of updates.

...helps us master concepts

Even if the composite parts of a "clever" solution aren't by themselves useful, it still makes us better at the overall language, and that's inherently valuable. A few years ago I wrote Crimes with Python's Pattern Matching. It involves writing horrible code like this:

from abc import ABC

class NotIterable(ABC):

    @classmethod
    def __subclasshook__(cls, C):
        return not hasattr(C, "__iter__")

def f(x):
    match x:
        case NotIterable():
            print(f"{x} is not iterable")
        case _:
            print(f"{x} is iterable")

if __name__ == "__main__":
    f(10)
    f("string")
    f([1, 2, 3])

This composes Python match statements, which are broadly useful, and abstract base classes, which are incredibly niche. But even if I never use ABCs in real production code, it helped me understand Python's match semantics and Method Resolution Order better.

...prepares us for necessity

Sometimes the clever way is the only way. Maybe we need something faster than the simplest solution. Maybe we are working with constrained tools or frameworks that demand cleverness. Peter Norvig argued that design patterns compensate for missing language features. I'd argue that cleverness is another means of compensating: if our tools don't have an easy way to do something, we need to find a clever way.

You see this a lot in formal methods like TLA+. Need to check a hyperproperty? Cast your state space to a directed graph. Need to compose ten specifications together? Combine refinements with state machines. Most difficult problems have a "clever" solution. The real problem is that clever solutions have a skill floor. If normal use of the tool is at difficult 3 out of 10, then basic clever solutions are at 5 out of 10, and it's hard to jump those two steps in the moment you need the cleverness.

But if you've practiced with writing overly clever code, you're used to working at a 7 out of 10 level in short bursts, and then you can "drop down" to 5/10. I don't know if that makes too much sense, but I see it happen a lot in practice.

...builds comradery

On a few occasions, after getting a pull request merged, I pulled the reviewer over and said "check out this horrible way of doing the same thing". I find that as long as people know they're not going to be subjected to a clever solution in production, they enjoy seeing it!

Next week's newsletter will probably also be late, after that we should be back to a regular schedule for the rest of the summer.

Video overview

Overview: LAPP, as part of the ESCAPE Collaboration work programme, and in collaboration with the CC-FR Competence Centre is organizing the third Gray Scott summer school from 23 June to 4 July 2025. This summer school on High Performance Computing, in a unique format and entirely free of charge, will be dedicated to programming and optimization on Heterogeneous Architectures.

The school will cover the optimisation of computations on different types of hardware (CPU, GPU), presenting their respective characteristics, architectures and bottlenecks. It will cover generic optimisation methods applicable to all types of hardware, as well as the various libraries, technologies and languages available to achieve the best possible performance. Ideally, the peak performance of the machine.

• Hardware: CPU, GPU
• Languages considered: C++17, C++20, CUDA, Fortran, Rust, Python, Julia
• Libraries considered: SYCL, Eve, Numpy, cunumerics, legate, Jax, Thrust, cuPy, pycuda and PyTorch
• Compilers considered: G++, Clang++, nvc++, gfortran, nvfortran, dpc++. 
• Profiling tools: Valgrind, Maqao, Perf, NSight, Malt and NumaProf

All the methods will be illustrated on simple examples, such as Hadamard products, reductions, barycentre calculations and matrix products, in order to be applied to a single problem: the simulation of a Gray Scott reaction.

This problem is simple enough to be understood quickly and complex enough for compilers to have difficulty optimising it without help. Each method will be broken down into a simple version, using default options, and one or more advanced versions, which will allow their advantages and disadvantages to be discussed and quantified.

How to attend the Gray Scott School 2025:

NCC Slovenia is offering a distance learning in Ljubljana, where one of the various satellites in Europe will take place.

The satellite will take place in hybrid format - the speakers will be present in France, and will stream via Zoom. Our lecturers will be in the room to help participants with access and implementation. At the same time, there will be a discord next to it, where the discussion will take place. 

Date and location:

• 23.6., 24.6., 26.6 - 4.7.2025 Faculty of Mechanical Engineering, Aškerčeva c. 6, (Room II/3B)
• 25. 6. 2025 IJS - Teslova ulica 30, 1000 Ljubljana,  

Overview: Together with NVIDIA and OpenACC organization, EuroCC2 will host a virtual Profiling AI Software Bootcamp on July 10, 2025.

The Profiling AI Software Bootcamp covers the process and tools needed to profile AI and machine learning applications to fully utilize high-performance systems. Attendees will learn to profile applications using NVIDIA Nsight™ Systems, a system-wide performance analysis tool; analyze and identify optimization opportunities; and improve performance of applications to scale efficiently across systems of any quantity or size of CPUs and GPUs. Additionally, this bootcamp will walk through the system topology to learn the dynamics of multi-GPU and multi-node connections and architecture.

People who complete the bootcamp are encouraged to apply to participate in the upcoming EuroCC AI Hackathon, which will be open for applications shortly.

Due to EuroCC2 regulations, generic or private email addresses cannot be accepted. Please use your official university or company email address to prove your affiliation when applying.

Application Deadline: 16th June 2025

Prerequisites: Basic experience with Python programming and PyTorch distributed training. 

Event format: This bootcamp will be hosted online in Central European Summer Time (CEST). All communication will be through Zoom, Slack and email.

Compute Resources: Attendees will be given access to a GPU cluster for the duration of the bootcamp. 

Description: In the three-day course, the use of the OpenFOAM software package, which is currently the most developed open-source CFD system, will be demonstrated. As the name itself suggests, it is an open-source system that any user can enhance according to their needs. Initially, the use of ParaVIEW, a graphical environment for visually reviewing and processing data from OpenFOAM, will be shown. This will be followed by an explanation of how the OpenFOAM environment, with demonstrations of simple examples. Since the foundation of CFD is the mesh, the use of three open-source mesh generators will be demonstrated: GMSH, BlockMesh, and SnappyHexMesh. Subsequently, the application of various areas within the OpenFOAM environment will be explained and demonstrated, including:

• Fluid transport
• Transient simulations
• Transient data processing (animation, particles in flow)
• Multiphase flows
• Multi-region simulation (Multi-region)
• Running cases in an HPC system utilizing OpenFOAM's parallel capabilities
  
  

Difficulty: Advanced

Language: According to applications

Date and time:  16. 06. 2025 from: 9:00 - 13.00 
                            17. 06. 2025 from: 9:00 - 13:00
                            18. 06. 2025 from: 9:00 - 13.00

Max. number of participants: 30

Virtual location: ZOOM

Prerequisite knowledge: The basics of the Linux operating system and the basics of fluid mechanics and Python programming.

Target audience: The training is aimed at students and staff in academia and industry who want to learn more about the OpenFOAM open source CFD platform.

Workflow: The training is on-line, in the mornings. The interactive work is done via remote access to the HPC system at ULFS. 

After the workshop you wil:

• Be able to connect to HPC@ULFS with NoMachine client and work in HPC Linux environment
• Understand the theoretical background of the Computational Fluid Mechanics (CFD), especially of the Finite Volume Method (FVM)
• Be able to set up CFD mesh using different open source programs for CFD mesh design (OF – Block Mesh, GMSH)
• Be able to setup complete OF case (mesh, pysical model, inital and boundary conditions, ...)
• Be able to setup and run various OF cases in parallel on an HPC cluster
• Be able to preview and post-process OF results

Organiser:

Lecturers:

Four-day intensive training for early-stage researchers:

• When: 22. - 26. September 2025
• Where: University of Nova Gorica, Gorica, Slovenia (campus Rožna Dolina: map)

This workshop is tailored for PhD students and early-career scientists eager to learn how to discover and engineer nanobodies — single-domain antibody fragments derived from camelid heavy-chain antibodies.

Participants will engage in a program consiting of lectures, hands-on laboratory sessions, and interactive computational tutorials. You will learn to identify nanobody candidates both in silico (using computational tools) and in vitro (through wet-lab panning techniques).

🔬 What You’ll Learn

• How nanobody libraries are constructed, characterized, and screened

• Computational workflows to model, rank, or design nanobody candidates

• Hands-on training with phage display and wet-lab selection of antigen binders

🎯 Who Should Apply?

This workshop is open to PhD students with a basic background in biochemistry, molecular biology or related fields. It’s ideal for researchers ready to integrate nanobody discovery into their work—computationally, experimentally or both. We will select 12 participants based on their submitted abstract and motivation letter. To encourage learning from each other, all accepted participants are expected to deliver a 10-minute short presentation in the daily PhD2PhD sessions. Successful applicants will be notified and asked to pay a €300 registration fee (see FAQ for what is included).

🧠 PhD2PhD Session

Each registered participant presents either their current PhD project as it relates to nanobody research or a method/idea they plan to adopt. Talks are strictly 10 minutes, followed by a moderated discussion with peers and lecturers. Participation in these sessions is a requirement of registration.

🤝 Collaboration & Networking

The program includes informal discussion rounds, dedicated networking events, and social activities designed to foster connections and future collaborations.

💰 Funding & Support

This workshop is supported by:

Meteorologi na Neurje.si poročajo, da segrevanje Sredozemskega morja že sedaj dosega rekordne stopnje. To morje je sicer že dlje časa nadpovprečno toplo, vendar v teh dneh prihaja do intenzivne faze segrevanja. Vztrajno območje visokega pritiska nad osrednjim Sredozemljem, pomanjkanje vetra in malo oblakov prispevajo k temu dvigu temperature morske vode.  

Nobenega dvoma ni, da kljub vplivom naravnih dejavnikov, kot so morski tokovi in atmosferska nihanja, glavno vlogo pri povečanih temperaturah igra dvig koncentracije toplogrednih plinov v atmosferi. Povečane koncentracije teh plinov so posledica nebrzdanega fosilnega kapitalizma, ki je iz podzemlja osvobodil na tisoče ton dolgo pokopanega premoga in nafte. Fosilna goriva kapital uporablja za neskončno širjenje proizvodnje in večanje svojih dobičkov. Kljub silovitemu zaostrovanju podnebne krize, ki ga te dni z vročinskim valom še kako občutimo na lastni koži in ki se šteje v vse večjih smrtnih žrtvah,  se ta trend v zadnjih letih še krepi, na primer s ponovnim odpiranjem termoelektrarn v Nemčiji ter skrajno reakcionarnimi potezami trenutne ameriške administracije (Drill, baby, drill!).

Povečane koncentracije toplogrednih plinov v atmosferi in s tem segrevanje podnebja prinašajo tudi katastrofalne posledice za morske ekosisteme. Povečana absorpcija ogljikovega dioksida iz atmosfere zakisljuje morja, zaradi česar kalcifikacijski organizmi, kot so korale, plankton in školjke težje gradijo svoje oklepe in skelete. To vpliva tudi na druge morske organizme in ima kaskadne učinke v prehranjevalni verigi. 

Oceani se že od sedemdesetih dalje segrevajo, saj posrkajo velik del presežne toplote, ki se kopiči v atmosferi. Toplejša morja povzročijo migracije morskih organizmov, kar prav tako spremeni prehranjevalne verige in poruši ekosisteme. V skrajnih primerih ekstremni vročinski valovi pobijejo morske organizme na nekem območju.

Prav tako se s segrevanjem morske vode zmanjšuje vsebnost kisika v njej, kar lahko v kombinaciji s povečeno količino hranilnih snovi v vodi povzroči cvetenja morja in pomanjkanje kisika za morske organizme. Tudi to lahko povzroča velike motnje v ekosistemih.

Ti dejavniki posebno močno vplivajo na zaprta morja, kakršno je Sredozemsko morje, še več škode pa povzročijo v Jadranskem bazenu, ki je še bolj nepretočen.

Dvig temperature morja pa  nima le uničujočih posledic za morske ekosisteme, temveč vpliva tudi na poznopoletne in zgodnjejesenske nevihte, nalive in posledično poplave. Namreč večja kot je temperaturna razlika med toplim in vlažnim sredozemskih zrakom ter hladnejšim zrakom s kontinenta, močnejši so ti vremenski pojavi. Tako vemo, da čez nekaj mesecev obstaja večja možnost za hude nevihte in poplave. Takšne smo na primer lani spremljali v Španiji in pred dvema letoma doživeli v Sloveniji.

Četudi ne moremo zanemariti naravnih oceansko-atmosferskih nihanj je jasno, da je ta dvig morske temperature posledica podnebnih sprememb, ki jih povzročajo vedno večje količine sežganih fosilnih goriv. Ta poganjajo sistem, ki omogoča rast kapitalu, ki se ne meni ne za propadle morske ekosisteme, ne za obubožane milijone na globalnem jugu in ne za gore trupel čez katere koraka. Ustavi ga lahko le organizirano delavsko gibanje, ki bo zmožno ustvariti svet, v katerem bomo demokratično odločali o zadovoljevanju potreb vseh, ne da bi pri tem uničevali naravo in s tem materialne pogoje svojega bivanja. Na nas pa je, da to gibanje zgradimo.

The post VROČE SREDOZEMLJE, MRTVE KORALE, POPLAVLJENA MESTA first appeared on Rdeča Pesa.

Foto: Peter Žiberna

Ta novica nas glede na zadnje trende oboroževanja, vojaškega hujskanja in militarizacije ne preseneča toliko kot dejstvo, da smo glede kolektivne zaveze dviga proračunskih sredstev izvedeli kar iz Trumpove objave, ki jo je delil na družabnih omrežjih. Gre za sporočilo generalnega sekretarja Nata Marka Rutteja, ki se je želel pohvaliti ameriškemu predsedniku:

»Dragi gospod predsednik, dragi Donald,

Čestitke in hvala za odločno akcijo v primeru Irana, to je bilo res neverjetno in nekaj, česar si nihče drug ne bi upal. Zaradi tega smo vsi bolj varni. Pred teboj je še en velik uspeh nocoj v Hagu. Ni bilo lahko, ampak na koncu so vsi podpisali dvig na 5%.

Donald, pripeljal si nas do prelomne točke za Ameriko, Evropo in svet. Dosegel boš to, česar ni še noben ameriški predsednik.«

V skupni izjavi sprejeti v Hagu naj bi se članice Nata zavezale k dvigu obrambnih izdatkov na pet odstotkov BDP-ja do leta 2035. Od tega naj bi namenile 1,5 odstotka za naložbe povezane, z njo. Slednji odstotek bi naj predstavljal to, k čemur nas je napeljeval domač politični vrh. Češ da bomo »pretentali« Nato in s tem denarjem gradili bolnice in »drugo infrastrukturo«. Pa je to res? 

Takole nadaljuje Rutte: »Evropa bo plačala veliko, kot bi tudi morala, in to bo tvoja zmaga.«. Trump je z objavo zasebnih sporočil zgolj razkril ustaljene prakse odločanja v Natu. Gre za jasno hegemonijo in uresničevanje imperialističnih teženj ZDA, ki bo preko Nata izčrpala že tako skrčene javne sisteme socialnega varstva, zdravstva, šolstva in najbolj prizadela delovne ljudi.

Kaj pa naš politični vrh? Golob podpisuje peticije za Palestino, izraža skrb za palestinske otroke in se za medije rokuje s palestinskimi športniki. A ko je treba dejansko ukrepati in prevzeti odgovornost, stisne rep med noge in se dela nemočnega državljana namesto predsednika vlade. Slednji je dejal: Slovenija tako “ostaja zavezana obrambni (oziroma bolje rečeno morilski) drži Nata. Očitno ne vidi ali noče videti povezave med genocidom v Palestini in oboroževanju Izraela s strani članic Nata.

 Naš vladajoči razred deluje povsem skladno z ameriškim in nemškim vladajočim razredom. Med njimi ni nobene razlike, zato nas ne bodo prepričali z argumentom, da denar, ki ga bomo dali Natu pravzaprav ne gre za vojaške misije v tujini, pa za izraelske bombe in za profite tuje vojaške industrije.

Morda Tanja Fajon res verjame, da Nato služi obrambi, mi pa vemo, da gre za pakt nasilja, agresije in uničenja.  Ustvarja nevidne sovražnike, zato da bi nas prepričali, da smo v nevarnosti. A največja nevarnost za nas je obstanek v Natu paktu. Zato je izgradnja močne protiimperialistične fronte nujna, da se skupaj upremo vojaškemu diktatu vojne industrije in vojnih dobičkarjev. Prvi korak je izstop Slovenije iz Nata. Korak v tej smeri smo naredili tudi včeraj na protestnih shodih (Ljudska fronta – vojni kontra) v Ljubljani in Kopru.

The post “NI BILO LAHKO, AMPAK NA KONCU SO VSI PRISTALI NA 5%” first appeared on Rdeča Pesa.

“Vse strani pozivam, da naj stopijo korak nazaj, naj se vrnejo za pogajalsko mizo. Iranu ne sme biti dovoljeno, da bi razvil jedrsko orožje.” Tako groteskno je nočne zločinske bombne napade ZDA na Iran, komentirala visoka predstavnica Evropske unije (EU) za zunanjo politiko, Kaja Kallas. Iran je več desetletji žrtev popolnoma neupravičenih ekonomskih sankcij s strani držav imperialističnega centra. Zadnjih deset dni pa je tarča terorističnega raketiranja ter bombandiranja združenih izraelsko-ameriških sil. Skladno z logiko vladajočih razredov na Zahodu pa ga je njihova zvesta predstavnica, Kallas, postavila v vlogo agresorja in “faktorja nestabilnosti” na Bližnjem vzhodu. 

Takšnemu razumevanju, ki nam ga vsakodnevno množično servirajo osrednji mediji in njihovi (prikriti) agenti imperialističnega tabora, se je potrebno odločno postaviti po robu. Iran ni agresor. Izrael, ki že več kot 20 mesecev izvaja genocid nad Palestinkami in Palestinci, je sprožil obsežne raketne in letalske napade na Iran. Cilj Izraela je jasen in večplasten:

1.) Z bombandiranjem povzročiti čim več smrti in razdejanja, preko tega sprožiti zamenjavo iranskih oblasti in ustoličiti režim, ki bo deloval v skladu z njihovimi ekspanzionističnimi interesi ter interesi celotnega kolektivnega zahoda; 

2.) Obrniti pozornost svetovne javnosti od genocida v Gazi. Samo v zadnjih desetih dneh je izraelski okupator pobil najmanj 450 Palestink in Palestincev. Mnoge od njih so izraelske krogle pokosile medtem, ko so sestradani čakali na pakete hrane; 

3.) Zagotoviti obstanek vlade Benjamina Netanjahuja na oblasti. Vsa “koalicijska nesoglasja” so bila pozabljena, ko so prva izraelska letala poletela na krvavo misijo na vzhod. 

Ker Izrael ni bil zmožen zlomiti iranskega odpora, še več, mnogi valovi iranskih raketnih napadov so pokazali na relativno šibkost izraelski obrambnih sistemov (poročanje o tem je zaradi medijske cenzure v Izraelu strogo prepovedano), so se v agresijo neposredno vpletle ZDA. Ameriški napad je zločinski akt, ki je nelegalen celo po pravilih mednarodnega prava in pomeni zgolj dodatno zaostrovanje situacije na terenu. Trumpovo pojasnilo po njem (“Sedaj je čas za mir.”), pa je moč razumeti zgolj kot slabo priredbo zdaj že legendarnega slogana iz protestov proti vojni v Vietnamu (“Bombing for peace is like fucking for virginity”).

Takšni agresiji se je potrebno upreti. Pokazati moramo solidarnost z izstradanimi Palestinkami in Palestinci ter napadenimi Irankami in Iranci. Ameriško-izraelska koalicija, podprta s strani držav članic NATO pakta ne napada zgolj njih, ampak poskuša z izsiljenim konfliktom zatreti vsa prizadevanja po svetu, ki gredo v smeri miru, sodelovanja med delovnimi ljudmi sveta in svobodne Palestine. 

Priložnosti za takšen upor in izkaz solidarnosti imamo že ta teden:

• Jutri, 23.6 ob 18:00 v Rušah (Trg vstaje) na “Ruškem shodu za mir v Palestini”.
• V torek, 24.6 ob 17:00 na Kogresnem trgu v Ljubljani na “Protestu proti oboroževanju, vojni in zvezi Nato”. 
• V torek, 24. 6., Protest proti oboroževanju, imperialističnim vojnam in Natu v Kopru ob 18.00 na Titovem trgu

Pridite, da nas bo čim več!

En svet, en boj!

The post AMERIŠKI ZLOČINSKI NAPAD NA IRAN – UPRIMO SE VOJNI! first appeared on Rdeča Pesa.

Povezava do dogodka.

Stop genocidu!
Stop vojni!
Stop stradanju otrok!
ZA MIR!

23.6.2025, ob 18. uri, bo na Trgu vstaje v Rušah potekal Shod za mir v Palestini. Protest organizira Zveza borcev za vrednote NOB Ruše. Pridi in pokaži, da je bilo dovolj genocidnih politik!

The post Jutri, 23.6., RUŠKI SHOD ZA MIR V PALESTINI! first appeared on Rdeča Pesa.

Pridruži se nam 24. junija ob 17.00 v Ljubljani na Kongresnem trgu in ob 18.00 v Kopru na Titovem trgu na protestu proti militarizaciji in NATO paktu! Vse napredne sile stare celine, od Soluna do Stockholma, se bodo med 22. in 24. junijem zbirale na ulicah, kjer bomo izkazovale svoje nasprotovanje militarističnim, oboroževalskim in natovskim politikam, ki jih bo vladajoči razred sprejemal v Haagu na srečanju vrha zveze NATO.

Evropska unija in NATO nas vse bolj potiskata v vojno, ki koristi le vojnim dobičkarjem in političnim interesom zahodnega kapitala. Evropa in z njo Slovenija se pogrezata v militarizacijo in drastičen dvig vojaških izdatkov – temu se moramo upreti!

Vpliv vojaške industrije in vojaških politik, za katerimi stojijo vojni hujskači domačih in tujih vladajočih razredov, je vedno večji. Namesto mirovne politike Slovenija danes solidarnost kaže s pošiljanjem orožja na tuje fronte in z zaostreno vojaško retoriko. Naši politiki ne delajo za mir, ampak za vojno!

EU je sprejela 800 milijard evrov vreden proračun za vojaško porabo. Na račun že tako razpadajočih socialnih storitev bomo nakupovali orožje! NATO in Evropska unija pritiskata na članice, naj povečajo vojaško porabo, razpravljajo o skupni vojski in celo o ponovni uvedbi vojaškega roka.

Slovenija po diktatu NATO pakta že načrtuje višanje porabe na 1,4 milijarde evrov za vojaški proračun, kar je skoraj pol milijarde več, kot je bilo prvotno predvideno. Vendar nenasitna zveza NATO od nas zahteva še več, do 2030 zahtevajo, da za oboroževanje prispevamo kar 5 % svojega BDP. Denar za orožje, tanke in vojskovanje bodo vzeli iz žepov delovnih ljudi. Še bolj kot sedaj bo trpelo naše šolstvo, zdravstvo, domovi za ostarele, pokojnine.

Slovenski vladajoči razred z našim denarjem finančno in politično podpira tako vojno v Ukrajini kot genocid nad Palestinci, ki ga izvaja Izrael. Samo še vprašanje časa je, kdaj bodo na fronto poslali naše brate in sestre. Ne bomo umirali za interese zahodnega kapitala!

ZATO POZIVAMO:

• K izstopu iz NATO pakta!
• Proti militarizaciji!
• Proti večanju vojaških izdatkov!
• Proti služenju v vojskah, ki branijo interese tujih kapitalistov!

The post PRIDI NA PROTEST LJUDSKA FRONTA – VOJNI KONTRA! first appeared on Rdeča Pesa.

Objavljamo pismo, ki nam ga je poslala mariborčanka Urška, ki se je, skupaj s svojo mamo, udeležila četrtkovega protesa. 

Mariborčani,

hvala vsem, ki ste prišli in javno pokazali, da vam je mar. (Hvala tudi vsem, ki ste delili, sponzorirali in govorili okoli o protestu, ki je še kako pomemben). Fun fact za vse, ki podcenjujejo našo “slabo” udeležitev na protestu: včasih se iz malega lahko razvije veliko. In vse, kar se potrebuje, so zgolj 3,5% populacije, ki drži skupaj (in verjamem, da se tega mnogo ljudi, ki je raziskovalo psihologijo množic, tudi zaveda). Včasih morajo stvari tudi dozoreti, zatorej brez skrbi. Vedno je tu potencial za napredek/rast, vprašanje pa je, če smo ga zmožni videti in če mi znamo dati svoj čas. 

Naučili so nas, da se velikokrat moramo prilagoditi, da sistem tako pač je, da se moramo zmanjšati, da je ok, če v letu 2025 vse živo razpada, če starejši občani nekje na daljni postaji čakajo 60-90 min na soncu brez dostopa do vode, wcja, da je ok, da so vozniki brez časa za malice in se pajsajo ure na vročini v avtobusu, da je ok, da gibalno ovirani nimajo dostopa do bolnice (kar bi morala biti čista osnova), dijaki do šole, da se vrata avtobusa zatikajo ipd… Naučeni smo sprejeti to kot našo normalo. Ker tako pač je, ker naj bi bili tiho, poslušni, (vstavi pridevnik) ____. Včasih je pa dovolj le par ljudi, ki reče: no, ne rabi biti ravno tako. Mogoče pa ni ok. Mogoče pa je lahko drugače. Mogoče pa en glas opogumi še 2 druga. In mogoče imamo ljudje več vpliva kot si predstavljamo. Mogoče smo vzor mladini, ki nas (kljub telefonom) vseeno gleda. In mogoče smo močnejši, ko stopimo skupaj.  Kdo bi vedel. 

Še en fun fact: Vsak dan imamo možnost, da si sami ustvarimo boljši svet. Lahko samo smo in jamramo nad sistemom. Lahko pa aktivno ustvarjamo novega. Vsak se vsak dan odloča kakšne odločitve bo sprejel. Lahko smo del problema, lahko pa se fokusiramo na rešitev in implementacijo novih idej, izboljšanja sistema, ustvarjanje novega. To hkrati pomeni, da ne čakamo, da bo nekdo drug naredil stvari za nas. Ker se same več kot očitno ne bodo zrihtale. Pa naj bo to šolstvo, zdravstvo, karkoli. Sprememba je edina konstanta v življenju, sami se pa vsak dan odločamo ali bomo aktivno sodelovali v njej. Hvala še enkrat. Vesela in hvaležna sem, da se Maribor aktivno prebuja. Mamo mi to.

Mariborčanka Urška

The post MARIBORČANKA PO PROTESTU: “MAMO MI TO” first appeared on Rdeča Pesa.

Včeraj je Trgu svobode potekal protest za boljši javni potniški promet, ki ga je organizirala Pobuda za boljši javni potniški promet v Mariboru. Protestniki so se od Trga svobode sprehodili proti občini, nadaljevali so po Maistrovi, Tyreševi in Slovenski ulici. Več kot sto petdeset protestnikov je med drugim glasno vzklikalo: “busi gor, arso dol,” “manj avtov, več busov,” “busi za ljudi, ne za župana,” “jebeš profit, za županovo rit.” Na prehodu za peščce pred občino jim je v znak solidarnosti pohupal tudi voznik Marproma, ki je takrat vozil avtobus. 

Protestniki so zahtevali, da: 

• mora biti JPP kakovostna alternativa avtomobilu,
• se mora povečati frekventnost, tudi med vikendi in ob večerih,
• morata biti mestni in primestni promet povezana,
• se morajo vrniti  linije, ki so prej učinkovito povezovale ključne dele mesta, 
• mora biti Tezno neposredno povezano z UKC, 
• morajo biti potniki, delavci in lokalne skupnosti vključeni v načrtovanje in spremembe linij, 
• se morajo izboljšati delovni pogoji voznikov voznikov in voznic ter drugih zaposlenih v JPP.

Ti “kreativci” naj sedejo na invalidski voziček in vozijo po klancu

Franc Žiberna iz Mestne četrti Tezno je dejal, da so Tezenčani od vseh Mariborčanov najbolj prizadeti zaradi zmanjšanja števila frekvenc avtobusnih linij G3 in P12 ter ukinitvi ali preusmeritvi linije 1 Tezno (sedaj G1). Z novo linijo G1 so iz uporabe izločili ključna postajališča: Ljubljanska II. gimnazija, ZD Magdalena, UKC ter Glavni trg. “Tukaj in na vseh izpuščenih postajališčih pripravljavci sprememb niso sploh razmišljali o starejših ljudeh, mamicah z otroškimi vozički ter o gibalno oviranih ljudeh in bolnih,” pravi. Žiberna je bil velik uporabnik avtobusa 1 Tezno, saj je samostojno obiskoval ambulante v UKC in Magdaleni. Zdaj tega več ne more.

Namesto spoštljivega odgovora pa so Tezenčani prejeli komentar, da se naj tisti, ki bodo namenjeni v ZD Magdalena in UKC Maribor, pač odpravijo peš od postaje pri Europarku. “Ti “kreativni” ljudje naj sedejo na invalidski voziček in se s te postaje odpravijo na pot pod Titovim mostom (klančina prestrma) do glavnega vhoda v UKC ali od postaje vrnejo nazaj na peš nadhod nad Titovo cesto (turbokrožišče). Pot je dolga, s strmimi klanci in ob slabem vremenu tudi nemogoča,” je pojasnil. “Zaradi trme in vztrajanja župana z mestnim svetom stare linije G1 ne bo, pa pika. Vendar, dragi g. župan, takšno trmarjenje ne bo koristilo ne nam uporabnikom avtobusnega prometa ne vam, ko se boste kmalu pojavili na volitvah.” Tezenčani zahtevajo vrnitev linije G1. 

Fredi Magdič, prav tako iz Teznega je dejal, da so zadnje spremembe linij mestnega avtobusnega prometa so prizadele najbolj ranljive. “Namesto približevanja našim potrebam so na občini sledili le kapitalski logiki. Olajšali so dostop do trgovskih centrov, mnogim pa so otežili pot do bolnišnice, šol, kulturnih ustanov, pokopališč … Namesto modernega, efektnega in uporabnega mestnega javnega prometa smo dobili nepovezan cirkus, ki nikakor ne služi svojemu namenu: to je zmanjšanju števila osebnih avtomobilov v mestu. Nasprotno, še povečuje ga.”

Kakovosten javni promet koristi vsem 

Maja Šnuderl iz gibanja Mladi za podnebno pravičnost Maribor poudarja, da kakovosten, frekventen in dostopen javni potniški promet koristi vsem prebivalcev, ne le tistim, ki ga uporabljajo. Zmanjša količino avtomobilov, kar pomeni manj zastojev, hrupa, onesnaženosti zraka ter potrebe po parkiriščih, ki pogosto stojijo na nekdaj zelenih površinah. Šnuderl je ogoročena nad zmanjšano frekventnostjo avtobusov: “Na praktično vseh linijah se je število odhodov zmanjšalo, najbolj izven prometnih konic in ob vikendih. V Zrkovcih morajo danes čakati na avtobus kar 90 minut, v Limbušu 75 minut, do pokopališča Dobrava pa vozi linija 12 namesto vsakih 20 minut sedaj le še vsako uro.” 

Ministrstvo za okolje, podnebje in energijo je pozvala, naj ne ne zvišuje cen vozovnic, saj bi v času podnebne krize in vsesplošne draginje morali javni promet narediti kar se da dostopen in konkurenčen avtomobilu. “Potrebujemo ustrezne avtobusne povezave, ki ne bodo namenjene le šolarjem v času prometnih konic, temveč tudi delavcem za prihod na službo, ter vsem uporabnikom omogočale ustrezno mobilnost tudi popoldan, zvečer in med vikendi,” je sklenila Šnuderl.

Luka Mofardin iz Mreže za pravičen prehod je dejal, da podnebna kriza ni oddaljena grožnja: “Občutimo jo že sedaj. Vremenske katastrofe, vročina, vse hujši delovni pogoji. Pozna se z draginjo, uničenimi domovi in vse večjo negotovostjo.” Izpostavil je, da delavke in delavci pogosto izgubljamo ure vsak dan samo zato, da sploh pridemo do službe – ker javnega prevoza enostavno ni ali pa je slab. “Zato mora biti pravični prehod javno usmerjen, skupnostno voden in zgrajen od spodaj. In naj se začne tukaj – z bojem za javni promet, ki služi ljudem in okolju, ne kapitalu. Zato danes ne protestiramo samo proti slabemu prometnemu sistemu – protestiramo za drugačen svet. Svet, v katerem bomo skupno dobro postavili pred zasebni interes,” je sklenil.

Vozniki v prenovo niso bili vključeni

Govor voznika Marproma je prebral moderator, voznik pa ostaja anonimen. Kot je zapisal, se ne more izpostavljati, saj so bili nekateri sodelavci že tarče klicev direktorja z opozorili, da ni pametno govoriti proti občini. Voznik je zapisal, da se v kompletnem projektu prenove linij kaže aroganca odgovornih iz mariborske občine: “Prenovo so zaupali fakulteti in tujemu načrtovalcu, Ljubljančanu, ki o potrebah Mariborčanov nima pojma. V projekt nismo bili vključeni niti mi, vozniki, ki problematiko mestnega prometa poznamo najbolje. Vsaj operativno.”

Vozniki so občino opozarjali, da za prenovo linij potrebujejo več avtobusov, več voznikov in delujoč vozni park z delujočimi avtobusi. Opozarjali so, da bo del voznikov dislociran in ne bo mogel niti na malico ali na stranišče, saj so linije, oz. postajališča postavljena tako, da si odmaknjen od vsega. Za potrebe novih linij bi bilo potrebovali med 15 in 20 novih avtobusov in dvakrat toliko voznikov, sporoča. A naleteli so na gluha ušesa. 

Vozniki in voznice si želijo boljših pogojev dela, prilagojenih linij uporabnikom, spoštovanje pravice do malice, počitka in prostih vikendov. Nasprotujejo poslovanje na meji dopustnega in varčevanja na zaposlenih in potnikih. Frekvenca se mora povečati na vseh linijah. Voznik je v govoru prosil potnice in potnike k razumevanju, da niso vozniki krivi za nedelujoče klime, zamude, razpadajoče avtobuse in nedelujoča vrata. 

O razmerah dela na Marpromu in krčenju javnega prevoza je spregovorila tudi Ana Onić, upokojena delavka iz Marproma. Pozvala je k solidarnosti do voznic in voznikov, ki da se trudijo za potnike, a problemi, ki jih je nakopala občina, žal niso v njihovih rokah. 

Minimum ni dovoljJerneja Breznik iz Ekosocialistične iniciativa Klas je poudarila, da so ljudje z več tisoč podpisi pod tremi peticijami pokazali, da ne gre za posameznike, temveč za skupno zahtevo po dostopnem prometu za osnovne potrebe – pot do službe, šole, bolnišnice, pokopališča. “Krčenje javnih storitev gre zmeraj na škodo delovnih ljudi in poslabša kvaliteto naših življenj,” je dejala. Zgolj vrnitev v prejšnje stanje ni dovolj. Javni potniški promet se ne sme zadovoljiti zgolj z minimalnim standardom. Prav tako ne sme biti podrejen profitni logiki. Mestni in primestni promet morata biti bolje povezana. Javni potniški promet mora biti podružbljen, o njem morajo odločati potniki in delavci. Vozniki in voznice pa morajo imeti boljše delovne pogoje. “Motite se, če si mislite, da se bomo zadovoljili s kozmetičnimi popravki. Ne pristajamo na ignoranco in posmeh ter ne bomo odnehali dokler javni prevoz ne bo resnično služil našim potrebam.”

The post Busi gor – Arso dol! first appeared on Rdeča Pesa.

Pokojninsko reformo Golobove vlade, ki bo najbolj prizadela delavke in delavce z najnižjimi dohodki in najtežjimi poklici, želi koalicija kar čim prej spraviti pod streho. Z njo vladajoči varčujejo na plečih tistih, ki imajo najmanj, medtem ko kapital ostaja popolnoma nedotaknjen. Proti škodljivi reformi se pojavlja vse več odpora, ki je hkrati vse bolj organiziran.

Danes je Delavska koalicija na tiskovni konferenci predstavila naslednje korake za sprožitev referenduma proti škodljivemu predlogu pokojninske reforme, ki bo predvidoma sprejet še pred začetkom parlamentarnih počitnic. Zavezništvo združuje borbene sindikate in druge organizacije, ki povezujejo več deset tisoč delavcev iz najrazličnejših panog.

Kot pravijo, bomo “zaradi nove pokojninske reforme garali dlje, pokojnine pa bodo še naprej prenizke”. Nova pokojninska reforma nam prinaša:

Poznejše upokojevanje: 

Pokojnine so že danes prenizke, delovne obremenitve pa previsoke – nova reforma pa predlaga upokojitve šele pri 62 ali celo 67 letih. Mnoge delavke in delavci komaj zdržijo do 60. leta, še posebej v fizično napornih poklicih, kot so gradbeništvo, zdravstvo in industrija. Vlada utemeljuje reformo s trditvijo, da “živimo dlje”, a ob tem spregleda, da sta družbena blaginja in produktivnost danes precej višji kot nekoč. 

Nepravičen izračun pokojnin: 

Nova formula za izračun pokojnin bo številnim delavcem znižala pokojnine – namesto da bi šteli le najboljša leta, se bo pokojnina izračunavala na podlagi 40 let delovne dobe (minus 5 najslabših let), namesto dosedanjih 24 najugodnejših. Ker večina ljudi nima visokih in stabilnih plač, bodo v izračun vključena tudi obdobja z nižjimi dohodki, kar bo močno znižalo povprečje. Posebej prizadeti bodo prekarci in vsi, ki so delali v manj plačanih poklicih. 

Nižanje vrednosti pokojnin: 

Reforma bo dolgoročno zmanjševala realno vrednost pokojnin. Zdaj so pokojnine vezanje na plače, ki rastejo hitreje od inflacije. Reforma želi pokojnine vezati predvsem na inflacijo, kar pometni, da bo čez 30 let kar 80 % upokojencev prejemalo manj od minimalne plače – to ni dostojno staranje, temveč revščina.

Popušča delodajalcem:

Reforma ne predvideva dviga prispevkov za delodajalce. Po reformi bodo delavci prispevali še vedno skoraj dvakrat več kot delodajalci (15,5 % proti 8,85 %). Namesto da bi odgovornost nosili vsi, bo breme spet padlo le na delavce. Pokojninska blagajna se ne krepila, temveč varčevala – na hrbtih delavcev in delavk.

Izigrava delavce:

Reforma je bila sprejeta brez resnega sodelovanja delavcev ali upokojenk. Javno razpravo so skrajšali, odločanje pa prestavili v čas dopustov. Vlada se izogiba dialogu in namesto soglasja vsiljuje škodljive rešitve.

Delavska koalicija je že v nizkem štartu za pričetek referendumske akcije. Na njihovem spletnem mestu www.stoppokojninski.si in prek Facebooka in Instagrama bodo obveščali, kdaj bodo začeli zbirati podpise Hkrati vabijo delavstvo, upokojence in študente, da se jim pridružite, da skupaj ubranimo naše penzije in postavimo potrebe ljudi pred interes kapitala.

O pokojninski reformi smo pri Rdeči pesi pisali že večkrat, osrednje prispevke za razumevanje njene škodljivosti pa lahko najdete tukaj: 

https://rdecapesa.com/kako-dolgo-bomo-se-delali/

https://rdecapesa.com/mescev-mit-o-medgeneracijskem-konfliktu/

https://rdecapesa.com/pokojninska-reforma-in-demografsko-vprasanje/

https://rdecapesa.com/demografsko-vprasanje-2-del-ucinki-na-pretocni-sistem/

https://rdecapesa.com/za-dostojno-starost-vseh-ne-dobicek-kapitala/

https://rdecapesa.com/politicna-ekonomija-pokojninske-reforme/

@STOP pokojninski

The post STOP POKOJNINSKI REFORMI! first appeared on Rdeča Pesa.

“Mi, delovni ljudje Irana – učitelji, medicinske sestre, delavci, upokojenci – od vojne, militarizma, bombardiranja in imperialističnih politik nimamo nič. Običajni ljudje, zlasti delavski razred, plačujejo ceno vojne s svojimi življenji, zdravjem in domovi,” sporočajo delavske organizacije in skupine upokojenih delavcev v Iranu v skupni izjavi za javnost. Iransko delavstvo je izrazilo ostro nasprotovanje vojaški eskalaciji v regiji in obsodilo še vedno trajajoč genocid v Gazi.

Med podpisniki so Sindikat delavcev avtobusnega podjetja Teheran in predmestja, Sindikat delavcev sladkorne tovarne Haft Tappeh in Zavezništvo upokojencev. Poudarjajo, da iranski delavci od vojne nimajo ničesar – le uničenje in poglabljanje revščine.

Trenutna nestabilna in nevarna situacija v Iranu in na Bližnjem vzhodu zahteva skupno ukrepanje. Ostro obsojajo nedavne izraelske zračne napade na infrastrukturo, stanovanjska območja, poslovne stavbe. Zavračajo izraelske trditve, da Izrael ni sovražen do iranskega naroda, to je zgolj del propagande. Opozarjajo na nedavno grožnjo izraelskega obrambnega ministra, da bo “Teheran zgorel”, ter na stalno podporo Zahoda takšnim vojaškim dejanjem.

Delavke in delavci so kritični do ZDA in Izraela, ki sta odgovorna za genocid v Gazi in druge zločine v regiji. Obsojajo tišino Združenih narodov in mednarodnih institucij. Kapitalizem in imperializem sta kriva za vojne, okoljski kolaps in trpljenje ljudi, pišejo v izjavi.

Iranski delavski razred od vojne nima ničesar: “Ekonomske sankcije, vojaški proračuni in represija so že ustvarili lakoto, smrt in razseljenost. Vojna bo to še poslabšala.”

Poudarjajo, da tudi glede Islamske republike nimajo nobenih iluzij. Režim označujejo kot represiven, avanturističen in protidelavski. Kritizirajo desetletja zatiranja delavskih protestov, zanikanje sindikalnih pravic ter zapiranje in mučenje delavskih aktivistov.

“Naš boj je družbeni in razredni boj. Zanašamo se sami nase in  nadaljujemo s protesti za kruh, delo in svobodo. Naš boj je povezan z delavci in svobodoljubnimi ljudmi po vsem svetu. Stop vojni. Stop militarizmu. Zahtevamo takojšnje premirje.”

Podpisniki pozivajo sindikate, skupine za človekove pravice, mirovne in okoljske organizacije ter protivojne aktiviste po vsem svetu, naj se pridružijo njihovi zahtevi po koncu bombardiranja, vojnih zločinov in uničevanja okolja – ter naj izrazijo solidarnost z ljudmi Irana in Bližnjega vzhoda v njihovem boju za mir, pravičnost in dostojanstvo.

The post IRANSKE DELAVKE IN DELAVCI: “OD VOJNE NIMAMO NIČ!” first appeared on Rdeča Pesa.

Najbolj brutalen in za delovne ljudi škodljiv ukrep je podaljšanje spodnjega in zgornjega pogoja upokojitvene starosti s 60 na 62 let za tiste s 40 leti pokojninske dobe brez dokupa oz. s 65 na 67 let za tiste z najmanj 15 leti dobe. Sistemsko gledano ukrep postane še bolj radikalen, ko pomislimo, da se za dve leti navzgor premikajo tudi vse ostale pravice, recimo pravica do pridobitve vdovske in invalidske pokojnine. 

Vlada ukrep utemeljuje z dvema argumentoma. Prvi je, da smo pri tako zakonsko pri upokojitveni starosti kot pri podatkih o efektivnem izstopu iz trga dela med najnižjimi med državami OECD. A ne pozabimo, da Slovenija v EU spada med države z najvišjimi stopnjami intenzivnosti dela. Kakorkoli že, z vidika napredne politike je globalno gledano relativno hitro upokojevanje svojevrsten dosežek: pomeni, da Slovenija ni podlegla najhujšim reformam financializacije in podaljševanja delovne aktivnosti. To deloma priznava tudi Ministrstvo za delo, ki v izročku za medije zapiše: “To seveda lahko štejemo kot dosežek, nekaj pozitivnega za ljudi – dokler si to lahko privoščimo.” 

Izjava je v mnogih pogledih zavajajoča: predpostavlja namreč, da staranje mehanično določa izdatke v prihodnosti, kar smo v preteklih objavah že demantirali. Poleg tega pa je tudi cinična, saj je na področju oboroževanja Slovenija že izpogajala odstop od fiskalnih pravil za povečanje naložb v oboroževanje. Če neupogljivi zakoni fiskalnih jastrebov velajajo za upokojence in delavce, se ti zlomijo ob blišču orožarske industrije. 

Omenimo še drug klasičen argument za podaljševanje upokojitvene starosti: podaljševanje pričakovanega življenjskega obdobja. Težava te argumentacije je, da tudi podatki OECD in Eurostat kažejo, da se rast pričakovanega življenja upočasnjuje. Poročilo OECD »Pensions at Glance 2023«, glavna referenca birokratskih aparatov po Evropi, ugotavlja podobno:

»Življenje se še naprej podaljšuje in ta trend se bo predvidoma nadaljeval, čeprav se je hitrost izboljševanja v starosti v zadnjem času upočasnila, zlasti glede na COVID-19. Leta 2022 bo pričakovana življenjska doba pri starosti 65 let v povprečju znašala 83,0 leta za moške in 86,2 leta za ženske. /…/ V povprečju držav OECD naj bi se pričakovana življenjska doba pri starosti 65 let do leta 2065 podaljšala za 4,4 leta med ženskami in 4,9 leta med moškimi.«

Zveni še zmeraj spodbudno, a za oblikovanje politik ne prav informativno. Pričakovano življenjsko obdobje verjetno sploh ni primeren kazalnik za določanje upokojitvene starosti: veliko bolj primerno je upoštevati pričakovana zdrava leta življenja, kjer pa je slika drastično drugačna. Pričakovana zdrava leta življenja so se v Sloveniji v zadnjih 10 letih za ženske gibala nekje med 59 leti in 69 leti, za moške pa med 58 in 65 leti, odvisno od družbene in ekonomske klime. Zadnji razpoložljivi podatki NIJZ iz leta 2022 kažejo, da so pričakovana zdrava leta za moške 65 let, za ženske pa 68,5 let. Predlog vlade bi torej zgornjo mejo za upokojitev dvignil celo za dve leti nad slovensko povprečje za moške, verjetno pa tudi nad povprečje za vse fizične delavke in delavce po vsej državi. 

Dodajmo, da Ministrstvo nima nobenih podatkov o prihodnjih trendih zdravega življenja. Ne da bi sami špekulirali o teh trendih povejmo le, da glede na krhkost slovenskega zdravstvenega sistema, povečevanje absolutne in relativne revščine ter napovedi krize, nadaljnja rast pričakovanih zdravih let življenja ni zagotovljena. 

Za konec poskusimo orisati še nekatere posledice omejenega ukrepa za državo, kapital in delavce. Po naših grobih ocenah bo dvig zgornje meje upokojitvene starosti na 67 let pomenil, da se bo zaradi vpliva zvišanja upokojitvene starosti za 2 leti število delovno aktivnih zvišalo za vsaj 3 odstotke. Menimo, da bi z ukrepom vlada v naslednjih 10 letih lahko privarčevala vsaj med 0,7 in eno odstotno točko slovenskega BDP – a gre le za preprosta ugibanja. 

Z vidika države gre za varčevanje, z vidika kapitala pa za razširitev bazena poceni delovne sile. Podatki kažejo, da plače nižje izobraženih po 54 letu stagnirajo ali padajo. Razpoložljivi podatki SURS za desetletne starostne skupine prebivalstva in stopnje izobrazbe kažejo, da se neto plače povečujejo za vse stopnje izobrazbe do starosti 54 let. Nato ravni plač bolj kot ne stagnirajo do starosti 65 let in več za nizko izobražene posameznike in povprečno izobražene posameznike. Znižujejo se za srednje izobražene posameznike in le rahlo naraščajo za višje izobražene. Kapital torej s povišanjem upokojitvene starosti prejme dodaten bazen rezervne industrijske armade, ki je večinoma cenejša (bolj ranljiva, z manjšo pogajalsko močjo itd.) od mlajših delavcev. Kakšne so posledice za delavce, pa prepuščamo v premislek pozornim bralkam in bralcem. 

The post KAKO DOLGO BOMO ŠE DELALI? first appeared on Rdeča Pesa.

Na Poletno muzejsko noč bo v muzeju prost vstop na stalno razstavo “Kaj pa programje?” in razstavo “Pol-pismeni“.

Zunaj pa bo na voljo muzejska knjižnica na prostem pri na novo pridobljenem legendarnem Kiosku K67. V primeru slabega vremena čitalnica odpade.

The post Čitalnica na prostem ob retro računalniških revijah first appeared on Računalniški muzej.

Na Poletno muzejsko noč vas ob 19. uri vabimo na voden ogled stalne razstave “Kaj pa programje?” v angleškem jeziku. Zberemo se pri muzejski blagajni, ogled pa traja približno 45 minut.

Na prostem bo ob tej priložnosti postavljena tudi muzejska knjižnica pri na novo pridobljenem legendarnem kiosku K67. V primeru slabega vremena čitalnica odpade.

On the Summer Museum Night, we invite you to a guided tour of the permanent exhibition ‘What about software?‘ in English, starting at 7 PM. We will gather at the museum ticket desk, and the tour will last approximately 45 minutes.

On this occasion, an open-air museum library will also be set up next to the newly acquired legendary K67 kiosk. In case of bad weather, the reading corner will be cancelled.

The post Voden ogled stalne razstave (v angleškem jeziku) first appeared on Računalniški muzej.

Lepo vabljeni na 3. Retro Gaming Kupi/Prodaj/Menjaj dogodek v Sloveniji! Dogodek bo potekal po principu Garažne razprodaje/ Bolšjega trga (“Buy/Sell/Trade Event”). Vse platforme dobrodošle, od ZX Spectruma in Atarija, do Nintendo Switch 2 in Playstation 5.

Informacije:

• V muzeju sta na voljo WC in garderoba v kleti (omarice, ki se zaklenejo s kovancem za 1€, ki ga potem dobiš nazaj). Izven teh omaric ničesar ne bo možno hraniti v muzeju.
• Zelo je pomembno, da ne bomo moteči za okolico (bloke in druge uporabnike objekta Celovška 111), da bo izkušnja takšne tržnice pred muzejem pustila dober vtis.
  Dovoljena je izključno uporaba dela ploščadi pred muzejem in sosednjim e-kolesar.si dolžine 35 metrov znotraj parkirnih ovir, označenih z muzejskim logotipom.
• Dostop z vozili je omejen na bližnja parkirišča, npr. pred Kinom Šiška (Trg prekomorskih brigad) ter Parkirišče Šiška, Janez d.o.o., Celovška 135.
• Do same lokacije z vozilom žal ne morete priti – vožnja in parkiranje po celotni ploščadi in travi okrog muzeja sta strogo prepovedani!
• Prav tako je strogo prepovedano parkirati za muzejem na rumeno označenih mestih, ki so last stanovalcev bloka.

Drobni tisk:

• Računalniški muzej zagotavlja samo prostor za dogodek. Vse transakcije so med prodajalcem in kupcem.
• Za svoje stvari odgovarjate sami, v primeru izgube ali uničenja lastnine ne odgovarjamo.
• V primeru slabega vremena dogodek odpade.

The post Retro tržnica na Poletno muzejsko noč first appeared on Računalniški muzej.

Na Poletno muzejsko noč vas ob 20. uri vabimo na voden ogled stalne razstave “Kaj pa programje?” v hrvaškem jeziku. Zberemo se pri muzejski blagajni, ogled pa traja približno 45 minut.

Na prostem bo ob tej priložnosti postavljena tudi muzejska knjižnica pri na novo pridobljenem legendarnem kiosku K67. V primeru slabega vremena čitalnica odpade.

Za vrijeme Ljetne muzejske noći pozivamo vas na vođeni obilazak stalnog postava ‘A što je s programjem?‘ na hrvatskom jeziku, s početkom u 20 sat. Okupljamo se kod muzejske blagajne, a obilazak traje oko 45 minuta.

Na otvorenom će tom prigodom biti postavljena i muzejska knjižnica uz novo nabavljeni legendarni kiosk K67. U slučaju lošeg vremena, čitaonica se otkazuje.

The post Voden ogled stalne razstave (v hrvaškem jeziku) first appeared on Računalniški muzej.

Na Poletno muzejsko noč vas ob 18. uri vabimo na voden ogled stalne razstave “Kaj pa programje?” v slovenskem jeziku. Zberemo se pri muzejski blagajni, ogled pa traja približno 45 minut.

Na prostem bo ob tej priložnosti postavljena tudi muzejska knjižnica pri na novo pridobljenem legendarnem kiosku K67. V primeru slabega vremena čitalnica odpade.

The post Voden ogled stalne razstave first appeared on Računalniški muzej.

Na Poletno muzejsko noč vas ob 21. uri vabimo na voden ogled stalne razstave “Kaj pa programje?” v italijanskem jeziku. Zberemo se pri muzejski blagajni, ogled pa traja približno 45 minut.

Na prostem bo ob tej priložnosti postavljena tudi muzejska knjižnica pri na novo pridobljenem legendarnem kiosku K67. V primeru slabega vremena čitalnica odpade.

Per la Notte estiva dei musei vi invitiamo alle ore 21:00 a una visita guidata in lingua italiana della mostra permanente “E i programmi?”. Il punto di ritrovo è presso la biglietteria del museo; la visita durerà circa 45 minuti.

All’esterno, in questa occasione, sarà allestita anche una biblioteca museale accanto al leggendario chiosco K67 recentemente acquisito. In caso di maltempo, la “sala di lettura” non sarà disponibile.

The post Voden ogled stalne razstave (v italijanskem jeziku) first appeared on Računalniški muzej.

Z Uradom RS za mladino pripravljamo izvedbo petih praktičnih delavnic za razumevanje in uporabo tehnologij umetne inteligence v mladinskem delu. Delavnice bo izvajal Računalniški muzej, ki delavnice razumevanja in uporabe umetne inteligence izvaja že od leta 2023. Delavnice bodo priložnost za druženje, izmenjavo izkušenj in uvodno spoznavanje z orodji in tehnologijami, ki vam lahko pomagajo pri konkretnem delu z mladimi. Želimo spodbuditi skupno učenje, pomoč pri izzivih, s katerimi se srečujemo, in iskanje svežih, skupno oblikovanih rešitev za podporo mladim pri vedno bolj digitalnem odraščanju.

Zaželeno je, da prinesete s seboj svoj osebni prenosni računalnik, v nasprotnem primeru ga bomo zagotovili mi.
Cilj delavnice:

• Povečati razumevanja tehnologije UI ter njene razširjenosti in načinov uporabe
• Povečati zavedanje o vplivu na razvoj poklicev in veščin uporabe digitalne tehnologije
• Vpeljati sistem kritičnega razmišljanja o raznolikih aspektih uporabe UI in neposrednega vpliva na življenjske situacije mladih
• Opremiti mladinske delavce z metodami za spodbujanje informiranega in aktivnega opredeljevanja mladih do tehnologij UI ter izražanje aktivnega državljanstva
• Povečati poznavanje in sposobnost uporabe praktičnih orodij UI za obogatitvene programe in programe učne pomoči ter socialne integracije
• Spoznati praktična orodja za administrativno razbremenitev mladinskega dela
• Spodbuditi razmišljanja o konkretni uporabi UI v mladinskem delu 

Število udeležencev je zaradi narave delavnic omejeno, zato predlagamo, da se čimprej prijavite – povezava do prijavnice.

Vljudno vabljeni k udeležbi in zavedni, odgovorni ter predvsem ustvarjalni rabi najnovejših tehnologij!

Potek delavnice

9:15 – 9:30 Sprejem in uvod

Registracija, pozdrav in predstavitev poteka dneva

9:30 – 10:15 Osnove UI: “Umetna inteligenca in svet”

Uvodno predavanje s primeri, skupinska diskusija

10:15 – 11:45 Etična vprašanja in praktične vaje za razvijanje kritičnega mišljenja

Študije primerov in skupinsko praktično delo

11:45 – 12:30 Odmor za skupinsko kosilo

Pogostitev, odmor in priložnost za spoznavanje prisotnih udeležencev in organizacij

12:30 – 14:00 Praktična uporaba UI orodij za mladinsko delo

Praktično delo v digitalnih okoljih s prosto dostopnimi orodji za uporabo tehnologij U

14:00 – 14:30 Naslednji koraki in zaključek

Skupinski razmislek o konkretni uporabi UI v mladinskem delu, evalvacija

The post Mladinsko delo 4.0: Umetna inteligenca v praksi – odgovorno in uporabno (BREŽICE) first appeared on Računalniški muzej.

Z Uradom RS za mladino pripravljamo izvedbo petih praktičnih delavnic za razumevanje in uporabo tehnologij umetne inteligence v mladinskem delu. Delavnice bo izvajal Računalniški muzej, ki delavnice razumevanja in uporabe umetne inteligence izvaja že od leta 2023. Delavnice bodo priložnost za druženje, izmenjavo izkušenj in uvodno spoznavanje z orodji in tehnologijami, ki vam lahko pomagajo pri konkretnem delu z mladimi. Želimo spodbuditi skupno učenje, pomoč pri izzivih, s katerimi se srečujemo, in iskanje svežih, skupno oblikovanih rešitev za podporo mladim pri vedno bolj digitalnem odraščanju.

Zaželeno je, da prinesete s seboj svoj osebni prenosni računalnik, v nasprotnem primeru ga bomo zagotovili mi.
Cilj delavnice:

• Povečati razumevanja tehnologije UI ter njene razširjenosti in načinov uporabe
• Povečati zavedanje o vplivu na razvoj poklicev in veščin uporabe digitalne tehnologije
• Vpeljati sistem kritičnega razmišljanja o raznolikih aspektih uporabe UI in neposrednega vpliva na življenjske situacije mladih
• Opremiti mladinske delavce z metodami za spodbujanje informiranega in aktivnega opredeljevanja mladih do tehnologij UI ter izražanje aktivnega državljanstva
• Povečati poznavanje in sposobnost uporabe praktičnih orodij UI za obogatitvene programe in programe učne pomoči ter socialne integracije
• Spoznati praktična orodja za administrativno razbremenitev mladinskega dela
• Spodbuditi razmišljanja o konkretni uporabi UI v mladinskem delu 

Število udeležencev je zaradi narave delavnic omejeno, zato predlagamo, da se čimprej prijavite – povezava do prijavnice.

Vljudno vabljeni k udeležbi in zavedni, odgovorni ter predvsem ustvarjalni rabi najnovejših tehnologij!

Potek delavnice

9:15 – 9:30 Sprejem in uvod

Registracija, pozdrav in predstavitev poteka dneva

9:30 – 10:15 Osnove UI: “Umetna inteligenca in svet”

Uvodno predavanje s primeri, skupinska diskusija

10:15 – 11:45 Etična vprašanja in praktične vaje za razvijanje kritičnega mišljenja

Študije primerov in skupinsko praktično delo

11:45 – 12:30 Odmor za skupinsko kosilo

Pogostitev, odmor in priložnost za spoznavanje prisotnih udeležencev in organizacij

12:30 – 14:00 Praktična uporaba UI orodij za mladinsko delo

Praktično delo v digitalnih okoljih s prosto dostopnimi orodji za uporabo tehnologij U

14:00 – 14:30 Naslednji koraki in zaključek

Skupinski razmislek o konkretni uporabi UI v mladinskem delu, evalvacija

The post Mladinsko delo 4.0: Umetna inteligenca v praksi – odgovorno in uporabno (KOPER) first appeared on Računalniški muzej.

We’re thrilled to announce the spring edition of the Slovenia Ruby User Group meetup!

Mark your calendar on Monday, June 16th, 2025, we’ll be gathering from 18:00 to 21:00 at the Računalniški muzej / Slovenian Computer History Museum.

We’ll be trying out an alternative format this time:
– Show-and-tell
– Open floor discussion

This means that the content of this meetup is entirely up to the attendees!

Have an interesting project you’d like to talk about? Bring it along! Got a technical problem you’d like to discuss? Bring it up! Got new approaches on your mind? Don’t be afraid to challenge the status quo!

As always, we’re keeping the floor open for any lightning talks. If you have an idea, a project, or a Ruby gem you’re passionate about, bring it along!
Post the knowledge exchange, we’ll go for food and drinks.

Whether you’re a seasoned Ruby professional, a newbie who’s just getting started, or anywhere in between, this is the place for you.
Don’t miss out on Summer Ruby meetup!

We can’t wait to see you there.

The post Spring Ruby meetup first appeared on Računalniški muzej.

V prvem delu bo Kristijan Tkalec (kiki, lapor) predstavil plan Zadruge Na Prostem za lokalizacijo in testiranje sistema za vodenje šol, AlekSIS. Namen je, da se migrira slovenske šole na odprtokodne rešitve.

Nato bomo nadaljevali z izdelavo spletne strani in boljših komunikacijskih kanalov znotraj skupnosti. Če bo interes, se dotaknemo še teme https://endof10.org/

vir slike: David Ravoy (CC-BY-4.0)

The post c| srečanje № 26: Zadružno spraviti FOSS v slovenske šole & mostovanje naprej first appeared on Računalniški muzej.

Centralna tehniška knjižnica Univerze v Ljubljani bo v sredo, 25. 6. 2025 zaradi praznika zaprta.

Vaš CTK.

Foto: Nebojša Tejić, STA

Poletni delovni čas

(velja od 7. 7. 2025 do 17. 8. 2025)

ponedeljek, torek, četrtek, petek: 8:00 – 14:00
sreda: 8.00 – 18.00*
sobota: 9:00 – 13:00
*Opomba: v sredo poteka izposoja do 14.00, od 14.00 do 18.00 pa le s pomočjo knjigomata.

Izposoja gradiva:
iz skladišča: 8.00 – 14.00
iz prostega pristopa: 8.00 – 14.00

Ostali oddelki:
ponedeljek – petek: 8.00 – 14.00
sobota: zaprto

Centralna tehniška knjižnica Univerze v Ljubljani v sodelovanju z Makedonsko študentsko organizacijo v Sloveniji vabi študentke in študente na sproščeno jutranje srečanje ob kavi, ki bo potekalo to soboto 13. 6. 2025 ob 9.00 pred vhodom v CTK (Trg republike 3, Ljubljana).

Dogodek je namenjen ustvarjanju prijetnega vzdušja med izpitnim obdobjem – priložnost za druženje, klepet, izmenjavo spodbud in nekaj minut oddiha ob skodelici dobre kave.

Vabljeni, da prinesete svojo najljubšo skodelico – za najbolj izvirne skodelice bomo pripravili simbolične nagrade.

Dogodek poteka v okviru podpornega okolja za študente, ki ga CTK razvija v sodelovanju s študenti.

Veselimo se vaše družbe!

Na Univerzi v Ljubljani bo 11. junija 2025 potekalo strokovno srečanje visokošolskih knjižnic z naslovom “Izhodišča za strateški razvoj knjižničarstva”. Dogodek bo osredotočen na prihodnost visokošolskih knjižnic v luči trajnostnega razvoja, tehnoloških sprememb in odprte znanosti.

Ključne točke srečanja:

• Uvodna predavanja bodo podali predstavniki Univerze v Ljubljani in gostja Martina Pronk iz združenja LIBER, ki bo govorila o strateškem načrtovanju knjižnic.
• Vsebinski sklopi bodo obravnavali:
  • Vrednote v visokošolskem prostoru, kot so odprta znanost, informacijska pismenost in trajnostnost.
  • Tehnološki razvoj, vključno z uporabo umetne inteligence in razvojem slovenskega jezikovnega modela.
  • Odličnost storitev, kjer bodo predstavljeni primeri dobrih praks iz različnih knjižnic UL.

Dogodek bo potekal na Pedagoški fakulteti UL, udeležba pa je možna ob predhodni prijavi.

Povezavi do originalnih objav:

• Univerza v Ljubljani – napoved dogodka
• Knjižničarske novice – podrobnejši opis programa

SCOAP³ (Sponsoring Consortium for Open Access Publishing in Particle Physics) vabi zainteresirano javnost s področja odprte znanosti na spletni forum. Predstavljena bo nova pogodbena struktura SCOAP3 in vrednotenje elementov odprte znanosti, vključenih v novo shemo.

Spletni forum je odprt za vse, vključno s predstavniki sodelujočih institucij iniciative SCOAP3 (nacionalna kontaktna točka za Slovenijo je CTK) ter člani širše znanstvenoraziskovalne skupnosti. Udeležba je priložnost, da se predstavnikom mednarodnega vodstva SCOAP3 in operativni ekipi v CERN-u postavijo vprašanja.

Dogodek bo potekal v četrtek, 18. junija 2025, v obliki spletnega seminarja, čas trajanja je 90 minut. Spletni forum se bo odvijal v dveh programsko enakih sejah, s pričetkom:

1. seja: ob 9:00 (dopoldne)
2. seja: ob 17:00 (popoldne)

Udeležba je brezplačna, prijava na dogodek ni potrebna.

Program (obe seji):

• Uvodna predstavitev: Ianko Lopez, konzorcij Madrono, Španija, predsednik foruma SCOAP3 – 10 minut
• Predstavitev strukture pogodbe 4. faze SCOAP3 in elementov odprte znanosti: Anne Gentil-Beccot, ekipa SCOAP3 CERN – 20 minut
• Rezultati prvega ocenjevanja: Pia Kretschmar, ekipa SCOAP3 CERN – 10 minut
• Perspektiva partnerjev SCOAP3: Anna Vernon, Charles Brophy (JISC, Združeno kraljestvo) – 20 minut
• Perspektiva CrossRef: Helena Cusijn, Kornelia Korzec, CrossRef – 10 minut
• Moderirana razprava z vprašanji udeležencev – 10 minut

Podrobnosti o dogodku in udeležba na forumu sta na voljo na naslednji povezavi: https://indico.cern.ch/event/1549610/.

Univerzitetna knjižnica Univerze v Novi Gorici vabi na delavnici o odprti znanosti, na katerih bodo strokovnjaki iz Centralne tehnične knjižnice Univerze v Ljubljani in ARNES-a predstavili portal Odprta knjižnica: Center za zagotavljanje kakovosti v znanstvenem komuniciranju, neetične prakse založnikov pri znanstvenem objavljanju, avtorskopravna vprašanja ter vlogo storitev in infrastrukture pri napredku znanosti in raziskav.

• Tretja delavnica na temo odprte znanosti na UNG bo v ponedeljek, 2. junija 2025, od 10.00 do 13.45 v Vipavi (predavalnica P-1.5).
  
• Četrta delavnica na temo odprte znanosti na UNG bo v torek, 3. junija 2025, od 10.00 do 13.45 v Rožni Dolini (predavalnica P7-Kompas).

Delavnici bosta potekali v angleškem jeziku. Udeležba je možna v fizični obliki ali prek Zoom-a. Informacije o programu in prijavah so dostopne na zgornjih povezavah.

Delavnici potekata v okviru Odprte knjižnice: Centra za zagotavljanje kakovosti v znanstvenem komuniciranju v okviru Akcijskega načrta za odprto znanost.

Morebitna vprašanja v zvezi z delavnico lahko naslovite na e-pošto: library@ung.si.

Centralna tehniška knjižnica Univerze v Ljubljani vabi raziskovalke in raziskovalce ter druge zaposlene v raziskovalnih organizacijah na predstavitev Raziskovalna etika in integriteta na Univerzi v Ljubljani: strateški razvoj in izzivi.

Univerza v Ljubljani je konec leta 2024 ustanovila novo organizacijsko enoto za raziskovalno etiko in integriteto. Gre za pomemben korak v smeri zagotavljanja odgovornega ravnanja v znanosti, spoštovanja etičnih načel ter preprečevanja neustreznih praks v raziskovalnem okolju. Enoto vodi prof. dr. Nina Peršak, ki bo 19. junija 2025 od 10:00 do 10:45 v prostorih CTK, Trg republike 3, Ljubljana, predstavila organizacijske in vsebinske vidike delovanja Univerze v Ljubljani na tem področju.

Predstavitev je brezplačna in bo potekala le v živo v prostorih CTK. Število mest je omejeno. Vabljeni!

Prijava na delavnico.

Za dodatne informacije pišite na e-naslov info@odprta-knjiznica.si.

Predstavitev poteka v okviru Odprte knjižnice in Akcijskega načrta za odprto znanost.

Centralna tehniška knjižnica Univerze v Ljubljani vas vabi na delavnico Umetna inteligenca in avtorsko pravo v raziskovalni dejavnosti, ki bo potekala 27. maja 2025 od 10:00 do 13:30 v prostorih CTK, Trg republike 3, Ljubljana, in v spletnem okolju Zoom.

Namen delavnice je raziskovalke in raziskovalce ter druge zaposlene v raziskovalnih organizacijah seznaniti z aktualnimi vprašanji avtorskega prava v povezavi z razvojem in uporabo umetne inteligence (UI) ter poudariti odgovornosti raziskovalcev pri uporabi orodij UI z vidika možnih kršitev avtorskih pravic.

Delavnico bo vodil izr. prof. dr. Matija Damjan.

Po uvodni predstavitvi slovenskega in evropskega okvira avtorskega prava bo na delavnici predstavljena uporaba avtorskih del pri usposabljanju modelov UI in vprašanje kršitve avtorskih pravic. Predstavljena bodo avtorskopravna vprašanja v povezavi z izhodnimi vsebinami UI ter odgovornost in etika raziskovalcev pri uporabi orodij UI. Poseben del delavnice bo namenjen razpravi o konkretnih primerih uporabe UI v raziskovalnem procesu. Razprava bo vključevala vnaprej posredovana vprašanja in dileme udeležencev.

Delavnica je brezplačna. Število mest za udeležbo v živo je omejeno.

Prosimo, da udeleženci pošljejo vprašanja, povezana z vsebino delavnice, vnaprej na e-naslov: info@odprta-knjiznica.si.

Prijava na delavnico:

• udeležba prek spleta (Zoom)

Delavnica je financirana v okviru Akcijskega načrta za odprto znanost za izvedbo Ukrepa 6.2 ReZrIS30.

Vabimo vas na otvoritev mikro muzeja, posvečenega pionirju vesoljske tehnologije Hermanu Potočniku Noordungu. Gre za potujočo razstavo, ki obiskovalcem ponuja vpogled v njegovo življenje, delo ter vizijo prihodnosti vesoljskih raziskav. Obenem predstavlja tudi izbrane vsebine Centra Noordung, ki na sodoben način združuje znanost, umetnost in tehnologijo.

Dogodek je v okviru Meseca občanske znanosti, ki poteka aprila.

Program:

• pozdravni nagovor direktorja Centralne tehniške knjižnice v Ljubljani mag. Mira Pušnika,
• nagovor ambasadorke Občanske znanosti dr. Zarje Muršič,
• predstavitev Mreže občanske znanosti – Mitja V. Iskrić,
• predstavitev izobraževalnih aktivnosti Centra Noordung – Monika Tisel.

Po otvoritvi je organizirano še predavanje z naslovom “Noordungove vizije“, ki bo osvetlilo pomen njegove zapuščine ter aktualnost njegovih zamisli v sodobnem času.

Pridružite se nam v petek, 25. aprila 2025 ob 14h v naši knjižnici!

V mesecu maju in juniju 2025 bomo imeli podaljšane vikende

• 10.5., 11.5.
• 17.5., 18.5.
• 24.5., 25.5.
• 31.5., 1.6.
• 7.6., 8.6.
• 14.6., 15.6.
• 21.6., 22.6.
• 28.6., 29.6.

Odprti bomo med 9.00 in 24.00 uro.

V času podaljšane odprtosti bodo nekatere storitve omejene:

• fizični vpis (ali podaljšanje članarine) bo možen le v soboto do 17.00 ure;
• ostali oddelki so med vikendom zaprti;
• izposoja gradiva iz skladišča ni možna;
• knjige si lahko izposodite iz prostega pristopa preko knjigomata;
• gradivo lahko vrnete preko knjigomata.

Mestna občina Ljubljana (MOL) je skrbnica številnih nepremičnin, tudi tistih, v katerih delujejo šole, vrtci, kulturne, športne, zdravstvene in druge javne ustanove; v njeni domeni je upravljanje, urejanje in vzdrževanje lokalne javne infrastrukture, kot so ceste, trgi, kolesarske steze in pločniki, parkirišča, parki, otroška igrišča, kopališča, pokopališča; pa tudi vzdrževanje in skrb za ljubljanske mestne gozdove. Nepremičnega premoženja in z njim povezanih obveznosti ima torej ogromno, vzdrževanje in prenova pa potekata pod geslom “Prenavljamo. Za vas.”

To geslo je v očeh MOL piarovsko izvrstno. Neposredno naj bi nagovarjalo prebivalce Ljubljane ter druge uporabnike mesta in jim dajalo občutek, da je prav vsa energija, vložena v projekte prenove, namenjena le njim: izboljšanju njihovega bivalnega okolja in izboljšanju kakovosti življenja v že tako “najlepši prestolnici”. Osnovna premisa gesla je, da vse izhaja iz čudovito skrbnega odnosa do javnega dobra in dobra vsakokratnega prebivalca.

Žal je resničnost povsem drugačna.

Primer prenove Trga mladinskih delovnih brigad (Trg MDB)

Prostor nenavadne, skoraj trikotne oblike na stičišču Tržaške ceste, Aškerčeve in Rimske ulice ter Prešernove ceste in Groharjeve ulice so leta 1956 poimenovali Trg mladinskih delovnih brigad in tako simbolično počastili spomin na organizirane delovne skupine mladih prostovoljcev, ki so zlasti v povojnem obdobju v nekdanji Jugoslaviji opravljale dela javnega pomena.

Na severnem delu območja, prepredenega s prometnimi cestami in precej zasedenega s parkiranimi avtomobili, je bil umeščen manjši park z zelenico in brezovim gajem, ob katerem sta stala tramvajska vagona z gostinsko ponudbo. V prostoru so bila precej zaznavna visoka drevesa ob križišču Rimske ulice in Prešernove ceste, ki so v vročih poletnih dneh s prijetno senco ščitila letni vrt nekdanje gostilne Lovec.

V zadnjih letih MOL na tem območju nadaljuje intenzivno in invazivno prenovo prometne infrastrukture. Celoviti prenovi Tržaške ceste je leta 2021 sledila še korenita prenova Trga MDB z uradnim namenom “zvišati kakovost javnega prostora in Trgu mladinskih delovnih brigad povrniti vlogo trga, območje pa narediti privlačnejše tudi za ponudnike poslovno-trgovskih storitev”. Projekt urbanistično-arhitekturne ureditve je bil, kljub investiciji, ki presega zakonsko določeno vrednost, naročen brez javnega natečaja, njegova predstavitev in javna obravnava pa nejasni in zavajajoči.

Na severnem delu trga tako avtomobilov ni več, tramvajska vagona sta izginila, odstranjenih je bilo tudi nekaj zdravih in košatih dreves. Urejena je bila enotna ploščad za mešani promet pešcev in kolesarjev, v osi Tržaške ceste stoji nov spomenik braniteljem mesta Ljubljane leta 1991. Na novi ploščadi je tudi prostor za parkiranje lastniških koles in postajališče za Bicikelj, ne manjka niti pitnik – unikatno oblikovana skulptura. Obseg zelenih površin je radikalno zmanjšan – zelenice, ohranjen brezov gaj in nekaj na novo zasajenih drevesc so ujeti v pravilne okrogle izreze v novem tlakovanju. Močno zaznaven in prepoznaven element nove urbane opreme so dolge klopi in okrogli nizki elementi iz svetlega teraca, ki “usmerjajo” oziroma – bolje rečeno – ovirajo poti pešcev in kolesarjev, hkrati pa preprečujejo dostop avtomobilom. Celota po svoje deluje sterilno, hkrati pa je prenasičena z elementi urbane opreme. Da bi prostor lahko postal prijeten za preživljanje prostega časa, ni zelo verjetno, saj je povezava trga proti izredno prometni cesti premočna in preveč odprta.

Trg MDB ima novo, svetlejšo fizično podobo, urejeno in očiščeno neželenih avtomobilov, vendar s tem tudi preprečen dostop z avtomobili stanovalcem in ponudnikom poslovno-trgovskih storitev do stavb na zahodni strani ploščadi. Mogoče je estetsko nadgrajena ploščad res privlačnejša, a gotovo manj praktična za ponudnike poslovno-trgovskih storitev, nikakor pa ne pripomore k boljši kakovosti življenja okoliških stanovalcev, še manj k varnejšemu in prijetnejšemu doživljanju prostora za vse, tudi za naključne obiskovalce.

Trg MDB leži ob enem najprometnejših križišč v mestnem središču in se po podatkih ARSO uvršča med točke v mestu, najbolj onesnažene s prašnimi delci. Da bi se okoljski kazalniki izboljšali, so si najbližji sosedje ob napovedani prenovi želeli predvsem obširnejše ozelenitve tega območja in zasaditve gostih zelenih ovir med glavno prometnico in trgom. Opravljena prenova tako nikakor ne izpolnjuje pričakovanj, hkrati pa tudi ne sledi najnovejšim trendom trajnostnega razvoja, ki jih določa boj proti podnebnim spremembam: na območju je precej manj travnatih in veliko več tlakovanih površin kot pred prenovo, popolnoma po nepotrebnem so podrli več zdravih, odraslih dreves, tudi vse kostanje, ki so rasli pred nekdanjo gostilno Lovec. Nekatera odstranjena drevesa so bila sicer nadomeščena z mladimi drevesci, a ta še dolga leta ne bodo mogla tako blagodejno učinkovati na mikroklimo tega območja, kot bi ohranjeno vitalno odraslo drevje – vprašanje pa je, ali se ne bodo prej posušila, tako kot številna mlada drevesa, ki jih je na enak način v beton in pesek posadila MOL. Velike tlakovane površine, četudi svetle, položaj le še dodatno poslabšujejo.

Stanovalci hiš na zahodni strani trga, ki večinoma živijo v najemniških stanovanjih, so bili po prenovi območja postavljeni pred neprijetno dejstvo, da čez novo ploščadi z avtomobili nimajo več dostopa do hiš, niti v posebnih primerih ali primerih nujne intervencije (dostava, rekonstrukcija, reševalno vozilo, gasilci id.). Najprej je bilo sicer načrtovano, da bo na prenovljenem trgu promet urejen po načelu skupne rabe prostora (shared space), vendar je še v času gradnje “zaradi neprimernega ravnanja nekaterih voznikov motornih vozil, ki so z nevestno vožnjo in parkiranjem uničili nove površine”, prišlo do enostranske in z oškodovanimi prebivalci neusklajene spremembe. Trg je postal le pešcem in kolesarjem namenjeno območje, kjer pa poti pešcev in kolesarjev niso jasno razmejene. Ker je območje kolesarsko zelo obremenjeno, je taka ureditev manj primerna, saj se zaradi nje oboji, pešci in kolesarji, pogosto znajdejo v nevarnih, stresnih in konfliktnih situacijah.

Dostop do objektov na zahodni strani trga ob novi ploščadi je mogoč le z zadnje, to je dvoriščne strani, čez funkcionalna zemljišča in dvorišča v notranjosti območja stanovanjskih blokov Vrtača, zamejenega z zapornico. Lastniki problematiziranih objektov, ki v njih praviloma ne živijo, so mestu – za ceno asfaltiranja notranjih dvorišč na račun investicije za prenovo trga – tako rešitev potrdili. Etažni lastniki funkcionalnih zemljišč, po katerih služnostna pot poteka, pa dodatni obremenitvi z avtomobili za dovoz do stavb, za katere služnost ni dogovorjena, nasprotujejo. Argumenti za nasprotovanje temeljijo na povečanju prometa skozi sosesko, s čimer je zmanjšana varnost na dovozu brez urejenega pločnika, preozkem za dvosmerni promet, povečane so obremenitve okolja z izpuhi in hrupom, vse to pa občutno poslabšuje bivalne razmere v soseski.

Oškodovani stanovalci so oktobra 2021 na MOL naslovili nasprotovanje in zahtevo, naj se dostop z motornimi vozili do objektov ob novi ploščadi ponovno zagotovi. Z mestne občine so prejeli odgovor, da prenovitvena dela še niso končana in da je sedanje stanje “le začasna ureditev”. Na pobudo stanovalcev je bil na lokaciji sklican tudi sestanek z ljubljanskim županom, ki se je razvil v neprijeten dogodek, na katerem so bili stanovalcem arogantno predstavljeni “močni” argumenti, bolje rečeno argumenti moči, zakaj bo začasna ureditev (p)ostala stalna: “Zato, ker sem se jaz tako odločil.”

Zaradi glasno in odločno izraženega nezadovoljstva z novo ureditvijo so bili kritiki deležni celo obiska inšpekcije MOL: zahtevala je odstranitev zapornic, ki naj bi bile postavljene nepravilno. Zapornice so ostale, saj je bilo v nadaljnjih postopkih dokazano, da nepravilnosti ni – postavljene so bile skladno s pridobljenim soglasjem pristojnih služb že leta 1998.

Čeprav bi bila ureditev omejenega in nadzorovanega dostopa z motornimi vozili do objektov preprosto rešljiva z vgradnjo enega samega potopnega stebrička, ki bi zamenjal en betonski omejitveni element, je po več kot letu položaj še vedno nespremenjen.

V realizaciji projekta, ki ne prispeva k okoljskim izboljšavam in ne upošteva socioloških elementov, to je potreb in želja okoliških stanovalcev – ki so v resnici izredno skromne in bi jim bilo preprosto ustreči – poleg tega pa je njegova ekonomska upravičenost vprašljiva, se kaže dejanski odnos načrtovalcev in mestne oblasti do meščanov in mestnega proračuna.

Primer prenove Plečnikovega podhoda

Vzporedno s prenovitvenimi deli na Trgu MDB je potekala tudi preobrazba Plečnikovega podhoda (povezave parka Zvezda s Plečnikovim trgom pred Maximarketom), le 14 let po zadnji – celoviti – prenovi. Kaj je bil razlog za to popolnoma nepotrebno, več kot milijon evrov vredno investicijo, lahko samo špekuliramo, kajti na spletni strani MOL najdemo zgolj skopo obvestilo: “S prenovo smo popestrili in oživili prostor podhoda in ga naredili privlačnejšega, predvsem pa varnejšega za uporabnike. Obnovili smo talne, stropne in stenske površine, uredili lokale ter javne sanitarije.” Konkretnih razlogov, ki bi klicali po takojšnji intervenciji, kot so zamakanje, nevarni tlaki, poškodbe, ni bilo. Prenova, ki je bila namenjena izključno “face-liftingu”, je bila, kot kaže, pravzaprav izkoriščena za umestitev novih lokalov ob stranice podhoda. Prvotna ureditev je bila preprosta, funkcionalna in trpežna, posebna zaradi zanimivih kovinskih oblog sten, namenjena pa je bila izključno povezavi med trgoma za pešce in kolesarje. Zamenjala jo je modna podoba z velikimi steklenimi vitrinami iz krivljenega stekla, za katerimi samevajo prazni lokali, saj zanje ni nobenega zanimanja; pešci in kolesarji pa so prisiljeni vijugati po preostalem, močno zoženem vmesnem prostoru.

Gre za šolski primer privatizacije urbanega prostora in podrejanja tržni logiki, ki pa se v tem primeru glede na samevanje novih prostorov ne more upravičiti niti s pričakovanim dobičkom, kar pomeni, da gre za še en propadel posel, zaradi katerega je javni prostor okrnjen.

Primer Slovenske ceste

Posledice fenomena privatizacije urbanega prostora so dobro opazne na osrednji ljubljanski ulici – Slovenski cesti, kjer se je občina lotila zahtevne naloge preobrazbe glavne mestne prometnice (po kateri je bila vožnja s kolesom prepovedana) v javni prostor, namenjen pešcem, kolesarjem in uporabnikom javnega potniškega prometa. Že leta 2013 je bila na osrednjem delu Slovenske ceste uvedena sprememba prometnega režima, s katero je bila odpravljena tranzitna pot za osebni motorni promet, omogočila pa je vožnjo kolesarjem. Sledila je celovita prenova: na osrednjem delu površine je urejeno ožje cestišče s svetlim betonskim tlakom, namenjeno avtobusom in dostavi, široke površine na obeh straneh cestišča, v sklopu katerih je bil zasajen tudi nov drevored malih jesenov, pa so namenjene uporabi pešcev in kolesarjev.

A navidezno razkošne površine, namenjene pešcem in kolesarjem, so se hitro začele krčiti. Že izvorno so bile na teh površinah urejene sive in sterilne avtobusne postaje z dolgimi linijami nadstrešnic, načrtovana pa je bila tudi umestitev številnih elementov urbane opreme, kot so klopi, stojala za kolesa, koši za smeti. Kasneje so se pojavili prostostoječi tristrani panoji in osvetljene vitrine za reklamno oglaševanje, katerih število se neprestano povečuje, čeprav ovirajo pešce in kolesarje, zmanjšujejo preglednost nad prostorom, odvračajo pozornost mimoidočih in preprečujejo oziroma uničujejo razgled na tako imenovano najlepše mesto na svetu. Najspornejša pa je ureditev zunanjih “teras” gostinskih lokalov, umeščenih ob Slovenski cesti, ki vsako sezono zasedajo več kvadratnih metrov javnega prostora. Gre za tiho polaščanje in prikrito privatizacijo mestnega prostora, ki je vedno bolj izpostavljen tržni logiki. Prebivalci smo vse manj “lastniki” oziroma “upravniki” svojega mesta, to razlastninjenje pa poteka pod krinko napredka in izboljšav.

Žal tudi na severnem in osrednjem delu Slovenske ceste, enako kot na Trgu MDB, površine, namenjene vožnji s kolesom, niso jasno opredeljene, tako da morajo kolesarji najti najugodnejšo pot glede na trenutne razmere: če na cesti ni avtobusov, je seveda izbira cestišče (kolesarjenje z avtobusom tik za hrbtom ni prijetno, obvoz na postaji stoječega avtobusa po sredini cestišča pa je, če v nasprotni smeri pripelje drug avtobus, skoraj smrtno nevarno početje, saj med voziloma ni dovolj prostora za varno vožnjo), sicer pa so prisiljeni v iskanje poti med vsemi v prostor umeščenimi “ovirami” in pešci. Kolesarji so sicer dobili dovoljenje za vožnjo skozi mestno središče, a kako se bodo skozenj prebili, se morajo odločiti sami. Načeloma je zanje priporočena uporaba peščevih površin, hitrost vožnje pa mora biti prilagojena hitrosti hoje. Dejansko večina kolesarjev, ki uporabljajo peščeve površine, kljub priporočilom ne prilagaja hitrosti vožnje hitrosti pešcev, hkrati pa veliko pešcev popolnoma prezre to, da so površine namenjene skupni rabi, in na kolesarje niso pozorni. Plod trenutne prometne ureditve in prometne (ne)kulture udeležencev so nevarne situacije za pešce, mimo katerih nevarno hitro in nevarno blizu švigajo živčni ljudje na kolesih, in za kolesarje, ki jim nepozorni pešci brez nakazane namere, da bodo spremenili smer hoje, nepričakovano zaprejo pot. To pravzaprav za kolesarje ni velika pridobitev.

Primer prenove Tavčarjeve ulice in Miklošičevega parka

V istem obdobju kot Trg MDB je bila prenovljena tudi Tavčarjeva ulica skupaj z Miklošičevim parkom. Javne površine so dobile nove tlake, javno razsvetljavo, nekaj elementov nove urbane opreme, poskrbljeno je bilo za ureditev zelenih parkovnih površin, izvedene so bile izboljšave za pešce in javni potniški promet. A bistvena bi bila ureditev dvosmernega prometa za kolesarje v sicer enosmerni ulici. Posebej označena kolesarska steza je urejena v smeri vožnje motornega prometa, kolesarska steza, ki bi bila namenjena vožnji v nasprotni smeri, pa ni bila izvedena, da so ob cesti lahko uredili pas parkirišč in da sta za motorni promet ostala dva ločena vozna pasova, eden za zavijanje na desno in drugi na levo.

Zamujena je bila torej lepa priložnost za izvedbo prenove ulice in uvedbo nove prometne ureditve, ki bi bila skladna s smernicami Prometne politike MOL in Celostne prometne strategije, katerih ključni cilj je omejevanje osebnega motornega prometa in spodbujanje ljudi, da uporabljajo bolj trajnostne načine transporta – pešačenje, kolesarjenje in javni prevoz.

MOL prenavlja. Brez nas.

MOL prenavlja. Domnevno za nas, meščanke in meščane, a pravzaprav brez nas. Brez pravočasnega dialoga z javnostjo, brez upoštevanja potreb in želja meščanov in najpogosteje s popolnim neupoštevanjem oziroma zavračanjem dobronamernih opozoril glede pomanjkljivosti predvidenih ali izvedenih rešitev.

MOL prenavlja. Za nas. A brez nas. Kot da MOL bolje od nas ve, kaj potrebujemo in kaj je za nas koristno. Naše pripombe in kritike niso samo nezaželene, pogosto so prezrte in še večkrat cinično zavrnjene, so tudi namerno utišane. V zameno pa v MOL pričakujejo, da bomo prebivalci in prebivalke Ljubljane samo tiho hvaležni in veseli, ker naj bi oblastniki tako dobro skrbeli za nas in za naše skupno dobro. Če ljubljanske mestne oblasti ne morejo razumeti, da je njihova poglavitna vloga braniti splošni interes in skrbeti za kakovostno urejanje prostora ZA VSE, ki v mestu živijo, potem moramo kaj ukreniti. Če MOL deluje invazivno, moramo prebivalci ukrepati radikalno.

Začnimo s prispodobo: novodobni »ljubljanski zmaj« grozi, da bo mestnemu organizmu iz njegovega najožjega, najvitalnejšega dela starega mestnega jedra, iz njegove znamenite tržnice, »iztrgal srce« in mu s tem ukradel tudi »dušo«, njegov »elan vital«, ki se skriva v večplastnem, pisanem in živahnem fenomenu te posebne, javne, odprte tržnice.

Nadaljujmo strokovno: pri t. i. prenovi tržnice, katere ključni del v njeni sredici, na območju nekdanjega samostana, predvideva ogromno podzemno garažo, gre za velik anahronizem, za poskus promocije že davno preživelega koncepta, ki se v času svetovnih metakriz, nujnosti vzdržnega razvoja, zelenega prehoda, odzivov na podnebne spremembe, trajnostne mobilnosti, participacije – v odprti, sodobni, demokratični družbi nikakor ne bi smel zgoditi! Garaža v ta prostor ne sodi po nobenem od strokovnih ali življenjskih meril kakovostne presoje: po prometnem, urbanističnem, arhitekturnem, dediščinskem, arheološkem, geološkem, hidrološkem, gradbeno-tehničnem, socialnem, pietetnem, simbolnem, duhovnem, agrikulturnem id.

Oglejmo si pobliže ta napovedani poseg, ki bi bil za izjemne okoliške stavbe in ljudi med njimi katastrofalen in ireverzibilen!

Urbicid je izraz, ki opisuje namerno uničevanje ali »ubijanje mesta«, z neposrednimi ali posrednimi sredstvi. Izraz so sprva uporabljali urbanisti in arhitekti za opis praks prestrukturiranja mest v Združenih državah Amerike v 20. stoletju. Za uničevanje materialnega in duhovnega bogastva ter življenja v mestu se sicer uporabljajo različna sredstva (bombardiranje, neustrezni urbani posegi, prenaseljenost ob preveliki gostoti, onesnaževanje z nečistimi tehnologijami in druga).

Kratka zgodovina povsem preživelega projekta

Leta 2009 je bila izdana posebna številka mednarodne revije za teorijo arhitekture Arhitektov bilten z naslovom Gradbišče Ljubljana. V njej se nas je kar nekaj avtorjev ukvarjalo z grožnjo načrtovane garaže pod osrednjo ljubljansko tržnico, pa tudi z drugimi bolj ali manj spornimi gradbeno-arhitekturnimi temami v prestolnici.

Sam sem svoj prispevek naslovil Ljubljana; Potemkinova vas? Turbo urbanizem in arhitektura na primeru Ljubljane in njene tržnice in v njem na celovit način prikazal razloge, zakaj je gradnja garaže pod tržnico v vseh pogledih nelegitimna: strokovno, družbeno, ekološko in etično.

Zgodba se je začela že nekaj let prej, leta 2006, takoj po volitvah, ko je župan s svojo ekipo napovedal projekt garaže pod tržnico. Takrat je bila ustanovljena civilna iniciativa »Tržnice ne damo«, ki smo se ji pridružili generacijsko, strokovno in človeško zelo različni zaskrbljeni prebivalci mesta.

Že takrat pa je bilo kritičnemu strokovnemu pogledu kristalno jasno, da gre za zastaran projekt iz nekih povsem drugih časov, ko je bila modernizacija Evrope po vojni imperativ in je odmev generičnega modernizma s svojim mobilizacijskim potencialom, ki je ignoriral stara mesta, dediščino in tradicijo, na naši celini s svojimi posegi naredil več škode kot med vojno Luftwaffe, kot se je z obžalovanjem, a duhovito izrazil nobelovec Josif Brodski.

Po opravljeni temeljiti kritiki moderne, smo soočeni s povsem drugačnimi preizkušnjami. Goli »progresizem«, ki je zagovarjal prostorski napredek za vsako ceno, je že vsaj od sedemdesetih let (»meje rasti«), jasneje od devetdesetih (Agenda 21 in načela trajnostnega razvoja) in še posebej danes popoln anahronizem. Preživel je predvsem v manj demokratičnih okoljih, kjer neodvisna strokovnost in transparentna participacija javnosti nista spoštovani. Takšna družbena okolja (ljubljanska demokratura je značilen primer) niso ozavestila spremenjene paradigme, ki izhaja iz skupne zavesti, da živimo v časih resnih metakriz (ekološke, energetske, etične, socialne, vojne, migrantske …), ki jih je treba reševati s povsem drugimi, vzdržnimi, sonaravnimi, kulturnimi, regenerativnimi, odprtimi pristopi. Tako usklajeni in senzibilizirani odnosi na strokovnih poljih in znotraj participativne demokracije vodijo v varovanje in razvoj javnega dobra (in javnih prostorov), ne pa v špekulativne, tendenciozne zagovore partikularnih interesov.

Izvotljeni smisel in namerna slepota: hiter pregled projekta po temah

Stroka ne nasprotuje resnični prenovi tržnice, ki bi vključevala (pre)ureditev programov, talnih površin (npr. z označenimi tlorisi samostana in drugih stavb), urbane opreme ter podzemnega muzeja na območju srednjeveških vzhodnih vrat in barbakana (npr. po predlogu arhitektov Kovača in Kerševana), a garaža v to kategorijo seveda ne spada. Programsko prenovo (ki jo na MOL absurdno navajajo kot enega izmed glavnih razlogov za garažo) bi lahko že davno začeli, saj imajo upravljanje tržnice v svojih rokah. Tudi ostali smiselni vidiki prenove bi že lahko potekali, a mestna oblast trmasto in slepo, kljub prevladujočim odklonilnim stališčem vpletenih strok in javnosti, vztraja pri tem skrajno agresivnem projektu, ki je sporen prav z vseh zornih kotov.

V urbanistično-prometnem smislu je povsem jasno, da garaža v srednjeveško mestno jedro ne sodi! V duhu trajnostne mobilnosti se mora sodobni individualizirani promet ustaviti na zunanjih ali morebiti notranjih prometnih obročih (P + R, »park and ride«), od tam pa naj za dostop v mesto prevladujejo dober javni promet, kolesarjenje in pešačenje. Prav zaradi oblikovanja javnih mestnih prostorov v merilu človeka so bila dela Jožeta Plečnika leta 2021 razglašena za Unescovo, izjemno, univerzalno dediščino človeštva! Na Vodnikovem trgu pa bi »drzni snovalci prenove« promet z uvoznimi (30-metrskimi!?) klančinami pripeljali na peščeve površine tik pred Plečnikove arkade ob Zmajski most. Ali je komu mar, da bi njegova arhitektura zaradi takega posega zelo verjetno ne le na tržnici, temveč v celoti izgubila status svetovne dediščine?

V »arhitekturnem« smislu gre za najhujši možni kontrast: za vdor v najžlahtnejši in najvitalnejši del mestnega jedra z najbolj banalno, zgolj utilitarno podzemno strukturo, ki nima nobene dodane vrednosti. Med izjemno stavbno dediščino, v prostor torej, do katerega je treba pristopati skrajno spoštljivo in z veliko mero občutljivosti: med Plečnikove tržnice, stolnico, semenišče, župnišče, srednjeveške meščanske stavbe in Mahrovo hišo naj bi se v mehko sredico nekdanjega frančiškanskega samostana z njegovim križnim hodnikom, na območje najstarejših ljubljanskih pokopališč, med mnoge v grobnice pokopane žlahtne meščane umestil ogromen betonski kolos, namenjen avtomobilom. Ta bi pregreval prostor, tudi drevesa na raščenem terenu bi padla, »učinek vroče točke« bi se še povečal, hkrati pa bi ustvaril veliki jez za zaledne vode,  ki mu ne bi uspelo zadržati ali ponikati meteornih voda. Čeprav se ve, da MOL že ves ta čas, kljub večinskemu nasprotovanju stroke in prebivalcev, vodi (netransparentne) postopke s svojo sporno agendo, so pri zavarovanju tega prostora zatajili skoraj vsi odločevalci, od kulturnega in prostorskega ministrstva do Zavoda za varstvo kulturne dediščine (ZVKDS), ki jim v letih, ko je bila grožnja za poseg več kot očitna, ni uspelo doseči temeljitega zavarovanja tega izjemnega kompleksa.

Pomensko, ontološko je morda najmočnejši razlog, ki poleg zaščite vrhunske dediščine govori proti garaži pod tržnico, pietetne in etične narave. Ugrez betonskega kolosa v sredico nekdanjega samostanskega kompleksa ne bi bil le brezobziren potop v zgodovino, temveč bi se dotaknil zelo občutljivega, najstarejšega odnosa v človeški družbi: odnosa do umrlih, pokopanih prednikov. Na tem vprašanju se kulture vzpostavijo ali padejo, pa zato ni treba v prazgodovino ali do antične Antigone, ampak sežejo te etične dileme tudi v sodobni čas. Od župana bi sicer težko pričakovali ozaveščen, kaj šele kulturen odnos do pokojnih na ljubljanskem teritoriju (ve se, da pokojnikom, »ki mu niso pogodu«, ne dopusti pokopa na ozemlju MOL-a!?), kljub vsemu pa se pri tej temi čudimo odsotnosti večje ozaveščenosti pri vseh vrstah notranjih in zunanjih sodelavcev.

Socialni, ekološki, agrikulturni vidik: ne nazadnje se dotaknimo še tistega manj materialnega vidika tržnice, ki pa predstavlja najbolj vitalni, regionalni in lokalni del utripa starega mestnega jedra, torej življenja na njej sami! Vrnimo se k temeljem agri-kulture, torej k prvi med kulturami, ki nam vsem omogoča, da na tem planetu sploh preživimo. Tržnica, zasnovana po zgledu antične Agore in Stoe (ki ju je Plečnik tako izvirno in vrhunsko reinterpretiral), je prostor srečevanja in izmenjave dobrin – živilskih in tudi kulturnih, človeških nasploh. Prebivalci Ljubljane že dobro stoletje udejanjajo živo tradicijo »romanja na tržnico« (še posebej ob sobotah), kjer lahko izbirajo ne le doma pridelane, izbrane izdelke z regionalnih kmetij, temveč se srečajo z branjevkami, prijatelji ali naključnimi obiskovalci ali turisti. Kljub županovim pritiskom večina domačih prodajalcev (a ne posrednikov) nasprotuje garaži pod tržnico, zavedajoč se, da bi večletna »ugasnitev« delovanja na tej lokaciji pregnala ne le njih, temveč verjetno onemogočila tudi ponovno oživitev danes povsem žive tradicije (saj lahko predvidimo umik kupcev v nakupovalna središča).

Postavimo enačbo: na eni strani katastrofalen ogljični odtis garažnega objekta (z vsemi zelo verjetnimi hudimi posledicami za objekte kulturne dediščine vred), na drugi pa kritični čas t. i. zelenega prehoda, Novega evropskega Bauhausa, načel regenerativnega razvoja itd. Večje nasprotje si je težko zamisliti, celo v našem mestu; namesto da bi že pred leti zakopali tam, kjer bi se res lahko zgodile strukturne spremembe, torej pri poglobitvi železnice, ki bi ponovno povezala središče Ljubljane z njenim severom in zahodom, hočejo kopati tam, kjer je najmanj primerno, v sami sredici mesta.

Hkrati pa iz MOL skoraj perverzno zvenijo izjave, s katerimi se mesto še vedno prodaja kot »zelena prestolnica Evrope«, saj počne številne skoraj diametralno nasprotne reči: izpeljala je velike, nestrokovne goloseke na Rožniku – v zadnjem letu celo na erozijsko občutljivih strminah Grajskega griča, še vedno nam grozi skrajno invazivni poseg »prenove« Plečnikovega stadiona, v Tivoliju se je zgodila urbanistično, arhitekturno in materialno izjemno sporna megastruktura Ilirije in pod sabo pokopala Bloudkovo diskretno zasnovo kopališča. Vrh vsega se je pri potniškem središču Ljubljane pred kratkim začela graditi urbanistično slabo zasnovana in arhitekturno generično oblikovana, zgolj komercialna Emonika. Še slabše pa kaže s šibko, necelovito premišljenimi in načrtovanimi »novimi« železniškimi povezavami skozi mesto in okoli njega. Ali kot je že pred leti zatrdil prijatelj; kjer ni vizije, vladajo provizije! Morda danes velja še bolj v drugo smer: kjer vladajo provizije, ne more biti prave vizije (razvoja)!

Vsa zagotovila MOL-ove »stroke«, da do poškodb na objektih ter težav z vodami (ki proti Ljubljanici pritiskajo z Grajskega griča in okolice) nikakor ne more priti, so seveda bolj »pobožne želje« oz. tendenciozno zavajanje. Geo- in hidromehanik z dolgoletnimi bogatimi izkušnjami (tudi v tujini) zatrjuje, da na tako težek teren za gradnjo, kot je na tej lokaciji, v življenju še ni naletel. Resne poškodbe na semeniščnem objektu, ki v knjižnici premore tudi vrhunske Quaglieve freske, pa tudi na Plečnikovih arkadah ob Ljubljanici, so se pokazale že med gradnjo Mesarskega mostu.

Takšna vrsta posega se v razviti Evropi danes ne bi mogla zgoditi, vse »primerjave«, ki se skušajo uporabiti za njen zagovor, pa so skoraj povsem neprimerljive z večplastno in kompleksno naravo Vodnikovega trga in deplasirane – tako po lokacijah, bogastvu dediščine, razlogih za poglobitev, tehničnih okoliščinah gradnje, socialni dinamiki v prostor. Dve primerljivi garaži (čeprav v manj občutljivem kontekstu) so pred nekaj leti sicer začeli graditi v Novem Sadu, a sta obe na okoliških objektih povzročili resne razpoke, prodiranje vode itd., pa še končani nista. Medtem politika v mestu, ki je bilo s porušenim nadstreškom in žrtvami jeseni povod za velike študentske proteste v Srbiji, napoveduje še garažo pod osrednjo (Ribjo) tržnico (!?), prebivalci pa so se že povezali v civilno iniciativo, da bi jo ubranili!

Predstavniki stroke, ki tak poseg zagovarjajo, odražajo po eni strani zelo šibko in plitko kulturno zavest, po drugi strani pa naivno prepričanje, da je mogoče v tako občutljivem kontekstu vse natančno predvideti, zadostiti bistvenim lastnostim zgradb in pravilom stroke ter se pri tem še izogniti hujšim posledicam invazivnega posega.

Boljša možnost: garaža pod grajskim hribom

Resni strokovnjaki se zavedamo, da za garažo pod tržnico obstaja nesorazmerno boljša možnost: garaža pod grajskim hribom (primerljiva bi bila s tisto v Salzburgu)! Zasnova zanjo je bila pripravljena in predstavljena že pred nekaj leti, v tekmi primerjalnih kategorij pa tisto pod tržnico prekaša tako rekoč v vseh parametrih, saj:

• ne bi posegla v izjemno kulturno dediščino okoli Vodnikovega trga;
• s klančinami ne bi posegla v odprti prostor za pešce pred Plečnikovimi arkadami (se pravi, v Unescovo dediščino);
• bi tržnica nemoteno (ali le z minimalnimi zastoji v primeru prenove tlakov in drugih potrebnih posegov) delovala še naprej;
• je geologija grajskega griča za poseg ugodna;
• med gradnjo mehanizacija ne bi povzročila hudih težav s hrupom, vibracijami, prašenjem;
• garaža v hribu ne bi posegla v lastniška razmerja;
• bi bistveno bolj celovito in radialno napajala celotno srednjeveško mestno jedro;
• bi ponujala občutno več parkirnih mest in bi bila ekonomsko nesorazmerno cenejša od predlagane, za katero so ocene za parkirno mesto že zrasle v vrtoglave višine!

Ljudje in strokovnjaki jasnega uvida in dobre volje se zaradi vsega napisanega še vedno entuziastično borimo za prave rešitve in za-upamo, da bodo – kot v primerljivi bitki »med Davidom in Goljatom« – navsezadnje zmagale pravica, resnica in lepota!

Preteklo soboto, 14. junija, smo na Osrednji ljubljanski tržnici pod Plečnikovimi arkadami pripravili javno tribuno, na kateri so obiskovalci, branjevke, strokovnjaki in druge uporabnice predstavili svoje izkušnje s tržnico in poglede na prenovo, ki jo načrtuje Mestna občina Ljubljana (MOL) in vključuje tudi gradnjo podzemne garažne hiše.

Klara Stanič: »Podrobno sledim, kaj se dogaja. Redno obiskujem tržnico, ker stanujem blizu in ker sem prepričana, da je bolje, da gre denar prodajalcem na tržnici kot trgovskim verigam. Rada bi poudarila, da v medijih doslej še ni bila posebej omenjena finančna konstrukcija prenove tržnice in gradnje garažne hiše, ki naj bi ju plačali davkoplačevalci. Branjevkam, branjevcem naj bi s tem dali parkirna mesta, ampak nihče ne pove, za koliko denarja in kako naj bi se vse skupaj financiralo ter amortiziralo. V zvezi s tem smo zaprosili za informacije javnega značaja, ampak smo z MOL dobili odgovor, da nam teh podatkov ne morejo dati, ker sta prenova in gradnja razporejeni na različne postavke. Že zdaj je treba opozoriti, da bo to ogromen zalogaj. Prejšnji teden smo dobili informacijo, da naj bi celotna investicija znašala 61,3 milijona evrov, vendar ni jasno, na podlagi česa je bil izračunan takšen znesek. Jasno pa je, da bo s tem projektom fizično na tržnici in tudi finančno v proračunu nastala velika luknja. Izvedeti moramo, kako in kdaj bo MOL to luknjo zapolnil.«

Martina Lipnik: »Osrednja ljubljanska tržnica je izjemna kulturna dediščina, ki bi bila po teh načrtih, kot kaže, uničena. Prva stopnja arheoloških raziskav bi lahko trajala leto ali dve, kar pomeni, da bo v tem času vse stalo. Glede na vse nejasnosti bodo gradbeni projekti v tem času obstali v zraku, kljub temu pa se že pridobiva gradbeno dovoljenje. Tudi presoja vplivov na svetovno kulturno dediščino pod varstvom Unesca, kar Plečnikove tržnice so, še ni bila opravljena. MOL je raje pridobila pravno mnenje, da Unescovo varstvo nima veljave pri pridobitvi gradbenega dovoljenja. Dokumentacija je tako izjemno pomanjkljiva in drugačna niti ne more biti. Tudi poročilo o vplivih na okolje, na katero se sklicuje soglasje Zavoda za varstvo kulturne dediščine, je pomanjkljivo. Težava bo nastala, če bo gradbeno dovoljenje na ministrstvu za okolje in prostor dejansko izdano, saj tega za nazaj potem ne bo mogoče več spreminjati. Obravnava na ministrstvu je pretekli teden potekala, kot da gre za običajen objekt brez vpliva na okolje, kar je škandalozno. S tem posegom se bo namreč spremenila hidrogeologija območja. Da bi ugotovili morebitne vplive, bi morali namestiti pet pezometrov za meritve zemeljnih in vodnih razmer pod zemljo. Na izsledke bi bilo treba počakati vsaj eno leto, medtem pa se sploh ne bi smelo projektirati.«

Milan Kovač: »Dve tretjini življenja se že ukvarjam z arheološko dediščino. S kolegom Petrom Kerševanom sva se s prenovo tržnice začela ukvarjati že leta 2008 in tudi oblikovala zamisel za prenovo, ki bi vključevala arheološki muzej (Kovačev in Kerševanov idejni projekt podrobneje predstavljamo na tej povezavi). Dediščina na Osrednji ljubljanski tržnici ni izjemna le v slovenskem prostoru, ampak na evropski ravni. Zelo pomembno je, da se ta dediščina ne uniči, tako kot se je kolišče ali Chopinov podhod, ki pričata o simptomatskem uničevanju ljubljanske dediščine. Na mestu tržnice so frančiškani dobili prostor za samostan že za časa življenja Frančiška Asiškega, tri desetletja kasneje je samostan na tem mestu tudi prvič dokumentiran. Tukaj je bilo glavno ljubljansko pokopališče, kjer so frančiškani pokopavali svoje brate, pokopani pa so tudi umrli iz mestnega špitala, saj so že v 12. stoletju frančiškani dobili dovoljenje, da pri cerkvi in samostanu v grobnice pokopljejo tudi laike. Na sredi tržnice je tako 19 grobnic najpomembnejših družin takratne Kranjske – dokumentacija kaže, da je tam pokopanih 280 ljudi. Ti so plačali veliko denarja, da so dobili jamstvo za večno oskrbo svojih duš. Po odhodu frančiškanov je to ostalo nedorečeno vse do danes. V dogovoru z MOL je že bilo uničeno dvojno obzidje pri Mahrovi hiši, kaj vse se bo še uničilo, ostaja nedorečeno. MOL predlaga na primer zagatne stene zunaj varovanega območja, kar pa bo vplivalo tudi na cerkev Marijinega vnebovzetja. Vprašanje je, kako se bodo izkopavanja sploh izvajala, saj je v načrtu, da bodo odstranili drevesa, postavili ploščo, zabili pilote, pod to ploščo pa nato odstranjevali kleti in grobnice samostana. To je skrajno nenavadno, s tem je res vse postavljeno na glavo. Da bi ljudje s približno 100 stojnic pravočasno pripeljali blago iz načrtovane garaže na površino in nazaj, bi potrebovali kar 35 dvigal. To je tudi teoretično popolnoma nemogoče izpeljati, a se v to nihče na MOL ni poglobil. Prav tako ne v to, da garaže sploh niso potrebne. Potrebni so le minimalni posegi. Poseg, ki je zdaj načrtovan, pa bo brez dvoma uničujoč. Kaj pomeni gradnja pod zemeljskim površjem na tržnici, kažejo že Mesarski most in prostori pod njim, kjer v dilatacijo ob vsakem nalivu teče voda, ki povzroča, da se konstrukcija pogreza in nastajajo razpoke. Pa je tam samo ena etaža, v garažni hiši so načrtovane tri.«

Marko Mitja Feguš: »Pozabljamo, da je bila Mahrova hiša za tri milijone evrov že ponujena Akademiji za gledališče, radio, film in televizijo (AGRFT) s skritim namenom, da se cvinger prebije. Že od takrat je jasno, da je pri tržnici za ljubljanskega župana pomemben samo posel, ne prihodnost tržnice in ne ljudje, ki jo uporabljajo in v mestu živijo. To smo takrat preprečili s preselitvijo AGRFT v nekdanje prostore Fakultete za kemijo. Ne bodimo naivni, ne pogovarjamo se o prenovi, gre za posel. Vloga za gradbeno dovoljenje za ta projekt je nedopustna, neustavna in proti vsem normam. Plečnikove arkade so nekoč že bile popravljene, a izkazalo se je, da plošča ne zdrži nadtlaka deževnice, saj je bilo naročilo iz leta 1937 izvedeno popolnoma diletantsko. Če se bo na tem območju spet zgodil kakršenkoli izkop, bo vse vzel hudič – nadtlak bo vrgel v zrak del Plečnikovih tržnic.«

Vito Rus: »Vprašati se moramo, koliko je Ljubljana zadolžena. V Šiški je mestna oblast pod Jankovićevim vodstvom naredila katastrofo. Kakšen Bellevue?! Naj najprej plača za Stožice! A ne smemo biti naivni, ’levi’ in ’desni’ igrajo, da so sprti, vendar delujejo z roko v roki, vsaj, ko gre za posle. Že 33 let doživljamo te katastrofe, odkar so nam ukradli družbeno lastnino.«

Marinka Kurelič: »Ravno na tem mestu smo imeli pred 18 leti in pol prvo tiskovno konferenco iniciative Tržnice ne damo. V teh letih smo veliko naredili, čeprav očitno ne dovolj, pa tržnica še vedno stoji. Edini prostor v središču mesta je, kjer lahko kupujemo domače pridelke: zvečer so na polju, zjutraj že na stojnicah. Tržnica je tudi eden redkih prostorov za spontano srečevanje. Vrvež ob sobotah je prekrasen, to je res doživetje, kar dela ta prostor edinstven na svetu! Vse skupaj dopolnjuje še neprecenljiva dediščina: Plečnikove arkade, prekrasna stavba semenišča z baročno knjižnico in freskami, ki jih ni mogoče restavrirati, ker ni več materialov za to, stolnica, nad vsem tem grad in zraven Ljubljanica! Že ko je Zoran Janković prvič kandidiral, je imel tržnico v svojem programu, in od takrat se organiziramo. Njemu in kapitalski mafiji je v interesu, da se ta prostor uniči. Ni jim mar mnenje neodvisnih strokovnjakov, da je tukaj najslabša zemljina, posebej občutljiv prostor zaradi voda z Grajskega griča, zaradi česar je vsak izkop zelo tvegan. Kjerkoli na tem območju kopljejo, sosednje stavbe razpokajo: Vila Urbana, Kapitelj, Fabianijev most. Odkar na Kongresnem trgu stoji garaža – tudi tam se je organizirala iniciativa proti njej, a žal ni vztrajala – Uršulinska cerkev doživlja degradacijo, pospešeno propadanje, zaradi česar se bo nekega dne samo še sesula. Vse stavbe v okolici garaže so ob dežju poplavljene. Spodnje stavbe ob Ljubljanici – na primer Filharmonija – so že razpokane in lezejo proti Ljubljanici; vsak lahko vidi fuge in dilatacije, postopno visenje. Glede na to, da na Kongresnem trgu zemljina ni tako občutljiva, kot je na tržnici, lahko predvidimo, da bo tukaj škoda še večja. Janković želi izsiliti garažo. Ukinil je promet čez Tromostovje, ne da bi poskrbel za nadomestne poti, zaradi česar reševalna vozila nimajo dostopa do starejših ljudi, manjše trgovinice pa umirajo. Janković uživa v trpinčenju ljudi. Ne smemo dovoliti, da nam uniči kulturne spomenike, ki jih moramo ohraniti za zanamce.«

Knjižničarka iz samostanske knjižnice: »Freska, ki je v semenišču, je posebna zaradi vsebine – znanost, umetnost sta prepleteni z vrednotami vere, ljubezni in resnice. Pomembna je tudi glede na kakovost, ker še ni bila restavrirana, razen razpok po potresu. Nikjer na svetu po našem vedenju ne obstajajo freske iz tega obdobja, ki bi bile tako živih barv. Vsi, ki vstopijo, s turisti vred, ostrmijo. Popolnoma neodgovorno bi bilo to izpostaviti porušenju in podtalnici.«

Aleksander Ostan: »Načrti MOL za prenovo so bili že takrat pred dvema desetletjema zastareli, zdaj pa je to že popolna karikatura. Takšni posegi so se drugod po Evropi delali po drugi svetovni vojni, ko je bila v ospredju ponovna zgraditev porušene Evrope. Redki primeri se še dogajajo, ampak nikjer na taki ravni. Kar je najbolj sporno, pa je odnos do pokojnikov – pieteta. Tudi promet se že tri desetletja drugod po Evropi razvija v smeri trajnostne mobilnosti, s katero se prednost daje pešcem, kolesarjem in javnemu prometu. Popolnoma zgrešeno bi bilo, da bi v staro mestno jedro vabili avtomobilski promet. Posledica bo izjemno velik ogljični odtis. Vseh drugih srednje- in dolgoročnih posledic ob takšnem posegu pa sploh ni mogoče oceniti, vse je lahko zgolj špekulacija. Tudi stroka je tako postala plen pritiskov MOL. Obstaja pa veliko bolj smiselna alternativa garaži pod tržnico, in to že 30 let – garažna hiša pod Grajskim gričem. Če že potrebujemo garažno hišo, kar bi morala biti stvar široke javne razprave, bi z garažno hišo pod gričem pridobili neprimerno več parkirnih mest, tudi tehnološko bi bila veliko lažje izvedljiva. Jasno je, da bo načrt MOL, če bo uresničen, pomenil ustavitev tržnice za zelo dolgo: vse skupaj bi trajalo desetletje, če se ne bi vmes zgodila finančna luknja in bi vse obstalo – kot se je na primer zgodilo s športnim parkom v Stožicah. Za tem projektom očitno stojijo veliko močnejši zasebni interesi, če ga MOL kljub vsem strokovnim in drugim argumentom še vedno potiska naprej.«
(Aleksander Ostan je svoj pogled na prenovo tržnice podrobneje predstavil v članku na tej povezavi.)

Milan Kovač: »Glede projekta podzemne garažne hiše pod gradom sem povprašal občino v Salzburgu: tam je eno parkirno mesto stalo približno 17.500 evrov, kasnejša pa 22.500 evrov. Do zdaj so bili samo za projektiranje garažne hiše pod ljubljansko tržnico in dozidave Mahrove hiše porabljeni štirje milijoni in 300 tisoč evrov – za ta denar bi v Salzburgu postavili 200 parkirnih mest. A nič od tega zaradi županovega agresivnega nastopa ne gre skozi. Na javni razpravi sem bil priča, kako je strahotno nadrl prodajalko, ki si je upala izraziti mnenje, potem pa nikogar več sploh ni pustil k besedi. Prodajalci si zato ne upajo nič reči, saj se bojijo županovega maščevanja. Najti moramo možnost za anonimno izražanje mnenj in glasovanje, ki bi pod resnim nadzorom javnosti predstavilo dejansko mnenje uporabnikov tržnice.«

Sanja Simić: »Zelo smo se trudili na javno tribuno povabiti tudi branjevce in branjevke, a zaradi strahu si ne upajo javno nastopati. Straši jih tudi raven razprave, s katero se vračamo 20 let v preteklost, hočejo predvsem vedeti, kaj naj pričakujejo v prihodnosti. Veseli pa so, da so našli sogovornike. Žal mi je, da si tisti, ki so prišli, niso upali govoriti. A so nam v pogovorih odkrito povedali, da nasprotujejo garaži, da ne potrebujejo hladilnic, da se bojijo, da bo demontaža tržnice trajala dolgo in se ne bodo nikoli vrnili. Potrebujejo nove senčnike, tlake, pitnike, osnovno izboljšanje razmer. Zanje in za nas je tržnica mesto srečevanja – zadnji tak prostor srečevanja v Ljubljani, kjer se združujemo starejši in mlajši. Ljudje večinoma prihajajo peš, s kolesom, javnim prometom.«
(Nekaj pogovorov z branjevci in branjevkami lahko preberete na tej povezavi.)

Sanja Fidler: »Ena največjih vrednosti tržnice je, da je dostopna, ljudska, da lahko pride sem prodajat branjevka s tremi korenčki, če želi. Ne želim si kakršnekoli prenove, tudi garaže ne, ker te prenove tržnice vizualno spreminjajo v pokopališča – večina rešitev po Sloveniji in drugod je neznosna, obupna. Toda največja težava je, da česarkoli se mestna oblast dotakne, kar ’obnavlja’, postane potem manj dostopno za ljudi. Na MOL sem že pisala, kako bodo zagotovili enako dostopnost tudi po prenovi. Dileme ni, da se bo za male kmete uporaba tržnice podražila in da nekateri ne bodo mogli ostati. Naša tržnica je izjemna, ekološka tržnica – evropski dragulj! Njen namen je, da je nekoliko kaotična, živahna, ljudska. Zakaj bi jo spreminjali v črno-bel supermarket na prostem?! Hladilnica že obstaja, a uporabljajo jo preprodajalci, ne proizvajalci. Toda naša izkušnja je, da župan vse, v kar se zagrize, na koncu tudi iztisne. Zato se moramo organizirati, informirati čim več meščanov in meščank ter skupaj to preprečiti.«

Klara Stanič: »Za tržnico ni potrebna neka nova vizija, včasih si je preprosto treba prizadevati za ohranitev tistega, kar imamo. Lahko se polepša, vzdržuje, posodobitev pa ni nujno dobra. Poglejte, kam nas je brezglava modernizacija pripeljala: nekoč je bilo ’centrašev’ 42 tisoč, zdaj jih je le še 24 tisoč. Številna stanovanja se oddajajo na spletnih platformah, stanovanjske hiše se spreminjajo v hotele. Po drugi strani bomo v okolici središča Ljubljane kmalu dobili še več ljudi zaradi Emonike, novih stanovanj, ki bodo zrasla pri Pivovarni Union, in drugih projektov. Kam bodo vsi ti hodili, če bo tržnica zaprta?«

Arne Vehovar: »Projekt gradnje garažne hiše pod tržnico je že zelo daleč, v procesu pridobitve gradbenega dovoljenja, vsa ostala potrebna soglasja institucij že ima. Ministrstvo za okolje in prostor si zakonodajo razlaga po svoje. Občutek imam, da ljudje na ministrstvu ne želijo dati dovoljenja, a ko bodo izpolnjeni vsi pogoji, dovoljenje morajo izdati. Ustna obravnava pretekli torek je bila po osmih urah prerekanj prekinjena in se bo nadaljevala jeseni. Pragmatično bi bilo vzpostaviti dialog z ministrstvom in glede na splošno razpoloženje nasprotovanja projektu pomagati oblikovati pravno interpretacijo, ki bi vodila v zavrnitev gradbenega dovoljenja. Če bi se to zgodilo, projektant ne more začeti pripravljalnih del. Tako pridobimo čas do naslednjih volitev, po katerih glavni investitor mogoče ne bo več na položaju ali pa se bo spremenila sestava mestnega sveta in bo ta uvidel, da je projekt nesmiseln.«

Iva Badar: »Pred leti so mediji na predvolilnem soočenju kandidate za ljubljanskega župana vprašali, kaj počnejo za konec tedna. Le eden je odgovoril, da se sprehodi čez tržnico in po središču mesta, vsi drugi – tudi sedanji župan – so odgovorili, da komaj čakajo na petek, da lahko gredo iz mesta. Na naslednjih volitvah moramo izvoliti človeka, ki bo imel mesto rad.«

Kaja Lipnik Vehovar: »Služba za odnose z javnostmi na MOL ni v službi mesta in ljudi, ampak župana in sedanjega mestnega sveta. Temu se je treba upreti z organiziranim obveščanjem ljudi. MOL je ravno te dni odprla svojo anketo, ki sicer ljudi ne sprašuje po mnenju o gradnji tržnice, a lahko to vnesemo pod okvirček ’drugo’ ter tako izrazimo svoje mnenje. To lahko tudi javno beležimo in zbiramo, da bo postopek bolj transparenten.«
(Prispevek Kaje Lipnik Vehovar o propagandni akciji MOL, ki se nanaša na projekt prenove tržnice, lahko preberete na tej povezavi.)

Martina Lipnik: »Treba je pritisniti, da bo postopek pridobitve gradbenega dovoljenja postal javen. Ministrstvo moramo zasuti z vprašanji, zakaj se ljudje ne morejo udeležiti javne razprave, in zahtevati snemanje obravnave.«

Marko Mitja Feguš: »Vložiti moramo tudi ovadbi na Nacionalni preiskovalni urad in državno tožilstvo proti osebi, ki vodi postopek pridobitve gradbenega dovoljenja, in proti županu.«

Foto: Matjaž Rušt

Koalicija sindikatov in delavskih organizacij ostro zavrača predlog pokojninske reforme, ki ga je vlada nedavno poslala v parlamentarno obravnavo. Pri tem je poudarila, da je reforma spisana izrazito v škodo delavcev, še posebej tistih najranljivejših, zato je poslanske skupine maja pozvala k vložitvi treh dopolnil. Ker ne poslanske skupine ne vlada njihovih dopolnil niso pripravljeni sprejeti, se obeta zakonodajni referendum.

Predstavniki in predstavnice delavstva so ob tem prepričani, da v državi ni sindikata, ki ne bi podpiral njihovih zahtev, in da bodo zbrali potrebnih 40.000 podpisov za razpis referenduma ter na njem tudi zavrnili škodljivo pokojninsko reformo. Čeprav so bile njihove zahteve po dopolnilih naslovljene na poslanske skupine, jih je na sestanek povabil minister za delo, družino, socialne zadeve in enake možnosti Luka Mesec. “Ker po sestanku ocenjujemo, da ne poslanci, ne ministri vladne koalicije niso naredili resnih korakov k odpravi škodljivih delov reforme in poskrbeli za pravičnejšo delitev bremena, bomo pričeli z aktivnostmi za sprožitev zakonodajnega referenduma,” so zapisali v sporočilu za javnost. Ob tem so presenečeni nad pasivno držo poslanskih skupin: “Najmanj nenavadno se nam zdi, da poslanke in poslanci o tako ključni reformi nimajo nobenega samostojnega mnenja, ki bi v čemerkoli odstopalo od vladne linije.” Vladi očitajo, da reforma sploh ni potrebna, saj je pokojninska blagajna stabilna, in da je to le izgovor za varčevanje na plečih delavcev in delavk: »Delodajalci bodo še naprej v sistem vplačevali pol manj kot delavci, država pa ne bo namenila nobenih dodatnih sredstev, pač pa bo z reformo (znova) varčevala.« Kritike letijo tudi način priprave reforme “za zaprtimi vrati”, saj “sindikatom in javnosti ni bilo na voljo tako rekoč nič časa za razpravo in odzivanje”, podprta pa ni bila s projekcijami in izračuni novih pokojnin.

Na očitke, da je reforma izrazito protidelavsko naravnana in da se je sprejemala na izključujoč način, so se odzvali na ministrstvu za delo, družino, socialne zadeve in enake možnosti. “Podpiramo vsakršno prizadevanje za izboljšanje položaja delavcev in širšo javno razpravo o pokojninski reformi, k čemur smo zadnji dve leti tudi aktivno prispevali. Pokojninska reforma je navsezadnje rezultat pogajanj s socialnimi partnerji in pred tem številnih usklajevanj z različnimi deležniki,” so zapisali in dodali: “Članstvo sindikatov, ki v Sloveniji predstavlja delavstvo, je sodelovalo v pol leta trajajočih pogajanjih o prav vseh delih reforme. Pred tem je razprava o reformi potekala od prve predstavitve izhodišč julija 2023. Reforma je bila tudi večkrat v zadnjih dveh letih obravnavana s številnimi upokojenskimi organizacijami in vsemi drugimi zainteresiranimi deležniki. Vlada ni nikogar izločala iz razprav in ničesar ni skrivala. Teza, da sindikalne centrale, ki sodelujejo v socialnem dialogu, ne predstavljajo delavstva, postavlja pod vprašaj celoten socialni dialog med vlado, sindikati in delodajalci.”

Tri poglavitne spremembe pokojninske reforme, ki jih zahteva delavska koalicija, so:

1. Umik zvišanja upokojitvene starosti, ki je eden od pogojev za pridobitev pravice do starostne pokojnine, na 62 oziroma 67 let – kot predvideva 17. člen predloga zakona. »Ukrep postavlja na laž predlagateljevo trditev, da je ’40 let dela dovolj’, saj bodo delavci, ki so na primer začeli delati pri 20 letih, morali do izpolnitve pogoja delati 42 let. Splošno zvišanje upokojitvene starosti je diskriminatorno, saj ne upošteva delovnih razmer v različnih poklicih, ki izrazito vplivajo na način staranja in tudi umrljivost delavcev«.

2. Umik podaljševanja referenčnega obdobja za izračun pokojninske osnove s 24 let na 40 (–5) let – kot predvideva 20. člen predloga zakona. »Daljšanje pomeni znižanje pokojninskih prejemkov«, to pa bi med drugimi izrazito prizadelo delavce, ki so bili dlje časa v prekarnih delovnih razmerjih. Zaradi podaljševanja referenčnega obdobja naj bi se pokojninska osnova nekaterim znižala tudi za deset odstotkov in več, v povprečju pa za štiri odstotke. Kar naj bi tudi “izpodbilo učinke predlaganega zvišanja odmernega odstotka”, ukrepa, s katerim ministrstvo za delo, družino, socialne zadeve in enake možnosti utemeljuje svojo trditev, da je reforma prvi v zgodovini, ki v ospredje postavlja “dostojne pokojnine.”

3. Umik novega načina usklajevanja pokojnin z rastjo plač in inflacijo, ki se trenutno izvaja v razmerju 60 odstotkov rasti plač in 40 odstotkov rasti cen (inflacija), po novem predlogu pa bi se postopno spremenilo v razmerje 20 odstotkov rasti plač in 80 odstotkov rasti cen. »Ukrep gre izrazito v škodo delavcem, saj so plače v zadnjih 25 letih rasle v povprečju 1,5-krat hitreje kot življenjski stroški. To pomeni, da bo upokojenec ob upokojitvi prejemal 70 odstotkov plače, po 20 letih pa zgolj še 53 odstotkov plače,« je izračunala delavska koalicija in dodala, da bi ta ukrep prizadel tudi že zdaj upokojene ljudi.

Široko delavsko koalicijo trenutno sestavlja 25 sindikatov in drugih delavskih civilnodružbenih organizacij: Sindikat poklicnega gasilstva Slovenije, Sindikat delavcev gostinstva in turizma Slovenije, Glosa – sindikat kulture in narave Slovenije, Sindikat kemične, nekovinske in gumarske industrije Slovenije, Sindikat kmetijstva in živilske industrije Slovenije, Sindikat državnih organov Slovenije, Zasuk – sindikat za ustvarjalnost in kulturo, Cedra – Center za družbeno raziskovanje, Študentsko društvo Iskra, Sindikat Mladi Plus, Gibanje za dostojno delo in socialno družbo, Konferenca sindikatov zavarovalništva Slovenije, Sindikat delavcev statističnega urada, Sindikat Lidl, Delavska svetovalnica, Ljudska iniciativa Velenje, Zavod Solidar, Sindikat Radia Študent, Sindikat carinikov Slovenije, Sindikat poštnih delavcev Slovenije, Sindikat delavcev rudarstva in energetike Slovenije, Mirovni inštitut, Iniciativa Glas ljudstva, Iniciativa Mestni zbor Maribor in Konfederacija sindikatov 90 Slovenije.

Novosti glede kampanje in zbiranja podpisov za referendum lahko spremljate na spletni strani koalicije.

LJUDSKA FRONTA – VOJNI KONTRA!

Pridružite se nam na protestu v torek, 24. junija ob 17. uri na Kongresnem trgu v Ljubljani.

Evropska unija je pred kratkim sprejela proračun, ki za 800 milijard viša izdatke za oboroževanje. S tem se nikakor ne bo gradilo miru in varnosti, temveč zgolj krepilo vojaško gospodarstvo in militarizem, ki postavljata dobičke pred človeška življenja.

V Sloveniji se soočamo z razpadom javnih zdravstvenih in socialnovarstvenih storitev, javnega šolstva in vrtcev, oskrbe starejših, stanovanjsko krizo, vse slabšimi življenjskimi pogoji za delavstvo in študentstvo ter vse bolj prisotno revščino. Vlada opravičuje višanje vojaških izdatkov in militarizacijo z izgovorom, da se preprosto moramo oborožiti in da nam varnost zagotavlja članstvo v zvezi NATO. To članstvo nas kvečjemu ogroža, istočasno pa nas stane socialne države! Slovenija mora izstopiti iz te morilske zveze.

Frančiškani so prišli v Ljubljano leta 1233, le nekaj let po smrti sv. Frančiška leta 1226. Naselili so se na območju današnje tržnice ob vzhodnem mestnem obzidju, prvič omenjenem leta 1243.

Arheološke ostaline iz srednjega in novega veka na območju vzhodnega mestnega obzidja od Gradu z obrambnim jarkom, Kloštrskimi mestnimi vrati, dvižnim mostom, trdnjavo barbakan in dvojnim obzidjem do Vodnega stolpa ob Ljubljanici ter ostaline cerkve Marijinega vnebovzetja z grobnico Turjaških, pokopališče s kostnico in obokane kleti nekdanjega frančiškanskega samostana, ki jih je občasno uporabljala tudi bolnišnica, so izredno dobro ohranjeni. Iz arhivske dokumentacije pa je razvidno, da je na območju nekdanjega frančiškanskega samostana med drugim še 19 neodkritih grobnic fevdalnih družin in mestnih veljakov z 280 pokopanimi.

Vse to je popisano v sodobnih arhivih mesta Ljubljane in arhivih, ki jih hrani frančiškanski samostan na Prešernovem trgu, dostopno vsem – tudi Mestni občini Ljubljana (MOL) in projektantom garaž pod tržnico. S kolegom Kerševanom sva se zgrozila nad predvideno gradnjo kanalizacije, ki naj bi potekala skozi najpomembnejše arheološko najdišče iz srednjega in novega veka v Ljubljani. Najin idejni projekt prenove osrednje tržnice je nastal z namenom javnosti predstaviti možnost prenove tržnega prostora tako, da se ohrani bogata arheološka zapuščina.

Na podlagi srednjeveške dokumentacije (ki so jo kasnejša arheološka izkopavanja potrdila) sva izdelala idejni projekt zaščite trdnjave – barbakana – in srednjeveškega muzeja z vhodom iz Mahrove hiše. Že 19. decembra 2009 sva ga predstavila MOL, Zavodu za varstvo kulturne dediščine (ZVKDS), Mestnemu muzeju (MGML) in izbranemu projektantu prenove. Župan Zoran Janković je projekt odobril in predlagal dopolnitev predloga s povezavo z žičnico na grad.

Po predstavitvi idejnega projekta MOL, ZVKDS in Mestnemu muzeju ter po pozitivnem odzivu župana Jankovića sva sledila arheološkim izkopavanjem, prilagajala projekt stanju na terenu in dopolnjevala zasnovo s povezavo z žičnico in gradom. Bila sva presenečena, ko sva v časopisih zasledila, da najin idejni projekt nadaljuje Kombinat arhitekti, d. o. o., še bolj pa po obisku na MOL, kjer sva ugotovila, da gre za plagiat. Na ponovno zahtevo po pregledu dokumentacije nama MOL ogleda ni dovolila, nekaj mesecev kasneje pa sva prejela od civilne pobude Tržnice ne damo nov projekt Kombinata, d. o. o., z nekaterimi spremembami. Srednjeveški muzej je v Kombinatovem projektu dobil novo ime Arheološki center Ljubljane. Od takrat ni nobenih informacij, kaj namerava MOL z arheološko dediščino na Vodnikovem in Krekovem trgu. Zadnji načrti, ki so bili predstavljeni javnosti, arheološke dediščine sploh ne obravnavajo.

Prodajalci garaže ne potrebujejo

Zaradi specifičnosti delovanja tržnice je pred projektiranjem prenove tržnice potrebna podrobna analiza delovanja in potreb pridelovalcev s podeželja, prekupčevalcev s sadjem in zelenjavo ter prišlekov s Ponte Rossa v Trstu, ki širijo svoje dejavnosti na naši tradicionalni tržnici.

Garaže prodajalci ne potrebujejo. Tisti iz bližnje okolice pridelke s kombiji pripeljejo do stojnic, jih razložijo na stojnice in odpeljejo vozila domov, ker jih čez dan potrebujejo doma. Popoldne, ob zaključku prodajnega dneva, se vrnejo s kombiji do stojnice, naložijo neprodane pridelke in odpadke, ki jih uporabijo kot krmo za živali, ter počistijo okolico stojnice. Potrošniki želimo na tržnici sveže pridelke. Prodajalci pripominjajo, da so z dosedanjim načinom zadovoljni, in dodajajo, da za shranjevanje v podzemnih prostorih za številne stojnice, ki bi potrebovale transport sočasno zjutraj in popoldne, število načrtovanih dvigal nikakor ne zadostuje. Opozarjajo tudi, da tržnica obratuje v dopoldanskem času, sočasno kot v aktualnem projektu predvideni administrativni oddelki MOL v Mahrovi hiši, kar bi povzročilo prometni infarkt in nedovoljen vpliv na skupna področja z živilskimi pridelki.

Parkirna mesta za obiskovalce tržnice niso potrebna, saj ti v veliki večini prihajajo peš iz bližnjega okoliša. Redke stranke, ki kupujejo cele platoje paradižnikov, pa se lahko odpeljejo v BTC, kjer je velikokoličinska prodaja sadja in zelenjave cenejša, parkirna mesta pa zagotovljena. Poleg tega je v neposredni bližini tržnice podzemna garaža pod trgovskim centrom Spar, ki ni polno zasedena niti ob sobotah, ko meščani množično prihajajo na tržnico.

Prenova tržnice je potrebna

Prenova tržnice pa je vsekakor potrebna. Potrebni so prenova in dopolnilo hladilnic, prostor za ravnanje z odpadki, skladišča za embalažo, skladišča za demontirane stojnice, grelce in drugo tehnično opremo, prenova sedanjih dvigal in gradnja novih … Vse to je mogoče namestiti v kletnih prostorih Mahrove hiše. V atriju Mahrove hiše pa urediti pokrito tržnico.

Tudi prekupčevalci s sadjem in zelenjavo podzemne garaže ne potrebujejo, potrebujejo pa skladišče in hladilnice ter garderobe.

Prodajalci, ki so se s tržaškega Ponte Rossa preselili na ljubljansko tržnico, ne spadajo na tradicionalno glavno ljubljansko tržnico. Mestne oblasti bi morale najti drugo lokacijo za to vrsto dejavnost.

Sanitarije so že bile zgrajene leta 2010 v sklopu Mesarskega mosta in dopolnjujejo Plečnikovo ureditev ob Zmajskem mostu.

Dozidava Mahrove hiše in uporaba kleti frančiškanskega samostana

Mahrova hiša, zgodovinska znamenitost Ljubljane, ki je delno zgrajena na zasutem obrambnem jarku, se naslanja na obzidje in ni nikoli posegala na prostor onkraj obzidja.

Zavod za varstvo kulturne dediščine (ZVKDS) je v kulturnovarstvenih pogojih odredil, da se Mahrova hiša lahko dozida le na območju cvingerja – med obema mestnima obzidjema. Nerazumljivo je, da je ZVKDS na svoj odlok kasneje pozabil in z izdanim pozitivnim mnenjem k projektu dovolil dozidavo Mahrove hiše prek srednjeveškega obzidja, kar bo estetsko in okoljevarstveno negativno vplivalo tudi na Plečnikove arkade na seznamu Unescove svetovne kulturne dediščine.

Marca 2012 so arheologi odkrili nedotaknjene kletne oboke samostanskih prostorov. Po potresu so odstranili ruševine; kletni prostori so ostali nepoškodovani, napolnili so jih le z ostanki potresnih ruševin Liceja. Frančiškani so bili posestniki vinogradov, pričakovati je, da je imel samostan tudi vinske kleti, zato velike obokane kleti ne presenečajo. Po najinem predlogu se očiščene samostanske kleti na omejenem območju lahko vključijo v obnovo tržnice.

Uvoz v podzemlje vpliva na Plečnikovo dediščino

K projektu obnove, ki ga zagovarja MOL, sodi uvoz v garažo med Plečnikovimi arkadami in Mahrovo hišo pri Zmajskem mostu. Varovane Plečnikove arkade bi bile tako estetsko, pa tudi okoljevarstveno ogrožene s tresljaji in z obremenitvami z izpušnimi plini številnih obiskovalcev upravne zgradbe v Mahrovi hiši – če bi bila izpeljana dozidava. Izničen bi bil Plečnikov ambient med arkadami in Mahrovo hišo do Zmajskega mosta. Poleg tega bi bil oviran površinski dostop do stojnic na trgu.

Spomenik solataricam na tržnici

Dejavnost solataric iz predmestij Krakovo in Trnovo, ki so mesto stoletja oskrbovale z zelenjavo, cvetjem in sadjem, tako da so to vsakodnevno s cizami dovažale na tržnico, je zamrla. Že maja 2010 sva MOL predlagala spomenik solataricam ob izlivu Gradaščice. Mestna občina je predlog odobrila, a se do danes ni zgodilo nič. Kot alternativo spomeniku solataricam ob izlivu Gradaščice predlagam lokacijo na prenovljeni tržnici.

Zapisano tudi v imenu Petra Kerševana, soavtorja vse do leta 2023.

Foto: Matjaž Rušt

Ilustracije: Peter Kerševan, Milan Kovač

Objavljamo nekaj pogovorov s prodajalci, branjevkami in njihovimi kupci, ki so se odvili med obiskovanjem Osrednje ljubljanske tržnice v preteklih tednih. Večina na odprti tržnici na Vodnikovem trgu je izrecno proti garaži. V sklopu prenove bi radi videli zgolj obnovo tlakov, več vodnih pip, boljša stranišča in nove senčnike.

Sobota, okrog enajstih:

Nakupovalka (na Vodnikovem trgu kupuje češnje neposredno pri pridelovalcu): Dober dan. Kako ste?

Pridelovalec: Dobro. Pa vi?

Nakupovalka: Dobro, hvala. Vas lahko nekaj vprašam? Kaj si mislite o prenovi tržnice?

Pridelovalec: Kot bi mi iztaknili oko. Tržnica je duša Ljubljane.

Sobota, okrog poldneva:

Prodajalka (v pokriti tržnici): Dober dan.

Nakupovalka: Dober dan. Vas lahko nekaj vprašam? A ste seznanjeni s predvidenimi načrti za prenovo tržnice?

Prodajalka: Ja, so nam predstavili.

Nakupovalka: Kaj pa vi mislite o njih?

Prodajalka: Mislim, da bo zame to dobro, ker bo prišlo več ljudi in bom lahko več prodala, saj bodo imeli kje parkirati.

Nakupovalka: Kaj pa če nihče ne bo prišel, ker bodo tisti, ki so proti, blokirali vhod v garažo? A ne mislite, da je škodljivo vleči avtomobilski promet v središče mesta?

Prodajalka: Pa … nisem o tem premišljevala. Mogoče res ne.

Torek, okrog enih:

Nakupovalka (se ustavi pri ljubljanski solatarici, ki dvakrat na teden prinaša svojo robo na tržnico): A ste seznanjeni z načrti za prenovo tržnice?

Solatarica: Sem seznanjena. Proti sem. Mali prodajalci sploh ne potrebujemo garaže, hladilnic, nič od tega. Če se bo to zgodilo, nas ne bo več, ker se nam ne bo izplačalo.

Naslednja sobota, okrog enih:

Dva gospoda kupujeta sir v pokriti tržnici in se pogovarjata. Nakupovalka čaka v vrsti. Eden od gospodov opazi nakupovalko in reče drugemu: “Daj pohiti, gospa čaka”.

Nakupovalka: Nič hudega. Vas lahko nekaj vprašam?

Gospod 1: Ja, ni problema.

Nakupovalka: Kaj pa vi mislite o prenovi tržnice?

Gospod 1: S tem se ne obremenjujem.

Gospod 2: Jaz pa sem proti. On nima hrbtenice.

Nakupovalka (se v smehu obrne proti prodajalki): A vidite, da prihajamo tudi zato, da se pogovarjamo, ne samo, da nakupujemo.

V Ljubljani ta čas poteka izjemno intenzivna propagandna akcija “Naj živi tržnica”, ki jo izvaja Mestna občina Ljubljana (MOL), naročnica in investitorka projekta Prenove osrednje ljubljanske tržnice. Vse od vložitve zahteve za izdajo gradbenega dovoljenja na ministrstvu za naravne vire in prostor (MNVP) novembra lani akcija poteka v javnem prostoru na osrednji tržnici, kjer so s tematskimi plakati oblepljene kovinske zaščitne ograje kostanjevega drevoreda ob Plečnikovih arkadah na Vodnikovem trgu, v tisku, na televiziji in na spletnih družbenih omrežjih. Namenjena je predvsem preoblikovanju močno prisotnega negativnega mnenja dela javnosti o načrtovani prenovi. MOL projekt predstavlja kot “nujno prenovo”, ki bi prodajalcem s posodobitvami in dopolnitvami osnovne infrastrukture omogočala “boljše delovne razmere za zagotavljanje sveže in kakovostne ponudbe za obiskovalce tržnice”. A poglavitni del projekta, ki se mu župan nikakor ne more ali ne želi odpovedati, je sporen in pri znatnem delu splošne in strokovne javnosti zelo kritiziran ter zavračan načrt za gradnjo štirietažne podzemne garažne hiše (za približno 250 osebnih avtomobilov in 30 dostavnih vozil) pod odprto tržnico na Vodnikovem trgu.

Na MOL obljubljajo: “Na tržnici je prometni kaos. To bomo spremenili. Z načrtovano prenovo tržnice bomo vzpostavili kakovosten javni prostor, prometno obremenitev mesta občutno zmanjšali, skrajšali prometne poti ter vsakodnevno vožnjo z večjimi dostavnimi vozili.” (naj živi tržnica) V tretji in četrti podzemni etaži so predvidena parkirna mesta za prebivalce ožjega mestnega središča, v drugi pa parkirna mesta, namenjena obiskovalcem tržnice. Prva etaža garažne hiše naj bi bila namenjena parkirnim mestom za dostavna vozila prodajalcev in prostorom za dostavo in odvoz blaga, pri čemer bi bilo treba blago s tovornimi vozički s samo dvema dvigaloma pretovarjati iz kletne etaže na parter (in obratno). Predvideni postopek je zapleten in vprašljivo funkcionalen: pred začetkom in po izteku delovnega dne na tržnici bi bili vsi prodajalci v ozkem časovnem okviru vezani le na dve tovorni dvigali, kar je jamstvo za zmedo in kaos.

Zamisel za garažno hišo pod osrednjo ljubljansko tržnico se je sicer porodila že v času Jugoslavije. Leta 1985 je bil razpisan in izpeljan javni natečaj za Vodnikov trg in garažo pod njim, potem pa je bila zamisel za garaže pod tržnico pozabljena. V devetdesetih letih prejšnjega stoletja je bila sprejeta strategija urejanja prometa v mestnem središču skupaj z umestitvijo tunelske garažne hiše v hrib pod Ljubljanskim gradom, ki bi učinkovito rešila problem individualnega, predvsem mirujočega avtomobilskega prometa v ljubljanskem srednjeveškem jedru. Leta 1997 so se začele priprave za izvedbo garažne hiše v Grajskem griču. Žal se je z menjavo oblasti leta 1998 projekt popolnoma ustavil. Leta 2006 pa je novoizvoljeni župan Zoran Janković ponovno obudil zamisel o podzemni garažni hiši pod Vodnikovim trgom in pristala je celo med prednostnimi projekti nove mestne oblasti. Že naslednje leto je bila javnost seznanjena z idejnimi nastavki “prenove” osrednje tržnice in gradnjo podzemne garažne hiše z več kot 600 parkirnimi mesti, ki naj bi bila namenjena novemu Hotelu Kresija in ne mestni tržnici! Ozaveščeni prebivalci, ki so zbrali skoraj 10.000 podpisov proti takšni preureditvi, civilnodružbene pobude, nevladne organizacije in strokovnjaki z različnih področij so takoj začeli opozarjati, da umeščanje podzemne garaže v ta prostor ni primerno. Leta 2010 je tudi Nacionalni svet za kulturo podal mnenje, da bi izvedba načrtovanih posegov ogrozila kulturno dediščino na Vodnikovem trgu.

Takrat so bila na tem trgu že opravljena arheološka izkopavanja, ki so potrdila predvidevanja, da je ob nekdanjih vzhodnih, Kloštrskih vratih v srednjeveškem mestnem obzidju izjemno bogato arheološko najdišče. Našli so ostanke obrambnega sistema srednjeveške Ljubljane z mostom in barbakanom, temelje dvižnega mostu Kloštrskih vrat, okrogli stolp ob Ljubljanici, ostaline gotske cerkve in minoritskega (frančiškanskega) samostana s cerkvijo iz 13. stoletja. Na tem območju je bilo od 13. do konca 18. stoletja ljubljansko pokopališče; najdeni so bili tudi posmrtni ostanki in bronasta posoda, kanopa, s shranjenim srcem plemiča kneza Ferdinanda II. Auersperga (1655–1706). Najdbe so pokazale, da gre za izjemen prostor kulturne dediščine in leta 2012 je ministrstvo za kulturo arheološko najdišče na Vodnikovem trgu začasno razglasilo za kulturni spomenik državnega pomena. MOL je vložila zahtevo za presojo ustavnosti in zakonitosti razglasitve, saj naj bi bil odlok ministrstva po njenem mnenju “grobo posegal v ustavno in zakonsko varovane pravice MOL, ker ji onemogoča izvedbo načrtovanega projekta”. Nato je leta 2013 ljubljanski mestni svet sprejel Odlok o razglasitvi arheološkega najdišča na Vodnikovem, Ciril-Metodovem in Krekovem trgu za kulturni spomenik lokalnega pomena.

Gradnja garažne hiše na predvideni lokaciji ni sprejemljiva niti po urbanističnih merilih.

Gradnja podzemne garaže, katere predvideni obseg se je med 18-letnim razvojem projekta sicer že bistveno zmanjšal, bi za velik del pod tlakom (in-situ) ohranjene bogate srednjeveške arheološke dediščine še vedno pomenila poguben poseg. Dokončno uničenje našega skupnega bogastva mnogoplastnega kulturnega prostora z banalno gradnjo nepotrebne in za prostor škodljive podzemne garažne hiše v neposredni bližini dveh velikih parkirnih hiš, ki v ničimer ne prispeva k posodobitvi in dopolnitvi osnovne infrastrukture za tržnico, nikakor ne bi smelo biti dopuščeno. Gradnja garažne hiše na predvideni lokaciji ni sprejemljiva niti po urbanističnih merilih. Reševanje težav dostopnosti in mirujočega prometa v mestnem središču z gradnjo novih parkirnih zmogljivosti ni skladno s sodobnimi prometnimi strategijami niti s sodobnimi trendi razvoja mobilnosti v naprednih mestih, ki na prvo mesto postavljajo javni in kolesarski promet ter urejanje za pešačenje privlačnega javnega prostora.

V času intenzivnih podnebnih sprememb in čezmernega segrevanja urbanih prostorov bi bila gradnja garažne hiše v mestnem središču škodljiva tudi zaradi uničevanja mikroklimatskih razmer in zmanjševanja površin raščenega terena v odprtem javnem prostoru. Pozidava celotnih parcel zaradi umikanja mirujočega prometa pod zemljo v Ljubljani postaja prevladujoča praksa, ki omogoča čezmerno izrabo parcel nad terenom in ima – zaradi učinka vročih točk in dodatnega pregrevanja mesta ter nezmožnosti zadrževanja in ponikanja meteornih voda – izrazito negativen učinek na lokalno podnebje. Predvidena rešitev bi sicer nadomestila sedanja drevesa z novimi, a ta bi bila mlada, z majhnimi krošnjami, zaradi plitkega in omejenega rastišča nad betonsko streho podzemne garaže pa bi rasla v bistveno slabših razmerah kot zdaj rastoča. Zaradi tega ne bi zadovoljivo opravljala svoje vloge vitalne infrastrukture, ki ima izjemen pomen pri zagotavljanju kakovostnejših življenjskih razmer v urbanem prostoru: s senčenjem površin in s tem zniževanjem temperature okolice v poletnih mesecih ter z zmanjševanjem onesnaženosti zraka in obremenjevanja komunalne infrastrukture, ki odvaja meteorno vodo. Gradnja bi zaradi obsežnih gradbenih del z globokimi posegi v teren pomenila tudi izredno obremenitev okolja z vibracijami. Negativnih učinkov vibracij na okoliške kulturne spomenike (semenišče, župnišče, Plečnikove tržnice in stolnica) po javno razpoložljivih podatkih, ki so navedeni v projektni dokumentaciji, ni mogoče izključiti niti ni mogoče vnaprej predvideti obsega škode. Neodvisna strokovna ocena nevarnosti nastanka poškodb teh objektov pa ni izdelana.

Tveganjem je izpostavljena tudi Plečnikova ureditev tržnice, kulturni spomenik državnega pomena, ki je bil leta 2021 v sklopu izbora Plečnikovih del uvrščen na Unescov seznam svetovne kulturne dediščine. Celotno območje, ki ga obravnava projekt Prenove osrednje ljubljanske tržnice, je v vplivnem območju svetovne dediščine, zato bi bilo treba v proces odločanja o primernosti projekta pred kakršnimikoli dokončnimi odločitvami vključiti tudi mednarodno strokovno skupnost (Unesco) in po njenih pravilih pripraviti presojo vplivov na dediščino (angl. Heritage Impact Assessment – HIA). V sklopu presoje bi morale biti obdelane različne variantne rešitve (prenova tržnice brez gradnje garaže, prenova tržnice in garažna hiša pod Grajskim gričem, prenova tržnice z garažo pod Vodnikovim trgom itd.). A predpisani postopek ni bil izpeljan in dokončna ocena tveganja za Plečnikovo dediščino še ni znana. Če Unescova komisija prepozna nevarnost, da lahko spomenik oziroma spomeniško območje zaradi načrtovanih posegov v prostor izgubi značilnosti, ki opredeljujejo njegovo izjemno univerzalno vrednost, ga lahko prestavi na seznam ogrožene svetovne dediščine, v skrajnem primeru pa ga lahko s seznama svetovne dediščine celo izbriše. Za Plečnikovo delo je značilno na človeka osredotočeno humano oblikovanje urbanega okolja, Plečnikove intervencije pa so bile v prostor umeščene z izjemnim posluhom za mestni, naravni in kulturni kontekst, ki je že obstajal. Čeprav nas akcija MOL prepričuje, da “v Mestni občini Ljubljana mesto že ves čas urejamo v Plečnikovem duhu, s čimer vzdržujemo in spoštujemo njegova dela in tradicijo”, prenova ljubljanske tržnice z gradnjo podzemne garaže s predvidenim uvozom na območju za pešce na prvo mesto postavlja avtomobil in tako ni skladna s Plečnikovo vizijo urejanja mesta.

Zavod za varstvo kulturne dediščine Ljubljana je 14. oktobra 2024 po dveh negativnih mnenjih in številnih zahtevah po dopolnitvi dokumentacije projektu Prenove osrednje ljubljanske tržnice v tretjem poskusu vendarle izdal pozitivno kulturnovarstveno mnenje. Isti zavod, ki z množico strokovnih utemeljitev zlahka zavrne projekt namestitve tako rekoč neopaznega, kvadratni meter in pol velikega steklenega nadstreška nad vhodna vrata v večstanovanjsko stavbo na območju naselbinske dediščine, je dal zeleno luč za projekt, katerega dokumentacija je nezadovoljivo obdelana, ki potencialno ogroža množico spomenikov državnega pomena in pomeni dokončno uničenje znatnega dela srednjeveške arheološke dediščine! Slovenska ustava v 5. in 73. členu zavezuje državo in lokalne skupnosti k varovanju kulturne dediščine in skrbi za ohranjanje te. Pri projektu Prenove osrednje ljubljanske tržnice je glavni investitor in naročnik MOL – lokalna skupnost, državni Zavod za varovanje kulturne dediščine pa je k projektu, nedvomno uničujočemu za kulturno dediščino, dal pozitivno mnenje.

Od novembra 2024 je na ministrstvu za naravne vire in prostor (MNVP) za projekt ‘prenove’ tržnice tekel integralni postopek pridobivanja gradbenega dovoljenja. Do 11. decembra 2024 je potekala javna razgrnitev projekta. Takrat je imela zainteresirana javnost vpogled v projektno dokumentacijo in možnost k projektu podati pripombe. Zainteresirana javnost (pravne in fizične osebe, civilne pobude z zadostno podporo javnosti in nevladne organizacije) z izkazanim pravnim interesom se je lahko tudi priglasila v integralni postopek izdaje gradbenega dovoljenja kot stranski udeleženec. Pristojno ministrstvo je prejelo več kot 100 pripomb k projektnim rešitvam in skoraj 100 zahtev po sodelovanju v postopku!

Stališča MNVP do prejetih pripomb javnosti še niso znana, o zavrnitvi možnosti sodelovanja v postopku pridobivanja gradbenega dovoljenja kot stranski udeleženci pa so bili obveščeni zavrnjeni priglasitelji, med njimi tudi nevladne organizacije z delovanjem v javnem interesu na področjih urejanja prostora in/ali kulture (ki zajema tudi kulturno dediščino). Razlog? V Gradbenem zakonu (GZ-1) je v 3. členu določeno, da se med zainteresirano javnost, ki ima pri okoljskem odločanju pravni interes, uvrščajo nevladne organizacije, ki v javnem interesu delujejo na področju varstva okolja ali ohranjanja narave skladno z zakoni o varovanju okolja in varstva narave.

Okolje je izjemno širok pojem. Zakon o varstvu okolja (ZVO-2) navaja: »Okolje je tisti del narave, kamor seže ali bi lahko segel vpliv človekovega delovanja.« Zajema torej vse od narave in naravnih habitatov, rastlinskih in živalskih vrst, naravnih danosti, kakovosti zraka, vode, prisotnosti in odsotnosti hrupa do grajenega okolja (kamor spada tudi kulturna dediščina). Grajeno okolje je produkt prostorskega načrtovanja, torej urejanja prostora, kakovostno urejanje prostora pa je bistveno za kakovost (urbanega) okolja. Kljub temu je delovanje nevladnih organizacij s področja varstva okolja zelo ozko opredeljeno v Pravilniku o določitvi kriterijev za izkazovanje pomembnejših dosežkov delovanja nevladne organizacije za podelitev statusa nevladne organizacije v javnem interesu na področju varstva okolja (Url RS 104/2024). Usmerjeno je predvsem v onesnaževanje: zmanjševanje izpustov toplogrednih plinov, trajnostno ravnanje z odpadki, varstvo zraka, voda in tal pred izpusti onesnaževal, preprečevanje industrijskega onesnaževanja …

Za projekte, ki zaradi velikosti, obsega, lokacije ali drugih značilnosti lahko pomembno vplivajo na okolje, je treba opraviti presojo vplivov na okolje in pridobiti okoljevarstveno soglasje. Presojo vplivov na okolje, pri kateri »se ugotavljajo, opišejo in ocenijo dolgoročni, kratkoročni, posredni ali neposredni vplivi nameravanega posega na človeka, tla, vodo, zrak, biotsko raznovrstnost in naravne vrednote, podnebje in krajino, pa tudi na človekovo nepremično premoženje in kulturno dediščino ter njihova medsebojna razmerja«, je bilo treba izpeljati tudi za projekt Prenove osrednje ljubljanske tržnice.

Za vse posege v prostor, še posebej pa za posege v intenzivno urbanizirano okolje, bogato s kulturnimi spomeniki in dediščino, bi moralo predvsem za nevladne organizacije s statusom delovanja v javnem interesu na področju urejanja prostora in kulture (kulturne dediščine) veljati, da imajo po zakonu izkazan pravni interes in možnost sodelovanja kot stranski udeleženci v integralnih postopkih za izdajo gradbenega dovoljenja. A po črkobralski interpretaciji pomanjkljivih določb gradbenega zakona pristojno ministrstvo nevladnim organizacijam na področjih urejanja prostora in kulture ne priznava statusa upravičene zainteresirane javnosti, zato ne morejo pridobiti vloge stranskega udeleženca v postopku izdaje gradbenega dovoljenja. V vlogi stranskih udeležencev v integralnem postopku izdaje gradbenega dovoljenja kot zagovorniki narave nastopajo nevladne organizacije, ki v javnem interesu delujejo na področju varstva okolja ali ohranjanja narave, grajeno okolje (kulturna krajina, javni prostor, kulturna dediščina ipd.) pa svojih braniteljev iz vrst strokovne zainteresirane javnosti nima.

Glede na vse očitnejšo zlorabo oblasti, ki je zaradi lastnih komercialnih interesov pripravljena žrtvovati našo skupno kulturno dediščino, je prišel čas, da se civilna družba začne povezano in organizirano upirati takšni samovolji.

Our company recently announced a fundraise. We were grateful for all the community support, but the Internet also raised a few of its collective eyebrows, wondering whether this meant the dreaded “enshittification” was coming next.

That word describes a very real pattern we’ve all seen before: products start great, grow fast, and then slowly become worse as the people running them trade user love for short-term revenue.

It’s a topic I find genuinely fascinating, and I've seen the downward spiral firsthand at companies I once admired. So I want to talk about why this happens, and more importantly, why it won't happen to us. That's big talk, I know. But it's a promise I'm happy for people to hold us to.

What is enshittification?

The term "enshittification" was first popularized in a blog post by Corey Doctorow, who put a catchy name to an effect we've all experienced. Software starts off good, then goes bad. How? Why?

Enshittification proposes not just a name, but a mechanism. First, a product is well loved and gains in popularity, market share, and revenue. In fact, it gets so popular that it starts to defeat competitors. Eventually, it's the primary product in the space: a monopoly, or as close as you can get. And then, suddenly, the owners, who are Capitalists, have their evil nature finally revealed and they exploit that monopoly to raise prices and make the product worse, so the captive customers all have to pay more. Quality doesn't matter anymore, only exploitation.

I agree with most of that thesis. I think Doctorow has that mechanism mostly right. But, there's one thing that doesn't add up for me:

Enshittification is not a success mechanism.

I can't think of any examples of companies that, in real life, enshittified because they were successful. What I've seen is companies that made their product worse because they were... scared.

A company that's growing fast can afford to be optimistic. They create a positive feedback loop: more user love, more word of mouth, more users, more money, more product improvements, more user love, and so on. Everyone in the company can align around that positive feedback loop. It's a beautiful thing. It's also fragile: miss a beat and it flattens out, and soon it's a downward spiral instead of an upward one.

So, if I were, hypothetically, running a company, I think I would be pretty hesitant to deliberately sacrifice any part of that positive feedback loop, the loop I and the whole company spent so much time and energy building, to see if I can grow faster. User love? Nah, I'm sure we'll be fine, look how much money and how many users we have! Time to switch strategies!

Why would I do that? Switching strategies is always a tremendous risk. When you switch strategies, it's triggered by passing a threshold, where something fundamental changes, and your old strategy becomes wrong.

Threshold moments and control

In Saint John, New Brunswick, there's a river that flows one direction at high tide, and the other way at low tide. Four times a day, gravity equalizes, then crosses a threshold to gently start pulling the other way, then accelerates. What doesn't happen is a rapidly flowing river in one direction "suddenly" shifts to rapidly flowing the other way. Yes, there's an instant where the limit from the left is positive and the limit from the right is negative. But you can see that threshold coming. It's predictable.

In my experience, for a company or a product, there are two kinds of thresholds like this, that build up slowly and then when crossed, create a sudden flow change.

The first one is control: if the visionaries in charge lose control, chances are high that their replacements won't "get it."

The new people didn't build the underlying feedback loop, and so they don't realize how fragile it is. There are lots of reasons for a change in control: financial mismanagement, boards of directors, hostile takeovers.

The worst one is temptation. Being a founder is, well, it actually sucks. It's oddly like being repeatedly punched in the face. When I look back at my career, I guess I'm surprised by how few times per day it feels like I was punched in the face. But, the constant face punching gets to you after a while. Once you've established a great product, and amazing customer love, and lots of money, and an upward spiral, isn't your creation strong enough yet? Can't you step back and let the professionals just run it, confident that they won't kill the golden goose?

Empirically, mostly no, you can't. Actually the success rate of control changes, for well loved products, is abysmal.

The saturation trap

The second trigger of a flow change is comes from outside: saturation. Every successful product, at some point, reaches approximately all the users it's ever going to reach. Before that, you can watch its exponential growth rate slow down: the infamous S-curve of product adoption.

Saturation can lead us back to control change: the founders get frustrated and back out, or the board ousts them and puts in "real business people" who know how to get growth going again. Generally that doesn't work. Modern VCs consider founder replacement a truly desperate move. Maybe a last-ditch effort to boost short term numbers in preparation for an acquisition, if you're lucky.

But sometimes the leaders stay on despite saturation, and they try on their own to make things better. Sometimes that does work. Actually, it's kind of amazing how often it seems to work. Among successful companies, it's rare to find one that sustained hypergrowth, nonstop, without suffering through one of these dangerous periods.

(That's called survivorship bias. All companies have dangerous periods. The successful ones surivived them. But of those survivors, suspiciously few are ones that replaced their founders.)

If you saturate and can't recover - either by growing more in a big-enough current market, or by finding new markets to expand into - then the best you can hope for is for your upward spiral to mature gently into decelerating growth. If so, and you're a buddhist, then you hire less, you optimize margins a bit, you resign yourself to being About This Rich And I Guess That's All But It's Not So Bad.

The devil's bargain

Alas, very few people reach that state of zen. Especially the kind of ambitious people who were able to get that far in the first place. If you can't accept saturation and you can't beat saturation, then you're down to two choices: step away and let the new owners enshittify it, hopefully slowly. Or take the devil's bargain: enshittify it yourself.

I would not recommend the latter. If you're a founder and you find yourself in that position, honestly, you won't enjoy doing it and you probably aren't even good at it and it's getting enshittified either way. Let someone else do the job.

Defenses against enshittification

Okay, maybe that section was not as uplifting as we might have hoped. I've gotta be honest with you here. Doctorow is, after all, mostly right. This does happen all the time.

Most founders aren't perfect for every stage of growth. Most product owners stumble. Most markets saturate. Most VCs get board control pretty early on and want hypergrowth or bust. In tech, a lot of the time, if you're choosing a product or company to join, that kind of company is all you can get.

As a founder, maybe you're okay with growing slowly. Then some copycat shows up, steals your idea, grows super fast, squeezes you out along with your moral high ground, and then runs headlong into all the same saturation problems as everyone else. Tech incentives are awful.

But, it's not a lost cause. There are companies (and open source projects) that keep a good thing going, for decades or more. What do they have in common?

• An expansive vision that's not about money, and which opens you up to lots of users. A big addressable market means you don't have to worry about saturation for a long time, even at hypergrowth speeds. Google certainly never had an incentive to make Google Search worse.

  (Update 2025-06-14: A few people disputed that last bit. Okay. Perhaps Google has ccasionally responded to what they thought were incentives to make search worse -- I wasn't there, I don't know -- but it seems clear in retrospect that when search gets worse, Google does worse. So I'll stick to my claim that their true incentives are to keep improving.)

• Keep control. It's easy to lose control of a project or company at any point. If you stumble, and you don't have a backup plan, and there's someone waiting to jump on your mistake, then it's over. Too many companies "bet it all" on nonstop hypergrowth and don't have any way back have no room in the budget, if results slow down even temporarily.

  Stories abound of companies that scraped close to bankruptcy before finally pulling through. But far more companies scraped close to bankruptcy and then went bankrupt. Those companies are forgotten. Avoid it.

• Track your data. Part of control is predictability. If you know how big your market is, and you monitor your growth carefully, you can detect incoming saturation years before it happens. Knowing the telltale shape of each part of that S-curve is a superpower. If you can see the future, you can prevent your own future mistakes.

• Believe in competition. Google used to have this saying they lived by: "the competition is only a click away." That was excellent framing, because it was true, and it will remain true even if Google captures 99% of the search market. The key is to cultivate a healthy fear of competing products, not of your investors or the end of hypergrowth. Enshittification helps your competitors. That would be dumb.

  (And don't cheat by using lock-in to make competitors not, anymore, "only a click away." That's missing the whole point!)

• Inoculate yourself. If you have to, create your own competition. Linus Torvalds, the creator of the Linux kernel, famously also created Git, the greatest tool for forking (and maybe merging) open source projects that has ever existed. And then he said, this is my fork, the Linus fork; use it if you want; use someone else's if you want; and now if I want to win, I have to make mine the best. Git was created back in 2005, twenty years ago. To this day, Linus's fork is still the central one.

If you combine these defenses, you can be safe from the decline that others tell you is inevitable. If you look around for examples, you'll find that this does actually work. You won't be the first. You'll just be rare.

Side note: Things that aren't enshittification

I often see people worry about enshittification that isn't. They might be good or bad, wise or unwise, but that's a different topic. Tools aren't inherently good or evil. They're just tools.

1. "Helpfulness." There's a fine line between "telling users about this cool new feature we built" in the spirit of helping them, and "pestering users about this cool new feature we built" (typically a misguided AI implementation) to improve some quarterly KPI. Sometimes it's hard to see where that line is. But when you've crossed it, you know.

   Are you trying to help a user do what they want to do, or are you trying to get them to do what you want them to do?

   Look into your heart. Avoid the second one. I know you know how. Or you knew how, once. Remember what that feels like.

2. Charging money for your product. Charging money is okay. Get serious. Companies have to stay in business.

   That said, I personally really revile the "we'll make it free for now and we'll start charging for the exact same thing later" strategy. Keep your promises.

   I'm pretty sure nobody but drug dealers breaks those promises on purpose. But, again, desperation is a powerful motivator. Growth slowing down? Costs way higher than expected? Time to capture some of that value we were giving away for free!

   In retrospect, that's a bait-and-switch, but most founders never planned it that way. They just didn't do the math up front, or they were too naive to know they would have to. And then they had to.

   Famously, Dropbox had a "free forever" plan that provided a certain amount of free storage. What they didn't count on was abandoned accounts, accumulating every year, with stored stuff they could never delete. Even if a very good fixed fraction of users each year upgraded to a paid plan, all the ones that didn't, kept piling up... year after year... after year... until they had to start deleting old free accounts and the data in them. A similar story happened with Docker, which used to host unlimited container downloads for free. In hindsight that was mathematically unsustainable. Success guaranteed failure.

   Do the math up front. If you're not sure, find someone who can.

3. Value pricing. (ie. charging different prices to different people.) It's okay to charge money. It's even okay to charge money to some kinds of people (say, corporate users) and not others. It's also okay to charge money for an almost-the-same-but-slightly-better product. It's okay to charge money for support for your open source tool (though I stay away from that; it incentivizes you to make the product worse).

   It's even okay to charge immense amounts of money for a commercial product that's barely better than your open source one! Or for a part of your product that costs you almost nothing.

   But, you have to do the rest of the work. Make sure the reason your users don't switch away is that you're the best, not that you have the best lock-in. Yeah, I'm talking to you, cloud egress fees.

4. Copying competitors. It's okay to copy features from competitors. It's okay to position yourself against competitors. It's okay to win customers away from competitors. But it's not okay to lie.

5. Bugs. It's okay to fix bugs. It's okay to decide not to fix bugs; you'll have to sometimes, anyway. It's okay to take out technical debt. It's okay to pay off technical debt. It's okay to let technical debt languish forever.

6. Backward incompatible changes. It's dumb to release a new version that breaks backward compatibility with your old version. It's tempting. It annoys your users. But it's not enshittification for the simple reason that it's phenomenally ineffective at maintaining or exploiting a monopoly, which is what enshittification is supposed to be about. You know who's good at monopolies? Intel and Microsoft. They don't break old versions.

Enshittification is real, and tragic. But let's protect a useful term and its definition! Those things aren't it.

Epilogue: a special note to founders

If you're a founder or a product owner, I hope all this helps. I'm sad to say, you have a lot of potential pitfalls in your future. But, remember that they're only potential pitfalls. Not everyone falls into them.

Plan ahead. Remember where you came from. Keep your integrity. Do your best.

I will too.

Tedenske novice

Vse novice

The post L’mit novičke appeared first on DrogArt.

Na Pravni fakulteti v Ljubljani bo potekala raziskava o uporabi konoplje za samozdravljenje v obliki polstrukturiranih intervjujev z uporabniki in uporabnicami, ki konopljo za samozdravljenje pridobivajo na črnem trgu. Samozdravljenje naj bo razumljeno zelo široko. 

Pogovori bodo predstavljali pomemben vpogled v družbene dejavnike, izkušnje ter občutke uporabnikov in uporabnic ter sicer pomenili dragocen prispevek k znanosti na tem področju. Intervjuji bodo anonimizirani in okvirno trajali med 60 ter 90 minut.

Vsi udeleženci in udeleženke v raziskavi ste lepo vabljeni k sodelovanju!

Za več informacij se obrnite na izvajalki raziskave: dr. Kristino Čufar (kristina.cufar@pf.uni-lj.si) in Nino Žnidaršič (nina.znidarsic@inst-krim.si).

The post Sodeluj v raziskavi o uporabi konoplje za samozdravljenje appeared first on DrogArt.

OBVESTILO
Sporočamo, da bo info točka v Ljubljani v torek 10.6. zaprta v sredo 11.6. bo obratovala med 10. in 14. uro.

Dnevni center za mlade v Ljubljani deluje nemoteno po običanjem urniku.

Hvala za razumevanje,

tvoja ekipa DrogArt

The post Spremenjen urnik DrogArt info točke v Ljubljani appeared first on DrogArt.

V sodelovanju z Društvom Stigma bomo za osebe, ki imajo izkušnjo uporabe drog, organizirali testiranje na HIV, virusne hepatitise in SPO. Testiranje je brezplačno in anonimno.

Hvala Društvu Stigma in projeku Expand za tole priložnost! Več info na letaku.

The post Testiranje na HIV in HEP na DrogArtu appeared first on DrogArt.

OBVESTILO
Sporočamo, da bo info točka v Ljubljani od torka 3.6. do petka 6.6. obratovala med 10. in 14. uro.

Dnevni center za mlade v Ljubljani in sprejem vzorcev za testiranje, delujejo nemoteno po običanjem urniku.

Hvala za razumevanje,

tvoja ekipa DrogArt

The post Spremenjen urnik DrogArt info točke v Ljubljani appeared first on DrogArt.

OBVESTILO
Sporočamo, da bo info točka v Ljubljani od torka 27.5. do petka 30.5. obratovala med 10. in 14. uro.

Dnevni center za mlade v Ljubljani in sprejem vzorcev za testiranje, delujejo nemoteno.

Hvala za razumevanje,

tvoja ekipa DrogArt

The post Spremenjen urnik DrogArt info točke v naslednjem tednu appeared first on DrogArt.

Tedenske novice

Vse novice

The post L’mit novičke appeared first on DrogArt.

OBVESTILO
Sporočamo, da bo info točka v Ljubljani zaprta v ponedeljek 19.5., v torek 20.5. bosta zaprta info točki v Ljubljani in Mariboru in od srede do petka bo info točka v Ljubljani obratovala med 10 in 14 uro.

Dnevni center za mlade v Ljubljani in sprejem vzorcev za testiranje, delujejo nemoteno.

Hvala za razumevanje,

tvoja ekipa DrogArt

The post Spremenjen urnik DrogArt info točke v naslednjem tednu appeared first on DrogArt.

OBVESTILO
Sporočamo, da bo od torka 13.5. do petka 16.5.2025, zaprta DrogArt infotočka v Ljubljani. Dnevni center za mlade v Ljubljani in sprejem vzorcev za testiranje, delujeta nemoteno.

Še vedno smo za vse informacije dosegljivi preko telefona (01 439 72 70) med 10.00 in 16.00 uro.

Hvala za razumevanje,

tvoja ekipa DrogArt

The post Od torka 13.5. do petka 16.5.2025 bo DrogArt infotočka v Ljubljani zaprta appeared first on DrogArt.

OBVESTILO

Od srede, 7. 5. 2025, do petka 9. 5. 2025 bo infotočka v Ljubljani delovala spremenjeno, in sicer:

• telefonska dosegljivost med 9h in 15h,
• osebna dosegljivost (prevzem materiala, pakiranje…) po predhodnem telefonskem dogovoru.

Tel.: 01 439 72 70.

Dnevni center, svetovalnica in testiranje potekajo nemoteno.

Hvala za razumevanje,
tvoja ekipa DrogArt

The post Spremenjeno delovanje info točke v Ljubljani appeared first on DrogArt.

Aktivne snovi

MDMA (184 mg)

Dodaten opis

Pri več kot 1,5 mg MDMA na kg telesne teže se hitreje pojavijo neželeni učinki, kot so zategovanje čeljusti, mišični krči, panična reakcija in epileptični napad. V naslednjih dneh se po zaužitju večjih odmerkov MDMA lahko pojavi povečana depresija, pomanjkanje koncentracije, motnje spanja, izguba apetita in občutek močne brezvoljnosti. Simptomi po nekaj dneh izzvenijo.

Upoštevaj spodnje smernice zmanjševanja tveganj!

Disclaimer: Količina MDMA v tableti je zgolj informativne narave in se lahko pri tabletah z istim logotipom in barvo bistveno razlikuje.

Datum testa

13.6.2025

Zmanjševanje tveganj

• Prilagodi odmerek glede na svojo težo in izkušenost. Literatura navaja, da je odmerek MDMA 1─1,5 mg/kg telesne mase, kar za 60 kg težkega človeka znaša 60─90 mg.
• Bodi zelo pozoren, če MDMA uporabljaš prvič, ali če ne veš, koliko čist MDMA imaš. Učinki so lahko zelo raznoliki in nekateri ljudje čutijo veliko bolj intenzivno negativne učinke (tako fizične kot psihične). Zmeraj začni z majhnimi dozami (npr. četrtinko ekstazija ali lahko dozo MDMA-ja v kristalih) in počakaj vsaj 2h.
• Delaj redne premore med plesom.
• Vsako uro spij do pol litra izotoničnega napitka, če plešeš, drugače pa manj.
• Ne mešaj različnih drog med seboj, ne mešaj z zdravili.
• Ne jemlji različnih tablet v eni noči.
• Poskrbi za ustrezno prehrano in dovolj spanca med tednom.
• Delaj pavze med uživanjem MDMA-ja (2-3 mesece med eno uporabo in drugo).
• Če opaziš težave, ki bi bile lahko povezane z uporabo ekstazija, poišči pomoč.

The post Super Mario (MDMA) appeared first on DrogArt.

Aktivne snovi

3-CMC (okvirno 93 %)

Dodaten opis

Rezultati analize, narejene v Nacionalnem laboratoriju za zdravje, okolje in hrano, so pokazali, da vzorec v obliki prahu, ki se je v Ljubljani prodajal kot sladoled (3-MMC), dejansko vsebuje 3-CMC .

O snovi 3-CMC ni na voljo veliko informacij, predvideva pa se, da povzroča podobne stranske učinke kot drugi sintetični katinoni, in sicer: povišan srčni utrip, povišan krvni tlak, vznemirjenost, psihoze, epileptični napad, pregretje telesa, bolečine v prsih, itn. V povezavi z uporabo 3-CMC je pet držav EU poročalo številne zastrupitve in smrtne primere.

Datum testa

31.1.2025

Zmanjševanje tveganj

• V letošnjem in lanskem letu smo zaznali večje število lažnih produktov, ki so se prodajali kot sladoled (3-MMC) in mefedron. Če ga uporabljaš, se zato še posebej priporoča uporabo anonimne storite testiranja drog.

• Trenutno je na voljo malo informacij o tveganjih povezanih s 3-CMC in ostalimi katinoni. 4-kloroamfetamin (4-CA, amfetaminski derivat) je znan kot zelo nevrotoksična substanca. Ker sta si 4-CA in 3-CMC strukturno zelo podobna, obstaja verjetnost, da gre tudi v primeru 3-CMCja za toksično substanco. Trenutno ni nobenih raziskav, ki bi to potrdile, vendar se priporoča, da se vnosu omenjene spojine izognemo.

Vzorec je v okviru anonimnega zbiranja vzorcev psihoaktivnih snovi zbrala info točka Združenja DrogArt. Analizo vzorca je izvedel Nacionalni laboratorij za zdravje, okolje in hrano. Obvestilo je pripravil Nacionalni inštitut za varovanje zdravja.

The post 3-CMC prodan kot sladoled (4-MMC) v Ljubljani appeared first on DrogArt.

Aktivne snovi

2C-B (11 mg)

Dodaten opis

Tabletka vsebuje psihedelik 2C-B. Ker se običajno prodaja v obliki tablet, je možna nenamerno zamenjava s ekstazi tabletami, ki vsebujejo MDMA. Zaradi možnega manjšega učinka pri tabletah z manjšo vsebnostjo 2C-B obstaja nevarnost redoziranja in s tem zaužitja velike količine 2C-B.

Upoštevaj spodnje smernice zmanjševanja tveganj!

Disclaimer: Količina 2C-B v tableti je zgolj informativne narave in se lahko pri tabletah z istim logotipom in barvo bistveno razlikuje.

Datum testa

13.6.2025

Zmanjševanje tveganj

• Bodite pazljivi pri doziranju. Lahka doza za 2C-B je 2-10 mg, srednja doza 10-20 mg in močna doza 20-30 mg.
• 2C-B se vedno jemlje na prazen želodec, saj v nasprotnem primeru ob začetku učinkovanja, lahko povzroči neprijetno slabost in krče. Poskrbite torej za lahek obrok vsaj 3-4 ure preden vzamete 2CB. V primeru slabosti pomaga, če vstanete in se nekoliko sprehodite.
• Glede na svoje psihadelične učinke nosi 2C-B s seboj vsa tveganja, ki veljajo za psihadelične droge: paranoične reakcije, bad tripi, izguba stika z realnostjo. Poskrbi za  primerno okolje uporabe v katerem se dobro počutiš in da si v dobri psihofizični kondiciji (set in setting).
• Če se odločiš za uporabo na partiju, je bolje da vzameš manjšo dozo (brez halucinacij) in da svojim prijateljem poveš kaj si vzel/a.
• Če plešete na 2C-B-ju pazite (prav tako kot pri MDMA), da vsake toliko časa popijete nekoliko požirkov brezalkoholne tekočine.

The post NASA rocket (2C-B) appeared first on DrogArt.

Aktivne snovi

MDMA (184 mg)

Dodaten opis

Pri več kot 1,5 mg MDMA na kg telesne teže se hitreje pojavijo neželeni učinki, kot so zategovanje čeljusti, mišični krči, panična reakcija in epileptični napad. V naslednjih dneh se po zaužitju večjih odmerkov MDMA lahko pojavi povečana depresija, pomanjkanje koncentracije, motnje spanja, izguba apetita in občutek močne brezvoljnosti. Simptomi po nekaj dneh izzvenijo.

Upoštevaj spodnje smernice zmanjševanja tveganj!

Disclaimer: Količina MDMA v tableti je zgolj informativne narave in se lahko pri tabletah z istim logotipom in barvo bistveno razlikuje.

Datum testa

13.6.2025

Zmanjševanje tveganj

• Prilagodi odmerek glede na svojo težo in izkušenost. Literatura navaja, da je odmerek MDMA 1─1,5 mg/kg telesne mase, kar za 60 kg težkega človeka znaša 60─90 mg.
• Bodi zelo pozoren, če MDMA uporabljaš prvič, ali če ne veš, koliko čist MDMA imaš. Učinki so lahko zelo raznoliki in nekateri ljudje čutijo veliko bolj intenzivno negativne učinke (tako fizične kot psihične). Zmeraj začni z majhnimi dozami (npr. četrtinko ekstazija ali lahko dozo MDMA-ja v kristalih) in počakaj vsaj 2h.
• Delaj redne premore med plesom.
• Vsako uro spij do pol litra izotoničnega napitka, če plešeš, drugače pa manj.
• Ne mešaj različnih drog med seboj, ne mešaj z zdravili.
• Ne jemlji različnih tablet v eni noči.
• Poskrbi za ustrezno prehrano in dovolj spanca med tednom.
• Delaj pavze med uživanjem MDMA-ja (2-3 mesece med eno uporabo in drugo).
• Če opaziš težave, ki bi bile lahko povezane z uporabo ekstazija, poišči pomoč.

The post Super Mario (MDMA) appeared first on DrogArt.

Aktivne snovi

MDMA (153 mg)

Dodaten opis

Pri več kot 1,5 mg MDMA na kg telesne teže se hitreje pojavijo neželeni učinki, kot so zategovanje čeljusti, mišični krči, panična reakcija in epileptični napad. V naslednjih dneh se po zaužitju večjih odmerkov MDMA lahko pojavi povečana depresija, pomanjkanje koncentracije, motnje spanja, izguba apetita in občutek močne brezvoljnosti. Simptomi po nekaj dneh izzvenijo.

Upoštevaj spodnje smernice zmanjševanja tveganj!

Disclaimer: Količina MDMA v tableti je zgolj informativne narave in se lahko pri tabletah z istim logotipom in barvo bistveno razlikuje.

Datum testa

13.6.2025

Zmanjševanje tveganj

• Prilagodi odmerek glede na svojo težo in izkušenost. Literatura navaja, da je odmerek MDMA 1─1,5 mg/kg telesne mase, kar za 60 kg težkega človeka znaša 60─90 mg.
• Bodi zelo pozoren, če MDMA uporabljaš prvič, ali če ne veš, koliko čist MDMA imaš. Učinki so lahko zelo raznoliki in nekateri ljudje čutijo veliko bolj intenzivno negativne učinke (tako fizične kot psihične). Zmeraj začni z majhnimi dozami (npr. četrtinko ekstazija ali lahko dozo MDMA-ja v kristalih) in počakaj vsaj 2h.
• Delaj redne premore med plesom.
• Vsako uro spij do pol litra izotoničnega napitka, če plešeš, drugače pa manj.
• Ne mešaj različnih drog med seboj, ne mešaj z zdravili.
• Ne jemlji različnih tablet v eni noči.
• Poskrbi za ustrezno prehrano in dovolj spanca med tednom.
• Delaj pavze med uživanjem MDMA-ja (2-3 mesece med eno uporabo in drugo).
• Če opaziš težave, ki bi bile lahko povezane z uporabo ekstazija, poišči pomoč.

The post Moncler (MDMA) appeared first on DrogArt.

Aktivne snovi

Bromazolam (~ 6 mg)

Dodaten opis

Analiza Nacionalnega laboratorija za zdravje, okolje in hrano je pokazala, da vzorec v obliki pravokotne modre tabletke z napisom »B707« vsebuje okvirno 6 mg bromazolama (masa celotne tabletke je 390,63 mg). Tabletka je bila kupljena na temnem spletu.

Bromazolam sodi v skupino benzodiazepinov, vendar je slabo raziskan in o njem ni veliko znanega. Srednji odmerek po poročanju uporabnikov znaša 1 – 2mg, kar pomeni, da zaužitje že ene tabletke predstavlja večje tveganje za predoziranje. Benzodiazepini lahko povzročijo močno sedacijo in depresijo dihanja (upočasnjeno dihanje, dihalni zastoj). Benzodiazepini v večjih dozah zaradi svojih depresorskih učinkov lahko povzročijo predoziranje, ki lahko vodi v komo. Smrtno nevarno pa je tudi njihovo kombiniranje z drugimi depresorskimi substancami. Hkrati povzročajo močno psihično in fizično zasvojenost.

Po poročanju so v UKC Maribor v povezavi s tem vzorcem obravnavali tri zastrupitve.

Datum testa

6.5.2025

Zmanjševanje tveganj

• Če se že odločiš za uporabo, uživaj benzodiazepine v majhnih dozah in jih nikoli ne mešaj z ostalimi depresorskimi drogami (alkohol, opiati, GHB/GBL …), saj obstaja velika nevarnost predoziranja.
• Ne uporabljaj jih pogosto, saj povzročajo močno zasvojenost.
• Na uporabo se predhodno pripravi in si doze pripravi vnaprej, saj se pri benzodiazepinih pogosto pojavita lažen občutek treznosti in kompulzivno redoziranje.
• Nikoli ne vozi nikogar ali ničesar pod vplivom benzodiazepinov.
• Svojih težav ne skušaj reševati na lastno pest z benzodiazepini s črnega trga, raje obišči zdravnika ali pa se oglasi v DrogArtovi ali kateri drugi svetovalnici.
• Ob morebitnem nastanku zasvojenosti poišči kvalitetno strokovno pomoč (osebni zdravnik, psihiater, DrogArt, Stigma, druge nevladne organizacije …)
• Po partiju se ne »spuščaj« z benzodiazepini. Mešanje s katerimi koli substancami je vedno nevarno početje. Svojemu telesu raje privošči kvaliteten obrok in kakovosten spanec, ki bo slej ko prej nastopil sam.
• Pri benzodiazepinih, kupljenih na črnem trgu, je še posebej pomembno laboratorijsko testiranje zaradi možnosti ponaredkov oziroma lažnih tablet. Četudi na tableti piše npr. »Xanax«, to ni nikakršno zagotovilo, da tableta zares vsebuje alprazolam, ampak lahko vsebuje kateri drug, močnejši benzodiazepin ali pa čisto nekaj drugega.
• Če oseba, ki je zaužila benzodiazepin, izgubi zavest, jo položi v položaj za nezavestne in ne odlašaj s klicem na 112.

The post Modra tableta “B 7 0 7” z visoko vsebnostjo bromazolama appeared first on DrogArt.

Aktivne snovi

MDMA (151 mg)

Dodaten opis

Pri več kot 1,5 mg MDMA na kg telesne teže se hitreje pojavijo neželeni učinki, kot so zategovanje čeljusti, mišični krči, panična reakcija in epileptični napad. V naslednjih dneh se po zaužitju večjih odmerkov MDMA lahko pojavi povečana depresija, pomanjkanje koncentracije, motnje spanja, izguba apetita in občutek močne brezvoljnosti. Simptomi po nekaj dneh izzvenijo.

Upoštevaj spodnje smernice zmanjševanja tveganj!

Disclaimer: Količina MDMA v tableti je zgolj informativne narave in se lahko pri tabletah z istim logotipom in barvo bistveno razlikuje.

Datum testa

6.6.2025

Zmanjševanje tveganj

• Prilagodi odmerek glede na svojo težo in izkušenost. Literatura navaja, da je odmerek MDMA 1─1,5 mg/kg telesne mase, kar za 60 kg težkega človeka znaša 60─90 mg.
• Bodi zelo pozoren, če MDMA uporabljaš prvič, ali če ne veš, koliko čist MDMA imaš. Učinki so lahko zelo raznoliki in nekateri ljudje čutijo veliko bolj intenzivno negativne učinke (tako fizične kot psihične). Zmeraj začni z majhnimi dozami (npr. četrtinko ekstazija ali lahko dozo MDMA-ja v kristalih) in počakaj vsaj 2h.
• Delaj redne premore med plesom.
• Vsako uro spij do pol litra izotoničnega napitka, če plešeš, drugače pa manj.
• Ne mešaj različnih drog med seboj, ne mešaj z zdravili.
• Ne jemlji različnih tablet v eni noči.
• Poskrbi za ustrezno prehrano in dovolj spanca med tednom.
• Delaj pavze med uživanjem MDMA-ja (2-3 mesece med eno uporabo in drugo).
• Če opaziš težave, ki bi bile lahko povezane z uporabo ekstazija, poišči pomoč.

The post Moncler (MDMA) appeared first on DrogArt.