Connexion
"Rendering Doom in a database is obviously a bad idea," Lukas Vogel writes in a lengthy blog post explaining how exactly he managed to render Doom using an SQL database.
OK, that's not entirely accurate. The SQLDoom project uses a small Python client to handle input and output, drive the game's timing, and display each frame to the screen. Behind that, a series of CedarDB tables tracks the game geometry and state, while about 1,300 lines of SQL queries spread across 89 common table expressions implement the game logic and generate 35 bitmap framebuffers per second.
In this, SQLDoom is a major improvement over Vogel's previous DoomQL project, which last year set out to build "a multiplayer Doom-like shooter entirely in SQL." Unfortunately, that effort ended up with raycasting-based, grayscale ASCII graphics that were more akin to the simplistic 90-degree-angled maps of Wolfenstein 3D. The newer SQLDoom, on the other hand, generates full-color 640x480 frames that look like they could have come from the original Doom executable.
SQL Server on Azure Local is generally available. Review disconnected deployment requirements, separate licensing, and recovery planning before adopting it.
The post Microsoft Makes SQL Server on Azure Local Generally Available appeared first on TechRepublic.
Oracle AI Database@AWS expands to 22 regions and adds a pay-per-use Exadata option, giving enterprises more flexibility for cloud database migrations.
The post Oracle and AWS Expand Database Partnership With Exadata Service and 22-Region Footprint appeared first on TechRepublic.
In the US, fired and laid-off workers often have their digital credentials deactivated before they learn about the loss of their jobs; indeed, the inability to log in to a corporate system may be the first an employee knows of the situation.
Although not a generous or humane approach to staff reduction, it does follow from the simple fact that a fired employee with access to company systems is a security risk.
Just ask the Akhter twin brothers, accused of wiping out 96 databases hosting US government information in the minutes after both were fired last year from their shared employer.
Four protesters are suing to stop the Department of Homeland Security (DHS) and the Federal Bureau of Investigation (FBI) from seizing DNA samples from Americans arrested while peacefully protesting Immigration and Customs Enforcement (ICE) activity.
In a complaint filed in an Illinois district court on Wednesday, protesters arrested at the Broadview ICE facility during "Operation Midway Blitz"—when thousands of federal agents flooded Chicago—demanded an injunction to stop alleged violations of the First and Fourth Amendments, as well as the Administrative Procedure Act.
They have accused the federal government of "wrongfully arresting peaceful protesters, collecting their DNA, uploading their genetic profiles to government databases, and storing their DNA samples in federal labs—permanently."
In a world awash in high-tech security tools like passkeys, quantum-safe algorithms, and public-key cryptography, it can be refreshing to get back to the simple things... like a good old-fashioned canary trap.
The canary trap is a simple tool often used to identify leakers or double agents. To make one, you simply share a document, image, or database but make tiny changes that are unique to each recipient. That way, if those changes show up verbatim in any leak of the information, you know immediately which recipient was behind the leak.
You don't often see canary traps in the news, though they have long been a staple of spy fiction (and practice), so an account out of Canada last week caught my eye.
Lateo.net - Flux RSS en pagaille (pour en ajouter : @ moi) 