Tootfinder

Proč !== v JS není bezpečné pro porovnšvšní tajných řetězců - #WebDev

Proč !== v JS není bezpečné pro porovnávání tajných řetězců
Operátor !== v JavaScriptu není constant-time. Při porovnávání hesel, tokenů nebo API klíčů to umožňuje timing attack.

#Steady-#Klimacrew
#BahnMonitor-Projekt: 1. Wie kommt man an Live-Daten der Deutschen Bahn?
Im November konnte ich per Zufall mit einem

Python-Projekt mit Bahn-API: 1. Zugang einrichten
Entdecke, wie du mit Visual Studio Code und ChatGPT ein Python-Projekt realisierst – inklusive Vibe Coding und Bahn-API-Zugriff.

Visual Studio (MSVC) Text Encoding #i18nFails
i18nfails.1a23.studio/posts/visual-studio-msvc-text-encoding

Visual Studio (MSVC) Text Encoding | i18n fails
Microsoft can never escape the historical burden of code pages.

Mira Murati's Thinking Machines Lab makes Tinker, its API for fine-tuning language models, generally available, adds support for Kimi K2 Thinking, and more (Thinking Machines Lab)
https://thinkingmachines.ai/blog/tinker-general-availability/

Tinker: General Availability and Vision Input
Today we are announcing four updates to Tinker: No more waitlist New reasoning model: Kimi K2 Thinking New inference interface that is compatible with the OpenAI API Vision input support with Qwen3-VL General availability The waitlist is over! Everybody can use Tinker now; sign up here to get started. See the Tinker homepage for available models and pricing, and check out the Tinker cookbook for code examples. More reasoning with Kimi K2 Thinking Users can now fine-tune Kimi K2 Thinking on Ti…

Installing Visual Studio 2026 to see what all the buzz is about. Planning to migrate my project data web api from .NET 9 to 10, along with the new ide.
#programming #visualstudio #dotnet <…

#konkurssit ja Orvon hiljaisuus

(PDF) Multi-algorithmic software for visual-to-auditory sensory substitution (VASS) #NWP2025, FUMN…

SplatBus: A Gaussian Splatting Viewer Framework via GPU Interprocess Communication
Yinghan Xu, Th\'eo Morales, John Dingliana
https://arxiv.org/abs/2601.15431 https://arxiv.org/pdf/2601.15431 https://arxiv.org/html/2601.15431
arXiv:2601.15431v1 Announce Type: new
Abstract: Radiance field-based rendering methods have attracted significant interest from the computer vision and computer graphics communities. They enable high-fidelity rendering with complex real-world lighting effects, but at the cost of high rendering time. 3D Gaussian Splatting solves this issue with a rasterisation-based approach for real-time rendering, enabling applications such as autonomous driving, robotics, virtual reality, and extended reality. However, current 3DGS implementations are difficult to integrate into traditional mesh-based rendering pipelines, which is a common use case for interactive applications and artistic exploration. To address this limitation, this software solution uses Nvidia's interprocess communication (IPC) APIs to easily integrate into implementations and allow the results to be viewed in external clients such as Unity, Blender, Unreal Engine, and OpenGL viewers. The code is available at https://github.com/RockyXu66/splatbus.
toXiv_bot_toot

J'aime

• YouTube
• Spotify
• Apple Music…

I wasn't surprised to see Rob Sanderson quoted in this, because rich vs aligned semantics - specifically , wanting both at the same time - is *such* a cultural heritage data interoperability problem #MuseTech
From: @…

Pieter Colpaert (@pietercolpaert@mastodon.social)
Attached: 2 images There’s a tension between being semantically rich (using your own terms and definitions), and being semantically aligned, in which you try to reuse terms from other vocabularies. I think we need a new concept: eventual #interoperability. I propose to start rich with your own vocabularies, and only make alignments when there’s a concrete reason for building those. https://pietercolpaert.be/interoperability/2026/01/08/eventual-interoperability #knowledgegraphs #apis #li…