Notices by Elly, nasty enby :heart_pan: (elizafox@mst3k.interlinked.me), page 47

Traffic management and prioritisation are good network practises, not cardinal sins. They are also only adjacent to what net neutrality is about.

How I think your average Ars Technica idiot thinks net neutrality works is "my torrents can just go line speed and also and also I don't get bandwidth caps" and that is not what net neutrality means at all, actually.

There's so much misunderstanding around how net neutrality works, and every argument I've seen to try to explain it to laypeople boils down to either "lies to children" style explanations, or outright fabrications.

Ignorance of how the Internet actually works is widespread. A lot of people (leftists, but even normal people) think it's just this magical thing you just shove packets into and you get packets back. This is not how it works at all. It is mostly made up of quid pro quo deals, whether it be roughly equal exchanges of traffic (peering), or you pay for it (transit).

No one wants to discuss how things like peering, transit, laying fibre, etc. work. Or how the Internet is presently /powered/ by what is essentially unregulated Capitalism, for better or for worse, and how a "free pipe" basically *does not exist* and *someone* is always paying for transit.

Because that's not fun.

Sigh, the enormous amount of misunderstanding of how the Internet works is astounding, even amongst people who should know better.

I'm thankful for 👏 SPANKO 👏

The past is easy. You get new limitations. You get new intrigue and plot points. But I feel like it's been done to death in Star Trek. We literally know basically /everything/ from the first warp flight to TOS and a bit in-between TOS and TNG. Just do the freaking future already.

@guinan @Trev @er1n s1 was when Roddenberry still played an active role... but he was clearly in his twilight years. It also suffered from early installment weirdness, as most shows do.

s2 was affected by the strike. Really bad. It was also when Crusher was introduced, that didn't help.

s3 saw the introduction of new writers. Roddenberry was basically gone.

Also, they kept going overbudget. They had bottle episodes to keep it cheap late-season (which often blew the budget anyway).

GIVE ME LIBERTY, OR GIVE ME FAIR AND REASONABLE COMPENSATION IN RETURN

PSA: not a good idea to mix household cleaning solvents

vinegar + bleach = chlorine gas and heat

ammonia + bleach = chloramine gas, incredibly poisonous and can kill you in a confined space

isopropyl alcohol + bleach = chloroform, can be poisonous to the liver

peroxide + vinegar = parecetic acid, corrosive and irritating

vinegar + ammonia or vinegar + baking soda = ineffective cleaning solution

peroxide + bleach = oxygen gas, if there is a source of ignition it can be an explosion hazard

mst3k doesn't really block too many people. When we do, their behaviour has been so egregious and incorrigible there is literally no way forward. Instance bans are also very much "last-resort" and we've only got four of them.

We do filter a lot of instances from the FTL, though. That's usually sufficient to protect users. If it's not, we re-evaluate it as it comes up.

𝗺𝘀𝘁𝟯𝗸 𝗦𝘁𝗮𝘁𝗶𝗼𝗻

🔴 𝗟𝗶𝗻𝗲

𝗖𝗼𝗻𝗻𝗲𝗰𝘁𝗶𝗼𝗻 🔵 𝘁𝗼 𝗠𝗮𝘀𝘁𝗼𝗱𝗼𝗻 𝗦𝗼𝗰𝗶𝗮𝗹 𝗦𝘁𝗮𝘁𝗶𝗼𝗻 ↘️

I think another part of IRC being user-hostile is that most server software is horrifically inflexible and rigid. Virtually every ircd in active development was never really designed to do much more than what it does now. So bolting anything new on is like trying to put lipstick on a pig.

They would rather bicker over STS, because proposals of any substance or genuine improvement basically die on arrival because one of two things happens with every proposal:

1) Major stakeholder is like "THIS SUCKS I AM NEVER IMPLEMENTING THIS"

2) Insistence that "THEY SHOULD CONFORM TO WHAT WE'RE DOING"

and I care about IRC but I just, I can't deal with that kind of "standardisation".

IRCv3 would rather worry more about STS (the solution: DEPRECATE PLAINTEXT, EVERY DECENT NETWORK SUPPORTS SSL) than solve real problems

I tried to fix numerics, and I got almost nowhere.

the IRC development community (mostly server-side, but a bit client-side too) is full of huge egos and people with their own impossible visions of the protocol, and finding a neutral broker everyone can accept is basically fucking impossible

Every time someone says "why doesn't someone just modernise and fix IRC?" I just smh

'cause we tried.

@Trev @KitRedgrave @bea smells like another way to keep poor people out of tech.

"you must have this much money and this much of your own tech before joining our club"

it's gross