joecot

I've been watching all of today's Echo announcement threads wondering the same thing. If any of these products -- with /maybe/ the exception of the earbuds -- were posted on April Fools, we'd have chuckled and moved on without a thought.

Keep reading. You can use persistent memory for the ramdisk so it'll be maintained between system reboots https://memcached.org/blog/persistent-memory/

3 pages rules are free. You need at least 2 page rules per website you want to use with Backblaze and Cloudflare, and that's for bare minimum workability.

For a commercial company paying $5-10 a month to save TBs of bandwidth via Backblaze & Cloudflare is a no brainer. It's just unfortunately not very workable for small projects. Github Pages works with Cloudflare for static sites just fine though.

Backblaze B2 + Cloudflare would be a perfect combination for hosting a static site. Unfortunately there's no way to map a Backblaze bucket to a domain, so even if you use cloudflare to point www.mydomain.com to it your files still show up at www.mydomain.com/path/to/bucket.

But it certainly works if you need to CDN a bunch of large files.

I absolutely agree with that sentiment. And if that only affected individuals, I would agree and accept that point.

The problem is that it affects the entire society. If a society needs to get information to form an opinion on something (say, breaking US Politics), and goes to Liberal or Centrist publications (New York Times, Washington Post, Wall Street Journal), the articles are behind a paywall. If they go check a Right publication (Fox News, Infowars), it's free and readily available.

When one of our biggest issues is a lack of public knowledge, it's counterproductive to make that knowledge inaccessible, when the misinformation is not.

This is one of the biggest problems with news currently.

Big breaking story about US politics? New York Times, Wall Street Journal, Washington Post all have important articles about it. You find them linked in Google News, reddit, Hacker News, and Facebook. And they're all behind paywalls.

But if you get your "news" from Fox News, Infowars, or even farther extreme sites like Stormfront.... it's free and instantly accessible. This causes some serious problems.

Can you just let people prepay a certain amount and deduct from that every month? You don't want to charge 30 cents a month, but I'd happily prepay $10-15 and have it deducted from the total every month.

If the problem is not wanting to support a bunch of small accounts, I totally get that, but if the problem is credit card fees every month, there are lots of ways to avoid that.

I'll be happy to give it a go once they put their Linux client back out.

After Hipchat died, I tried to get my company to move to Discord instead of Slack. We ended up not doing so, because Discord's TOS does not allow commercial use, only personal use.

https://discordapp.com/terms

This is likely why there are few integrations developer use in Discord as well.

Sure, it is possible that IPFS would spread out the usage across the other users, and this could still work for people bypassing Cloudflare. But there's no demonstration here of that really working. Just that Cloudflare is really great at what it does.

And yes, it's a chicken/egg scenario -- how do you prove that IPFS adoption would negate the need for CDNs, without widespread IPFS adoption? But currently this isn't some amazing Slashdot proof solution. They needed to setup 3 servers and a whole bunch of software when a single server + free CDN would've accomplished the same thing, faster and cheaper. It's presented as though CDN+IPFS is why this works so great, when really it's just CDN and IPFS just makes it more complicated.

If the goal is to learn, try out new tech, break dependence on CDNs, then this is great, but a single note in the article that this is a learning opportunity and it can be done easier without IPFS would've saved the author a lot of back and forth in the comments here.

Yes, theoretically that's the goal. Given they're showing 160GB of transfer on their servers, it doesn't seem like that's working particularly effectively. Regardless, this implementation does not demonstrate at all that IPFS would save a site from an internet hug -- just that Cloudflare can.

> If CloudFlare is running IPFS naked, then IPFS seems to be scaling.

> If CloudFlare is caching IPFS, then it is CloudFlare saving their butts.

They are caching IPFS for people who don't support IPFS. They are not caching IPFS for people who do support IPFS, and instead passing the user through to the IPFS servers.

Which means Cloudflare is indeed saving their butts, because as soon as IPFS has widespread support, this falls flat on its face. Same as traditional hosting would without a CDN. Their IPFS setup may be able to distribute the load enough to avoid an internet hug crippling it (that's part of IPFS's point), but this setup in no way demonstrates that.

Except then you still have to cover the demand from requests which bypass Cloudflare through the dnslink entry.

Essentially it's a gimmicky system which is propped up by using Cloudflare, which ultimately fails once it actually gets user adoption, in a way the tradition setup (CDN + basic or even free hosting) would not. This only works because most users don't have IPFS support currently, and if they did the servers would grind to a halt just as they would with no CDN at all.

> It's fine to check out the implementation details for interest's sake, but let's just be clear that it all could have been done with a $5 VPS.

If you're just hosting a static site, it can be done for free. You can use Github pages (or any similar free static site host) + Cloudflare for free. Getting Slackdotted, HNed, or reddit hugged will all survive just fine, for free.

So to recap:

* Use a static site, maybe with a static site generator like Hugo

* Use a static site host, which could be github pages (free), s3 (cheap), or a $5 VPS anywhere running apache or nginx

* Use a free CDN, likely Cloudflare, to handle the brunt of the bandwidth.

The IPFS is interesting but way more work currently than any of this is worth. And if people are using IPFS compatible browsers, the load is being transferred to the IPFS servers anyway, which is worse than just using a regular hosting method and Cloudflare CDN. If IPFS actually had decent adoption, the method described would fall to a crippling internet hug.

The goal of IPFS is to distribute the load (for people with IPFS browsers), and it's possible the article's loadout would do that, but given he's seeing 160GB of transfer from his servers, it certainly doesn't seem to be doing that very effectively currently. And this setup does not in any way demonstrate IPFS is ready to do that, because Cloudflare is saving his servers' butts.

I've got a metal Capital One Venture card. I've had it for about a year. It's in a metal wallet, touching other cards. I see it has some superficial scratches on the front, but none of the lettering, numbers, or mag strip has worn down at all.

Agreed on both History of Rome [1] and Revolutions[2]. Also adding on "The History of Byzantium Podcast" by Robin Pierson[3], which continues where Mike left off with The History of Rome into the Eastern Empire.

I'll throw in "The British History Podcast" by Jamie Jeffers[4] as well, which does a really good job of explaining how life is like for the common people of Britain through history, and examining the historical sources he has to work with. Not many other history media to get into the details of the Anglo-Saxon Heptarchy!

1. https://thehistoryofrome.typepad.com/ 2. https://www.revolutionspodcast.com/ 3. https://thehistoryofbyzantium.com/ 4. https://www.thebritishhistorypodcast.com/

If you're running into EOL on your chromebook, strongly consider installing Ubuntu or GalliumOS on it to get a little more mileage. https://galliumos.org/ Gallium is Xubuntu + some extra chromebook specific fixes.

I started using Gallium after ChromeOS updates had slowed down my Chromebook enough to be pretty much unusable. It gave me an extra year or so of happiness with my chromebook before I moved on. But remembering how much I liked Linux on my laptop, and didn't want to get another chromebook I would have to drop ChromeOS from within a few years, I ended up back at a Dell laptop with Ubuntu on it.

> maintaining and updating your servers

sudo apt-get update && sudo apt-get dist-upgrade

> updating the free software

sudo apt-get update && sudo apt-get dist-upgrade

> backups

We setup a cronjob that backs up the server

> recovering from backups in situations where your servers fail?

We are able to recover in a reasonable timeframe. We take occasional server snapshots, and in the case of the machine completely going dark we could spin up one of those snapshots, dist-upgrade, and apply our git / Gitlab back and be back to normal.

Your concerns are good concerns for big companies. For small companies who don't need 99.99% SLA, running git/Gitlab on your own server is tremendously more reasonable than Github's paid plans.

The important line is at the very end:

> At launch, Aurora Multi-Master supports two node clusters in a single Region. Support for more writer nodes and placement of writers in multiple Regions is planned for future releases.

Great to see more high availability options, but yet again it's just in the same region. When we see the East region go down entirely more often than single availability zones. At least this time they mention that limitation in the announcement and an intention to fix it later. In the mean time I'll stick to our multi-region Galera setup.

We use Gitlab for work because the self-hosted version is free. For small companies Github is a pretty steep unnecessary expense, and we appreciate control over our own servers. Unless Github makes a self-hosted version there isn't really a comparison for us.

To me Github is about the community. Lots of open source software and forks of that software, you can put your profile on your resume. Gitlab has more features and self-hosting; Github has a coding social network.

Sure, I wish web servers had better options for this. If you're trying to do it on the web server level it seems like the current solution is a regex with your list of approved origins vs the origin header, and then setting Access-Control-Allow-Origin to the matching one. But the current examples, showing just setting the header multiple times, will lead devs down the garden path. Unless I'm missing something, which I very much hope I am.

I'm a little confused by the examples for Access-Control-Allow-Origin:

> Access-Control-Allow-Origin: http://www.one.site.com

> Access-Control-Allow-Origin: http://www.two.site.com

And in the examples setting both. Because in my experience you cannot set multiple [1]. Lots of people instead set it to * which is both bad and restricts use of other request options (such as withCredentials). It looks like the current working solution is to use regexes to return the right domain [2], but I'm currently having trouble getting that to work, so if there's some better solution that works for people I'd love to hear it.

1. https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Error... 2. https://stackoverflow.com/questions/1653308/access-control-a...

Your "article" reads like four or five separate blog or facebook posts scrunched together with no rhyme or reason. And it has the setup of a clickbait article, luring you in with a question, going on about a bunch of stuff not related to it at all, and then finally approaching the question at the very end but never _really_explaining it. Complete with a link to an unrelated software project and a separate link to donate to you (and we're donating for ... what? A VR input method you didn't really explain and has nothing to do with the headline?)

As a blog post for a random tech friend people follow, sure, that's fine. But I don't understand why this was posted to hacker news, and I don't understand why people voted it up.

Using triangulation to track a single person is one thing. Using it to track a million would be incredibly tedious. Whereas getting a list of everyone who got off at specific stations in specific timeframes is likely a single SQL query.

Because FreeDOS is the easiest and lightest OS to put on, since it doesn't even have a graphical interface. It sounds like they literally put the most basic OS possible on so they can sell it and claim to Microsoft the person won't turn around and pirate Windows immediately.

If they actually wanted them to use an OS that's not Windows, they'd preinstall Linux on it. But that's not the point.

Given the office makeup others have described (small startups and freelancers), and the networking events, it might give them an opportunity to convince their neighbors to host with them. Probably not entirely worth it, but if you need office space anyway, that is a slight marketing advantage. And given that GoDaddy hosting is really just reselling AWS servers, they need all the help they can get.

> Firefox is available on all platforms (including Chrome OS via the Android or Linux app)

Maybe this is a viable solution on brand new chromebooks, but on my Acer R11 both Android apps and Linux containers run pretty poorly. I use an Android app as my password tool just fine, but trying Firefox was a rather poor experience. And the linux container just dogs trying to do anything.

I have Ubuntu loaded on via crouton (to use tools like GIMP or actual VLC), but if chrome gets rid of ad blocking that removes much of the point of ChromeOS for me entirely.

Dany has shown a pattern of burning her enemies. Her enemies. Those that betray her, enemies in the field who don't bend the knee. Yet every time the thought of killing innocents comes up, she's gone extremely out of her way to avoid it. She kept her dragons locked up for years because they killed a single child.

There was plenty of development to have her destroy the Red Keep, and the horrifying thing would've been that she did so even though Cersei had filled it with innocent people. There was plenty of development to have her destroy the Lannister soldiers in the streets, leaving 0 quarter to the surrendering army.

There was no development to have her burn every inch of King's Landing and destroy all the people who lived there. There was no motive (Cersei pissed her off, but none of those people even liked Cersei), there was no benefit (none of those people would've cared who the Monarch was), there was no development leading to her personality cracking (your advisers deciding you're crazy and your nephew not kissing you right now just isn't enough to make you commit genocide).

That the ending the book is shooting for, almost certainly. D&D didn't earn it. Since they didn't earn it, they'd have been better off going with something else.

I agree that D&D are plotters now. The real problem is that they were panters for every season up to these last 2. They'd look at book characters and think "not that important" and leave them out, or wildly change events from the books to put out something that seemed more dramatic.

But like a kid who partied too hard senior year and found out his final project is due in a week, they seem to have woken up one day and realized they'd moved way, way too far from the source material, and then just jerked the wheel to steer it back in a straight line towards the intended book ending. Characters who've developed differently in the show than in the books? Whiplashed back to the book versions. The Night King taken down in a single episode, with no real understanding of what he was trying to do, or what any of it really meant. Dany destroying all of King's Landing, but instead of a culmination of increasingly morally grey choices as she takes the throne from a loved leader, she's murdering civilians who don't even like Cersei because a bunch of dudes kept saying she was crazy (or something).

Frankly I'd have preferred they just made up some hollywood ending that vaguely fit the direction they'd brought the show, instead of giving us all whiplash.

OK, that wasn't in the original "Exciting updates coming to your Mailchimp account" email. That appears to be from today in the "Updates to your Mailchimp account" email from Mailteam Legal. I'm guessing someone from legal saw that original email and puckered a bit, and drafted this clarification.