> I lived in DTLA for several years and regularly used Little Tokyo/Arts District station. It was not uncommon during peak hours to see people - myself included sliding down the railing.
The Little Tokyo stop had no stairs or escalators before 2023, since it was at grade then. Do you mean a different stop?
Also, the busiest stations with huge escalator length, like Union Station or Wilshire/Vermont, have so much open space that escalators are rarely a bottleneck in my experience. 7th St/Metro station is crazy crowded, but the escalators are short and people usually give you room to run down the escalator.
The only station I worry about for future congestion is the Grand Ave station, which has no escalators, but is so deep that you have to take an elevator since walking stairs is not reasonable except for emergencies.
Yep, you are correct. I am just now realizing that maybe this is why there was such a culture around it. Lil Tokyo was closest to this spot and we regularly would grab things from Sakura Market for each other, talk random shit etc... one day this guy was scared/sad about a girl he really liked and we convinced him to approach her and so we played Lupe (https://www.youtube.com/watch?v=YhuYwE-gAn0) on the whole ride - much to the annoyance of the other passengers.
There was also a respect that I cant forget; almost like it was a rhythm. Never a rush to beat someone else to the train. I remember that for a time due to our schedules we would meet at the top, smoke a J and chat for as long as we could then slide down and catch the redline (now called the B Line*) and part ways.
Note: He got the girl. we all lost contact - hope he/they are dong well.
\Note: I wonder if the redline was renamed because of the level of violence or if it was because of the purple line expansion.
There aren’t many primary and secondary colors. If you plan to have a more comprehensive system you’ll run out pretty quick. Chicago comes to mind. The newest one is pink and I’m not sure what they’d do if they built a new one.
This already exists. I got a Thinkpad T14s 2-in-1 last year from Lenovo, and it shipped with Ubuntu, which made the price around $50 cheaper if I recall. I replaced it with Debian, of course, but the battery life is fine and it is a quiet machine.
I also purchased the T14s Snapdragon two years ago, and it gets longer battery life (if you just use a terminal only, the battery life remaining will sometimes say 20 hours, but it's more like 14-15 realistically). However, it can get uncomfortably hot on the left edge at the speaker. The T14s 2-in-1 (Intel) does not have any hot spots, though.
The Thinkpad T14s 2-in-1 with Intel Core Ultra 5 has great battery life: 10+ hours with moderate usage. I also have the Snapdragon T14s which gets about 14 hours, but I'm still waiting to get full Linux support for this two year old laptop.
Note however, since I've been using my Thinkpad 2-in-1 on battery almost everyday for a year, it is somewhat degraded. upower shows
It's hard to show with any accuracy how likely a filesystem is to not break when the SHTF or something weird happens, or if they've handled all the weird corner cases, with any kind of automated test.
For that you have to dig into the methodology, look at the code, look at user reports, etc.
But you can get a pretty good approximation just from the philosophies and attitudes of the engineers and what they're talking about.
The talk I just gave at the Rust for Linux conference was all about that - how do we make the system debugable, the community aspect of how we respond to bug reports and talk to users, the prep work for the Rust conversion and formal verification and how we're approaching all that.
Reliability doesn't come out of nowhere, "all bugs are shallow with enough eyeballs" really doesn't apply to filesystems. You just have to plan for it, come up with a methodology, and do the work.
It's not materially better now. The devs are in denial about the problems because lots of big users are saying "works fine on my machine."
Sure, if you have lots of backups, if you have huge volumes on huge disks and they never fill up...
But it's the default in Fedora, Spiral Linux, Garuda Linux, siduction and others. Personal distros for people's own PCs and those are not well-supported enterprise kit.
SUSE takes snapshots before packages are installed. The package manager cannot tell if the disk will fill up as a result because on Btrfs the `df` command lies.
If its Btrfs root fills up and the OS writes to it, it 100% will self-destruct, and the `btrfs-repair` tool (`fsck` replacement) cannot fix drives and usually makes the corruption worse and renders the drive unreadable.
This is why in the earlier thread about swapfiles...
... I advised 2 commenters not to recommend keeping the OS and data in a single big volume. I got downvoted for it. I was rude. Well, I was, but I stand by my comments even though I'm sorry for my tone when I made them.
The more practical advice is to resize hard partitions down by 5-10%.
I have a loopback mount on an fallocate file with a btrfs filesystem inside of it at work. I'm using send/receive to make sure there is hope of recovery.
> The frontier LLM model makers have to push the edge to make new discoveries. You don't know what guardrails are needed until it hits you in the face (reusing walking in the dark analogy).
Guardrails? Restricting access to certain networks is supposed to be hard in 2026?
> Restricting access to certain networks is supposed to be hard in 2026?
Part of the power of LLM agents is that they can discover information on the internet as part of responding to a prompt. What kind of Allowlist or realistic denylist would permit that while also preventing them from accessing an obscure public wiki or Huggingface?
When testing, you restrict to a LAN which simulates the real internet. This would not be hard for a company which already copied the entire space-time of the internet. The LAN should be physically disconnected from the real internet. This is the first thing off the top of my head, and I have zero credentials in this space. C'mon.
If I recall (too lazy to check) folks made slight improvements to Perelman's work and published it in mainstream journals, satisfying the "qualifying outlet" requirement.
A much easier hack by their agents would be on their own systems, but I doubt we'll ever see an external message board full of openAI agents discussing their hacking of their own system. OpenAI not protecting itself from its agents would be irrational, but OpenAI not giving a shit about others is well known. You're giving them way too much credit.
Now that the revolution has apparently started, does anyone know of a version control system which uses encrypted storage? (I'm not concerned about performance, for I will use it for small projects only.)
Sorry, I did not specify the threat model. If I git push to an encrypted volume on a virtual server, like on Linode or Digital Ocean, anyone with access to the hardware can inspect unencrypted data on a live volume.
Concerning [5], the article says he was rejected at UC Santa Barbara. Haven't checked in a while, but I believe UCSB historically accepts 40-50% of first time applicants. The schools were not using SAT scores at the time, and UC has banned race considerations in admissions for nearly 30 years. Surely there's more to this story.
Most schools that say they don't consider race in admissions mean they don't use a racial quota where e.g. they require x% of the student body to be some minority or whatever. That's because such quotas have been ruled illegal. But the way admissions generally work is that your application is graded on a points system, and they get around the law by using a points modifier based on race. And that modifier can be adjusted as necessary to ensure they get exactly x% of the student body to be that minority. So it's racial quotas by proxy.
Another modifier is going to be parental income, which I think makes much more sense than race. But those two modifiers can compound to make it where something like an Asian from a high household income family needs to essentially be the next Einstein in order to be admitted over an average student who happens to be from a historically poor performing minority.
The Little Tokyo stop had no stairs or escalators before 2023, since it was at grade then. Do you mean a different stop?
Also, the busiest stations with huge escalator length, like Union Station or Wilshire/Vermont, have so much open space that escalators are rarely a bottleneck in my experience. 7th St/Metro station is crazy crowded, but the escalators are short and people usually give you room to run down the escalator.
The only station I worry about for future congestion is the Grand Ave station, which has no escalators, but is so deep that you have to take an elevator since walking stairs is not reasonable except for emergencies.
reply