7fb2adfb45bafcc01c80

I try to follow the Chicago Manual of Style, so for me it's Travis's. Generally that's the style guide used in fiction.

The Associated Press Stylebook just puts an apostrophe at the end of a proper noun ending with "s," however (although they will use an apostrophe-ess for common nouns, creating things like scissors's).

I'm still using my Galaxy S8 with only one problem: Verizon's voicemail app won't run on something this old. Every other app is fine. It figures that the only app that encourages me to upgrade is from the phone company.

Inuyasha often said he was evil and played the tough guy so he would be left alone, but he was usually compassionate and had a soft side.

I've been doing this for 30+ years and it seems like the push lately has been towards oversimplification on the user side, but at the cost of resources and hidden complexity on the backend.

As an Assembly Language programmer I'm used to programming with consideration towards resource consumption. Did using that extra register just cause a couple of extra PUSH and POP commands in the loop? What's the overhead on that?

But now some people just throw in a JavaScript framework for a single feature and don't even worry about how it works or the overhead as long as the frontend looks right.

The same is true with computing. We're abstracting containers inside of VMs on top of base operating systems which is adding so much more resource utilization to the mix (what's the carbon footprint on that?) with an extremely complex but hidden backend. Everything's great until you have to figure out why you're suddenly losing packets that pass through a virtualized router to linuxbridge or OVS to a Kubernetes pod inside a virtual machine. And if one of those processes fails along the way, BOOM! it's all gone. But that's OK; we'll just tear it down and rebuild it.

I get it. I understand the draw, and I see the benefits. IaC is awesome, and the speed with which things can be done is amazing. My concern is that I've seen a lot of people using these things who don't know what's going on under the hood, so they often make assumptions or mistakes that lead to surprises later.

I'm not sure what the answer is other than to understand what you're doing at every step of the way, and always try to choose the simplest route (but future-proofed).

Technically, each time that it is viewed it is a republication from copyright perspective. It's a digital copy that is redistributed; the original copy that was made doesn't go away when someone views it. There's not just one copy that people pass around like a library book.

Again, isn't that the site's prerogative?

I think there should at least be a recognized way to opt-out that archive.org actually follows. For years they told people to put

User-agent: ia_archiver
Disallow:

in robots.txt, but they still archived content from those sites. They refuse to publish what IP addresses they pull content down from, but that would be a trivial thing to do. They refuse to use a UserAgent that you can filter on.

If you want to be a library, be open and honest about it. There's no need to sneak around.

Like I said, I have no problems with individuals archiving it and not republishing it.

If I take a newspaper article and republish it on my site I guarantee you I will get a takedown notice. That will be especially true if I start linking to my copy as the canonical source from places like Wikipedia.

It's a fine line. Is archive.org a library (wasn't there a court case about this recently...) or are they republishing?

Either way, it doesn't matter for me any more. The pages are gone from the archive, and they won't archive any more.

Shouldn't that be the content creator's prerogative? What if the content had a significant error? What if they removed the page because of a request from someone living in the EU requested it under their laws? What if the page was edited because someone accidentally made their address and phone number public in a forum post?

how do you expect an archive to happen if they are not allowed to archive while it is still up.

I don't want them publishing their archive while it's up. If they archive but don't republish while the site exists then there's less damage.

I support the concept of archiving and screenshotting. I have my own linkwarden server set up and I use it all the time.

But I don't republish anything that I archive because that dilutes the value of the original creator.

Yes, some wikipedia editors are submitting the pages to archive.org and then linking to that instead of to the actual source.

So when you go to the Wikipedia page it takes you straight to archive.org -- that is their first stop.

It’s user-driven. Nothing would get archived in this case. And what if the content changes but the page remains up? What then? Fairly sure this is why Wikipedia uses archives.

That's a good point.

Pretty sure mainstream ad blockers won’t block a custom in-house banner. And if it has no tracking, then it doesn’t matter whether it’s on Archive or not, you’re getting paid the same, no?

Some of them do block those kinds of ads -- I've tried it out with a few. If it's at archive.org I lose the ability to report back to the sponsor that their ad was viewed 'n' times (unless, ironically, if I put a tracker in). It also means that if sponsorship changes, the main drivers of traffic like Wikipedia may not see that. It makes getting new sponsors more difficult because they want something timely for seasonal ads. Imagine sponsoring a page, but Wikipedia only links to the archived one. Your ad for gardening tools isn't reflected by one of the larger drivers of traffic until December, and nobody wants to buy gardening tools in December.

Yes, I could submit pages to archive.org as sponsorship changes if this model continues.

It was a much bigger deal when we used Google ads a decade ago, but we stopped in early 2018 because tracking was getting out of hand.

If I was submitting pages myself I'd be all for it because I could control when it happened. But there have times when I've edited a page and totally screwed it up, and archive.org just happened to grab it at that moment when the formatting was all weird or the wrong picture was loaded. I usually fix the page and forget about it until I see it on archive.org later.

I asked for pages like that to be removed, but archive.org was unresponsive until I used a DMCA takedown notice.