home.social

#cloudfare — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #cloudfare, aggregated by home.social.

  1. #Cloudfare

    "Cloudflare CEO’s Fascist Propaganda Memory Hole

    While researching an alleged Cloudflare blackmail of Canonical, I came across CEO Matthew Prince’s Twitter statements in January 2026 about an Italian fine over Piracy Shield non-compliance.

    In a far-reaching decision, the Italian Communications Authority Agcom has fined infrastructure giant Cloudflare exactly 14,247,698.56 Euros

    Notably, Prince responded with fascist propaganda aesthetics to frame himself in a battle with grotesque 'dark' skinned Europeans."

    flyingpenguin.com/cloudflare-c

  2. #Cloudfare

    "Cloudflare CEO’s Fascist Propaganda Memory Hole

    While researching an alleged Cloudflare blackmail of Canonical, I came across CEO Matthew Prince’s Twitter statements in January 2026 about an Italian fine over Piracy Shield non-compliance.

    In a far-reaching decision, the Italian Communications Authority Agcom has fined infrastructure giant Cloudflare exactly 14,247,698.56 Euros

    Notably, Prince responded with fascist propaganda aesthetics to frame himself in a battle with grotesque 'dark' skinned Europeans."

    flyingpenguin.com/cloudflare-c

  3. #Cloudfare

    "Cloudflare CEO’s Fascist Propaganda Memory Hole

    While researching an alleged Cloudflare blackmail of Canonical, I came across CEO Matthew Prince’s Twitter statements in January 2026 about an Italian fine over Piracy Shield non-compliance.

    In a far-reaching decision, the Italian Communications Authority Agcom has fined infrastructure giant Cloudflare exactly 14,247,698.56 Euros

    Notably, Prince responded with fascist propaganda aesthetics to frame himself in a battle with grotesque 'dark' skinned Europeans."

    flyingpenguin.com/cloudflare-c

  4. #Cloudfare

    "Cloudflare CEO’s Fascist Propaganda Memory Hole

    While researching an alleged Cloudflare blackmail of Canonical, I came across CEO Matthew Prince’s Twitter statements in January 2026 about an Italian fine over Piracy Shield non-compliance.

    In a far-reaching decision, the Italian Communications Authority Agcom has fined infrastructure giant Cloudflare exactly 14,247,698.56 Euros

    Notably, Prince responded with fascist propaganda aesthetics to frame himself in a battle with grotesque 'dark' skinned Europeans."

    flyingpenguin.com/cloudflare-c

  5. «El 38% de los casos de difusión ilícita de partidos de fútbol se realiza a través de la plataforma que dirige Matthew Prince»

    Entonces, ¿todo el pollo que montan los días de fútbol para evitar sólo el 38% de la retransmisiones piratas?

    #Tebas
    #LaLiga
    #Cloudfare

    eleconomista.es/tecnologia/not

  6. «El 38% de los casos de difusión ilícita de partidos de fútbol se realiza a través de la plataforma que dirige Matthew Prince»

    Entonces, ¿todo el pollo que montan los días de fútbol para evitar sólo el 38% de la retransmisiones piratas?

    #Tebas
    #LaLiga
    #Cloudfare

    eleconomista.es/tecnologia/not

  7. «El 38% de los casos de difusión ilícita de partidos de fútbol se realiza a través de la plataforma que dirige Matthew Prince»

    Entonces, ¿todo el pollo que montan los días de fútbol para evitar sólo el 38% de la retransmisiones piratas?

    #Tebas
    #LaLiga
    #Cloudfare

    eleconomista.es/tecnologia/not

  8. «El 38% de los casos de difusión ilícita de partidos de fútbol se realiza a través de la plataforma que dirige Matthew Prince»

    Entonces, ¿todo el pollo que montan los días de fútbol para evitar sólo el 38% de la retransmisiones piratas?

    #Tebas
    #LaLiga
    #Cloudfare

    eleconomista.es/tecnologia/not

  9. Some updates on my website maintenance woes:

    Starting last July, I built a new wiki for my translations of German folk tales. And soon after I started doing so, it started to experience frequent, hours-long outages. I started to research possible causes, but eventually concluded that the primary cause were so many requests from anonymous #scraper bot networks deserpate for new scraps of data to feed into their #LLM models that the wiki simply couldn't cope. Even when I increased my hosting plan _twice_ last September, this only served to make the outages less common - not to stop them.

    In March, I drastically reduced the amount of work I did on the wiki, as it was functionally complete - I had added more than 700 folk tales to it by that stage. Sure, there are always further tales to add - I didn't stop translating those tales, after all. But now I am adding 10-20 tales per month, not 100+.

    And funnily enough, I haven't noticed any major outages for this past month - or even minor ones. I guess the scraper bot networks noticed that I don't have that much new data to steal, and largely moved on to new prey they can harass.

    So, what can we conclude from this?

    If you are maintaining a website that produces lots of new content on a regular basis, you _will_ get hammered by these scrapers. robots.txt will do nothing - these use anonymous, ever-changing IP addresses. Maybe you can thwart them with #Cloudfare or similar technologies which I haven't tried out (I am a rank beginner when it comes to website administration, to be frank).

    Otherwise you will either have to slow down the publication of new content, pay lots of money for an oversized hosting plan, or live with periodic outages until the #AIBubble bursts, and there is no longer a trillion dollar business case for scraping every website a thousand times a month.

    wiki.sunkencastles.com/wiki/Ma

  10. Some updates on my website maintenance woes:

    Starting last July, I built a new wiki for my translations of German folk tales. And soon after I started doing so, it started to experience frequent, hours-long outages. I started to research possible causes, but eventually concluded that the primary cause were so many requests from anonymous #scraper bot networks deserpate for new scraps of data to feed into their #LLM models that the wiki simply couldn't cope. Even when I increased my hosting plan _twice_ last September, this only served to make the outages less common - not to stop them.

    In March, I drastically reduced the amount of work I did on the wiki, as it was functionally complete - I had added more than 700 folk tales to it by that stage. Sure, there are always further tales to add - I didn't stop translating those tales, after all. But now I am adding 10-20 tales per month, not 100+.

    And funnily enough, I haven't noticed any major outages for this past month - or even minor ones. I guess the scraper bot networks noticed that I don't have that much new data to steal, and largely moved on to new prey they can harass.

    So, what can we conclude from this?

    If you are maintaining a website that produces lots of new content on a regular basis, you _will_ get hammered by these scrapers. robots.txt will do nothing - these use anonymous, ever-changing IP addresses. Maybe you can thwart them with #Cloudfare or similar technologies which I haven't tried out (I am a rank beginner when it comes to website administration, to be frank).

    Otherwise you will either have to slow down the publication of new content, pay lots of money for an oversized hosting plan, or live with periodic outages until the #AIBubble bursts, and there is no longer a trillion dollar business case for scraping every website a thousand times a month.

    wiki.sunkencastles.com/wiki/Ma

  11. Some updates on my website maintenance woes:

    Starting last July, I built a new wiki for my translations of German folk tales. And soon after I started doing so, it started to experience frequent, hours-long outages. I started to research possible causes, but eventually concluded that the primary cause were so many requests from anonymous #scraper bot networks deserpate for new scraps of data to feed into their #LLM models that the wiki simply couldn't cope. Even when I increased my hosting plan _twice_ last September, this only served to make the outages less common - not to stop them.

    In March, I drastically reduced the amount of work I did on the wiki, as it was functionally complete - I had added more than 700 folk tales to it by that stage. Sure, there are always further tales to add - I didn't stop translating those tales, after all. But now I am adding 10-20 tales per month, not 100+.

    And funnily enough, I haven't noticed any major outages for this past month - or even minor ones. I guess the scraper bot networks noticed that I don't have that much new data to steal, and largely moved on to new prey they can harass.

    So, what can we conclude from this?

    If you are maintaining a website that produces lots of new content on a regular basis, you _will_ get hammered by these scrapers. robots.txt will do nothing - these use anonymous, ever-changing IP addresses. Maybe you can thwart them with #Cloudfare or similar technologies which I haven't tried out (I am a rank beginner when it comes to website administration, to be frank).

    Otherwise you will either have to slow down the publication of new content, pay lots of money for an oversized hosting plan, or live with periodic outages until the #AIBubble bursts, and there is no longer a trillion dollar business case for scraping every website a thousand times a month.

    wiki.sunkencastles.com/wiki/Ma

  12. Some updates on my website maintenance woes:

    Starting last July, I built a new wiki for my translations of German folk tales. And soon after I started doing so, it started to experience frequent, hours-long outages. I started to research possible causes, but eventually concluded that the primary cause were so many requests from anonymous #scraper bot networks deserpate for new scraps of data to feed into their #LLM models that the wiki simply couldn't cope. Even when I increased my hosting plan _twice_ last September, this only served to make the outages less common - not to stop them.

    In March, I drastically reduced the amount of work I did on the wiki, as it was functionally complete - I had added more than 700 folk tales to it by that stage. Sure, there are always further tales to add - I didn't stop translating those tales, after all. But now I am adding 10-20 tales per month, not 100+.

    And funnily enough, I haven't noticed any major outages for this past month - or even minor ones. I guess the scraper bot networks noticed that I don't have that much new data to steal, and largely moved on to new prey they can harass.

    So, what can we conclude from this?

    If you are maintaining a website that produces lots of new content on a regular basis, you _will_ get hammered by these scrapers. robots.txt will do nothing - these use anonymous, ever-changing IP addresses. Maybe you can thwart them with #Cloudfare or similar technologies which I haven't tried out (I am a rank beginner when it comes to website administration, to be frank).

    Otherwise you will either have to slow down the publication of new content, pay lots of money for an oversized hosting plan, or live with periodic outages until the #AIBubble bursts, and there is no longer a trillion dollar business case for scraping every website a thousand times a month.

    wiki.sunkencastles.com/wiki/Ma

  13. Some updates on my website maintenance woes:

    Starting last July, I built a new wiki for my translations of German folk tales. And soon after I started doing so, it started to experience frequent, hours-long outages. I started to research possible causes, but eventually concluded that the primary cause were so many requests from anonymous #scraper bot networks deserpate for new scraps of data to feed into their #LLM models that the wiki simply couldn't cope. Even when I increased my hosting plan _twice_ last September, this only served to make the outages less common - not to stop them.

    In March, I drastically reduced the amount of work I did on the wiki, as it was functionally complete - I had added more than 700 folk tales to it by that stage. Sure, there are always further tales to add - I didn't stop translating those tales, after all. But now I am adding 10-20 tales per month, not 100+.

    And funnily enough, I haven't noticed any major outages for this past month - or even minor ones. I guess the scraper bot networks noticed that I don't have that much new data to steal, and largely moved on to new prey they can harass.

    So, what can we conclude from this?

    If you are maintaining a website that produces lots of new content on a regular basis, you _will_ get hammered by these scrapers. robots.txt will do nothing - these use anonymous, ever-changing IP addresses. Maybe you can thwart them with #Cloudfare or similar technologies which I haven't tried out (I am a rank beginner when it comes to website administration, to be frank).

    Otherwise you will either have to slow down the publication of new content, pay lots of money for an oversized hosting plan, or live with periodic outages until the #AIBubble bursts, and there is no longer a trillion dollar business case for scraping every website a thousand times a month.

    wiki.sunkencastles.com/wiki/Ma

  14. Radiogeek 2829 – La IA de Amazon provoca fallos en su nube

    El programa 2829 de Radiogeek, les habló de varios temas importantes. WhatsApp finalmente está trabajando en mensajes programados; Google y Apple comienzan a probar RCS encriptado en Android e iOS 26.4; Anthropic acusa a los laboratorios chinos de inteligencia artificial de explotar a Claude mientras Estados Unidos debate la exportación de chips de IA; Aquí están todos los nuevos dispositivos que Apple planea lanzar la próxima semana y por último la IA de Amazon provoca fallos en su nube.

    https://open.spotify.com/episode/5A04rFb3GZrEZzEgdG9HL8?si=550fe9a4471a4752

    Toda esta información la pueden encontrar desde nuestra web http://www.infosertec.com.ar o bien desde el canal de Telegram/Whastapp, o Instagram.

    Esperamos sus comentarios.

    #APPLE #arielmcorg #cloudfare #google #IA #infosertec #nube #openai #PODCAST #PORTADA #RADIOGEEK #tech #tecnología #whastapp
  15. @TCatInReality

    Blocked meaning racism subversion from Musk, fascism and hate.

    #cloudfare - could you block the website to everywhere but Washington?

  16. @TCatInReality

    Blocked meaning racism subversion from Musk, fascism and hate.

    - could you block the website to everywhere but Washington?

  17. @TCatInReality

    Blocked meaning racism subversion from Musk, fascism and hate.

    #cloudfare - could you block the website to everywhere but Washington?

  18. @TCatInReality

    Blocked meaning racism subversion from Musk, fascism and hate.

    #cloudfare - could you block the website to everywhere but Washington?

  19. Hmm... Koncesionářské poplatky platím proto, aby mě pak #cloudfare nevpustil na web @irozhlas

  20. Hmm... Koncesionářské poplatky platím proto, aby mě pak #cloudfare nevpustil na web @irozhlas

  21. Añado en el lío este de LaLiga: Hace unos años, una conocida ETT(Empresa de trabajo temporal), me pasó una oferta donde #LaLiga me ofrecía un puesto de "verificador de bares" por estas movidas del pirateo.

    Ahora leo noticias como esta y se están quedando sin pasta ni para contratar a gente irse a bares a ser un chivato. Al chivato le dan 50€ en vez de un contrato de un mes para hacer el mindundi.

    Hay que seguir así, los usuarios tenemos que seguir retomando el control de internet ante las zarpas de una empresa privada que está actuando por encima de España e incluso países extranjeros para censurar #Cloudfare sin obtener resultado alguno.

    Edito y aclaro: No acepté la oferta, me entró curiosidad, a más que leía dentro de la plataforma de la ETT, menos sentido tenía.

    Link archivado: archive.ph/o6Imr

    #Tebas #Internet

  22. Añado en el lío este de LaLiga: Hace unos años, una conocida ETT(Empresa de trabajo temporal), me pasó una oferta donde #LaLiga me ofrecía un puesto de "verificador de bares" por estas movidas del pirateo.

    Ahora leo noticias como esta y se están quedando sin pasta ni para contratar a gente irse a bares a ser un chivato. Al chivato le dan 50€ en vez de un contrato de un mes para hacer el mindundi.

    Hay que seguir así, los usuarios tenemos que seguir retomando el control de internet ante las zarpas de una empresa privada que está actuando por encima de España e incluso países extranjeros para censurar #Cloudfare sin obtener resultado alguno.

    Edito y aclaro: No acepté la oferta, me entró curiosidad, a más que leía dentro de la plataforma de la ETT, menos sentido tenía.

    Link archivado: archive.ph/o6Imr

    #Tebas #Internet

  23. Añado en el lío este de LaLiga: Hace unos años, una conocida ETT(Empresa de trabajo temporal), me pasó una oferta donde #LaLiga me ofrecía un puesto de "verificador de bares" por estas movidas del pirateo.

    Ahora leo noticias como esta y se están quedando sin pasta ni para contratar a gente irse a bares a ser un chivato. Al chivato le dan 50€ en vez de un contrato de un mes para hacer el mindundi.

    Hay que seguir así, los usuarios tenemos que seguir retomando el control de internet ante las zarpas de una empresa privada que está actuando por encima de España e incluso países extranjeros para censurar #Cloudfare sin obtener resultado alguno.

    Edito y aclaro: No acepté la oferta, me entró curiosidad, a más que leía dentro de la plataforma de la ETT, menos sentido tenía.

    Link archivado: archive.ph/o6Imr

    #Tebas #Internet

  24. Añado en el lío este de LaLiga: Hace unos años, una conocida ETT(Empresa de trabajo temporal), me pasó una oferta donde #LaLiga me ofrecía un puesto de "verificador de bares" por estas movidas del pirateo.

    Ahora leo noticias como esta y se están quedando sin pasta ni para contratar a gente irse a bares a ser un chivato. Al chivato le dan 50€ en vez de un contrato de un mes para hacer el mindundi.

    Hay que seguir así, los usuarios tenemos que seguir retomando el control de internet ante las zarpas de una empresa privada que está actuando por encima de España e incluso países extranjeros para censurar #Cloudfare sin obtener resultado alguno.

    Edito y aclaro: No acepté la oferta, me entró curiosidad, a más que leía dentro de la plataforma de la ETT, menos sentido tenía.

    Link archivado: archive.ph/o6Imr

    #Tebas #Internet

  25. @joseli
    Llevaba tiempo sin mirarlo y también me estaba fallando.
    Parece que por la protección anti-bot de #Cloudfare.

    Este me funciona
    https://rss-bridge.org/bridge01/?action=display&bridge=InstagramBridge&context=Username&u=nombredelacuenta&media_type=all&format=Html

    Prueba a ver.

    Se llega desde aquí
    https://rss-bridge.org/bridge01/#bridge-InstagramBridge

    Un consejo, si vas a pedir ayuda, los mensajes mejor públicos y con la etiqueta de lo que buscas. En este caso #RSS.
    Lo leerá gente interesada en el tema y es más fácil tener respuestas.

    @macosas
  26. @joseli
    Llevaba tiempo sin mirarlo y también me estaba fallando.
    Parece que por la protección anti-bot de #Cloudfare.

    Este me funciona
    https://rss-bridge.org/bridge01/?action=display&bridge=InstagramBridge&context=Username&u=nombredelacuenta&media_type=all&format=Html

    Prueba a ver.

    Se llega desde aquí
    https://rss-bridge.org/bridge01/#bridge-InstagramBridge

    Un consejo, si vas a pedir ayuda, los mensajes mejor públicos y con la etiqueta de lo que buscas. En este caso #RSS.
    Lo leerá gente interesada en el tema y es más fácil tener respuestas.

    @macosas
  27. @joseli
    Llevaba tiempo sin mirarlo y también me estaba fallando.
    Parece que por la protección anti-bot de #Cloudfare.

    Este me funciona
    https://rss-bridge.org/bridge01/?action=display&bridge=InstagramBridge&context=Username&u=nombredelacuenta&media_type=all&format=Html

    Prueba a ver.

    Se llega desde aquí
    https://rss-bridge.org/bridge01/#bridge-InstagramBridge

    Un consejo, si vas a pedir ayuda, los mensajes mejor públicos y con la etiqueta de lo que buscas. En este caso #RSS.
    Lo leerá gente interesada en el tema y es más fácil tener respuestas.

    @macosas
  28. @joseli
    Llevaba tiempo sin mirarlo y también me estaba fallando.
    Parece que por la protección anti-bot de #Cloudfare.

    Este me funciona
    https://rss-bridge.org/bridge01/?action=display&bridge=InstagramBridge&context=Username&u=nombredelacuenta&media_type=all&format=Html

    Prueba a ver.

    Se llega desde aquí
    https://rss-bridge.org/bridge01/#bridge-InstagramBridge

    Un consejo, si vas a pedir ayuda, los mensajes mejor públicos y con la etiqueta de lo que buscas. En este caso #RSS.
    Lo leerá gente interesada en el tema y es más fácil tener respuestas.

    @macosas
  29. Dass #Cloudfare rumzickt, passiert jetzt regelmäßig, scheint mir.

  30. Dass #Cloudfare rumzickt, passiert jetzt regelmäßig, scheint mir.

  31. Dass #Cloudfare rumzickt, passiert jetzt regelmäßig, scheint mir.

  32. Захотів почитати новини...
    Що, знову???
    #cloudfare

  33. #cloudfare fucking itself up every few weeks is just another reason to stop using it (and every other huge corpo)

  34. #cloudfare fucking itself up every few weeks is just another reason to stop using it (and every other huge corpo)

  35. "cloudfare" = Fahrpreis der Wolke, Wolkenkost.

    "cloudflare" = Aufflackern der Wolke, Wolkenflimmern, Wolken-Leuchtsignal.

    #cloudflare #cloudfare

  36. "cloudfare" = Fahrpreis der Wolke, Wolkenkost.

    "cloudflare" = Aufflackern der Wolke, Wolkenflimmern, Wolken-Leuchtsignal.

    #cloudflare #cloudfare

  37. #cloudfare is down yet again (in Central Europe). I wonder which #IoT devices will be in the headlines this time

  38. #cloudfare is down yet again (in Central Europe). I wonder which #IoT devices will be in the headlines this time

  39. #cloudfare is down yet again (in Central Europe). I wonder which #IoT devices will be in the headlines this time

  40. #cloudfare is down yet again (in Central Europe). I wonder which #IoT devices will be in the headlines this time

  41. #cloudfare is down yet again (in Central Europe). I wonder which #IoT devices will be in the headlines this time