frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Lovable apps expose passport details and more than 200K private messages

https://www.crissyfield.de/research/lovable-en/
426•armcat•3h ago•141 comments

A Family Tree of Software Job Titles

https://zwischenzugs.com/2026/11/03/a-family-tree-of-software-job-titles/
100•umerf•3h ago•41 comments

PyPI's redesigned project pages with clearer security signals are now live

https://blog.pypi.org/posts/2026-11-06-ui-updates-complete/
164•rbanffy•5h ago•67 comments

KDE: The documentary [video]

https://tube.kockatoo.org/w/fFinNHfanLT7aBEb2B8y4c
302•mrkn1•7h ago•64 comments

Seagate's new hybrid drive raises some old questions

https://arstechnica.com/gadgets/2026/11/seagate-resurrects-the-ssd-hdd-hybrid-drive/
39•PaulHoule•3d ago•14 comments

Why get an expensive Pi when I have an old phone?

https://so.long.thanks.fish/why-pi-when-i-have-an-old-phone/
456•casi•4d ago•263 comments

'Grey Rocking': The Life-Improving Power of Being Really, Really Boring (2021)

https://www.esquire.com/uk/life/a38473153/grey-rock-technique-being-boring/
24•NaOH•2d ago•5 comments

Advancing science and engineering with Antigravity's /teamwork

https://research.google/blog/advancing-science-engineering-with-antigravitys-teamwork-feature/
127•acossta•7h ago•32 comments

LinkedIn, Monster take down over 1000 fake job postings after CBC investigation

https://www.cbc.ca/news/canada/linkedin-monster-take-down-over-1-000-fake-job-postings-after-cbc-...
96•gnabgib•2h ago•35 comments

Show HN: DeepSeek V3 in ~200 lines of pure Jax

https://github.com/Vaibhaav-Tiwari/deepseek-v3-jax
101•VaibhaavTiwari•6h ago•6 comments

Will we put data centers in space?

https://www.forethought.org/research/will-we-really-put-data-centers-in-space
28•simonebrunozzi•3h ago•68 comments

Reverse engineering a vintage diode-transistor logic chip

https://www.righto.com/2026/11/signetics-st680a-dtl-nand.html
64•dverlaeckt80•6d ago•2 comments

Generative AI uses more energy on non-English text

https://news.umich.edu/generative-ai-uses-more-energy-on-non-english-text/
146•DeepLogin•4d ago•89 comments

Show HN: A terminal-native idle factory game, written in Rust with ratatui

https://gitlab.com/snipedbywifi/terminactory
112•snipedbywifi•7h ago•24 comments

Demystifying phone unlocking tools: A technical overview

https://osservatorionessuno.org/blog/2026/05/demystifying-phone-unlocking-tools-a-technical-overv...
41•iloveyoutwo•6h ago•0 comments

Monkey Island: all 13 versions side by side

https://monkeyisland.pages.dev/
423•maximilianburke•16h ago•139 comments

Show HN: Fursoy – Out-of-order RV64IMAFDV core in SystemVerilog (Linux 6.6)

https://github.com/FURSOY/fursoy-cpu
55•fursoy•7h ago•16 comments

Dartmouth (Guarini) will not admit math PhD cohort this year

https://www.thedartmouth.com/article/2026/11/gandhi-fagell-guarini-will-not-admit-math-ph-d-cohor...
27•sebg•1h ago•2 comments

Tech Companies Are Trying to Shift the Concept of Privacy (Again)

https://www.eff.org/deeplinks/2026/11/tech-companies-are-trying-shift-entire-concept-privacy-again
364•gslin•8h ago•145 comments

Italy fines Meta $887M over Android users' data access

https://www.reuters.com/world/italy-fines-meta-887-million-over-android-users-data-access-2026-11...
262•giuliomagnifico•7h ago•170 comments

US IRS free online tax filing open source repo (2025)

https://github.com/IRS-Public/direct-file
107•accountinhn•3h ago•54 comments

Testing a Trash Can Faraday Cage

https://www.jefftk.com/p/testing-a-trash-can-faraday-cage
55•torutofu•2d ago•40 comments

How to Create Your Own Decentralized Messenger Protocol

https://karboosx.net/post/5j7jdDM3/how-to-create-your-own-decentralized-messenger-protocol
36•fagnerbrack•5h ago•8 comments

Let's Write a PostScript Interpreter

https://beyondloom.com/blog/postscript.html
91•RebelPotato•1d ago•14 comments

A visual explanation of reinforcement learning

https://aatishb.com/myriad/how-brains-learn/
87•aatish•7h ago•6 comments

Project Zero will disclose vulnerabilities 90 days after reporting

https://projectzero.google/2026/11/disclosure-policy.html
71•hacb•10h ago•9 comments

Creating a self booting ZIP archive

https://goliath32.com/blog/ziphead.html
23•gdgghhhhh•4h ago•4 comments

Formalizing US Tax Code (Using Lean)

https://lexifina.com/blog/formalizing-the-us-tax-code
116•dnw•5h ago•77 comments

Show HN: Agweb – a browser for agents that stays out of your way

https://github.com/paul-nameless/agweb
71•paul_nameless•7h ago•21 comments

C3 0.8.6:Library fetching,30% smaller safe-mode binaries,and stricter type rules

https://c3-lang.org/blog/c3_0_8_6_fetching_libraries/
34•DASD•2d ago•1 comments
Open in hackernews

EM-LLM: Human-Inspired Episodic Memory for Infinite Context LLMs

https://github.com/em-llm/EM-LLM-model
113•jbotz•1y ago

Comments

MacsHeadroom•1y ago
So, infinite context length by making it compute bound instead of memory bound. Curious how much longer this takes to run and when it makes sense to use vs RAG.
zfountas•1y ago
Hi MacsHeadroom, first author here. Thanks for the great questions about compute/memory trade-offs.

The quick take: To give you an example of processing speed, with a 7B model on an NVIDIA V100, EM-LLM processes (or generates) about 326 tokens/sec with a 51.2K context window (which is quite competitive for these old GPUs).

More broadly, EM-LLM is designed to make ultra-long contexts (memory-prohibitive for standard O(n^2) attention) computationally tractable. The Appendix C of our paper https://openreview.net/pdf?id=BI2int5SAC details how: significantly better attention scaling, efficient O(nm) memory formation, and large KV cache management via CPU/disk offloading. While there's a slight per-chunk overhead compared to the simplest retrieval methods initially, the crucial part is our ability to handle sequences at scales infeasible for full-context models. For instance, we're successfully using 8B models with 10M token contexts on a single GPU without prohibitive delays.

Regarding RAG in particular, EM-LLM often shows significant gains on tasks needing deep understanding of a single, long, coherent context. A key reason is that EM-LLM allows each layer to retrieve and integrate relevant information from different "episodes" of the context independently, offering more nuance than a typical single RAG step, for similar overall resource use.

mountainriver•1y ago
TTT, cannon layers, and titans seem like a stronger approach IMO.

Information needs to be compressed into latent space or it becomes computationally intractable

searchguy•1y ago
do you have references to

> TTT, cannon layers, and titans

najarvg•1y ago
This was the nearest reference I could find. Links to an unofficial pytorch implementation on Github are also linked in the threads somewhere - https://www.reddit.com/r/LocalLLaMA/comments/1i0q8nw/titans_...
vessenes•1y ago
is titans replicated? I feel like lucidrains couldn't replicate.
logicchains•1y ago
I think something like Titans explains Gemini's excellent long context performance. That would explain why the Titan team hasn't released the training code or hyperpameters used even though they said in the paper that they would, and why soon after that it came out that DeepMind would be holding off publishing new results for 6 months to avoid giving away competitive advantages.
p_v_doom•1y ago
Interesting. Before there even was attention I was thinking that the episodic memory model offers something that could be very useful for neural nets, so its cool to see people testing that
killerstorm•1y ago
Note that this works within a single sequence of tokens. It might be consistent with "episodic memory" metaphor if we consider a particular transformer run as its experience.

But this might be very different from what people expect from "memory" - i.e. ability to learn vast amounts of information and retrieve it as necessary.

This is more like a refinement of transformer attention: instead of running attention over all tokens (which is very expensive as it's quadratic), it selects a subset of token spans and runs fine-grained attention only on those. So it essentially breaks transformer attention into two parts - coarse-grained (k-NN over token spans) and fine-grained (normal).

It might be a great thing for long-context situations. But it doesn't make sense when you want millions of different facts to be considered - making them into long context is rather inefficient.

yorwba•1y ago
It would be inefficient if you had to do it from scratch for every query, but if you can do it once as a preprocessing step and reuse the prepared context for many queries, it might start to become more efficient than a shorter context that includes only some documents but has to be reprocessed because it's different every time.
killerstorm•1y ago
Yes, I think it might be a good solution where you have a context up to 10M of tokens and you do a lot of requests with that context. It might be relevant for agentic stuff which tends to produce long chat logs - especially with some gadgets on top, e.g. some 'episodes' might be completely removed as obsolete.

But I don't think it's a good solution for bigger amounts of data - as in that case it's more beneficial if that can be formed into independent memories.