#parse — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #parse, aggregated by home.social.
-
"Parse, don't validate" through the years with C++
https://derekrodriguez.dev/parse-dont-validate-through-the-years-with-c-/
#HackerNews #Parse #C++ #programming #software #development #coding #bestpractices
-
"Parse, don't validate" through the years with C++
https://derekrodriguez.dev/parse-dont-validate-through-the-years-with-c-/
#HackerNews #Parse #C++ #programming #software #development #coding #bestpractices
-
"Parse, don't validate" through the years with C++
https://derekrodriguez.dev/parse-dont-validate-through-the-years-with-c-/
#HackerNews #Parse #C++ #programming #software #development #coding #bestpractices
-
"Parse, don't validate" through the years with C++
https://derekrodriguez.dev/parse-dont-validate-through-the-years-with-c-/
#HackerNews #Parse #C++ #programming #software #development #coding #bestpractices
-
"Parse, don't validate" through the years with C++
https://derekrodriguez.dev/parse-dont-validate-through-the-years-with-c-/
#HackerNews #Parse #C++ #programming #software #development #coding #bestpractices
-
CVE Alert: CVE-2026-32944 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32944-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32944 #parse-community #parse-server
-
CVE Alert: CVE-2026-32886 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32886-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32886 #parse-community #parse-server
-
CVE Alert: CVE-2026-32944 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32944-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32944 #parse-community #parse-server
-
CVE Alert: CVE-2026-32886 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32886-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32886 #parse-community #parse-server
-
CVE Alert: CVE-2026-32944 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32944-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32944 #parse-community #parse-server
-
CVE Alert: CVE-2026-32886 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32886-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32886 #parse-community #parse-server
-
CVE Alert: CVE-2026-32944 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32944-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32944 #parse-community #parse-server
-
CVE Alert: CVE-2026-32886 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32886-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32886 #parse-community #parse-server
-
CVE Alert: CVE-2026-32944 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32944-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32944 #parse-community #parse-server
-
CVE Alert: CVE-2026-32886 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32886-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32886 #parse-community #parse-server
-
CVE Alert: CVE-2026-32728 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32728-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32728 #parse-community #parse-server
-
CVE Alert: CVE-2026-32770 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32770-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32770 #parse-community #parse-server
-
CVE Alert: CVE-2026-32878 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32878-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32878 #parse-community #parse-server
-
CVE Alert: CVE-2026-32728 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32728-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32728 #parse-community #parse-server
-
CVE Alert: CVE-2026-32770 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32770-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32770 #parse-community #parse-server
-
CVE Alert: CVE-2026-32878 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32878-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32878 #parse-community #parse-server
-
CVE Alert: CVE-2026-32728 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32728-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32728 #parse-community #parse-server
-
CVE Alert: CVE-2026-32770 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32770-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32770 #parse-community #parse-server
-
CVE Alert: CVE-2026-32878 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32878-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32878 #parse-community #parse-server
-
CVE Alert: CVE-2026-32728 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32728-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32728 #parse-community #parse-server
-
CVE Alert: CVE-2026-32878 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32878-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32878 #parse-community #parse-server
-
CVE Alert: CVE-2026-32770 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32770-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32770 #parse-community #parse-server
-
CVE Alert: CVE-2026-32728 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32728-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32728 #parse-community #parse-server
-
CVE Alert: CVE-2026-32770 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32770-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32770 #parse-community #parse-server
-
CVE Alert: CVE-2026-32878 - parse-community - parse-server - https://www.redpacketsecurity.com/cve-alert-cve-2026-32878-parse-community-parse-server/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-32878 #parse-community #parse-server
-
Parse, Don't Validate and Type-Driven Design in Rust
https://www.harudagondi.space/blog/parse-dont-validate-and-type-driven-design-in-rust/
-
Parse, Don't Validate and Type-Driven Design in Rust
https://www.harudagondi.space/blog/parse-dont-validate-and-type-driven-design-in-rust/
-
Parse, Don't Validate and Type-Driven Design in Rust
https://www.harudagondi.space/blog/parse-dont-validate-and-type-driven-design-in-rust/
-
Parse, Don't Validate and Type-Driven Design in Rust
https://www.harudagondi.space/blog/parse-dont-validate-and-type-driven-design-in-rust/
-
Parse, Don't Validate and Type-Driven Design in Rust
https://www.harudagondi.space/blog/parse-dont-validate-and-type-driven-design-in-rust/
-
I'm trying to #parse a string into an int in an #esphome lambda. I can use std::stoi() and it works, but I'm struggling at error management. It raises an #exception if the string is not parseable (i.e. "text" instead of "2"), but ESPHome disables the exceptions, so I can't simply try-catch it...
ATM the code is mostly working, but if the string isn't a valid int, the entire device crashes D:
How am I supposed to implement this? -
I'm trying to #parse a string into an int in an #esphome lambda. I can use std::stoi() and it works, but I'm struggling at error management. It raises an #exception if the string is not parseable (i.e. "text" instead of "2"), but ESPHome disables the exceptions, so I can't simply try-catch it...
ATM the code is mostly working, but if the string isn't a valid int, the entire device crashes D:
How am I supposed to implement this? -
I'm trying to #parse a string into an int in an #esphome lambda. I can use std::stoi() and it works, but I'm struggling at error management. It raises an #exception if the string is not parseable (i.e. "text" instead of "2"), but ESPHome disables the exceptions, so I can't simply try-catch it...
ATM the code is mostly working, but if the string isn't a valid int, the entire device crashes D:
How am I supposed to implement this? -
I'm trying to #parse a string into an int in an #esphome lambda. I can use std::stoi() and it works, but I'm struggling at error management. It raises an #exception if the string is not parseable (i.e. "text" instead of "2"), but ESPHome disables the exceptions, so I can't simply try-catch it...
ATM the code is mostly working, but if the string isn't a valid int, the entire device crashes D:
How am I supposed to implement this? -
I'm trying to #parse a string into an int in an #esphome lambda. I can use std::stoi() and it works, but I'm struggling at error management. It raises an #exception if the string is not parseable (i.e. "text" instead of "2"), but ESPHome disables the exceptions, so I can't simply try-catch it...
ATM the code is mostly working, but if the string isn't a valid int, the entire device crashes D:
How am I supposed to implement this? -
bsky URL parsing #TEST #parse #parsing #parser timothygu.me/urltester/#i...
URL parser tester -
[PARSE] - Ransomware Victim: SystemExec Co[.], Ltd[.] - https://www.redpacketsecurity.com/parse-ransomware-victim-systemexec-co-ltd/
#parse #dark_web #data_breach #OSINT #ransomware #threatintel #tor
-
[PARSE] - Ransomware Victim: SystemExec Co[.], Ltd[.] - https://www.redpacketsecurity.com/parse-ransomware-victim-systemexec-co-ltd/
#parse #dark_web #data_breach #OSINT #ransomware #threatintel #tor
-
[PARSE] - Ransomware Victim: SystemExec Co[.], Ltd[.] - https://www.redpacketsecurity.com/parse-ransomware-victim-systemexec-co-ltd/
#parse #dark_web #data_breach #OSINT #ransomware #threatintel #tor
-
[PARSE] - Ransomware Victim: SystemExec Co[.], Ltd[.] - https://www.redpacketsecurity.com/parse-ransomware-victim-systemexec-co-ltd/
#parse #dark_web #data_breach #OSINT #ransomware #threatintel #tor