neKristīne (@cresado) profile picture

[email protected] Par mazliet labāku pasauli. Tehnoloģijas, dati, statistika, fantastika.

LV
Joined November 2009
Photo by neKristīne (@cresado)Photo by neKristīne (@cresado)Photo by neKristīne (@cresado)Photo by neKristīne (@cresado)Photo by neKristīne (@cresado)Photo by neKristīne (@cresado)Photo by neKristīne (@cresado)Photo by neKristīne (@cresado)Photo by neKristīne (@cresado)Photo by neKristīne (@cresado)
Visiem, kas metas vainot ļaunos un briesmīgos telefonus Latvijas PISA vērtējumu katastrofā - ieteiktu palasīt pieejamos datus tālāk par virsrakstu (ja kas.. .viena no prasmēm, ko PISA pārbaudīja) (1/n)
4
14
52
7,256
neKristīne retweeted
天啊,终于有种有趣的方式来学普通话了 😂
83
572
118
4,550
772,354
NEW CVSS 10.0 JUST DROPPED ON <the security industry as a whole> Impact: The entire security industry as a whole is DOS'd and cannot function and is running on caffeine and 0 hours of sleep. There is no patch. This one is real bad.
11
54
8
382
47,898
neKristīne retweeted
Var runāt par demogrāfiju uz riņķi, bet tiklīdz publikā parādies ar bērnu, tā čupa zākātāju rullē acis: "nu kā tā var, bērnam jābūt krātiņā, publiski rādīt nedrīkst, izņemot kaut kādas ģimenes dienas izolētā teritorijā" Ja gribam bērnus, jāpieņem, ka bērni ir daļa no sabiedrības.
Militārā parāde 2027. Un stāsts nav par bērniem, kas to joprojām nesaprot. Ir civilā ssktotaju zona un ir augstākā militārā vadība un amatpersonas. 2027 aiz skatuves uzlieciet lūdzu arī bērniem karuseļus.
14
14
1
186
4,532
Būtu brīnišķīgi! Un žurnālisti varētu sākt uzdot jautājumus - ja savu nav un neviens rads/draugs nav ar mieru uz dažām stundām uzticēt, kam šāda persona vada valsti? Parāde godina gatavību sargāt valsti. Bērni ir valsts nākotne.
Militārā parāde 2027. Un stāsts nav par bērniem, kas to joprojām nesaprot. Ir civilā ssktotaju zona un ir augstākā militārā vadība un amatpersonas. 2027 aiz skatuves uzlieciet lūdzu arī bērniem karuseļus.
1
14
369
Atkal jau mums protokols un etiķete stingrāka kā Anglijas karalienei. Uz sitiena labāka bildīte ar Prinča Luija vēl nepareizāku uzvedību, kad bija jaunāks, neatradās. Francijas Bastīlijas dienas parādē arī visim gan partneri/es, gan bērni (tik bērnu sejas prese piesedz) ir norma
Nē. Šis. Nav. Ok. Ja nepatīk vārdi protokols un etiķete, tad varbūt der elementāra pieklājība un cieņa. Šī ir militārā parāde. Bet rodas iespaids,ka šo vecāku bērniem arī Tutas koncertā ļauj kāpt uz skatuves. Ļoti uzskatāmi par to, kāds nihilisms pret normām mūs sagaida.
10
7
69
4,501
Another simple explanation is that an average software update has a low to medium chance of breaking the system. Previously, orgs navigated this by performing extensive testing, then rolling out updates a few systems at a time. With the severity of some of these security issues being fixed, they can't afford to wait that long. The options are: risk breaking something by rolling out updates too fast, or get hacked and risk lots of things getting broken. Given that we just had a major vulnerability in PHP, and many organizations run PHP, it's not unexpected that we would see some major companies having software outages. PHP applications are highly version specific. Attempting to update PHP is a very well known cause of software breaking. Now, combine that with the fact that many orgs are running with less than the minimum viable number of employees. They got overexcited about AI and tripped over their own feet rushing to preemptively lay off double digit percentages of their workforce. I'm not surprised that there's a ridiculous number of major outages. I'm surprised that there aren't far more. It's amazing some of these companies have managed to hold it together as long as they have. But expect it to only get worse from here on.
33
116
16
739
37,986
neKristīne retweeted
Must must must must must must must must must must must must must must must must must must must must must must must must must must must must must must read if you’re learning harness engineering teapawt.net/theo/status/2113424203… teapawt.net/hwchase17/status/20429… teapawt.net/bytemohit/status/20634… teapawt.net/bibryam/status/2108946… teapawt.net/addyosmani/status/2053…
its hard finding good content on harness engineering for beginners. please drop resources if you have any worth reading or implementing
11
102
4
2,020
120,003
Un tā arī ir labāka kodēšanas pieeja darot to vecmodīgi, ar rociņām.
Like many others, most of my coding today is AI assisted. Unlike others, I don't just shit out prompts to take me to the next turn, I chop up work into bite sized chunks, make new sessions for those chunks, do what I need to, and then make a new session. My token costs are < 50% the teammates who have shared theirs with me. I can imagine I'm < 10% of many of the people in the AI building software bubble. It's not because I build less, I just don't send LLMs on wild goose chases or pollute future context with past problems. This is why the masses think open models are garbage in 2026 relative to frontier labs' models...they just don't know better.
3
300
neKristīne retweeted
苹果亲手给 Mac 上的 Docker Desktop 判了死刑,顺便把 GitHub 炸出了 51.5k Star 🧵 在 Mac 上跑容器,是所有后端和全栈工程师心中的痛。 你以为你在跑轻量级容器,实际上 Docker Desktop 在后台偷偷给你塞了一个吃掉 8G 内存的巨型 Linux 虚拟机,风扇转得像直升机起飞,企业版每年还得交着昂贵的订阅费。 苹果这次直接掀桌子了:开源了纯 Swift 编写的官方工具 apple/container。 最狠的不是它免费(Apache 2.0 协议),而是它底层硬核到变态的架构设计: 别人是“所有容器挤在一个臃肿的 VM 里”,苹果直接利用 macOS 26 的原生虚拟化框架,做到了 “一个容器,一个独立微型 VM”。 很多人第一反应:一个容器起一个 VM,内存和启动速度不得爆炸? 苹果的解法极其暴力:直接用 Swift 写了个 vminitd 塞进精简版 Linux 内核当初始进程,通过 vsock 走 gRPC 通信,把传统 Linux 启动时乱七八糟的系统服务全砍光了。既有硬件级的绝对安全隔离,又保留了毫秒级的冷启动,连跑 amd64 镜像都原生焊死了 Rosetta 2 硬件级加速。 更骚的是苹果官方给的示例库 container-examples。 他们专门写了个叫 containerization-sandboxy 的官方 Demo,教你用短短几十行代码把 Claude Code 这种 AI Coding Agent 关进独立的微型 VM 里跑,只挂载指定目录、卡死网络白名单。 这算盘珠子都崩我脸上了:当所有人都在狂推 Vibe Coding、让 AI 随便接管本地终端的时候,苹果已经在底层用微型 VM 给本地 AI Agent 焊死安全沙盒了——毕竟谁也不想因为 AI 一句幻觉出来的 rm -rf,把宿主机底裤都赔光。 工具链的终局,往往就是被操作系统原厂直接“收编”。 你的 Mac 上现在用的是 Docker Desktop、OrbStack,还是已经准备切到苹果原生 container 了?👇
67
86
11
1,143
148,960
neKristīne retweeted
MIT has an entire course on the stuff you should know at your first engineering job shell, git, debugging, profiling, shipping code the 2026 version even has agentic coding. all free. link: missing.csail.mit.edu/
36
346
18
4,747
157,562
The other thing that kind of bugs me (pun intended), is the "31% of intrusions are the result of software exploitation" statistic. It hides two different problems: Zero-day exploitation - the bad guys find a vulnerability before the good guys, then use it to hack into systems (a problem finding and reporting vulnerabilities reduces). N-Day exploitation - someone reports a vulnerability, a fix gets published, but then the threat actors rush to use the information from the fix to build an exploit before downstream users get a chance to install the fix (a problem finding and reporting vulnerabilities exacerbates). Since organizations typically take a long time to install security fixes, N-day exploits are extremely powerful, and also make up the majority of all software exploitation. There's also 100x more people who can create N-days from known vulnerabilities than can find and exploit Zero-days. The more vulnerabilities found, the more vulnerabilities N-day attackers have to choose from, and the more software fixes that downstream users have to juggle. Orgs struggle to even install the monthly Windows update within a month of it going live. Now mix in "every single product you use has critical vulnerability fixes every patch cycle so you have to install all 4,000 patches every month". And yeah.... It's pretty bleak. That's not to say vulnerability research shouldn't be done, isn't important, or isn't a net long term benefit (I feel like I have to say this because half the people on this fucking website have zero capacity for nuance and try to read every post in the most disingenuous way possible). But since the majority of exploitation is N-day exploitation, and vulnerability research increases N-day exploitation, using exploitation rate as a justification for pouring more resources into find vulnerabilities (but not helping fix or patch them), is just circular reasoning. Plenty of good arguments for why vulnerability research is important, but "we're showing the attackers more vulnerabilities that they can use, which is leading to them using more vulnerabilities" is not one of them. Equal effort needs to go into all part of the vulnerability management pipeline for this to work. But currently the effort drops by a factor of 10 from finding bugs to fixing bugs, then another factor of 10 from fixing bugs to ensuring the fixes get installed. Just reducing the disclosure window and telling everyone "don't worry, I'm sure you'll figure it out" is extremely likely to make the problem worse, not better.
13
13
1
92
9,518
It's fascinating how AI has just completely erased people's memory of pre-ChatGPT era automations. Not only were most hacking techniques already automated before "AI", many of those automations were actually faster and more effective.
56
103
10
1,756
43,572
Super hyped for Microsoft’s next product. Now that they’ve 10x’d every engineer with AI and stopped wasting resources on pointless stuff like keeping the infrastructure that runs 90% of the planet online, I have high expectations. I’m thinking time machine or resurrecting Jesus.
10
50
2
582
16,248
Strap citu, nopietns jautājums, kāpēc ar visu spiedienu OSiem un datubāzē izvēlēties atvērto kodu, tik ļoti padodamies Microsoft adeptu spiedienam lietot Teams (nevis daudz jēdzīgāko un privātumu mazāk aizskarošo Element). Excel un Exchange gan ir divi bez alternatīvu vaļi.
1
120
neKristīne retweeted
Tā kā @AndrisKulbergs prezentācija daudziem izraisīja bažas par to, ka Claude gatavotās vizualizācijas nav pietiekami reprezentabls veids valsts galvai, sagatavoju tos pašus datus vizuāli mājīgākā veidolā. Sveiciens no Dombrovska laikiem: docs.google.com/presentation…
10
9
1
53
8,413
neKristīne retweeted
Būs smieklīgi, ja mēģinājumi BEIDZOT salabot to Painta caurumu, kas atvēra durvis izpildīt jebkādu kodu uz upura datoru, būs izraisījuši šo problēmu. Ar to ielāpu nez kāpēc bija lielas problēmas. pcgamer.com/software/windows…
1
3
226
Nu ko, piektdiena, 13tais. Teams, Outlook, Copilot(daļēji), Office365(daļēji) un vēl. CNN laivo, BBC stāsta par 'recovery efforts not going as expected'. mailservices.isc.upenn.edu/c…
1
720
Trešā lieta par ko domāt, kad sanitācija+ūdens un siltums atrisināti - sakari. apraide.lv/ - vērts iepazīties un pievienoties jau tagad. Arī masveidīga sms of death sabojāti telefoni šim vēl būs derīgi, ja brīvprātīgie tīklu turēs un pārējie prātīsim pievienoties.
2
2
227
Savukārt tualešu tēmu patvertnēs mēs pagaidām risinām vienkārši nedodot atļauju iekārtot patvertni 'jo nav taču WC'. Piebilde: ja telpa plašākam lokam par ģimeni, svarīgi atcerēties par sieviešu privātumu un drošību arī WC. Varbūt igaunietēm ir kkas mūsu kultūrai derīgs
전쟁에서 사람을 가장 많이 죽인 건 총알이 아니라 ‘화장실 전염병’이라는 거 아시나요? 실제 미국 남북전쟁부터 현대전까지, 전시 사망자의 60% 이상은 총탄이 아니라 배설물 오염으로 인한 전염병으로 숨졌습니다. 단수가 시작되는 순간, 화장실이 집안에서 가장 위험한 ‘세균 폭탄’이 되는 이유와 생존법 🧵👇 --- 1/5 물이 안 나온다고 물을 길어와 변기에 붓는 건 자살행위입니다. 전력망이 끊기면 도시 상하수도 처리 펌프가 올스톱됩니다. 하수관로에 오물이 꽉 차오르면서 치명적인 유독가스와 폐수가 거꾸로 밀려 올라오기 시작합니다. 물을 억지로 붓는 순간, 집안 배수구와 변기에서 수천 가구의 오염수가 역류하는 생지옥이 벌어집니다. --- 2/5 배설물이 실내에 고이는 순간, 24시간 만에 생화학 재앙이 시작됩니다. 1. 콜레라·장티푸스·세균성 이질: 극심한 구토와 설사로 단 하루 만에 탈수 사망. 2. 파리·해충·쥐의 대번식: 오염원을 밟은 벌레들이 식량과 피부로 병원균을 전파. 3. 고농도 암모니아·황화수소 가스: 밀폐된 실내 공기를 오염시켜 호흡기 마비 유발. 약도 병원도 없는 재난 상황에서 전염병 감염은 곧 사형선고입니다. --- 3/5 단수가 확인되면 1초도 지체하지 말고 격리해야 합니다: 1. 기존 변기와 모든 배수구(욕조, 세면대)를 두꺼운 비닐과 방수 테이프로 완전 밀봉 (하수관 역류 가스와 세균 침투 원천 차단) 2. 비상 간이 화장실 구축: 5갤런(20L) 버킷이나 휴대용 프레임에 고밀도 중형 방수 비닐을 씌워 독립 격리 구역 만들기. --- 4/5 세균 증식을 물리적으로 차단하는 프레퍼들의 필수품: 1. 고흡수성 폴리머(SAP 가루) or 벤토나이트 모래: 수분을 즉시 흡수해 고체화시켜 박테리아 번식 원천 차단. 2. 차아염소산나트륨(락스) 희석액: 용변 즉시 분사해 병원균 99.9% 멸균. 3. 지퍼백 & 케이블타이: 1회 용변마다 진공 밀봉하여 공기와의 접촉 완벽 차단. --- 5/5 전염병 예방의 절대 규칙: "소변과 대변을 절대 섞지 마라." 수분(소변)이 대변의 박테리아와 만나는 순간 폭발적인 부패가 시작되어 유독가스가 발생합니다. 소변은 별도 용기에 받아 안전하게 버리고, 대변만 흡수제를 덮어 산소를 차단한 채 밀폐 통에 보관해야 합니다. 식량보다 먼저 챙겨야 할 것은 위생입니다. 유익했다면 RT 🔁 + 북마크 🔖 해두세요.
1
2
7
1,100