Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @[email protected]

  • 0 Posts
  • 560 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle
  • dan@upvote.autoTechnology@lemmy.worldCloudfare outage post mortem
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    5 hours ago

    there really isn’t much in the way of an alternative

    Bunny.net covers some of the use cases, like DNS and CDN. I think they just rolled out a WAF too.

    There’s also the “traditional” providers like AWS, Akamai, etc.

    I guess one of the appeals of Cloudflare is that it’s one provider for everything, rather than having to use a few different providers?


  • dan@upvote.autoTechnology@lemmy.worldCloudfare outage post mortem
    link
    fedilink
    English
    arrow-up
    9
    ·
    edit-2
    8 hours ago

    This can happen regardless of language.

    The actual issue is that they should be canarying changes. Push them to a small percentage of servers, and ensure nothing bad happens before pushing them more broadly. At my workplace, config changes are automatically tested on one server, then an entire rack, then an entire cluster, before fully rolling out. The rollout process watches the core logs for things like elevated HTTP 5xx errors.


  • dan@upvote.autoTechnology@lemmy.worldCloudfare outage post mortem
    link
    fedilink
    English
    arrow-up
    21
    ·
    edit-2
    8 hours ago

    Did you read the article? It wasn’t taken down by the number of bots, but by the number of columns:

    In this specific instance, the Bot Management system has a limit on the number of machine learning features that can be used at runtime. Currently that limit is set to 200, well above our current use of ~60 features. Again, the limit exists because for performance reasons we preallocate memory for the features.

    When the bad file with more than 200 features was propagated to our servers, this limit was hit — resulting in the system panicking.

    They had some code to get a list of the database columns in the schema, but it accidentally wasn’t filtering by database name. This worked fine initially because the database user only had access to one DB. When the user was granted access to another DB, it started seeing way more columns than it expected.








  • If you want to play files over SMB, you can just open the SMB mount in the file explorer and double click it. On Windows you can mount it as a network drive (like V: for videos) so even non-technical users understand it. I don’t understand how mpv is easier for that use case.

    With systems like Jellyfin and Plex, you can (and should!) turn off transcoding when streaming at home. The only times you should enable transcoding are when:

    1. You’re away from home on a slow internet connection (or your home internet has slow upload speed); or
    2. You’re streaming to a less powerful device that can’t handle the full bitrate of the video.

    Transcoding is very useful, because otherwise you’d need multiple copies of the same movie to handle different environments. Transcoding can dynamically adjust the bitrate based on the connection speed.





  • My guess would be that you’ve logged into all of the accounts in the same browser, and thus they all shared a common cookie or something similar (like LocalStorage) at some point. It’s a common tactic sites use to mark multiple accounts as being operated by the same person.




  • It was a feature built in to the web browser, providing a website, file sharing, a music player, a photo sharing tool, chat, a whiteboard, a guestbook, and some other features.

    All you needed to do was open the browser and forward a port, or let UPnP do it (since everyone still had UPnP enabled back then), and you’d get a .operaunite.com subdomain that anyone could access, which would hit the web server built into the browser.

    This was back in 2008ish, when Opera was still good (before it was converted to be Chromium-powered). A lot of people still used independent blogs back then, rather than everything being on social media, so maybe it was ahead of its time a bit.