Open post Napili B @napili@hachyderm.io · 4mo ago Replying to @robinhouston@mathstodon.xyz <p>User cachecrab on Twitter noticed that Google has a rather unusual interpretation of the query “20% of £1k”.</p> @robinhouston@mathstodon.xyz omg that still works!
Open post Napili B @napili@hachyderm.io · 6mo ago Replying to @scalzi@mastodon.social This is how old I am: I will NEVER call the first Star Wars film "A New Hope," get your bullshit retcon away from me, it is and always shall be Star Wars, forever and ever amen @scalzi what do you call "Revenge of the Jedi"?
Open post Napili B @napili@hachyderm.io · 2d ago Replying to @xssfox@cloudisland.nz Once again looking at contract wording for things and seeing "99.9% percentage of time that the backups are performed on time and free from errors and omissions" It seems fine until you go to actually apply it. What time frame? A day, a month, a year? Let's say a month, and our backup policy includes 10 resources backed up daily. A single failed backup drops us to 99.67% That's fine, we just run a bunch of reliable backups at the end of the month to catch up? Some of our backups are continuous point in time recovery. Do these count as 1 backup or 20 billion? If the continuous backup needs to restart is that a failure? @xssfox@cloudisland.nz the difficulty defining a meaningful SLO! Does 99.9% mean one failure at random out of a thousand? Or that backups are offline for 44 minutes a month? https://en.wikipedia.org/wiki/High_availability en.wikipedia.org