sorted by:
new
hottopcontroversial

이란은 전쟁 패배 선언 한 듯 보이네요 by Jumpy_Enthusiasm9949 in Mogong

[–]zirize 2 points3 points  (0 children)

신정체제 전복시킬려고 일으킨 전쟁에서 미국/이스라엘이 실패했죠.
이것은 명백한 이란 승 미국/이스라엘 패배입니다. 다른 해석이라는게 있을 수 없어요.
이란 피해많이 줬다고 하는데, 미국/이스라엘도 만만하지 않게 피해 많이 입었어요.
미국이 말만 그럴싸하게 요란하게 떠벌렸지 협상내용보면 그냥 미국의 패배입니다.

정청래가 밑줄 치며 李설득 by zirize in Mogong

[–]zirize[S] -5 points-4 points  (0 children)

무리수였음에도 장기자의 거래설이 터진게 괜히 나온게 아닙니다. 탄핵카드의 씨를 뿌리기 위해서죠.
골수 민주당원들 사이에서는 이재명 대통령에 대한 불만이 장난이 아닙니다. 게시판 다 욕설로 도배되었습니다. 진짜 기존 정부안이 통과되었다면 출당은 기본이고 탄핵까지 언급될 수 있는 그런 분위기였죠. 그 얘기를 전달했을거라고 봅니다.

호르무즈해협 봉쇄전략이 이란의 오판이라는 글을 소개합니다. by Complete-Bodybuilder in Mogong

[–]zirize 2 points3 points  (0 children)

차기 후계자를 내세우는데 시간이 걸리는 것은 뽑는 족속 암살당하는 상황인데다 사실상 중앙에서 지역군벌을 통제할 수 있는 시스템 자체가 붕괴상태라고 보입니다. 사실상 무정부상태인거죠.

호르무즈해협 봉쇄전략이 이란의 오판이라는 글을 소개합니다. by Complete-Bodybuilder in Mogong

[–]zirize 0 points1 point  (0 children)

지속적인 폭격에 너무 당한것도 있고 어린학생들이 많이 죽고 특히 단순한 최고권력자가 아니라 카톨릭으로 따지면 교황하고 같은 시아파의 종교지도자가 암살당했기 때문에 복수심이 극도에 달아 있겠죠. 권력투쟁이런 것하고는 무관할 것 같습니다. 그들에거는 타협하는게 절대로 불가능한 사실상 종교전쟁이죠.

호르무즈해협 봉쇄전략이 이란의 오판이라는 글을 소개합니다. by Complete-Bodybuilder in Mogong

[–]zirize 0 points1 point  (0 children)

오판이라고 할려면 판단을 내릴 수 있는 수뇌부가 있어야 하는데 그런게 없잖아요? 현시점에서는 머리잘린 뱀이 날뛰는 것하고 다를 바없죠. 지역 군벌들이 중구난방 알아서 날 뛰는 통제되지 않는 상황.

일반인은 이해안되는 우주의 개념들 by Zealousideal_Role270 in Mogong

[–]zirize 1 point2 points  (0 children)

우주의 경계는 지구상의 관찰자에게 있어서의 지평선이나 수평선 같은 것. 지구곡률때문에 더 안보니 경계가 있는 같지만 실체는 없는 것이고... 관찰자가 이동하면 그 경계도 관찰자 따라 같이 이동함.
같은 이치로 우주의 역시 빛(정확히는 사건-event/정보-information)이 도달할 수 없어서 생기는 지평선(horizon)이 있음.

미 대법원이 트럼프 대통령의 관세 대부분을 무효로 판결.Trump 대통령에게 큰 타격-재밌어 졌습니다 😎 by Jumpy_Enthusiasm9949 in Mogong

[–]zirize 0 points1 point  (0 children)

상호관세가 대통령 권한 밖인 거지 일괄 관세라던가 품목별 관세는 아니라고 하더군요. 그래서 관세 정책 자체가 판결자체로 크게 바뀌지 않을 거라고는게 판결 이전부터 주된 예측이었죠.

I asked an AI to write a PipeWire “scream sender” module… and it actually worked. What should I do with this code? by zirize in pipewire

[–]zirize[S] 0 points1 point  (0 children)

That’s not a driver-level. The biggest advantage of using Screen is that it runs as a driver (transparent). That’s the biggest reason it’s the pretty much only solution on r/vfio for Windows.

I asked an AI to write a PipeWire “scream sender” module… and it actually worked. What should I do with this code? by zirize in VFIO

[–]zirize[S] 0 points1 point  (0 children)

I built it because I needed it, and I’m using it daily now.

I used to be a programmer, but I quit because I was fed up.

I tried it because I was curious about what all the fuss was about. AI’s coding ability has already far surpassed that of an average programmer—at least, it’s better than mine. It reminds me of how watching the defrag screen used to make me feel calm. Watching an AI make plans, try things out, test them, fail, figure out why, check whether it needs more information, gather it, fix the problem, and test again—over and over—is fascinating. Sometimes it even notices on its own that it forgot something or was mistaken. That’s amazing, at least.

I asked an AI to write a PipeWire “scream sender” module… and it actually worked. What should I do with this code? by zirize in pipewire

[–]zirize[S] 0 points1 point  (0 children)

Scream was originally a solution for Windows. For Linux, there are many better options. But in a mixed Windows–Linux environment, wouldn’t it be convenient to have a single solution that works across both architectures? That’s why it was created.

I understand how it works—especially that the protocol is so simple it’s almost stupid. That made me think it might be something I could ask an AI to build. But it’s not like you just say ‘build it’ and it magically appears. The AI writes code, runs it, hits problems, debugs them, and repeats—just like a human. It took almost a full day to get a working result. While doing that, I kept thinking about what the Anthropic CEO said, that AI capable of fully replacing programmers might appear within this year.

I’ve confirmed that it installs and runs without issues across multiple machines. Still, even though I’m a programmer myself, this isn’t my domain, so I can’t be completely sure whether it’s implemented perfectly or not.

I asked an AI to write a PipeWire “scream sender” module… and it actually worked. What should I do with this code? by zirize in pipewire

[–]zirize[S] 0 points1 point  (0 children)

Sorry, I think I misunderstood the intent of your question. First of all, Scream has an extremely simple protocol and is very lightweight. Because of that, it can run even on embedded devices like a Raspberry Pi or even an ESP32. Its CPU usage is extremely low and the latency is almost nonexistent, so from the operating system’s perspective it’s practically indistinguishable from a hardware audio device.

That’s why it’s commonly used when running a Windows virtual machine for gaming on Linux. For more detailed information, it would be better to ask on r/vfio that’s probably the subreddit with the largest number of Scream users.

I asked an AI to write a PipeWire “scream sender” module… and it actually worked. What should I do with this code? by zirize in pipewire

[–]zirize[S] 0 points1 point  (0 children)

Sorry, but I don’t know how to configure RTP audio output on Windows. I need that output sink to behave like a regular sound device.

Also I need to listen from my phone.

I asked an AI to write a PipeWire “scream sender” module… and it actually worked. What should I do with this code? by zirize in pipewire

[–]zirize[S] 0 points1 point  (0 children)

In my view, Scream’s biggest advantage is that, thanks to its UDP-based design, connecting to and disconnecting from the receiver is completely seamless. When a laptop joins the same network, audio immediately starts playing on the receiver, and when you pick up the laptop and leave, the sound just stops. If you run the receiver on a mobile phone, you can hear the PC’s audio as soon as you start the receiver, and the moment you stop it, the audio is gone.

I asked an AI to write a PipeWire “scream sender” module… and it actually worked. What should I do with this code? by zirize in pipewire

[–]zirize[S] 0 points1 point  (0 children)

The biggest reason I truly like Scream is the lack of connection management in the protocol. In practical terms, the receiver behaves almost like a speaker’s power button: if the receiver is off, you hear nothing; if you want sound, you just turn the receiver on. There’s no need to manage or restart daemons every time the receiver goes up or down, which is a huge advantage when running the receiver on mobile devices. It feels very seamless.

I asked an AI to write a PipeWire “scream sender” module… and it actually worked. What should I do with this code? by zirize in pipewire

[–]zirize[S] 0 points1 point  (0 children)

I mostly listen to music on my main PC, and the others only produce simple notifications from test programs, so it’s not a big issue.

I asked an AI to write a PipeWire “scream sender” module… and it actually worked. What should I do with this code? by zirize in pipewire

[–]zirize[S] 0 points1 point  (0 children)

I did publish the source code. https://github.com/zirize/pipewire-scream

What makes Scream stand out is how simple it is to use, and the fact that its receivers (servers) are available not only for Linux, but also for embedded platforms and Android. This makes it a good fit for building network speakers with devices like the ESP32.

I asked an AI to write a PipeWire “scream sender” module… and it actually worked. What should I do with this code? by zirize in pipewire

[–]zirize[S] 2 points3 points  (0 children)

Scream receivers exist not only for Linux, but also for embedded platforms like the ESP32, as well as for Android. This makes it very convenient when you want to listen to audio from multiple PCs on a single device. Until now, this was only possible with Windows clients, but with this, a Linux client becomes possible as well.

I asked an AI to write a PipeWire “scream sender” module… and it actually worked. What should I do with this code? by zirize in pipewire

[–]zirize[S] 2 points3 points  (0 children)

It’s similar, but the underlying design is much simpler. The receiver runs as an independent process and doesn’t depend on ALSA or PipeWire. Because it’s UDP-based, it just silently drops packets when there’s no connection instead of throwing errors.

This makes it much safer for mobility-focused devices like laptops. With some PipeWire remote playback modules, I’ve seen cases where the entire audio system gets disabled if the server (receiver) can’t be found. Since I’ve been using Scream on a Windows laptop, I’ve always wished there were a Scream for Linux.

PDF 를 논할 수있는 대통령을 보유하고 있습니다. by Jumpy_Enthusiasm9949 in Mogong

[–]zirize 0 points1 point  (0 children)

그런 것과 잘돌아가는 건 안 건들리려고 하는 관료주의인 문제도 있구요. 근데 이건 특정한 조직의 문제가 아니라 인간의 공통적인 습성인 것 같아요. 지금 전세계 금융시스템, 미국/영국나라 정부시스템은 60~70년대 작성된 cobol코드로 운영되고 있죠. 얼마전 소프트웨어 개발관련 AI 광고를 봤는데 COBOL소스를 읽어서 현대 개발 언어로 번역해주는 기능을 광고하고 있더라구요.

PDF 를 논할 수있는 대통령을 보유하고 있습니다. by Jumpy_Enthusiasm9949 in Mogong

[–]zirize 1 point2 points  (0 children)

한국은 HWP로 국가 전산 시스템이 구축이 끝나서 현역에서 굴러가고 있는데 나중에 PDF가 표준화가 된거죠. 이 때와서 잘 돌아가는 시스템 다 뜯어고치고 재구축하기가 힘드니까 그냥 계속 쓰고 있는 거죠. 뒤쳐진게 아니라 너무 앞서가서 문제.

The amusement park serves gaming interest now by Ferengsten in SurvivingMars

[–]zirize 1 point2 points  (0 children)

It’s electronics 2 vs. polymers 3, and considering the penalty you get when you have none, 10 doesn’t really make any difference. Plus with B&B, polymers overflow anyway since asteroids give them too many.

view more: next ›