904 results for “Data_Ranger”
"nine pieces of work looking at health and community impacts... showed an ‘emerging and concerning issue’” https://www.opendatamanchester.org.uk/public-health-evidence-on-data-centres/
#Maptober 🗺️ 📍
J25 : Osmose ✔️
Osmose est un outil puissant qui permet de comparer des données OSM avec d'autres sources comme par exemple la base de données des établissements scolaires de data.gouv.fr.
On peut afficher directement les données manquantes ou à mettre à jour et après vérification, les publier dans #OSM.
An AI tutor could explain maths patiently while narrowing the history a child is allowed to encounter.
Excellent test scores would not tell us whose interests the system serves.
Schools need the power to inspect these tools, protect pupils’ data and change suppliers.
A new essay on education, AI and human freedom:
https://10billion.substack.com/p/why-educate-everyone-if-ai-can-do
Paris Marx examines the environmental and infrastructural strains of big tech expansion in a new book titled Hyperscale.
The work details the rapid build-out of data centers, grid capacity limits that sparked moratoriums in Dublin, Singapore, and the Netherlands, local disputes over water use in Oregon, and the clash between AI infrastructure goals and climate policies.
https://en.hacks.gr/pos-ta-kentra-dedomenon-ton-technologikon-kolosson-apeiloyn-to-perivallon/
WIPE WARNING: Rotate credentials and comb your access logs on that third-party learning platform now — if it touched your network, assume it's the weak point.
Reward: You've received the Everest Expedition Badge. It is made of data you no longer have.
#Ransomware #CyberSecurity #InfoSec #PwC #DataBreach #AchievementUnlocked (2/2)
Cybersecurity bounty hunter says Samsung TVs use AI to record audio and screenshots for ads
Small coding choices can make software easier to understand and maintain. One example in C# is how we initialize string properties in DTOs.
A DTO —Data Transfer Object— carries data between parts of an application. For example, it might carry a customer’s name from an API request into the application.
Consider these two approaches:
public sealed class CreateCustomerDtoWithNull
{
public string Name { get; init; } = null!;
}
public sealed class CreateCustomerDto
{
public string Name { get; init; } = string.Empty;
}
Both avoid the compiler warning about an uninitialized non-nullable property. Both initial values can be rejected by FluentValidation.
But they create different starting states.
For required text fields where missing and empty values are treated the same, I prefer string.Empty: it gives the property an actual string value without suppressing a compiler warning.
The difference becomes clearer when we look at what each declaration means.
With nullable reference types enabled, string expresses the intention that a property should not contain null.
However:
public string Name { get; init; } = null!;
initializes that property with null.
The ! suppresses the nullable warning. It does not create a value, check anything at runtime, or guarantee that something will replace the null later. Microsoft explicitly documents that the operator has no runtime effect. Microsoft: null-forgiving operator.
With:
public string Name { get; init; } = string.Empty;
the property starts with "": an actual string containing zero characters. It is different from " ", which contains a space. Microsoft: String.Empty.
This makes the initial state more consistent with the declared type. We have a string; we still need to check whether its content is acceptable.
“FluentValidation can catch both” is correct.
For example:
using FluentValidation;
public sealed class CreateCustomerDtoValidator
: AbstractValidator
{
public CreateCustomerDtoValidator()
{
RuleFor(x => x.Name)
.NotEmpty()
.WithMessage("Name is required.");
}
}
For strings, NotEmpty() rejects all of these:
Value Result
null Rejected
"" Rejected
" " Rejected
"Maria" Accepted
This behavior is documented by FluentValidation and can also be checked in its implementation. FluentValidation documentation, NotEmptyValidator source code.
The preference for string.Empty therefore concerns the object’s starting state and the clarity of the code.
It separates two responsibilities:
Also, validation does not fill in the missing name. It reports the problem so the application can reject the request.
In an ASP.NET Core application using Clean Architecture, a straightforward execution flow is:
API receives the request
→ DTO is created
→ Application validates the input
→ Domain creates a valid customer
→ Infrastructure saves the customer
The Application layer can execute validation before continuing:
await validator.ValidateAndThrowAsync(dto, cancellationToken);
// Continue with customer creation only after validation succeeds.
The API must then translate validation failures into an appropriate response, such as HTTP 400 with useful error messages.
The Domain should also protect its own essential rules when creating a customer. This keeps those rules effective when data arrives through another route.
Clean Architecture supports this separation of responsibilities. It does not prescribe a particular DTO initializer. Microsoft: common application architectures.
For a manager, the practical benefit is straightforward: clear starting states reduce the assumptions developers need to make. Reviewers can see what the object initially contains and where unacceptable input is rejected.
There are limits to this preference.
First, string.Empty only sets the initial value. Depending on serializer settings, an incoming JSON value such as "name": null can replace it. External input still needs validation. Microsoft: nullable annotations in System.Text.Json.
Second, sometimes null carries useful information. If a DTO should accurately represent missing input, a nullable property can be more appropriate:
public string? Name { get; init; }
The business rule can still require a name. The nullable type acknowledges that an incoming request may fail to provide one.
There are other reasonable designs too. Maarten Balliauw discourages using default! to silence warnings in JSON DTOs and discusses alternatives such as nullable properties, constructors, and required. His article supports avoiding hidden assumptions, rather than a universal preference for empty strings. Maarten Balliauw: nullable warnings in JSON models.
Ian Griffiths provides a useful counterargument: an empty string can also hide missing meaningful data if it is added simply to silence the compiler. This matters especially when objects are expected to be valid immediately after construction. Ian Griffiths: defeating the point with empty strings.
My preferred team convention is therefore:
For input DTOs where missing and empty text have the same meaning, use string.Empty and validate required content with NotEmpty(). Use nullable properties when absence matters. Use null! when there is a specific, justified initialization guarantee.
The aim is to keep the declared intention, actual starting value, and validation rules consistent—and easy for the next person to understand.
[email protected]#coding #csharp #dotnet #softwaredevelopment #software #development #engineering #inclusive #community
Why I Prefer string.Empty Over null! in Input DTOs
On Wednesday, EU Member States approved a change to the GDPR that would put the profit-making interests of OpenAI, Anthropic, Google, Meta and SpaceX over European's fundamental right to data protection. According to the approved text, processing personal data “in the context of AI” should automatically be lawful. In particular, Big Tech would be able to use all personal data collected over the past decades with virtually no restrictions, as long as this happens “in the context” of AI.
https://noyb.eu/en/ai-eu-member-states-approve-digital-expropriation-europeans-ai-companies
Just dropped mathslop 1.3, adding some new convenience features to my equation editor
@googlechrome
extension. Runs in the sidebar, no network access, no analytics, all data stored locally on your machine! And I fuzz it just in case!
Created it to run next to Khan Academy while I teach myself math, but maybe somebody else will also find it useful so I threw it up on the store.
https://chromewebstore.google.com/detail/mathslop/hapemhbhhkmgcmhpiffngdiahpbfdfcj
Healthcare is the third most targeted sector this week. Just over 120 stories hit the wire. Technology and government see higher volumes, but healthcare data isn't the same. It doesn't expire.
🌐 Danube River Update | Romania
📅 25 October 2026
Current levels:
💧 Brăila: -18 cm
💧 Calafat: -201 cm
💧 Călăraşi: -202 cm
💧 Corabia: -162 cm
💧 Drobeta Turnu Severin: 660 cm
💧 Galaţi: 12 cm
💧 Giurgiu: -209 cm
💧 Orșova: 2530 cm
💧 Tulcea: 10 cm
💧 Turnu Măgurele: -139 cm
💧 Zimnicea: -100 cm
🔗 View all data: https://danubealert.com/en/Romania
#RiverFlow #Romania #HydroData #StreamMonitoring #AquaticScience #DanubeAlert
🌐 Danube River Update | Hungary
📅 25 October 2026
Current levels:
💧 BAJA: -28 cm
💧 BUDAPEST: 38 cm
💧 DUNAUJVAROS: -92 cm
💧 ESZTERGOM: -10 cm
💧 KOMAROM: 1 cm
💧 MOHACS: -16 cm
🔗 View all data: https://danubealert.com/en/Hungary
#RiverFlow #Hungary #HydroData #StreamMonitoring #AquaticScience #DanubeAlert
🌐 Danube River Update | Croatia
📅 25 October 2026
Current levels:
💧 Vodomjer Jasenovac: -13 cm
💧 Vodomjer Osijek: -180 cm
💧 Vodomjer Slavonski Brod: -27 cm
💧 Vodomjer Vukovar: -90 cm
🔗 View all data: https://danubealert.com/en/Croatia
#RiverFlow #Croatia #HydroData #StreamMonitoring #AquaticScience #DanubeAlert
🌐 Danube River Update | Bulgaria
📅 18 August 2026
Current levels:
💧 AHS RUSE-GURGUE BRIDGE: 0 cm
💧 AHS VIDIN-KALAFAT BRIDGE: 183 cm
💧 GAUGE NOVO SELO: -76 cm
💧 GAUGE ORYAHOVO: -110 cm
💧 GAUGE RUSE: -124 cm
💧 GAUGE SILISTRA: -113 cm
💧 GAUGE SVISHTOV: -66 cm
🔗 View all data: https://danubealert.com/en/Bulgaria
#RiverFlow #Bulgaria #HydroData #StreamMonitoring #AquaticScience #DanubeAlert
🌐 Danube River Update | Austria
📅 25 October 2026
Current levels:
💧 Duernstein: 281 cm
💧 Grein: 707 cm
💧 Korneuburg: 180 cm
💧 Mauthausen: 431 cm
💧 Wilhering: 229 cm
🔗 View all data: https://danubealert.com/en/Austria
#RiverFlow #Austria #HydroData #StreamMonitoring #AquaticScience #DanubeAlert
🌍 Danube River Monitoring | Slovakia
📅 25 October 2026
Current water levels:
🌊 BRATISLAVA: 278 cm
🌊 KOMARNO: 47 cm
🌊 STUROVO: 835 cm
🔬 Full monitoring data: https://danubealert.com/en/Slovakia
#DanubeRiver #Slovakia #RiverEcology #WaterEnvironment #DanubeAlert
🌍 Danube River Monitoring | Serbia
📅 24 October 2026
Current water levels:
🌊 Апатин: -113 cm
🌊 Београд: 135 cm
🌊 Земун: 177 cm
🌊 Нови Сад: -70 cm
🌊 Панчево: 223 cm
🌊 Смедерево: 425 cm
🔬 Full monitoring data: https://danubealert.com/en/Serbia
#DanubeRiver #Serbia #RiverEcology #WaterEnvironment #DanubeAlert
🌍 Danube River Monitoring | Romania
📅 25 October 2026
Current water levels:
🌊 Brăila: -18 cm
🌊 Calafat: -201 cm
🌊 Călăraşi: -202 cm
🌊 Corabia: -162 cm
🌊 Drobeta Turnu Severin: 660 cm
🌊 Galaţi: 12 cm
🌊 Giurgiu: -209 cm
🌊 Orșova: 2530 cm
🌊 Tulcea: 10 cm
🌊 Turnu Măgurele: -139 cm
🌊 Zimnicea: -100 cm
🔬 Full monitoring data: https://danubealert.com/en/Romania
#DanubeRiver #Romania #RiverEcology #WaterEnvironment #DanubeAlert
🌍 Danube River Monitoring | Hungary
📅 25 October 2026
Current water levels:
🌊 BAJA: -28 cm
🌊 BUDAPEST: 38 cm
🌊 DUNAUJVAROS: -92 cm
🌊 ESZTERGOM: -10 cm
🌊 KOMAROM: 1 cm
🌊 MOHACS: -16 cm
🔬 Full monitoring data: https://danubealert.com/en/Hungary
#DanubeRiver #Hungary #RiverEcology #WaterEnvironment #DanubeAlert
🌍 Danube River Monitoring | Croatia
📅 25 October 2026
Current water levels:
🌊 Vodomjer Jasenovac: -13 cm
🌊 Vodomjer Osijek: -180 cm
🌊 Vodomjer Slavonski Brod: -27 cm
🌊 Vodomjer Vukovar: -90 cm
🔬 Full monitoring data: https://danubealert.com/en/Croatia
#DanubeRiver #Croatia #RiverEcology #WaterEnvironment #DanubeAlert
🌍 Danube River Monitoring | Bulgaria
📅 18 August 2026
Current water levels:
🌊 AHS RUSE-GURGUE BRIDGE: 0 cm
🌊 AHS VIDIN-KALAFAT BRIDGE: 183 cm
🌊 GAUGE NOVO SELO: -76 cm
🌊 GAUGE ORYAHOVO: -110 cm
🌊 GAUGE RUSE: -124 cm
🌊 GAUGE SILISTRA: -113 cm
🌊 GAUGE SVISHTOV: -66 cm
🔬 Full monitoring data: https://danubealert.com/en/Bulgaria
#DanubeRiver #Bulgaria #RiverEcology #WaterEnvironment #DanubeAlert
🌍 Danube River Monitoring | Austria
📅 25 October 2026
Current water levels:
🌊 Duernstein: 281 cm
🌊 Grein: 707 cm
🌊 Korneuburg: 180 cm
🌊 Mauthausen: 431 cm
🌊 Wilhering: 229 cm
🔬 Full monitoring data: https://danubealert.com/en/Austria
#DanubeRiver #Austria #RiverEcology #WaterEnvironment #DanubeAlert
Oneonta City School District Shuts Down Following Ransomware Attack
Oneonta City School District closed schools for two days after a ransomware attack encrypted its computer network and disrupted internal programs. The district is working with external experts to determine if student or staff data was stolen during the breach.
****
#cybersecurity #infosec #incident #ransomware
https://beyondmachines.net/event_details/oneonta-city-school-district-shuts-down-following-ransomware-attack-5-p-g-4-c/gD2P6Ple2L
🌊 Danube Water Levels - Hungary - 25.10.2026
📍 BAJA: -28 cm
📍 BUDAPEST: 38 cm
📍 DUNAUJVAROS: -93 cm
📍 ESZTERGOM: -9 cm
📍 KOMAROM: 1 cm
📍 MOHACS: -16 cm
📊 Full data: https://danubealert.com/en/Hungary
El País RSS Feed Bot 🤖
Steering clear of the Postal Service and delivering ballots in person: Voter fears ahead of the midterms
Some 4.5 million Americans have already cast their ballots early and in person, according to data from the University of Florida
Today in European digital sovereignty:
Italy and Japan sign semiconductor and tech investment pact
https://www.nupath.eu/italy-and-japan-sign-semiconductor-and-tech-investment-pact/
Gaia-X accelerates trusted data spaces with new leadership focus
https://www.nupath.eu/gaia-x-accelerates-trusted-data-spaces-with-new-leadership-focus/
EU states approve GDPR changes to ease AI data processing
https://www.nupath.eu/eu-states-approve-gdpr-changes-to-ease-ai-data-processing/
... #digitalsovereignty
Markets bet the US-Iran pause holds to month-end; the Gulf sky says otherwise
Two readings fit today's Iran data and they imply opposite positioning.
The first is that the shooting has effectively stopped: pricing on the halt continuing to month-end sits near 69%, and pricing on Khamenei's son as head of state at end-2026 near 87% implies traders expect a stable Iranian state rather than a collapsing one.
The second is that nothing has stopped, only…
Тестовые данные отдельно, код отдельно: 5 способов изолировать данные в автотестах на Java
Статья о том, как развести тестовые данные и код проверок в Java + TestNG. Пять способов — от параметров сборщика до Test Data Factory. С примерами, схемами и разбором ограничений. Для тех, кто только начинает писать автотесты на Java.
https://habr.com/ru/articles/1099006/
#тестирование #java #автоматизация_тестирования #testng #data_driven_testing #allure #aqa #автотесты #тестовые_данные #архитектура_тестов