There's Smithy, which tries to help design API operations around a resource in a CRUDL-like fashion - I think that's what you're getting at? https://awslabs.github.io/smithy/

There's also SOGo (https://www.sogo.nu/), which I'd be interested to see how Grommunio stacks up against that. SOGo has been pretty reliable for my personal deployments.

I also took News Literacy at Stony Brook in 2013. I think that was one of the more popular classes for students by then, especially since it allowed students to choose which gen ed humanities requirement (out of two) to satisfy that was otherwise a bit tedious to get.

Most people I know who went into the course just for credits came out with a greater appreciation for the course in general.

I see that you created an init script, but then you called systemctl. Any reason not to use systemd units?

Then one would not have the fun of writing

    #! /bin/sh
    ...
    source /lib/lsb/init-functions

and have it not work on systems where /bin/sh is (say) the Debian Almquist shell. (-:

`systemctl` works with init scripts, or the other way round?

Yep, also experiencing it here in NYC. I'm assuming it's because of the high traffic volume from the Microsoft/Github-related posts.

Site as an image: https://imgur.com/B15WzJZ

Probably licensing + pricing.

Amazon does have a Net Neutrality link on their front page - on the right sidebar for me at least.

That being said, it all just kind of feels underwhelming.

Are you logged in? It's not on the logged out page. Then again, Amazon probably doesn't care about the logged out page much anyway.

It looks pretty great - I'll definitely try it out when I have a chance!

I noticed that you mentioned the performance penalty using a file - how severe was the penalty for it?

Also, you mention that you used a single SATA disk to compare. What kind of disk was it? (SSD, HDD, other..?)

SSD was used as the backend device for the tests. If a file is used for LCFS backend, the performance will be limited by the underlying file system in which the file is hosted. LCFS is capable of working directly on top of device and can queue I/Os efficiently and avoid duplicate caching. One of the reasons for developing LCFS as a native file system was to avoid some of the disadvantages of a merged solution.

New update:

"Update at 11:35 AM PST: We have now repaired the ability to update the service health dashboard. The service updates are below. We continue to experience high error rates with S3 in US-EAST-1, which is impacting various AWS services. We are working hard at repairing S3, believe we understand root cause, and are working on implementing what we believe will remediate the issue."