IT Market Saturation: Evolution, Not Decline https://chat-to.dev/post?id=LzlSMFYyWjNndnhuQkt6bFNzSDhPQT09 #tech #technology #programming #engineer
Recent searches
Search options
#engineer
6 posts6 participants0 posts today
I'm an Engineer, not a child
I'm an #engineer, not a child...
What's the problem?
"Excessive de-burring on the buttstrap mating face. We'll probably need a bigger buttstrap."
*Snorts*
New Mac Attack is tricking Users into thinking their Computer is locked.
According to LayerX Labs, who have been tracking this campaign for more than a year, the phishing attack attempts to trick Mac users into thinking that their computers have been “locked” via a fake security warning that pops up while users are browsing the web.
https://layerxsecurity.com/blog/layerx-identifies-new-phishing-campaign-targeted-at-mac-users/
GIF
![[ImageSource: LayerX Labs]
The webpage then appears to be frozen which, like most phishing attempts, adds a sense of urgency and fear that something is wrong with your computer. The window that appears displays a warning that the computer has been subjected to a trojan virus and asks the user to enter in their Mac username and password.
The warning message [captured in a screenshot by LayerX Labs], contains some glaring errors that show it’s not legitimate: It does not conform to any of Apple’s styling either in color or general appearance and misspells macOS as “MacOS.”
It also provides a phone number to contact “support,” however, when [Macworld] called this number they only got a message playback that said the recipient was not available and to call back between 8am and 5pm – even though they were calling during that time frame. The number is obviously fake and will likely never be answered.
<https://www.macworld.com/article/2642938/new-mac-phishing-attack-causes-fake-freezes-to-nab-your-apple-id-password.html>](https://nerdculture.de/system/media_attachments/files/114/223/204/816/717/565/original/c3108acab7427601.jpeg "[ImageSource: LayerX Labs]
The webpage then appears to be frozen which, like most phishing attempts, adds a sense of urgency and fear that something is wrong with your computer. The window that appears displays a warning that the computer has been subjected to a trojan virus and asks the user to enter in their Mac username and password.
The warning message [captured in a screenshot by LayerX Labs], contains some glaring errors that show it’s not legitimate: It does not conform to any of Apple’s styling either in color or general appearance and misspells macOS as “MacOS.”
It also provides a phone number to contact “support,” however, when [Macworld] called this number they only got a message playback that said the recipient was not available and to call back between 8am and 5pm – even though they were calling during that time frame. The number is obviously fake and will likely never be answered.
<https://www.macworld.com/article/2642938/new-mac-phishing-attack-causes-fake-freezes-to-nab-your-apple-id-password.html>")
Minimal Linux OS runs in a 6MB PDF Document in Chrome.
A version of the Linux operating system can now be run inside a PDF opened by a Chromium-based browser. The developer [Ading2210] explains that Linux need a modified version of the TinyEMU RISC-V emulator.
![If you wish to try out the LinuxPDF, it requires a Chromium-based browser to work correctly (I checked, but it didn't work in Firefox on PC).
On the topic of speed and efficiency, [Ading2210] humbly admits that performance might be the largest problem with LinuxPDF. "The Linux kernel takes about 30-60 seconds to boot up within the PDF, which [is] over 100x slower than normal," notes the developer. With Chrome's current PDF engine having its Just-in-Time (JIT) compiler disabled, [Ading2210] sees no way of speeding up the code, for now.](https://nerdculture.de/system/media_attachments/files/114/211/704/385/933/637/original/7142a6047423bdbc.jpeg "If you wish to try out the LinuxPDF, it requires a Chromium-based browser to work correctly (I checked, but it didn't work in Firefox on PC).
On the topic of speed and efficiency, [Ading2210] humbly admits that performance might be the largest problem with LinuxPDF. \"The Linux kernel takes about 30-60 seconds to boot up within the PDF, which [is] over 100x slower than normal,\" notes the developer. With Chrome's current PDF engine having its Just-in-Time (JIT) compiler disabled, [Ading2210] sees no way of speeding up the code, for now.")
![[ImageSource: Ading2210]
The TinyEMU RISC-V emulator runs in the PDF thanks to a technique where its code is compiled "using an old version of Emscripten that targets asm.js instead of WebAssembly." This is embedded and loads in the PDF, subsequently auto-running a minimal Linux kernel targeting that architecture.
In this implementation, once you agree to 'Start Emulator' in your browser, you will see the LinuxPDF UI load, and a welcome message in the Linux viewport, as you wait for the OS to boot.](https://nerdculture.de/system/media_attachments/files/114/211/705/349/712/707/original/513838969c81eb99.png "[ImageSource: Ading2210]
The TinyEMU RISC-V emulator runs in the PDF thanks to a technique where its code is compiled \"using an old version of Emscripten that targets asm.js instead of WebAssembly.\" This is embedded and loads in the PDF, subsequently auto-running a minimal Linux kernel targeting that architecture.
In this implementation, once you agree to 'Start Emulator' in your browser, you will see the LinuxPDF UI load, and a welcome message in the Linux viewport, as you wait for the OS to boot.")
![[ImageSource: Ading2210]
Below the Linux viewport in the PDF is a soft keyboard created by an array of PDF buttons. However, it is likely quicker for everyone with a decent physical keyboard to input commands into the 'type here for keyboard inputs' field to the lower right of the keyboard UI area.](https://nerdculture.de/system/media_attachments/files/114/211/706/326/556/776/original/9f7e2d1a8c32c083.png "[ImageSource: Ading2210]
Below the Linux viewport in the PDF is a soft keyboard created by an array of PDF buttons. However, it is likely quicker for everyone with a decent physical keyboard to input commands into the 'type here for keyboard inputs' field to the lower right of the keyboard UI area.")
Quake ported to Arduino Nano Matter. [Using only 276kb RAM]
Nicola Wrachien with Silicon Labs created this fun handheld, porting Quake using the Arduino Nano Matter. For easy playing a custom controller shaped board was designed with joysticks and a screen.
![[ImageSource: Nicola Wrachien]
For a much tougher challenge, a group from Silicon Labs decided to port DOOM‘s successor, Quake, to the Arduino Nano Matter Board platform instead even though this platform has some pretty significant limitations for a game as advanced as Quake.
<https://community.silabs.com/s/share/a5UVm000000Vi1ZMAS/quake-ported-to-arduino-nano-matter-and-sparkfun-thing-plus-matter-boards?language=en_US>
To begin work on the memory problem, the group began with a port of Quake originally designed for Windows, allowing them to use a modern Windows machine to whittle down the memory usage before moving over to hardware. They do have a flash memory module available as well, but there’s a speed penalty with this type of memory. To improve speed they did what any true gamer would do with their system: overclock the processor. This got them to around 10 frames per second, which is playable, but not particularly enjoyable.
The further optimizations to improve the FPS required a much deeper dive which included generating lookup tables instead of relying on computation, optimizing some of the original C programming, coding some functions in assembly and only refreshing certain sections of the screen when needed.](https://nerdculture.de/system/media_attachments/files/114/206/081/241/901/037/original/72dec8d287dd1c33.png "[ImageSource: Nicola Wrachien]
For a much tougher challenge, a group from Silicon Labs decided to port DOOM‘s successor, Quake, to the Arduino Nano Matter Board platform instead even though this platform has some pretty significant limitations for a game as advanced as Quake.
<https://community.silabs.com/s/share/a5UVm000000Vi1ZMAS/quake-ported-to-arduino-nano-matter-and-sparkfun-thing-plus-matter-boards?language=en_US>
To begin work on the memory problem, the group began with a port of Quake originally designed for Windows, allowing them to use a modern Windows machine to whittle down the memory usage before moving over to hardware. They do have a flash memory module available as well, but there’s a speed penalty with this type of memory. To improve speed they did what any true gamer would do with their system: overclock the processor. This got them to around 10 frames per second, which is playable, but not particularly enjoyable.
The further optimizations to improve the FPS required a much deeper dive which included generating lookup tables instead of relying on computation, optimizing some of the original C programming, coding some functions in assembly and only refreshing certain sections of the screen when needed.")
End-to-End Encryption for RCS, enabling Secure Cross-Platform Messaging.
Text messages sent between iOS & Android devices will soon benefit from end-to-end encryption, after the GSM Association published new specifications for the RCS protocol that include support for cross-platform E2EE.
![The new GSMA specifications for RCS include E2EE based on the Messaging Layer Security [MLS] protocol via what's called the Rich Communication Services [RCS] Universal Profile 3.0.
"The new specifications define how to apply MLS within the context of RCS," Tom Van Pelt, technical director of GSMA, said. "These procedures ensure that messages and other content such as files remain confidential and secure as they travel between clients."
<https://www.gsma.com/newsroom/article/rcs-encryption-a-leap-towards-secure-and-interoperable-messaging/>
This also means that RCS will be the first "large-scale messaging service" to have support for interoperable E2EE between different client implementations from different providers in the near future.
The development comes nearly six months after the GSMA said it was working towards implementing end-to-end encryption [E2EE] to secure messages sent between the Android and iOS ecosystems. The move followed Apple's decision to roll out support for RCS in its own Messages app with iOS 18.
Google said, "We've always been committed to providing a secure messaging experience, and Google Messages users have had end-to-end encrypted [E2EE] RCS messaging for years. We're excited to have this updated specification from GSMA and work as quickly as possible with the mobile ecosystem to implement and extend this important user protection to cross-platform RCS messaging."](https://nerdculture.de/system/media_attachments/files/114/194/978/375/605/770/original/ae19ccf056d1258e.jpeg "The new GSMA specifications for RCS include E2EE based on the Messaging Layer Security [MLS] protocol via what's called the Rich Communication Services [RCS] Universal Profile 3.0.
\"The new specifications define how to apply MLS within the context of RCS,\" Tom Van Pelt, technical director of GSMA, said. \"These procedures ensure that messages and other content such as files remain confidential and secure as they travel between clients.\"
<https://www.gsma.com/newsroom/article/rcs-encryption-a-leap-towards-secure-and-interoperable-messaging/>
This also means that RCS will be the first \"large-scale messaging service\" to have support for interoperable E2EE between different client implementations from different providers in the near future.
The development comes nearly six months after the GSMA said it was working towards implementing end-to-end encryption [E2EE] to secure messages sent between the Android and iOS ecosystems. The move followed Apple's decision to roll out support for RCS in its own Messages app with iOS 18.
Google said, \"We've always been committed to providing a secure messaging experience, and Google Messages users have had end-to-end encrypted [E2EE] RCS messaging for years. We're excited to have this updated specification from GSMA and work as quickly as possible with the mobile ecosystem to implement and extend this important user protection to cross-platform RCS messaging.\"")
17 MarchL #TEPCO "Regarding the submission of "Decommissioning Implementation Plans" based on the Decommissioning Reserve Fund System" www.tepco.co.jp/press/releas... #Fukushima #genpastu #nuclear #energy #tech #engineer #policy
tepco.co.jp/press/release/...
Bluesky SocialBluesky
They are upgrading the #software running a #radar I work with. One of the tests is obviously how good the data looks. The new software has higher standard deviations than the old software (#statistics)
And that's it. They are trying to debug it based on just the std dev.
I looked at one of the tracks and there was clearly a time dependent trend.
I keep telling them and telling them that just thinking in terms of "standard deviation" is making them assume gaussian #noise sources.
But if you look at the #data as a *time series*, you will start thinking about the processing and what would be happening at different points in a track and how it might go wrong starting at certain points.
It's a purely software #engineer team--they know about radar (more than I do!), but aren't #system engineers.
It's been going on long enough that I want to say something to someone higher up. But I don't want to adopt another project....
GitHub uncovers new Ruby-SAML Vulnerabilities allowing Account Takeover Attacks.
Two high-severity security flaws have been disclosed in the open-source ruby-saml library that could allow malicious actors to bypass Security Assertion Markup Language (SAML) authentication protections.
GIF
![[ImageSource: GitHub]
"Attackers who are in possession of a single valid signature that was created with the key used to validate SAML responses or assertions of the targeted organization can use it to construct SAML assertions themselves and are in turn able to log in as any user," GitHub Security Lab researcher Peter Stöckli said in a post.
The Microsoft-owned subsidiary also noted that the issue boils down to a "disconnect" between verification of the hash and verification of the signature, opening the door to exploitation via a parser differential.
Versions 1.12.4 and 1.18.0 also plug a remote denial-of-service (DoS) flaw when handling compressed SAML responses (CVE-2025-25293, CVSS score: 7.7).
⚠️Users are recommended to update to the latest version to safeguard against potential threats.⚠️
The findings come nearly six months after GitLab and ruby-saml moved to address another critical vulnerability (CVE-2024-45409, CVSS score: 10.0) that could also result in an authentication bypass.](https://nerdculture.de/system/media_attachments/files/114/177/947/075/555/612/original/721ecee68734690f.jpeg "[ImageSource: GitHub]
\"Attackers who are in possession of a single valid signature that was created with the key used to validate SAML responses or assertions of the targeted organization can use it to construct SAML assertions themselves and are in turn able to log in as any user,\" GitHub Security Lab researcher Peter Stöckli said in a post.
The Microsoft-owned subsidiary also noted that the issue boils down to a \"disconnect\" between verification of the hash and verification of the signature, opening the door to exploitation via a parser differential.
Versions 1.12.4 and 1.18.0 also plug a remote denial-of-service (DoS) flaw when handling compressed SAML responses (CVE-2025-25293, CVSS score: 7.7).
⚠️Users are recommended to update to the latest version to safeguard against potential threats.⚠️
The findings come nearly six months after GitLab and ruby-saml moved to address another critical vulnerability (CVE-2024-45409, CVSS score: 10.0) that could also result in an authentication bypass.")
Deutschland …
Land der Dichter und Denker und Ingenieure.
Damals und heute. Bewahren und die #Innovationen.
#GottliebDaimler #Engineer. Happy Birthday Sir zum 191. Geburtstag.
Und der Mainstream damals:
„Das Pferd wird bleiben, aber die Automobilie ist nur eine vorübergehende Erscheinung.“
Build a Parametric Speaker of Your Own.
At the Hacker Hotel conference in the Netherlands, [Orange_Murker] presented an ultrasonic parametric speaker. It projects an extremely narrow beam of sound over a significant distance, but it’s not an audio frequency speaker at all.
![[ImageSource: Orange_Murker]
Those of you familiar with radio will recognize its operation; an ultrasonic carrier is modulated with the audio to be projected, and the speaker transfers that to the air. Just like the diode detector in an old AM radio, air is a nonlinear medium and it performs a demodulation of the ultrasound to produce an audio frequency that can be heard.
[Orange_Murker] spends a while going into modulation schemes, before revealing that she drove her speaker with a 40 kHz PWM via an H bridge. The speaker itself is an array of in-phase ultrasonic transducers, and she demonstrates the result on her audience.
<https://media.ccc.de/v/2025-201-build-your-own-parametric-speaker>](https://nerdculture.de/system/media_attachments/files/114/172/381/612/832/329/original/419ed72e02265621.png "[ImageSource: Orange_Murker]
Those of you familiar with radio will recognize its operation; an ultrasonic carrier is modulated with the audio to be projected, and the speaker transfers that to the air. Just like the diode detector in an old AM radio, air is a nonlinear medium and it performs a demodulation of the ultrasound to produce an audio frequency that can be heard.
[Orange_Murker] spends a while going into modulation schemes, before revealing that she drove her speaker with a 40 kHz PWM via an H bridge. The speaker itself is an array of in-phase ultrasonic transducers, and she demonstrates the result on her audience.
<https://media.ccc.de/v/2025-201-build-your-own-parametric-speaker>")
10x Engineering
Generate impressive-looking terminal output to look busy when stakeholders walk by and become an irreplaceable 10x developer in 30 seconds flat.
With rust-stakeholder.
GitHubGitHub - giacomo-b/rust-stakeholder: Generate impressive-looking terminal output to look busy when stakeholders walk by.Generate impressive-looking terminal output to look busy when stakeholders walk by. - giacomo-b/rust-stakeholder
Porting Doom to Typescript Types took 3.5 Trillion Lines, 90GB of RAM and a full Year of Work.
The feat was devised by Software Engineer Dmitri Mitropoulos, founder of Michigan Typescript and co-founder of Squiggleconf. He released a video showcasing the results of a year-long effort to get Doom running inside of Typescript's Types system.
![[ImageSource: Dmitri Mitropoulos]
Typescript is a language built on top of Javascript, that add static typing to catch many errant mistakes before your executes, think of it as guardrails which check that functions and other variables are being used correctly. While this is commonly used in all kinds of development, it's unheard of to run a game within Typescript's Type system.
The port itself runs inside three and a half trillion lines of types, totalling a gargantuan size of 177 TB. This is run through Typescript's Type tracker, which takes 12 days to compile the first frame of Doom (0.0000009645 fps). This meant that 20 million type instantiations were running every second in order to get the output.
Mitropoulos explained in the Michigan TypeScript Discord server that this could be improved to take "1 to 12 hours", as long as someone works on it, with the developer noting that he has notes for where potential performance optimizations could be made.
<https://discord.gg/pfKUSmSY>
This was done by running the project within a custom WASM runtime, which is then processed through Typescript within an editor to display a frame.
<https://github.com/MichiganTypeScript/typescript-types-only-wasm-runtime>](https://nerdculture.de/system/media_attachments/files/114/166/740/010/112/784/original/f54d5e08b8f270ce.png "[ImageSource: Dmitri Mitropoulos]
Typescript is a language built on top of Javascript, that add static typing to catch many errant mistakes before your executes, think of it as guardrails which check that functions and other variables are being used correctly. While this is commonly used in all kinds of development, it's unheard of to run a game within Typescript's Type system.
The port itself runs inside three and a half trillion lines of types, totalling a gargantuan size of 177 TB. This is run through Typescript's Type tracker, which takes 12 days to compile the first frame of Doom (0.0000009645 fps). This meant that 20 million type instantiations were running every second in order to get the output.
Mitropoulos explained in the Michigan TypeScript Discord server that this could be improved to take \"1 to 12 hours\", as long as someone works on it, with the developer noting that he has notes for where potential performance optimizations could be made.
<https://discord.gg/pfKUSmSY>
This was done by running the project within a custom WASM runtime, which is then processed through Typescript within an editor to display a frame.
<https://github.com/MichiganTypeScript/typescript-types-only-wasm-runtime>")
![Dmitri Mitropoulos further explained that each value within the Typescript Types system equates to a line of pixels [totalling 128,000 lines of pixels in total], resulting in a "resolution" of 320x200, displayed in ASCII.
To do this, the developer needed to remove limitations within the Typescript compiler itself, highlighting just how large the project got, with the Type tracker runtime consuming over 90 GB of RAM while it was running.
This huge overhead meant that common tools within Typescript could not be used, which meant that the herculean task of encoding every element of Doom in types. This required learning to develop elements like an L1 CPU cache, within Typescript Types itself. Due to Typescript requiring iteration on a single string from the left-hand side, binary algorithms had to be input in reverse.
"Oh, and AI can't help" Dmitri Mitropoulos added, describing that the work was so low level that AI couldn't possibly assist with any of the tasks. Too bad, Grok 3.
Mitropoulos said that he undertook the challenge after completing "every other" Types challenge, and wanted to understand why Doom wouldn't be able to run within Types. However, he managed to find "ridiculous" workarounds to make it all work, despite his own disbelief in the project.](https://nerdculture.de/system/media_attachments/files/114/166/742/069/675/680/original/110e43577d22fe1d.jpeg "Dmitri Mitropoulos further explained that each value within the Typescript Types system equates to a line of pixels [totalling 128,000 lines of pixels in total], resulting in a \"resolution\" of 320x200, displayed in ASCII.
To do this, the developer needed to remove limitations within the Typescript compiler itself, highlighting just how large the project got, with the Type tracker runtime consuming over 90 GB of RAM while it was running.
This huge overhead meant that common tools within Typescript could not be used, which meant that the herculean task of encoding every element of Doom in types. This required learning to develop elements like an L1 CPU cache, within Typescript Types itself. Due to Typescript requiring iteration on a single string from the left-hand side, binary algorithms had to be input in reverse.
\"Oh, and AI can't help\" Dmitri Mitropoulos added, describing that the work was so low level that AI couldn't possibly assist with any of the tasks. Too bad, Grok 3.
Mitropoulos said that he undertook the challenge after completing \"every other\" Types challenge, and wanted to understand why Doom wouldn't be able to run within Types. However, he managed to find \"ridiculous\" workarounds to make it all work, despite his own disbelief in the project.")
Ghost is hiring a staff product engineer. They’re building a better ecosystem for writers as an alternatives that cater to nazis. So…get some.
GhostStaff Product Engineer - GhostWe're looking for talented engineers with JavaScript experience to join the Ghost product team and work remotely, on Open Source software.
Job Alert! We have an exciting #hiring opportunity for an Infrastructure #Operations #Engineer! Don't miss your chance to apply—our application window closes on Monday, 17 March at 9am UTC.
Check out the full job posting here: https://bit.ly/3DN1kTI
Want to know more about what you'll do in this role? We've written a blog post highlighting our Operations Team and the impact you'll have. 
https://bit.ly/41TA3Hg
240 Million Windows 10 Users are vulnerable to six different Exploits.
Protect yourself Now!!!
If you’re running a Windows 10 PC, make sure you download the latest update right now. Microsoft patched 57 vulnerabilities affecting its foundational systems and core products, including six actively exploited zero-day vulnerabilities.
https://msrc.microsoft.com/update-guide/releaseNote/2025-Mar
GIF
![[ImageSource: Shutterstock]
However, these are the actively exploited vulnerabilities to worry about right now:
• CVE-2025-24993: This is a common buffer overflow exploit. In simple terms, criminals take advantage of a coding error and overload your system memory with more, which overwrites your current system memory.
• CVE-2025-24991: If an unsuspecting user mounts a nefarious virtual hard disk (VHD), this bug allows a hacker to read all of your data (even all the out-of-bounds stuff).
• CVE-2025-24984: This exploit allows an attacker to record all sensitive information into a log file for them to take. While it’s a concerning one, it does require the malicious actor to physically access your computer.
• CVE-2025-26633: A simple (but risky) bypass flaw in the Microsoft Management Console.
• CVE-2025-24985: This one also requires the attacker to convince a user to mount a VHD of their own volition. But once done, there is a privilege escalation flaw that can be exploited to take over the victim’s entire computer.
• CVE-2025-24983: This is a system-level exploit where a malicious actor can run a specially crafted program that exploits the Kernel Subsystem of Windows to give an attacker top privileges to your system.](https://nerdculture.de/system/media_attachments/files/114/161/162/797/465/639/original/baa978608da5f225.png "[ImageSource: Shutterstock]
However, these are the actively exploited vulnerabilities to worry about right now:
• CVE-2025-24993: This is a common buffer overflow exploit. In simple terms, criminals take advantage of a coding error and overload your system memory with more, which overwrites your current system memory.
• CVE-2025-24991: If an unsuspecting user mounts a nefarious virtual hard disk (VHD), this bug allows a hacker to read all of your data (even all the out-of-bounds stuff).
• CVE-2025-24984: This exploit allows an attacker to record all sensitive information into a log file for them to take. While it’s a concerning one, it does require the malicious actor to physically access your computer.
• CVE-2025-26633: A simple (but risky) bypass flaw in the Microsoft Management Console.
• CVE-2025-24985: This one also requires the attacker to convince a user to mount a VHD of their own volition. But once done, there is a privilege escalation flaw that can be exploited to take over the victim’s entire computer.
• CVE-2025-24983: This is a system-level exploit where a malicious actor can run a specially crafted program that exploits the Kernel Subsystem of Windows to give an attacker top privileges to your system.")