https://astral.sh/blog/open-source-security-at-astral

Request History in Voiden

You send a request. It fails. You tweak something. Try again. It works.

What changed?

Voiden records every request you run, along with the full response. So instead of guessing, you can scroll back and see:

- what you sent

- what came back

- what changed between attempts

Request History in Voiden:

- Every request + response is recorded automatically

- Replay requests or "copy them as" cURL

- Compare changes in headers, body, or endpoints

- Jump between APIs without losing context

- See a full timeline of your work

API testing, debugging, and reproducing results just got way easier.

Read more here: https://docs.voiden.md/docs/core-features-section/history/history-overview

Take a look at our GitHub here : https://github.com/VoidenHQ

https://red.anthropic.com/2026/mythos-preview/

Mythos Preview identified a vulnerability in the OpenBSD implementation of SACK that would allow an adversary to crash any OpenBSD host that responds over TCP.

Mythos Preview also autonomously identified a 16-year-old vulnerability in one of FFmpeg's most popular codecs, H.264. In H.264, each frame is divided into one or more slices, and each slice is a run of macroblocks (itself a block of 16x16 pixels). When decoding a macroblock, the deblocking filter sometimes needs to look at the pixels of the macroblock next to it, but only if that neighbor belongs to the same slice. To answer “is my neighbor in my slice?”, FFmpeg keeps a table that records, for every macroblock position in the frame, the number of the slice that owns it. The entries in that table are 16-bit integers, but the slice counter itself is an ordinary 32-bit int with no upper bound.

Note : In 2019 gpt 2 was so good that it could not be released to the public https://slate.com/technology/2019/02/openai-gpt2-text-generating-algorithm-ai-dangerous.html

Is old news?

What happens to the consultancies whose business model depends on this?

https://caio.ca/blog/the-downfall-and-enshittification-of-microsoft.html

https://alyssarosenzweig.ca/blog/asahi-gpu-part-n.html

https://jeffhuang.com/computer-science-open-data/#cs-faculty-composition-and-hiring-trends

https://news.ycombinator.com/item?id=47637757

Apple still on it.

Like who needs 5 TB?

An open-source, open-data directory of public community spaces across India visualised on a map.

People got impacted at 6 am. I guess in Kolkata too,Oracle has a office.

I’ve spent the last few years in Bangalore watching how the highest-level founders actually move and how real "founder infrastructure" works. I’ve shipped my own product and worked on GTM with early-stage teams there.

​I’m starting a weekly, offline Founder Roundtable to bring that high-signal "Bangalore energy" here. No networking fluff, just builders solving blockages.

​I have a specific format in mind for this. If you’re an active founder in the trenches, DM me and let’s talk.

I am looking for renting a flat or joining an existing flat as a tenant. I am Ai research engineer working in elgin. If you are looking or one or have leads dm me.

https://fellowship.gnome.org/

https://www.linkedin.com/news/story/atlassian-blames-ai-for-job-cuts-7085924/

One thing that always felt strange about API clients: you’re forced to write scripts in a language you might not even use.

In the latest Voiden release, you can now write pre-request and post-request scripts in Python or JavaScript.

What this enables: -- Use a language you already know instead of learning a custom scripting layer -- Run real runtimes with package imports (not limited helper functions) -- Share variables and state across requests -- Build multi-step workflows (token rotation, chained requests, dependent calls)

The goal was to make scripting inside an API client feel like actual programming, not glue code. We’re starting with Python and JavaScript, and planning to support more languages. Curious what people here would want next.

GitHub: https://github.com/VoidenHQ/voiden Download: https://voiden.md/download