#dsa — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #dsa, aggregated by home.social.
-
Day 10/60: String operations in JS
Today's note was about making string operations in js work with JavaScript strings, indexing, and character handling without losing correctness. I kept coming back to the same checks: decide early whether indexing, slices, or character arrays are the right representation in JavaScript, keep the transformation or scan state explicit instead of mixing index tricks together, and use string and array helpers deliberately so character handling does not become accidental.
The failure mode worth watching is mixing index assumptions and character handling without checking what the string API actually returns. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/60: String operations in JS
Today's note was about making string operations in js work with JavaScript strings, indexing, and character handling without losing correctness. I kept coming back to the same checks: decide early whether indexing, slices, or character arrays are the right representation in JavaScript, keep the transformation or scan state explicit instead of mixing index tricks together, and use string and array helpers deliberately so character handling does not become accidental.
The failure mode worth watching is mixing index assumptions and character handling without checking what the string API actually returns. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/60: String operations in JS
Today's note was about making string operations in js work with JavaScript strings, indexing, and character handling without losing correctness. I kept coming back to the same checks: decide early whether indexing, slices, or character arrays are the right representation in JavaScript, keep the transformation or scan state explicit instead of mixing index tricks together, and use string and array helpers deliberately so character handling does not become accidental.
The failure mode worth watching is mixing index assumptions and character handling without checking what the string API actually returns. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/60: String operations in JS
Today's note was about making string operations in js work with JavaScript strings, indexing, and character handling without losing correctness. I kept coming back to the same checks: decide early whether indexing, slices, or character arrays are the right representation in JavaScript, keep the transformation or scan state explicit instead of mixing index tricks together, and use string and array helpers deliberately so character handling does not become accidental.
The failure mode worth watching is mixing index assumptions and character handling without checking what the string API actually returns. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/60: String operations in JS
Today's note was about making string operations in js work with JavaScript strings, indexing, and character handling without losing correctness. I kept coming back to the same checks: decide early whether indexing, slices, or character arrays are the right representation in JavaScript, keep the transformation or scan state explicit instead of mixing index tricks together, and use string and array helpers deliberately so character handling does not become accidental.
The failure mode worth watching is mixing index assumptions and character handling without checking what the string API actually returns. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/60: String handling in Rust
Today's note was about making string handling in rust work with Rust slices, strings, and indices without losing correctness. I kept coming back to the same checks: decide early whether bytes, chars, or slices are the right representation in Rust, keep the transformation or scan state explicit instead of mixing index tricks together, and use iterators and owned buffers deliberately so UTF-8 handling does not become accidental.
The failure mode worth watching is mixing byte indexing and character assumptions in UTF-8 text. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/60: String handling in Rust
Today's note was about making string handling in rust work with Rust slices, strings, and indices without losing correctness. I kept coming back to the same checks: decide early whether bytes, chars, or slices are the right representation in Rust, keep the transformation or scan state explicit instead of mixing index tricks together, and use iterators and owned buffers deliberately so UTF-8 handling does not become accidental.
The failure mode worth watching is mixing byte indexing and character assumptions in UTF-8 text. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/60: String handling in Rust
Today's note was about making string handling in rust work with Rust slices, strings, and indices without losing correctness. I kept coming back to the same checks: decide early whether bytes, chars, or slices are the right representation in Rust, keep the transformation or scan state explicit instead of mixing index tricks together, and use iterators and owned buffers deliberately so UTF-8 handling does not become accidental.
The failure mode worth watching is mixing byte indexing and character assumptions in UTF-8 text. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/60: String handling in Rust
Today's note was about making string handling in rust work with Rust slices, strings, and indices without losing correctness. I kept coming back to the same checks: decide early whether bytes, chars, or slices are the right representation in Rust, keep the transformation or scan state explicit instead of mixing index tricks together, and use iterators and owned buffers deliberately so UTF-8 handling does not become accidental.
The failure mode worth watching is mixing byte indexing and character assumptions in UTF-8 text. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/60: String handling in Rust
Today's note was about making string handling in rust work with Rust slices, strings, and indices without losing correctness. I kept coming back to the same checks: decide early whether bytes, chars, or slices are the right representation in Rust, keep the transformation or scan state explicit instead of mixing index tricks together, and use iterators and owned buffers deliberately so UTF-8 handling does not become accidental.
The failure mode worth watching is mixing byte indexing and character assumptions in UTF-8 text. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/75: Sliding window - variable size
Today's note was about using a stable invariant so sliding window - variable size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.
The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/75: Sliding window - variable size
Today's note was about using a stable invariant so sliding window - variable size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.
The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/75: Sliding window - variable size
Today's note was about using a stable invariant so sliding window - variable size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.
The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/75: Sliding window - variable size
Today's note was about using a stable invariant so sliding window - variable size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.
The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/75: Sliding window - variable size
Today's note was about using a stable invariant so sliding window - variable size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.
The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/75: Sliding window - variable size
Today's note was about using a stable invariant so sliding window - variable size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.
The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/75: Sliding window - variable size
Today's note was about using a stable invariant so sliding window - variable size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.
The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/75: Sliding window - variable size
Today's note was about using a stable invariant so sliding window - variable size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.
The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/75: Sliding window - variable size
Today's note was about using a stable invariant so sliding window - variable size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.
The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/75: Sliding window - variable size
Today's note was about using a stable invariant so sliding window - variable size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.
The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/75: Sliding window - variable size
Today's note was about using a stable invariant so sliding window - variable size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.
The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/75: Sliding window - variable size
Today's note was about using a stable invariant so sliding window - variable size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.
The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/75: Sliding window - variable size
Today's note was about using a stable invariant so sliding window - variable size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.
The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/75: Sliding window - variable size
Today's note was about using a stable invariant so sliding window - variable size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.
The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Day 10/75: Sliding window - variable size
Today's note was about using a stable invariant so sliding window - variable size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.
The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.
-
Dobrindt: „Abschrecken, abwehren und abschalten“ in Kürze | heise online https://www.heise.de/news/Dobrindt-Abschrecken-abwehren-und-abschalten-in-Kuerze-11292023.html #CyberCrime #Hackback #hacking #Malware #DSA #DigitalServicesAct #Ransomware
-
Dobrindt: „Abschrecken, abwehren und abschalten“ in Kürze | heise online https://www.heise.de/news/Dobrindt-Abschrecken-abwehren-und-abschalten-in-Kuerze-11292023.html #CyberCrime #Hackback #hacking #Malware #DSA #DigitalServicesAct #Ransomware
-
Dobrindt: „Abschrecken, abwehren und abschalten“ in Kürze | heise online https://www.heise.de/news/Dobrindt-Abschrecken-abwehren-und-abschalten-in-Kuerze-11292023.html #CyberCrime #Hackback #hacking #Malware #DSA #DigitalServicesAct #Ransomware
-
Dobrindt: „Abschrecken, abwehren und abschalten“ in Kürze | heise online https://www.heise.de/news/Dobrindt-Abschrecken-abwehren-und-abschalten-in-Kuerze-11292023.html #CyberCrime #Hackback #hacking #Malware #DSA #DigitalServicesAct #Ransomware
-
AOC Surges to Lead in 2028 Primary for First Time—Most Accurate Pollster
https://www.newsweek.com/aoc-surges-lead-2028-primary-first-time-poll-11941529
> Ocasio-Cortez edged out other Democrats like Kamala Harris and Gavin Newsom in a new AtlasIntel poll of the 2028 primary field.
-
AOC Surges to Lead in 2028 Primary for First Time—Most Accurate Pollster
https://www.newsweek.com/aoc-surges-lead-2028-primary-first-time-poll-11941529
> Ocasio-Cortez edged out other Democrats like Kamala Harris and Gavin Newsom in a new AtlasIntel poll of the 2028 primary field.
-
AOC Surges to Lead in 2028 Primary for First Time—Most Accurate Pollster
https://www.newsweek.com/aoc-surges-lead-2028-primary-first-time-poll-11941529
> Ocasio-Cortez edged out other Democrats like Kamala Harris and Gavin Newsom in a new AtlasIntel poll of the 2028 primary field.
-
AOC Surges to Lead in 2028 Primary for First Time—Most Accurate Pollster
https://www.newsweek.com/aoc-surges-lead-2028-primary-first-time-poll-11941529
> Ocasio-Cortez edged out other Democrats like Kamala Harris and Gavin Newsom in a new AtlasIntel poll of the 2028 primary field.
-
AOC Surges to Lead in 2028 Primary for First Time—Most Accurate Pollster
https://www.newsweek.com/aoc-surges-lead-2028-primary-first-time-poll-11941529
> Ocasio-Cortez edged out other Democrats like Kamala Harris and Gavin Newsom in a new AtlasIntel poll of the 2028 primary field.
-
Ireland’s Coimisiún na Meán (CnaM) is investigating Meta for using “dark patterns” that may block users from choosing non-profiling feeds under the DSA. ⚖️
The probe follows a Dutch court ruling and could enforce EU-wide compliance for Facebook and Instagram, affecting millions of users. 🔍#TechNews #Meta #Facebook #Instagram #DigitalServicesAct #DSA #Privacy #FOSS #UserControl #Transparency #DigitalRights #EU #Europe #Ireland #Irish #Profiling #Dutch #NL #Netherlands
-
Ireland’s Coimisiún na Meán (CnaM) is investigating Meta for using “dark patterns” that may block users from choosing non-profiling feeds under the DSA. ⚖️
The probe follows a Dutch court ruling and could enforce EU-wide compliance for Facebook and Instagram, affecting millions of users. 🔍#TechNews #Meta #Facebook #Instagram #DigitalServicesAct #DSA #Privacy #FOSS #UserControl #Transparency #DigitalRights #EU #Europe #Ireland #Irish #Profiling #Dutch #NL #Netherlands
-
Ireland’s Coimisiún na Meán (CnaM) is investigating Meta for using “dark patterns” that may block users from choosing non-profiling feeds under the DSA. ⚖️
The probe follows a Dutch court ruling and could enforce EU-wide compliance for Facebook and Instagram, affecting millions of users. 🔍#TechNews #Meta #Facebook #Instagram #DigitalServicesAct #DSA #Privacy #FOSS #UserControl #Transparency #DigitalRights #EU #Europe #Ireland #Irish #Profiling #Dutch #NL #Netherlands
-
Ireland’s Coimisiún na Meán (CnaM) is investigating Meta for using “dark patterns” that may block users from choosing non-profiling feeds under the DSA. ⚖️
The probe follows a Dutch court ruling and could enforce EU-wide compliance for Facebook and Instagram, affecting millions of users. 🔍#TechNews #Meta #Facebook #Instagram #DigitalServicesAct #DSA #Privacy #FOSS #UserControl #Transparency #DigitalRights #EU #Europe #Ireland #Irish #Profiling #Dutch #NL #Netherlands
-
Ireland’s Coimisiún na Meán (CnaM) is investigating Meta for using “dark patterns” that may block users from choosing non-profiling feeds under the DSA. ⚖️
The probe follows a Dutch court ruling and could enforce EU-wide compliance for Facebook and Instagram, affecting millions of users. 🔍#TechNews #Meta #Facebook #Instagram #DigitalServicesAct #DSA #Privacy #FOSS #UserControl #Transparency #DigitalRights #EU #Europe #Ireland #Irish #Profiling #Dutch #NL #Netherlands
-
92% Evropejcev meni, da bi morala biti zaščita otrok na spletu naša 🔝prioriteta.
Zgraditi moramo digitalni svet, v katerem se bodo otroci lahko varno učili, igrali in družili.
Svet, v katerem bodo varni in svobodni.
To je naš cilj. To je cilj #DSA 👉https://digital-strategy.ec.europa.eu/sl/factpages/childrens-protection-online-high-priority-92-europeans
---
https://nitter.net/EKvSloveniji/status/2054205120733225033#m -
92% Evropejcev meni, da bi morala biti zaščita otrok na spletu naša 🔝prioriteta.
Zgraditi moramo digitalni svet, v katerem se bodo otroci lahko varno učili, igrali in družili.
Svet, v katerem bodo varni in svobodni.
To je naš cilj. To je cilj #DSA 👉https://digital-strategy.ec.europa.eu/sl/factpages/childrens-protection-online-high-priority-92-europeans
---
https://nitter.net/EKvSloveniji/status/2054205120733225033#m -
La #DSA obliga a Meta a habilitar el feed cronológico en Instagram y Facebook desde hace un año, pero la opción está medio escondida. Un dark pattern de libro, también prohibido. Por fin acaban de abrir una investigación para ver si les multan. Gracias a @edri por denunciarlo. https://edri.org/our-work/ireland-investigates-meta-for-breaching-the-dsa-a-year-on-from-our-complaint/
-
La #DSA obliga a Meta a habilitar el feed cronológico en Instagram y Facebook desde hace un año, pero la opción está medio escondida. Un dark pattern de libro, también prohibido. Por fin acaban de abrir una investigación para ver si les multan. Gracias a @edri por denunciarlo. https://edri.org/our-work/ireland-investigates-meta-for-breaching-the-dsa-a-year-on-from-our-complaint/
-
La #DSA obliga a Meta a habilitar el feed cronológico en Instagram y Facebook desde hace un año, pero la opción está medio escondida. Un dark pattern de libro, también prohibido. Por fin acaban de abrir una investigación para ver si les multan. Gracias a @edri por denunciarlo. https://edri.org/our-work/ireland-investigates-meta-for-breaching-the-dsa-a-year-on-from-our-complaint/
-
La #DSA obliga a Meta a habilitar el feed cronológico en Instagram y Facebook desde hace un año, pero la opción está medio escondida. Un dark pattern de libro, también prohibido. Por fin acaban de abrir una investigación para ver si les multan. Gracias a @edri por denunciarlo. https://edri.org/our-work/ireland-investigates-meta-for-breaching-the-dsa-a-year-on-from-our-complaint/
-
La #DSA obliga a Meta a habilitar el feed cronológico en Instagram y Facebook desde hace un año, pero la opción está medio escondida. Un dark pattern de libro, también prohibido. Por fin acaban de abrir una investigación para ver si les multan. Gracias a @edri por denunciarlo. https://edri.org/our-work/ireland-investigates-meta-for-breaching-the-dsa-a-year-on-from-our-complaint/
-
1/ 🥳 Big news for digital rights in Europe: Ireland’s Digital Services Coordinator, Coimisiún na Meán, has opened a formal investigation into Meta’s potential use of “dark patterns” that may prevent people from choosing feeds not based on profiling on Facebook and Instagram.
👏 We’re glad to see regulators taking these concerns seriously. This investigation could become a major step toward meaningful #DSA enforcement and stronger user rights across the EU.
Our reaction ➡️ https://lnkd.in/euyCMjcA
-
1/ 🥳 Big news for digital rights in Europe: Ireland’s Digital Services Coordinator, Coimisiún na Meán, has opened a formal investigation into Meta’s potential use of “dark patterns” that may prevent people from choosing feeds not based on profiling on Facebook and Instagram.
👏 We’re glad to see regulators taking these concerns seriously. This investigation could become a major step toward meaningful #DSA enforcement and stronger user rights across the EU.
Our reaction ➡️ https://lnkd.in/euyCMjcA
-
1/ 🥳 Big news for digital rights in Europe: Ireland’s Digital Services Coordinator, Coimisiún na Meán, has opened a formal investigation into Meta’s potential use of “dark patterns” that may prevent people from choosing feeds not based on profiling on Facebook and Instagram.
👏 We’re glad to see regulators taking these concerns seriously. This investigation could become a major step toward meaningful #DSA enforcement and stronger user rights across the EU.
Our reaction ➡️ https://lnkd.in/euyCMjcA
-
1/ 🥳 Big news for digital rights in Europe: Ireland’s Digital Services Coordinator, Coimisiún na Meán, has opened a formal investigation into Meta’s potential use of “dark patterns” that may prevent people from choosing feeds not based on profiling on Facebook and Instagram.
👏 We’re glad to see regulators taking these concerns seriously. This investigation could become a major step toward meaningful #DSA enforcement and stronger user rights across the EU.
Our reaction ➡️ https://lnkd.in/euyCMjcA