home.social

Search

76 results for “claus”

  1. Anti-Weihnachtsmarkt in Gladbach setzt auf Disco: Claus-Markt 2026

    „Warum nur in Berlin?“, fragte die Organisatorin des Claus-Markts, Myriam Topel. „Auch in Gladbach kann etwas Cooles passieren.“…
    #Moenchengladbach #Deutschland #Deutsch #DE #Schlagzeilen #Headlines #Nachrichten #News #Europe #Europa #EU #Mönchengladbach #Claus #Clausrasten #Geburtstag #Germany #Markt #Nordrhein-Westfalen
    europesays.com/de/1361430/

  2. Valencia secure David Otorbi until 2031 and raise clause to 60 million

    David Otorbi has extended his Valencia contract to 2031 after the club activated a clause in his deal,…
    #Spain #ES #Europe #Europa #EU #Valencia
    europesays.com/spain/104706/

  3. Britain is quietly seeking powers over foreign AI firms

    Last week, the British government quietly tabled a new clause for the Cyber Security and Resilience Bill that…
    #EuropeSays #Britain #Europe #EU #ai #AndyBurnham #HouseofLords #Labour #uncategorized
    europesays.com/britain/150650/

  4. For #FootpathFriday I chose an underground footpath that we followed during our vacation.
    Not the type of adventure if you're a bit claustrophobic, but I really like such caves.

    Enjoy!

    #photography #nature #caves #bayern #FränkischeSchweiz

  5. NEW PAPER!

    Thesis: Bc HHS Secy RFK, Jr's vaccine disinformation undermines all the major goals of the Free Speech Clause, it should be considered a free speech violation

    Also discussed: how AI may address or more likely exacerbate the spread of vaccine disinfo

    #vaccines #Kennedy #AI #disinformation #lawfedi #FediLaw #Health

    papers.ssrn.com/sol3/papers.cf

  6. New from Cambridge Elements:

    Lexicography and the Law
    Historical Dictionaries, Originalism, and the Emoluments Clause of the United States Constitution

    by Rebecca Shapiro

    Free to download until 19th November:
    cambridge.org/core/elements/le

    #LegalHistory

  7. On Virginia's coast there's a long underwater tunnel that is one of the absolute worst things on if, like me, you are really claustrophobic. It was always the worst part of visiting family in Virginia Beach.

  8. Work from anywhere | Litigation Associate Attorney (BigLaw Firms) (M&a)

    $140–400/hr on a remote contract with micro1.
    ✅ Reviewing M&A and private equity contracts with structured feedback
    ✅ Drafting sample agreements and clauses from deal experience
    ✅ Shaping legal rubrics that train AI models

    👉 Apply here: nearskill.in/jobs/litigation-a

    #WorkFromHome #ContractJobs #RemoteJobs #Ma

  9. I hate this constant deluge of vital security updates, not because these issues should have been found a very long time ago (though they should), nor because they tend to stem from excessive complexity of the software in the first place (though they do), but because I have to accept the bloat that comes along for the ride.

    The bloat increases complexity further, increasing brittleness, degrading performance, extending the dependency chain, and, most ironically, expanding the surface area for further vulnerabilities.

    I don't want to be part of your unnecessary arms race, please.

    (It bugs me in a similar way as the ridiculously named "bills" in the US that are packed with clauses unrelated or even counterintuitive to the spirit of the bill.)

  10. Capcom has taken emergency measures to halt the unauthorized access, and an investigation is ongoing — but the data, much like a save file after a hard reset, is already out there.

    Continued use of your email inbox constitutes agreement to receive phishing attempts dressed up as official Capcom correspondence. This is not a choice. This is a clause. (2/3)

  11. Panne Orange : les 10 heures sans réseau ne donnent droit à rien, une panne aussi longue en 2012 avait valu une journée offerte
    🗞️ JeChange - 🕐 22/10 07:05
    Aucun geste commercial n'est annoncé à ce stade, le 22 octobre au matin. Le précédent existe pourtant. En juillet 2012, une panne nationale de durée comparable avait valu aux abonnés forfait une journée de communications offerte, sans qu'aucune claus... [6126 chars]
    🔗 jechange.fr/telecom/mobile/new

  12. I've been hoping that FreeBSD will block LLM contributions given the substantial risk of harm they represent, and digging for information has been painful. It's unfortunate that the process is happening behind closed doors.

    I found a chilling link on the forums:

    forums.freebsd.org/threads/a-d

    The proposal linked there is deeply worrisome. See:

    >> 4.1. General Rule: Copyright Ownership <<

    >> As a general principle, if an AI service’s terms of service allow it, the copyright of generated code belongs to the user who prompted the model. However, each service has specific conditions that may restrict this ownership or limit how the generated code can be used. <<

    This appears to be factually incorrect. For reasoning, we can lookat the United States Copyright Office paper on the topic, and specifically on the copyrightability of generated works:

    copyright.gov/ai/Copyright-and

    Specifically, check out section IV, The Arguments for Legal Change, and in that, specifically paragraph three:

    "Most commenters that opined on this issue, however, agreed with the Office’s view that the Copyright Clause requires human authorship. They supported the conclusion that AI-generated material can only be protected where there is sufficient human involvement or where AI is used as a tool to enhance human expression."

    And again, from the OpenJDK Interim Policy:

    openjdk.org/legal/ai

    ...we read: "Whether a user of a generative AI tool has IP rights in content generated by the tool is the subject of active litigation."

    On the other end of the question, it's worth remembering that AI training on copyrighted material has been ruled to not be fair use:

    courthousenews.com/ai-training

    There are ethical and moral reasons to avoid LLMs and what's currently called generative AI, and it would be encouraging if more folks cared about them. But in the absense of ethics and morals, hopefully at least the legal hurdles will outweigh the vigorous support of the subset of FreeBSD developers captured by the siren's song of free mental labour.

    #freebsd #ai #llm

  13. #reflexion

    Vigilancia masiva, moderación opaca y explotación infantil en la era del algoritmo corporativo.

    El modelo de negocio de YouTube ha priorizado la medición y la retención de usuarios a expensas de la legalidad internacional y la seguridad de los menores de edad. En septiembre de 2019, la Comisión Federal de Comercio de los Estados Unidos (FTC) y el estado de Nueva York impusieron una multa de 170 millones de dólares a Google y su filial de video tras demostrarse que violaron la Ley de Protección de la Privacidad En Línea de los Niños (COPPA). La investigación comprobó que la plataforma recopiló conscientemente datos personales de menores de 13 años sin el consentimiento de sus padres para vender anuncios dirigidos de alta rentabilidad, utilizando canales de caricaturas y canciones infantiles como carnada comercial.

    La negligencia se extiende a la seguridad y la explotación de menores dentro de su ecosistema de creadores. Canales masivos de entretenimiento familiar operaron durante años vulnerando los derechos de los niños ante la inacción de los filtros de la empresa. El caso emblemático del canal Toy Freaks, que llegó a acumular 8 millones de suscriptores, demostró que el algoritmo de la plataforma monetizó y promovió activamente videos de menores en situaciones de maltrato simulado, vómito y pánico, atrayendo audiencias con conductas depredadoras. La clausura tardía del canal en 2017 y las posteriores quejas sobre filtraciones de contenido violento en la aplicación segregada YouTube Kids evidencian que el diseño de moderación de la compañía es incapaz de contener la explotación digital que su propia arquitectura de monetización.

    Los mecanismos de censura y la discrecionalidad en cuanto a cuentas sitúan a la corporación bajo un escrutinio regulatorio sin precedentes por prácticas de engaño al consumidor. La Comisión Federal de Comercio, bajo la dirección de la oficina de protección al consumidor, mantiene abierta una investigación por la opacidad en las suspensiones de cuentas, la desmonetización arbitraria y el "shadow banning" aplicado a los creadores de contenido. Mientras la jurisprudencia del Noveno Circuito de Apelaciones de EE. UU. ratificó que YouTube opera como un foro privado y no como un espacio público sujeto a la Primera Enmienda, las agencias de control analizan si la plataforma incurre en fraude civil al violar de forma deliberada sus propios términos de servicio. La falta de transparencia en sus directrices y la ausencia de un proceso de apelación exponen un modelo que funciona con una ética muy cuestionable.

    Es justo por eso que al menos aquí su servidor así como también todo el equipo preferimos plataformas libres como peertube.

    #PensamientoCritico #Etica #Comunicación #BigTech #YouTube

  14. Open-Meteo is a free API that is used to get weather data. It doesn't need a key or even a sign-up, allowing you to run your first request in a snap of your fingers. In this guide I will try to explain this API purely from a Python developer's viewpoint, and I will only cover the two major endpoints:

    • Geocoding - Used to convert the names of cities to their coordinates on a world map.

    • Forecast - The expected weather data for that location.

    Prerequisites: Python 3 installed and basic knowledge of Python.

    Usage terms: Open-Meteo is free for non-commercial use, and the data is licensed CC BY 4.0, so you must credit Open-Meteo. Check the official site for current rate limits and commercial terms.

    Set-up


    For the set-up you will first need to install the requests Python library by running this in your terminal.

    pip install requests

    Starting Out


    To start, let me provide you with the code to get the temperature in, say, Berlin, Germany. It is as follows:

    import requests

    response = requests.get(
    "https://api.open-meteo.com/v1/forecast",
    params={
    "latitude": 52.52,
    "longitude": 13.41,
    "current": "temperature_2m",
    },
    )

    data = response.json()
    print(data["current"]["temperature_2m"])

    Save this code in a file such as weather.py and run it in your terminal with python weather.py after installing the requests library. Here is what has been done in this code:

    1) We have imported the requests library to get data from an API.

    2) We have response, which is just a variable that holds the API's reply, set equal to the following:

    2.1) Get data from the API website using the API link.

    2.2) Set the params (parameters) as the latitude and longitude of the place. In this case they are the coordinates of Berlin. Then we ask for the current temperature at 2 metres above ground level (that is what 2m means).

    3) Now we close the parameters and the response query.

    4) Then we convert the response to a Python dictionary with .json() and print the current temperature value.

    Authentication


    None for free, non-commercial use, as requests are plain GET calls with no headers or keys. (Commercial subscription tiers use an API key.)

    Endpoint 1: Geocoding


    We will find exact locations from just the city names. Here is the base URL.

    geocoding-api.open-meteo.com/v…

    Here are the parameters:

    ParameterTypeRequiredDescriptionnamestringYesName of the city you want to check.countintegerNoNumber of results you want (Default 10).languagestringNoThe language you want the result in. Default (en for English).formatstringNoThe data format of the response default is json.countryCodestringNoFilters countries using its two letter code.apikeystringNoAuthentication key required only for commercial subscription tiers.


    Here is an example that looks up the location data for London:

    import requests

    response = requests.get(
    "https://geocoding-api.open-meteo.com/v1/search",
    params={"name": "London", "count": 1, "language": "en"},
    )

    data = response.json()
    print(data["results"][0])

    • You start by importing the requests module.
    • You set up the variable response with the URL as the base URL I provided above.
    • Then you enter the parameters. Only the name is required, everything else is optional.

    The response will be something like this:

    {
    "results": [
    {
    "id": 2643743,
    "name": "London",
    "latitude": 51.50853,
    "longitude": -0.12574,
    "elevation": 25.0,
    "feature_code": "PPLC",
    "country_code": "GB",
    "admin1_id": 6269131,
    "admin2_id": 2648110,
    "timezone": "Europe/London",
    "population": 8961989,
    "country_id": 2635167,
    "country": "United Kingdom",
    "admin1": "England",
    "admin2": "Greater London"
    }
    ]
    }

    Here is what these response fields mean.

    Attribute NamesDescriptionValuesidUnique identifier for the geoname location entity2643743nameName of the specific city or locationLondonlatitudeGeographic coordinate specifying north-south position51.50853longitudeGeographic coordinate specifying east-west position-0.12574elevationHeight above sea level measured in metres25.0feature_codeClassification code mapping the location typePPLCcountry_codeTwo-letter ISO country code for the nationGBadmin1_idUnique ID for the primary administrative division6269131admin2_idUnique ID for the secondary administrative division2648110timezoneWhich region is the location in.Europe/LondonpopulationTotal number of people living in the area8961989country_idUnique identifier for the country2635167countryFull name of the countryUnited Kingdomadmin1Name of the primary administrative level (e.g. state/province)Englandadmin2Name of the secondary administrative level (e.g. county)Greater London
    Note: If nothing matches, the response has no results key at all. Use data.get("results") instead of data["results"] to avoid a KeyError.


    Endpoint 2: Forecast


    Returns the forecast of conditions for the location.

    Base URL:

    api.open-meteo.com/v1/forecast

    Again, these are the parameters for this endpoint.

    ParameterTypeRequiredDescriptionlatitudefloatYesLatitude in decimal degrees (-90 to 90)longitudefloatYesLongitude in decimal degrees (-180 to 180)currentstringNoCurrent-condition variables, comma separatedhourlystringNoHourly variables, comma separateddailystringNoDaily summaries, comma separated. Requires timezonetimezonestringNoe.g. Asia/Kolkata or autotemperature_unitstringNocelsius (default) or fahrenheitforecast_daysintegerNoNumber of forecast days to return


    Now here are some common variable names that you may encounter in this endpoint.

    VariableUsed inMeaningtemperature_2mcurrent, hourlyAir temperature 2 m above groundrelative_humidity_2mcurrent, hourlyRelative humidity (%)wind_speed_10mcurrent, hourlyWind speed 10 m above groundweather_codecurrent, hourly, dailyWeather condition as a WMO codetemperature_2m_max / _mindailyDaily highest and lowest temperatureprecipitation_sumdailyTotal daily precipitation (mm)


    Here is an example:

    import requests

    response = requests.get(
    "https://api.open-meteo.com/v1/forecast",
    params={
    "latitude": 19.07,
    "longitude": 72.88,
    "current": "temperature_2m,wind_speed_10m",
    "daily": "temperature_2m_max,temperature_2m_min",
    "timezone": "Asia/Kolkata",
    "forecast_days": 3,
    },
    )

    data = response.json()
    print(data)

    Here's how this works:

    • You first import the requests module like always.

    • You again set up a variable that gets its data from the base URL I provided above. Make sure it is the URL of the 2nd endpoint and not the 1st.

    • You then define the parameters. Only the latitude and longitude of your chosen city are required. I chose Mumbai, India, so I have entered its coordinates.

    • Then you enter additional parameters and variables using the above table as a reference.

    • Then you convert the response with response.json(), store it in the variable data and print it.

    You will see something like this if you did it correctly (the times and values will differ, since this is live data):

    {
    "latitude": 19.07,
    "longitude": 72.88,
    "timezone": "Asia/Kolkata",
    "current_units": {
    "temperature_2m": "°C",
    "wind_speed_10m": "km/h"
    },
    "current": {
    "time": "2026-10-23T14:00",
    "temperature_2m": 32.1,
    "wind_speed_10m": 11.4
    },
    "daily": {
    "time": ["2026-10-23", "2026-10-24", "2026-10-25"],
    "temperature_2m_max": [33.5, 33.2, 32.9],
    "temperature_2m_min": [25.1, 24.8, 25.0]
    }
    }

    This is a trimmed version by the way (btw). Python's print will show it as a dictionary with single quotes, which is the same data.

    In Python this becomes a dictionary. Each key under daily holds a list, and the lists line up by position. Index 0 of temperature_2m_max belongs to the first date in time:

    daily = data["daily"]

    for date, high, low in zip(
    daily["time"], daily["temperature_2m_max"], daily["temperature_2m_min"]
    ):
    print(f"{date}: high {high}, low {low}")

    Errors


    When a request is invalid, the API returns HTTP status 400 and a JSON body explaining why.
    Here is an example of a script that will provide an error.

    import requests

    response = requests.get(
    "https://api.open-meteo.com/v1/forecast",
    params={"latitude": 120, "longitude": 72.88, "current": "temperature_2m"},
    )

    print(response.status_code)
    print(response.json())

    The reason for the error here is that latitudes go from -90° to 90° (longitudes go from -180° to 180°), so 120° is an invalid latitude. The error will look something like this:

    {
    "error": true,
    "reason": "Latitude must be in range of -90 to 90°. Given: 120.0."
    }

    Here are some common errors, their codes and fixes:

    StatusCauseFix400Invalid or missing parameter, or unknown variable nameRead the reason field and correct the request429Too many requestsSlow down and retry later5xxServer problemRetry after a short wait


    These were some common errors. You can refer to the official Open-Meteo documentation or the internet if you have an error that doesn't match the ones provided.

    One Final Example: Get the Forecast from a City Name Directly


    In this part you will learn to connect both endpoints to get the forecast by just the city name instead of latitudes and longitudes.

    import requests

    GEOCODING_URL = "https://geocoding-api.open-meteo.com/v1/search"
    FORECAST_URL = "https://api.open-meteo.com/v1/forecast"

    def get_coordinates(city):
    """Turn a city name into a place dictionary, or None if not found."""
    response = requests.get(GEOCODING_URL, params={"name": city, "count": 1})
    response.raise_for_status()
    results = response.json().get("results")
    return results[0] if results else None

    def get_current_weather(latitude, longitude):
    """Fetch current temperature and wind speed for a location."""
    response = requests.get(
    FORECAST_URL,
    params={
    "latitude": latitude,
    "longitude": longitude,
    "current": "temperature_2m,wind_speed_10m",
    "timezone": "auto",
    },
    )
    response.raise_for_status()
    return response.json()

    place = get_coordinates("Mumbai")

    if place is None:
    print("City not found.")
    else:
    weather = get_current_weather(place["latitude"], place["longitude"])
    current = weather["current"]
    print(f"{place['name']}, {place['country']}")
    print(f"Temperature: {current['temperature_2m']} °C")
    print(f"Wind speed: {current['wind_speed_10m']} km/h")

    Now here is what has been done.

    • You first import the required modules like always and provide the URLs for the two endpoints.

    • Now you make a function to get the coordinates of a city from its name, as coordinates are used in the forecast.

    • In that function you use requests.get() to get data on the entered city, and return the first result. If the request failed, raise_for_status() raises an exception.

    • You now make a second function to get the forecast of the city using endpoint 2.

    • You again set response equal to requests.get() from the base URL of the 2nd endpoint, not the first, with the latitude and longitude passed in and the other parameters of your choice.

    • You then get the response and return it.

    • You then call the get_coordinates() function and store the result in a variable place, with the city name in the brackets.

    • You then check if place is empty using an if place is None clause and print an error.

    • If the place isn't None, you use the second function you created to print the forecast of the selected city.

    Here is how the output can look:

    Mumbai, India
    Temperature: 32.1 °C
    Wind speed: 11.4 km/h

    Tips


    • Set timezone (or use auto) whenever you request daily data, or the request will fail.
    • Pass multiple variables as one comma-separated string, with no spaces.
    • Check current_units and daily_units in the response so you know what units you're reading.
    • Use response.raise_for_status() so failed requests raise an exception instead of passing silently.
    • Cache results instead of calling the API repeatedly for the same location.

    Weather data by Open-Meteo.com, licensed CC BY 4.0.#api #documentation #python #software #coding #development #engineering #inclusive #community
    How to get Weather-Data in Python using Open Meteo API.

  15. TL;DR: I run multiple AI agents in parallel — one researches, one implements, one reviews. The agents themselves are rarely the problem. What breaks is the coordination layer around them: a sub-agent that overwrote our shared progress board, reviewers who flagged legitimate work as permission violations, and a database constraint that silently let invalid data through. Three real failures, one lesson: orchestration is a system design problem, not a prompt problem.

    The setup


    I don't have "an AI agent." I have a team of them, and I'm the orchestrator.

    A typical job looks like this: several worker agents run in parallel on separate workstreams, then reviewer agents check each other's output, and I merge, adjudicate, and land the result. It works well — until it doesn't. And when it fails, it almost never fails the way you'd expect. The models don't hallucinate the system down. The wiring does.

    Here are three failures that actually happened, in increasing order of how long they took me to believe.

    1. The sub-agent that ate the shared state


    We had a shared task board: one element per orchestrator, tracking four parallel workstreams and the overall picture. It worked fine for weeks.

    Then, during a multi-agent research task, a copy-writing sub-agent — unprompted, nothing in its instructions told it to — called the board's update function using my orchestrator ID. The update API locates an element by ID and replaces it wholesale. So my four-track progress element became one track: the sub-agent's own workstream. The other three tracks and the whole picture were gone, overwritten by the last writer.

    Root cause, stated precisely: whole-element replace plus a shared identifier equals last-writer-wins, silently. No error. No conflict warning. The board just… changed shape.

    The fix was three rules, all now in our orchestration brief:

    1. Sub-agents never write shared state. Their instructions say explicitly: return your results to me; I store them centrally. If a prompt doesn't say this, assume the agent will improvise.
    2. Or give them their own IDs. If a sub-agent must write, it writes under its own namespaced ID (e.g., orchestrator-sub-N), never the orchestrator's.
    3. The orchestrator re-reads after every merge. After synthesizing results, I read my own board element back and check it wasn't clobbered. Trust, but verify — against your own tools.

    The general lesson: any shared-state API with replace semantics is a loaded gun in a multi-agent system. Single-writer or namespaced writes only. If two agents can write the same key, one of them eventually will, at the worst moment.

    2. The reviewers who cried wolf


    Next failure: parallel delivery with independent review. Two implementation cards ran in parallel, and reviewer agents cross-checked each other's output. Sounds rigorous. It produced a flood of "permission violation" reports.

    Every single one was a false positive.

    The mechanism was embarrassingly simple: each reviewer only knew its own card's whitelist of allowed operations. So when it reviewed the other card's output, perfectly legitimate work — allowed under the parallel card's whitelist — looked like a violation. The reviewers were doing their jobs correctly. Their jobs were scoped incorrectly.

    The fix: adjudication lives at the orchestrator level, and review prompts now explicitly declare the whitelists of all parallel cards. A reviewer can't judge what it can't see. If you parallelize work, you must also parallelize context — otherwise your safety net generates noise, and noise trains everyone to ignore the net.

    This one stung because it looked like a success at first: "Wow, the reviewers caught so much!" No. They caught nothing. They just couldn't see the whole board.

    3. The constraint that wasn't


    The third failure is my favorite, because it's not an AI failure at all — it's a database semantics failure that the multi-agent setup merely exposed.

    We had a JSONB column with a CHECK constraint like:

    CHECK ((data->>'status') IN ('active', 'archived'))

    Looks airtight. It is not. In SQL, when the key is missing — or the value is a scalar rather than an object — data->>'status' evaluates to NULL, and NULL IN (...) evaluates to UNKNOWN, not FALSE. And CHECK constraints only reject FALSE. UNKNOWN passes.

    An empty object {} sailed straight through. We proved it by inserting one.

    The fix is a single clause:

    CHECK (data->>'status' IS NOT NULL AND (data->>'status') IN ('active', 'archived'))

    Plus a contract test that tries to insert {} and asserts rejection — because the next person to touch this constraint will "simplify" it back.

    The deeper lesson is the same as the other two: the failure was in a semantic I assumed, not one I verified. I assumed CHECK meant "must match one of these." It actually means "must not be provably false." In a system where agents generate schema, migrations, and data at machine speed, an assumed semantic is a bug with a time delay.

    The pattern


    Three failures, one shape:

    FailureWhat I assumedWhat was actually trueBoard overwriteUpdates mergeUpdates replace, by IDReview false positivesReviewers see the whole jobReviewers see only their cardCHECK bypassCHECK means "must match"CHECK means "must not be false"


    None of these were intelligence failures. No agent was confused, lazy, or hallucinating. Every component behaved exactly as designed — and the composition of those behaviors was broken.

    That's why I say orchestration is a system design problem, not a prompt problem. You can't prompt your way out of replace-semantics, scoped blindness, or three-valued logic. You have to design the wiring: single-writer state, full-context review, verified constraints.

    A short checklist, if you run agent teams


    • Shared state: one writer, or namespaced IDs. Never let a worker write under the orchestrator's identity.
    • After every merge, read your own state back. Clobbering is silent; the only defense is a re-read.
    • Reviewers need the whole board. Declare every parallel card's whitelist in every review prompt, and adjudicate at the orchestrator level.
    • Treat every constraint as suspect until tested with the degenerate input. For JSONB: {}, missing keys, scalars. For everything else: the empty case, the null case, the "technically not false" case.
    • Pin the fix in a test, not a doc. Docs describe intent. Tests enforce semantics. The next agent to touch your constraint will not read your doc.


    Closing


    People ask me whether agent teams are "ready." Wrong question. The agents are ready. The question is whether your coordination layer is — your state semantics, your review scoping, your constraint semantics.

    Get those right, and the team is genuinely more than the sum of its parts. Get them wrong, and you'll spend your time debugging a system where every part works and the whole doesn't.

    The agents were fine. The wiring wasn't.#ai #agents #showdev #devops #software #coding #development #engineering #inclusive #community
    I Coordinate a Team of AI Agents. Here's What Actually Breaks

  16. Movilizaciones en la Cdmx | Marchas y concentraciones previstas para este viernes

    La agenda contempla protestas sindicales, estudiantiles y vecinales en distintas alcaldías de la Ciudad de México, con posibles afectaciones viales en zonas del Centro, Coyoacán, Tlalpan y otras demarcaciones. Las actividades incluyen demandas laborales, educativas, sanitarias y de justicia.

    Por Fausto Hernández | Reportero                                                       

    Las movilizaciones previstas para este viernes 23 de octubre en la Ciudad de México incluyen protestas de trabajadores de la salud, estudiantes universitarios, vecinos y organizaciones sociales, con actividades programadas desde las 07:00 horas y posibles afectaciones a la circulación.

    Las concentraciones se distribuirán en alcaldías como Cuauhtémoc, Coyoacán, Xochimilco, Tlalpan, Benito Juárez, Álvaro Obregón e Iztapalapa. Entre las principales demandas figuran mejoras salariales, abasto de medicamentos, seguridad escolar, justicia y atención a problemas sanitarios.

    La agenda proporcionada contempla también una marcha desde el Ángel de la Independencia hacia el Zócalo capitalino, además de protestas frente a instalaciones educativas, oficinas gubernamentales y tribunales. Los aforos son estimaciones y la realización de cierres viales dependerá del desarrollo de cada actividad.

    Marcha de trabajadores del IMSS

    A las 07:00 horas, integrantes de la Sección XXXII de la Ciudad de México del Sindicato Nacional de Trabajadores del Seguro Social (SNTSS) tienen prevista una caminata en silencio desde el Ángel de la Independencia hacia el Zócalo capitalino.

    La actividad se realizará en el marco del Día de la Médica y el Médico, bajo la consigna “Mucho decimos, nada escuchan”. El contingente, con un aforo estimado de 400 personas, exigirá un incremento de 10% al salario tabular, la convocatoria a un Congreso Nacional Extraordinario y un esquema de jubilación mutualista con beneficios de la Ley del Seguro Social de 1973.

    Entre sus demandas también figuran el abasto integral de medicamentos y material médico, la adquisición de tomógrafos y ultrasonidos, la realización de análisis clínicos y la contratación de más personal médico, de enfermería y especialistas. La agenda no descarta la incorporación de otras secciones sindicales.

    Protestas por educación y seguridad escolar

    A las 11:00 horas, estudiantes de la Universidad Nacional Autónoma de México (UNAM), pertenecientes a la Escuela Nacional Preparatoria número 8 Miguel E. Schulz, prevén concentrarse en el plantel ubicado en la alcaldía Álvaro Obregón.

    La comunidad estudiantil, con un aforo estimado de 70 personas, exige la destitución de profesores señalados por presunto acoso sexual, agresiones y conductas abusivas. También solicita garantías de seguridad dentro y en los alrededores de la escuela, así como una investigación sobre las denuncias presentadas.

    Al mediodía, estudiantes de la Universidad Autónoma Metropolitana (UAM), unidad Xochimilco, prevén movilizarse desde las instalaciones ubicadas en Calzada del Hueso 1100, en Coyoacán, hacia la Rectoría General, en Tlalpan.

    Con una asistencia estimada de 100 personas, demandan el cumplimiento de su pliego petitorio, que incluye el funcionamiento pleno de la biblioteca, insumos para los sanitarios, internet libre, mantenimiento de instalaciones deportivas y la desprivatización del Centro de Lenguas Extranjeras.

    También a las 11:00 horas, integrantes del Sindicato de la Unión de Trabajadores del Instituto de Educación Media Superior de la Ciudad de México (SUTIEMS) acudirán a la Subsecretaría de Educación Media Superior, ubicada en avenida Universidad 1200, colonia Xoco, alcaldía Benito Juárez.

    El sindicato prevé reunir a 200 personas para defender el modelo de educación pública, gratuita, laica y crítica del Instituto de Educación Media Superior, así como exigir respeto al contrato colectivo de trabajo.

    Por su parte, estudiantes de la Universidad Pedagógica Nacional (UPN) tienen prevista una concentración a las 12:00 horas en la unidad Ajusco, ubicada en la carretera Picacho-Ajusco 24, alcaldía Tlalpan.

    El grupo, con un aforo estimado de 45 personas, exige diálogo con las autoridades, cumplimiento de acuerdos pendientes, solución a deficiencias administrativas y de infraestructura, y medidas de seguridad y atención a denuncias de violencia de género. La agenda advierte que podrían bloquear vialidades.

    Exigen justicia y atención sanitaria

    A las 10:00 horas, una víctima de presunto abuso sexual tiene prevista una concentración frente al Tribunal Superior de Justicia de la Ciudad de México, ubicado en avenida Niños Héroes 119, colonia Doctores, alcaldía Cuauhtémoc.

    La persona exige una revisión imparcial de la resolución de no vinculación a proceso y del sobreseimiento relacionado con el caso. Se estima la participación de 30 personas y no se descarta la asistencia de colectivas feministas.

    A las 11:00 horas, el Comité Ejecutivo Nacional de la Coalición Nacional de Trabajadores de Salud prevé realizar la protesta artístico-cultural “En México no hay justicia para la salud”, frente al Tribunal Federal de Conciliación y Arbitraje, en avenida Diagonal 20 de Noviembre 275, colonia Obrera.

    La movilización, con un aforo estimado de 200 personas, busca que se revisen las condiciones laborales del personal sanitario, se garantice el suministro de medicamentos, se transparenten las compras públicas y se investiguen posibles irregularidades. También exige mantenimiento hospitalario y evaluación de las políticas de salud.

    A las 13:00 horas, integrantes de la colectiva Minerva se concentrarán en los juzgados penales de la Ciudad de México, en Doctor Lavista 114, colonia Doctores. Con una asistencia estimada de 15 personas, exigirán justicia para una mujer víctima de violencia familiar y un juicio conforme a la ley para el presunto responsable.

    Reclamos vecinales y derechos laborales

    Desde las 09:00 horas, vecinos de Santa María Tepepan, en Xochimilco, tienen previstas concentraciones en los cruces de avenida Guadalupe I. Ramírez con Nicolás Bravo y de 5 de Mayo con 16 de Septiembre.

    Los manifestantes, con un aforo estimado de 50 personas, exigen una revisión sanitaria y la clausura de la empresa Frío de Nepal, S.A. de C.V., dedicada al almacenamiento y conservación de productos perecederos. Denuncian malos olores, condiciones insalubres y proliferación de moscas que, aseguran, afectan viviendas y comercios cercanos. Se advierten posibles afectaciones viales.

    A las 16:00 horas, integrantes de la Unión General de Trabajadores de México, Sección 26, acudirán a las oficinas de la Secretaría de Gobierno, ubicadas en Lucas Alamán 122, colonia Tránsito, alcaldía Cuauhtémoc.

    El contingente, con un aforo previsto de 180 personas, defenderá sus derechos laborales y exigirá un salario justo e insumos suficientes para ofrecer servicios de calidad. –sn–

    Marcha de mujres | @SociedadN_

    ¡Conéctate con Sociedad Noticias! Suscríbete a nuestro canal de YouTube y activa las notificaciones, o bien, síguenos en las redes sociales: Facebook, Twitter e Instagram.

    También, te invitamos a que te sumes a nuestro canal de información en tiempo real a través de Telegram.

    #NoticiasMX #PeriodismoParaTi #PeriodismoParaTiSociedadNoticias #AbastoDeMedicamentos #ÁlvaroObregón #BenitoJuárez #bloqueosViales #Cdmx #Coyoacán #Cuauhtémoc #IMSS #Información #InformaciónMéxico #Iztapalapa #Justicia #manifestacionesCdmx #marchasHoyCDMX #México #Morena #movilizacionesSociales #noticia #noticias #NoticiasMéxico #NoticiasSociedad #seguridadEscolar #SindicatoNacionalDeTrabajadoresDelSeguroSocial #SN #Sociedad #SociedadNoticias #SociedadNoticiasCom #sociedadNoticias #SociedadNoticiasCom #Tlalpan #trabajadoresDeLaSalud #tráficoCdmx #UAMXochimilco #UNAM #UniversidadPedagógicaNacional #Xochimilco
  17. Causa Audi: Steht Audi bzw. der Volkswagen-Konzern eigentlich noch auf dem Boden der freiheitlich-demokratischen Grundordnung, wenn offen Wahlkampfhilfe für einen erwießenermaßen antidemokratischen US-Präsidenten geleistet wird?

    Wie steht das Land Niedersachsen als Großaktionär zu der Causa? Wurde das besprochen, liebe SPD? Waren die Gewerkschaften da einbezogen? Und zu welchen Bedingungen werden die Arbeiter in den USA dann bezahlt?

    zeit.de/wirtschaft/2026-10/aud

    #deutschland #bundesregierung #bundestag #politik #cdu #csu #spd #gruene #linke @Bundesregierung @bundestag @cdu @spd @GrueneBundestag @dielinke #merz #dampfplauderermaggus #soeder #niedersachsen #audi #volkswagen #vw #trump #trumpeltier

  18. Causal impacts of multimodal network expansions on urban mobility: Evidence from a fast-growing megacity sciencedirect.com/science/arti

  19. Por causa dos estudos, faz muitas semanas que eu não assisto filme nem série de ficção. Acho que vou fazer isso hoje porque estudar Direto Constitucional, Direito Administrativo, Ciência Política, Processo Legislativo e Comunicação Social não vai me ajudar com a ansiedade eleitoral, já que tá tudo relacionado. 😂 🤣

  20. hmm causa animal mas nao tem nada disso no plano de governo dele

  21. Em causa três adultos, uma criança e um bebé, sendo três casos importados, sem relação entre si, e que correspondem a pessoas que viajaram recentemente para um país com elevada incidência de sarampo.

    publico.pt/2026/10/22/sociedad

  22. Em causa está a restrição da circulação de camiões na estrada de acesso ao aterro de Sobrado em 2020. Paulo Esteves Ferreira e José Manuel Ribeiro vão recorrer da decisão.

    publico.pt/2026/10/22/politica

  23. @lilnickmuller
    Just causally hiring hit men in 2018

    Here lies Jeff. Died normal. Don't ask questions.

    #JaredKushner #bribes #corruptgovernment #FollowTheMoney #LockHimUp

  24. Justicia argentina desestima causa contra Milei y su hermana por supuesta criptoestafa

    La justicia argentina desestimó este viernes la causa contra el presidente Javier Milei y su hermana Karina, secretaria general de la Presidencia, por una presunta estafa vinculada al lanzamiento de la criptomoneda $LIBRA en 2025. En febrero de ese año, Milei difundió en X un proyecto de criptomoneda, llamada $LIBRA, y borró el tuit poco […]
    The post Justicia argentina desestima causa contra Milei y su hermana por supuesta criptoestafa appeared first on CR Hoy.

    #Gobierno #KarinaMilei #Milei #Mundo #Política

    crhoy.com/justicia-argentina-d

Share on Mastodon

Enter the server where you have an account.