Bloom filters: the niche trick behind a 16× faster API
https://www.reddit.com/r/programming/comments/1oyl5k1/bloom_filters_the_niche_trick_behind_a_16_faster/
submitted by /u/shared_ptr (https://www.reddit.com/user/shared_ptr)
[link] (https://incident.io/blog/bloom-filters) [comments] (https://www.reddit.com/r/programming/comments/1oyl5k1/bloom_filters_the_niche_trick_behind_a_16_faster/)
https://www.reddit.com/r/programming/comments/1oyl5k1/bloom_filters_the_niche_trick_behind_a_16_faster/
submitted by /u/shared_ptr (https://www.reddit.com/user/shared_ptr)
[link] (https://incident.io/blog/bloom-filters) [comments] (https://www.reddit.com/r/programming/comments/1oyl5k1/bloom_filters_the_niche_trick_behind_a_16_faster/)
ELI5 explanation of the CAP Theorem
https://www.reddit.com/r/programming/comments/1oynd1w/eli5_explanation_of_the_cap_theorem/
submitted by /u/trolleid (https://www.reddit.com/user/trolleid)
[link] (https://medium.com/@lukasniessen/this-is-a-super-simple-eli5-explanation-of-the-cap-theorem-5cd9e8469ab1) [comments] (https://www.reddit.com/r/programming/comments/1oynd1w/eli5_explanation_of_the_cap_theorem/)
https://www.reddit.com/r/programming/comments/1oynd1w/eli5_explanation_of_the_cap_theorem/
submitted by /u/trolleid (https://www.reddit.com/user/trolleid)
[link] (https://medium.com/@lukasniessen/this-is-a-super-simple-eli5-explanation-of-the-cap-theorem-5cd9e8469ab1) [comments] (https://www.reddit.com/r/programming/comments/1oynd1w/eli5_explanation_of_the_cap_theorem/)
Beyond the Vector API - A Quest for a Lower Level API #JVMLS
https://www.reddit.com/r/programming/comments/1oyo7i6/beyond_the_vector_api_a_quest_for_a_lower_level/
submitted by /u/BlueGoliath (https://www.reddit.com/user/BlueGoliath)
[link] (https://www.youtube.com/watch?v=YZLVj4UVSj0) [comments] (https://www.reddit.com/r/programming/comments/1oyo7i6/beyond_the_vector_api_a_quest_for_a_lower_level/)
https://www.reddit.com/r/programming/comments/1oyo7i6/beyond_the_vector_api_a_quest_for_a_lower_level/
submitted by /u/BlueGoliath (https://www.reddit.com/user/BlueGoliath)
[link] (https://www.youtube.com/watch?v=YZLVj4UVSj0) [comments] (https://www.reddit.com/r/programming/comments/1oyo7i6/beyond_the_vector_api_a_quest_for_a_lower_level/)
Running Java on iOS
https://www.reddit.com/r/programming/comments/1oyot0l/running_java_on_ios/
<!-- SC_OFF -->Given Apple's execution restrictions, this is an interesting approach. <!-- SC_ON --> submitted by /u/benevanstech (https://www.reddit.com/user/benevanstech)
[link] (https://www.infoq.com/news/2025/11/java-on-ios/) [comments] (https://www.reddit.com/r/programming/comments/1oyot0l/running_java_on_ios/)
https://www.reddit.com/r/programming/comments/1oyot0l/running_java_on_ios/
<!-- SC_OFF -->Given Apple's execution restrictions, this is an interesting approach. <!-- SC_ON --> submitted by /u/benevanstech (https://www.reddit.com/user/benevanstech)
[link] (https://www.infoq.com/news/2025/11/java-on-ios/) [comments] (https://www.reddit.com/r/programming/comments/1oyot0l/running_java_on_ios/)
New JavaScript engine written in Rust
https://www.reddit.com/r/programming/comments/1oyoxq6/new_javanoscript_engine_written_in_rust/
submitted by /u/Different-Maize1114 (https://www.reddit.com/user/Different-Maize1114)
[link] (https://github.com/Hans-Halverson/brimstone) [comments] (https://www.reddit.com/r/programming/comments/1oyoxq6/new_javanoscript_engine_written_in_rust/)
https://www.reddit.com/r/programming/comments/1oyoxq6/new_javanoscript_engine_written_in_rust/
submitted by /u/Different-Maize1114 (https://www.reddit.com/user/Different-Maize1114)
[link] (https://github.com/Hans-Halverson/brimstone) [comments] (https://www.reddit.com/r/programming/comments/1oyoxq6/new_javanoscript_engine_written_in_rust/)
His Legal Name Is One Letter—A reminder that bad validation rules hurt people
https://www.reddit.com/r/programming/comments/1oysdqb/his_legal_name_is_one_lettera_reminder_that_bad/
submitted by /u/grauenwolf (https://www.reddit.com/user/grauenwolf)
[link] (https://viewfromthewing.com/his-legal-name-is-one-letter-the-airline-rejects-it-and-says-just-call-yourself-aa-creating-chaos/?utm_source=fark&utm_medium=website&utm_content=link&ICID=ref_fark) [comments] (https://www.reddit.com/r/programming/comments/1oysdqb/his_legal_name_is_one_lettera_reminder_that_bad/)
https://www.reddit.com/r/programming/comments/1oysdqb/his_legal_name_is_one_lettera_reminder_that_bad/
submitted by /u/grauenwolf (https://www.reddit.com/user/grauenwolf)
[link] (https://viewfromthewing.com/his-legal-name-is-one-letter-the-airline-rejects-it-and-says-just-call-yourself-aa-creating-chaos/?utm_source=fark&utm_medium=website&utm_content=link&ICID=ref_fark) [comments] (https://www.reddit.com/r/programming/comments/1oysdqb/his_legal_name_is_one_lettera_reminder_that_bad/)
Verity v1.0.0: A data layer that enforces server-as-truth and eliminates optimistic updates
https://www.reddit.com/r/programming/comments/1oyv43v/verity_v100_a_data_layer_that_enforces/
<!-- SC_OFF -->I've been working on Verity, a framework-agnostic data layer that addresses a problem I kept running into: modern frontends blur server-owned truth-state with client-owned view-state, leading to optimistic updates, flicker, and user distrust. Core Philosophy: The server is the only source of truth Truth-state (server data) ≠ View-state (client UI concerns) Server emits directives describing what changed, not how to update the DOM Key Features: Directive-driven invalidation — server decides what needs refreshing Framework-agnostic core with adapters for Alpine, React, Vue, Svelte Multi-client synchronization via SSE Level conversion planning (derive "summary" from "full" without refetching) No optimistic updates — honest loading states instead Automatic coalescing, latest-wins guards, memory management Use Cases: Best for applications where server truth matters: real-time dashboards, multi-user tools, financial/healthcare/compliance systems, operational control rooms. Why not just use TanStack Query/Apollo? Those are excellent libraries, but they encourage optimistic updates and put invalidation logic in client code. Verity puts the server in control of the invalidation contract and refuses to lie to users about state. Examples included: The repo contains full-stack examples in multiple domains (invoice management, financial compliance, manufacturing monitoring, telehealth triage) with "baseline" versions that don't use Verity for direct comparison. Docs: https://verity.yidi.sh (https://verity.yidi.sh/) GitHub: https://github.com/YidiDev/verity License: MIT Would love to hear feedback from the community! <!-- SC_ON --> submitted by /u/yidisprei (https://www.reddit.com/user/yidisprei)
[link] (https://verity.yidi.sh/) [comments] (https://www.reddit.com/r/programming/comments/1oyv43v/verity_v100_a_data_layer_that_enforces/)
https://www.reddit.com/r/programming/comments/1oyv43v/verity_v100_a_data_layer_that_enforces/
<!-- SC_OFF -->I've been working on Verity, a framework-agnostic data layer that addresses a problem I kept running into: modern frontends blur server-owned truth-state with client-owned view-state, leading to optimistic updates, flicker, and user distrust. Core Philosophy: The server is the only source of truth Truth-state (server data) ≠ View-state (client UI concerns) Server emits directives describing what changed, not how to update the DOM Key Features: Directive-driven invalidation — server decides what needs refreshing Framework-agnostic core with adapters for Alpine, React, Vue, Svelte Multi-client synchronization via SSE Level conversion planning (derive "summary" from "full" without refetching) No optimistic updates — honest loading states instead Automatic coalescing, latest-wins guards, memory management Use Cases: Best for applications where server truth matters: real-time dashboards, multi-user tools, financial/healthcare/compliance systems, operational control rooms. Why not just use TanStack Query/Apollo? Those are excellent libraries, but they encourage optimistic updates and put invalidation logic in client code. Verity puts the server in control of the invalidation contract and refuses to lie to users about state. Examples included: The repo contains full-stack examples in multiple domains (invoice management, financial compliance, manufacturing monitoring, telehealth triage) with "baseline" versions that don't use Verity for direct comparison. Docs: https://verity.yidi.sh (https://verity.yidi.sh/) GitHub: https://github.com/YidiDev/verity License: MIT Would love to hear feedback from the community! <!-- SC_ON --> submitted by /u/yidisprei (https://www.reddit.com/user/yidisprei)
[link] (https://verity.yidi.sh/) [comments] (https://www.reddit.com/r/programming/comments/1oyv43v/verity_v100_a_data_layer_that_enforces/)
EHTML — Extended HTML for Real Apps. Sharing it in case it helps someone.
https://www.reddit.com/r/programming/comments/1oyw9g3/ehtml_extended_html_for_real_apps_sharing_it_in/
<!-- SC_OFF -->Hi everyone! I’ve been working on a project called EHTML, an HTML-first approach to building dynamic pages using mostly HTML. It lets you handle things like templating, loops, conditions, data loading, reusable components, and nested forms — all without a build step or heavy JavaScript setup. I originally built it to simplify my own workflow for small apps and prototypes, but I figured others who prefer lightweight or no-build approaches might find it useful too. It runs entirely in the browser using native ES modules and custom elements, so there’s no bundler or complex tooling involved. If you enjoy working close to the browser or like experimenting with minimalistic web development, you might find it interesting. Just sharing in case it helps someone or sparks ideas. Cheers! Link: https://e-html.org/ <!-- SC_ON --> submitted by /u/gyen (https://www.reddit.com/user/gyen)
[link] (https://e-html.org/) [comments] (https://www.reddit.com/r/programming/comments/1oyw9g3/ehtml_extended_html_for_real_apps_sharing_it_in/)
https://www.reddit.com/r/programming/comments/1oyw9g3/ehtml_extended_html_for_real_apps_sharing_it_in/
<!-- SC_OFF -->Hi everyone! I’ve been working on a project called EHTML, an HTML-first approach to building dynamic pages using mostly HTML. It lets you handle things like templating, loops, conditions, data loading, reusable components, and nested forms — all without a build step or heavy JavaScript setup. I originally built it to simplify my own workflow for small apps and prototypes, but I figured others who prefer lightweight or no-build approaches might find it useful too. It runs entirely in the browser using native ES modules and custom elements, so there’s no bundler or complex tooling involved. If you enjoy working close to the browser or like experimenting with minimalistic web development, you might find it interesting. Just sharing in case it helps someone or sparks ideas. Cheers! Link: https://e-html.org/ <!-- SC_ON --> submitted by /u/gyen (https://www.reddit.com/user/gyen)
[link] (https://e-html.org/) [comments] (https://www.reddit.com/r/programming/comments/1oyw9g3/ehtml_extended_html_for_real_apps_sharing_it_in/)
Exploring Vibe Coding - Early Impressions and Practical Framework
https://www.reddit.com/r/programming/comments/1oz5ye0/exploring_vibe_coding_early_impressions_and/
submitted by /u/Peefy- (https://www.reddit.com/user/Peefy-)
[link] (https://uselumis.ai/blogs/exploring-vibe-coding) [comments] (https://www.reddit.com/r/programming/comments/1oz5ye0/exploring_vibe_coding_early_impressions_and/)
https://www.reddit.com/r/programming/comments/1oz5ye0/exploring_vibe_coding_early_impressions_and/
submitted by /u/Peefy- (https://www.reddit.com/user/Peefy-)
[link] (https://uselumis.ai/blogs/exploring-vibe-coding) [comments] (https://www.reddit.com/r/programming/comments/1oz5ye0/exploring_vibe_coding_early_impressions_and/)
FFM - Java's new approach to interop with native code
https://www.reddit.com/r/programming/comments/1ozbr1m/ffm_javas_new_approach_to_interop_with_native_code/
submitted by /u/benevanstech (https://www.reddit.com/user/benevanstech)
[link] (https://developer.ibm.com/articles/j-ffm/) [comments] (https://www.reddit.com/r/programming/comments/1ozbr1m/ffm_javas_new_approach_to_interop_with_native_code/)
https://www.reddit.com/r/programming/comments/1ozbr1m/ffm_javas_new_approach_to_interop_with_native_code/
submitted by /u/benevanstech (https://www.reddit.com/user/benevanstech)
[link] (https://developer.ibm.com/articles/j-ffm/) [comments] (https://www.reddit.com/r/programming/comments/1ozbr1m/ffm_javas_new_approach_to_interop_with_native_code/)
Finding duplicated code with tools from your CS course
https://www.reddit.com/r/programming/comments/1ozdnhl/finding_duplicated_code_with_tools_from_your_cs/
submitted by /u/imachug (https://www.reddit.com/user/imachug)
[link] (https://purplesyringa.moe/blog/finding-duplicated-code-with-tools-from-your-cs-course/) [comments] (https://www.reddit.com/r/programming/comments/1ozdnhl/finding_duplicated_code_with_tools_from_your_cs/)
https://www.reddit.com/r/programming/comments/1ozdnhl/finding_duplicated_code_with_tools_from_your_cs/
submitted by /u/imachug (https://www.reddit.com/user/imachug)
[link] (https://purplesyringa.moe/blog/finding-duplicated-code-with-tools-from-your-cs-course/) [comments] (https://www.reddit.com/r/programming/comments/1ozdnhl/finding_duplicated_code_with_tools_from_your_cs/)
Microservices: Microliths as a resonable alternative
https://www.reddit.com/r/programming/comments/1ozflg5/microservices_microliths_as_a_resonable/
<!-- SC_OFF -->There are many fallacies related to Microservices people used to believe in (some still): that they improve design (architecture) on their own, just by the mere fact of a usage that they are needed because otherwise we cannot scale that they lead to simpler solutions ...and so on, many more It does not mean that they do not have their place - sometimes they do, but in the vast majority of the cases, they are neither required because of the predicted scalability needs nor because we have so many teams (like 10+, not 3 or 4) that we absolutely must separate each other on the service (process) level. But to be honest, the last argument is probably the strongest one can voice for having a few separate (micro)services: it often is objectively easier to work in parallel for multiple teams, if they all have their own service. That is where Microlits come in. They are a special kind of a (micro)service: A microlith is basically a service that is designed using the independent module design principles which avoids calls between modules/services while processing an external request. This typically requires some status and data reconciliation mechanism between services to propagate changes that affect multiple microliths. The reconciliation mechanism must be temporally decoupled from the external request processing. Having separated the processing of the external request and the communication between Microliths, we can split our monolithic application in several smaller parts without being hit by most of the distributed systems Complexity. The tradeoff is that we have to pay the price of temporally decoupled reconciliation between the Microliths. On the other hand, we do not need to deal with the problems that arise if a call to another service fails while processing an external request. <!-- SC_ON --> submitted by /u/BinaryIgor (https://www.reddit.com/user/BinaryIgor)
[link] (https://www.ufried.com/blog/microservices_fallacy_10_microliths/) [comments] (https://www.reddit.com/r/programming/comments/1ozflg5/microservices_microliths_as_a_resonable/)
https://www.reddit.com/r/programming/comments/1ozflg5/microservices_microliths_as_a_resonable/
<!-- SC_OFF -->There are many fallacies related to Microservices people used to believe in (some still): that they improve design (architecture) on their own, just by the mere fact of a usage that they are needed because otherwise we cannot scale that they lead to simpler solutions ...and so on, many more It does not mean that they do not have their place - sometimes they do, but in the vast majority of the cases, they are neither required because of the predicted scalability needs nor because we have so many teams (like 10+, not 3 or 4) that we absolutely must separate each other on the service (process) level. But to be honest, the last argument is probably the strongest one can voice for having a few separate (micro)services: it often is objectively easier to work in parallel for multiple teams, if they all have their own service. That is where Microlits come in. They are a special kind of a (micro)service: A microlith is basically a service that is designed using the independent module design principles which avoids calls between modules/services while processing an external request. This typically requires some status and data reconciliation mechanism between services to propagate changes that affect multiple microliths. The reconciliation mechanism must be temporally decoupled from the external request processing. Having separated the processing of the external request and the communication between Microliths, we can split our monolithic application in several smaller parts without being hit by most of the distributed systems Complexity. The tradeoff is that we have to pay the price of temporally decoupled reconciliation between the Microliths. On the other hand, we do not need to deal with the problems that arise if a call to another service fails while processing an external request. <!-- SC_ON --> submitted by /u/BinaryIgor (https://www.reddit.com/user/BinaryIgor)
[link] (https://www.ufried.com/blog/microservices_fallacy_10_microliths/) [comments] (https://www.reddit.com/r/programming/comments/1ozflg5/microservices_microliths_as_a_resonable/)
From Apache Spark to Fighting Health Insurance Denials • Holden Karau & Julian Wood
https://www.reddit.com/r/programming/comments/1ozgmwy/from_apache_spark_to_fighting_health_insurance/
submitted by /u/goto-con (https://www.reddit.com/user/goto-con)
[link] (https://youtu.be/qNO8U3-ZzCk?list=PLEx5khR4g7PJozVmHNpQTVrk1QRC7YaJu) [comments] (https://www.reddit.com/r/programming/comments/1ozgmwy/from_apache_spark_to_fighting_health_insurance/)
https://www.reddit.com/r/programming/comments/1ozgmwy/from_apache_spark_to_fighting_health_insurance/
submitted by /u/goto-con (https://www.reddit.com/user/goto-con)
[link] (https://youtu.be/qNO8U3-ZzCk?list=PLEx5khR4g7PJozVmHNpQTVrk1QRC7YaJu) [comments] (https://www.reddit.com/r/programming/comments/1ozgmwy/from_apache_spark_to_fighting_health_insurance/)
Requeuing Roulette in Event-Driven Architecture and Messaging
https://www.reddit.com/r/programming/comments/1ozhz1d/requeuing_roulette_in_eventdriven_architecture/
submitted by /u/Adventurous-Salt8514 (https://www.reddit.com/user/Adventurous-Salt8514)
[link] (https://event-driven.io/en/requeuing_roulette_in_messaging/) [comments] (https://www.reddit.com/r/programming/comments/1ozhz1d/requeuing_roulette_in_eventdriven_architecture/)
https://www.reddit.com/r/programming/comments/1ozhz1d/requeuing_roulette_in_eventdriven_architecture/
submitted by /u/Adventurous-Salt8514 (https://www.reddit.com/user/Adventurous-Salt8514)
[link] (https://event-driven.io/en/requeuing_roulette_in_messaging/) [comments] (https://www.reddit.com/r/programming/comments/1ozhz1d/requeuing_roulette_in_eventdriven_architecture/)
The CMDB as an architecture source
https://www.reddit.com/r/programming/comments/1oziiwz/the_cmdb_as_an_architecture_source/
<!-- SC_OFF -->Many organizations assume their CMDB can double as an architectural source of truth because it contains applications, servers, owners, service lines, capabilities, and relationships. But the CMDB was built for IT service management workflows, not for architecture, and that mismatch creates problems the moment you look deeper. The main problems are the different definitions of the terms, a capability of business application can mean something very different. The lifespan of the data, Capabilities for example can come and go in CMDBS depending on the current needs. And the conceptual base, if you base your architecture on ITSM, your architecture will also be ITSM based. That might be an issue for EA. I use a data filter in my architecture to still use the data, but transform it to use in my architectural tool. The main conclusion is: a CMDB is essential for IT operations, but it is not an architecture repository. Using it as one leads to confusion, rework, and the wrong mental model of the organization. You definitely should still use the information in there, but don't carbon copy it. <!-- SC_ON --> submitted by /u/GeneralZiltoid (https://www.reddit.com/user/GeneralZiltoid)
[link] (https://frederickvanbrabant.com/blog/2025-11-15-the-cmdb-as-an-architecture-source/) [comments] (https://www.reddit.com/r/programming/comments/1oziiwz/the_cmdb_as_an_architecture_source/)
https://www.reddit.com/r/programming/comments/1oziiwz/the_cmdb_as_an_architecture_source/
<!-- SC_OFF -->Many organizations assume their CMDB can double as an architectural source of truth because it contains applications, servers, owners, service lines, capabilities, and relationships. But the CMDB was built for IT service management workflows, not for architecture, and that mismatch creates problems the moment you look deeper. The main problems are the different definitions of the terms, a capability of business application can mean something very different. The lifespan of the data, Capabilities for example can come and go in CMDBS depending on the current needs. And the conceptual base, if you base your architecture on ITSM, your architecture will also be ITSM based. That might be an issue for EA. I use a data filter in my architecture to still use the data, but transform it to use in my architectural tool. The main conclusion is: a CMDB is essential for IT operations, but it is not an architecture repository. Using it as one leads to confusion, rework, and the wrong mental model of the organization. You definitely should still use the information in there, but don't carbon copy it. <!-- SC_ON --> submitted by /u/GeneralZiltoid (https://www.reddit.com/user/GeneralZiltoid)
[link] (https://frederickvanbrabant.com/blog/2025-11-15-the-cmdb-as-an-architecture-source/) [comments] (https://www.reddit.com/r/programming/comments/1oziiwz/the_cmdb_as_an_architecture_source/)
dockerlings: Learn Docker in your terminal
https://www.reddit.com/r/programming/comments/1ozoptb/dockerlings_learn_docker_in_your_terminal/
submitted by /u/Desperate_Pin2090 (https://www.reddit.com/user/Desperate_Pin2090)
[link] (https://github.com/furkan/dockerlings) [comments] (https://www.reddit.com/r/programming/comments/1ozoptb/dockerlings_learn_docker_in_your_terminal/)
https://www.reddit.com/r/programming/comments/1ozoptb/dockerlings_learn_docker_in_your_terminal/
submitted by /u/Desperate_Pin2090 (https://www.reddit.com/user/Desperate_Pin2090)
[link] (https://github.com/furkan/dockerlings) [comments] (https://www.reddit.com/r/programming/comments/1ozoptb/dockerlings_learn_docker_in_your_terminal/)
Memory-corrupting Pong
https://www.reddit.com/r/programming/comments/1ozotap/memorycorrupting_pong/
<!-- SC_OFF -->Allocating heap memory on the screen <!-- SC_ON --> submitted by /u/ArchAndStarch (https://www.reddit.com/user/ArchAndStarch)
[link] (https://arhan.sh/blog/memory-corrupting-pong/) [comments] (https://www.reddit.com/r/programming/comments/1ozotap/memorycorrupting_pong/)
https://www.reddit.com/r/programming/comments/1ozotap/memorycorrupting_pong/
<!-- SC_OFF -->Allocating heap memory on the screen <!-- SC_ON --> submitted by /u/ArchAndStarch (https://www.reddit.com/user/ArchAndStarch)
[link] (https://arhan.sh/blog/memory-corrupting-pong/) [comments] (https://www.reddit.com/r/programming/comments/1ozotap/memorycorrupting_pong/)
Pre-PEP: Rust for CPython
https://www.reddit.com/r/programming/comments/1ozr1mo/prepep_rust_for_cpython/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://discuss.python.org/t/pre-pep-rust-for-cpython/104906) [comments] (https://www.reddit.com/r/programming/comments/1ozr1mo/prepep_rust_for_cpython/)
https://www.reddit.com/r/programming/comments/1ozr1mo/prepep_rust_for_cpython/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://discuss.python.org/t/pre-pep-rust-for-cpython/104906) [comments] (https://www.reddit.com/r/programming/comments/1ozr1mo/prepep_rust_for_cpython/)
Think in Math. Write in Code
https://www.reddit.com/r/programming/comments/1ozr2ob/think_in_math_write_in_code/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://www.jmeiners.com/think-in-math/) [comments] (https://www.reddit.com/r/programming/comments/1ozr2ob/think_in_math_write_in_code/)
https://www.reddit.com/r/programming/comments/1ozr2ob/think_in_math_write_in_code/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://www.jmeiners.com/think-in-math/) [comments] (https://www.reddit.com/r/programming/comments/1ozr2ob/think_in_math_write_in_code/)
k-anonymity, the parent of all privacy definitions
https://www.reddit.com/r/programming/comments/1ozr2xy/kanonymity_the_parent_of_all_privacy_definitions/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://desfontain.es/blog/k-anonymity.html) [comments] (https://www.reddit.com/r/programming/comments/1ozr2xy/kanonymity_the_parent_of_all_privacy_definitions/)
https://www.reddit.com/r/programming/comments/1ozr2xy/kanonymity_the_parent_of_all_privacy_definitions/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://desfontain.es/blog/k-anonymity.html) [comments] (https://www.reddit.com/r/programming/comments/1ozr2xy/kanonymity_the_parent_of_all_privacy_definitions/)
Building a Simple Search Engine That Works
https://www.reddit.com/r/programming/comments/1ozr3ey/building_a_simple_search_engine_that_works/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://karboosx.net/post/4eZxhBon/building-a-simple-search-engine-that-actually-works) [comments] (https://www.reddit.com/r/programming/comments/1ozr3ey/building_a_simple_search_engine_that_works/)
https://www.reddit.com/r/programming/comments/1ozr3ey/building_a_simple_search_engine_that_works/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://karboosx.net/post/4eZxhBon/building-a-simple-search-engine-that-actually-works) [comments] (https://www.reddit.com/r/programming/comments/1ozr3ey/building_a_simple_search_engine_that_works/)