Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

So this guy is now S3. All of S3

chaos.social

Post reply on HN
Print view View original

261–270 of 522 posts

Re: So this guy is now S3. All of S3

#261

Post by philsnow »

mikepurvis wrote: post #176
CydeWeys wrote: post #125

Earlier quoted context omitted.

I guess I'm not too surprised in that, unlike domain names, these aren't obviously exposed to end users, so terseness doesn't particularly matter. Verbose and descriptive is honestly better for most names.

And given that bucket names are a giant shared namespace, there's absolutely an incentive toward lots of prefixing to help ensure you get the ones you want.

> ensure you get the ones you want

Also to try to avoid having to special-case any logic in terraform etc.

Say you're working on a family of sites for tradespeople like plumber.io, electrician.io, carpenter.io, etc. A fair number of people from India have "occupational surnames" like Miller, Contractor, Builder, Sheriff, etc. Suddenly one Mr. Dev Contractor registers a bucket "contractor-dev" and you have to special-case your bucket names in your terraform.

Re: So this guy is now S3. All of S3

#262

Post by SquibblesRedux »

ShadowBanThis01 wrote: post #229
steveklabnik wrote: post #36

Earlier quoted context omitted.

Hacker News discourages "editorializing" the title, which means there's incentive to repeat what's being linked to exactly. Most of the time, it's a good thing, but in cases like this is where this falls over. (You can also see this in the other direction parent comment, for what it's worth, "Jack Dorsey's New Twitter" isn't really accurate, as far as I'm concerned. It is more informative overall, though.)

Describing or at least providing context is not editorializing. I don't know how this "discouragement" is phrased, but it should instead encourage (if not require) that titles mean something to a general audience (at least as represented by HN's users). I am routinely down-modded and even banned for merely asking for more-descriptive titles. It's anti-user, anti-community, anti-usefulness, and douchey. All we needed…

In this case, I agree something more descriptive would have been helpful. Even the comments have been mysterious, given the linked web site only returns "429 Too Many Requests".

Re: So this guy is now S3. All of S3

#263

Post by mal-2 »

rvz wrote: post #227
neoromantique wrote: post #205

Earlier quoted context omitted.

Mastodon is by design about small niche communities rather than centralised twitter alternative.

That is not the point. If someone sent any link or post that is from that Mastodon instance and it went viral, the entire instance will be sent to the ground and out for hours, making the post unavailable to be viewed. The worst part is journalists and the media have to be told that posting a link from a 'small niche community' on Mastodon will send a flood of traffic that will knock it down offline also giving the i…

It's a fair criticism but I don't feel so fatalistic. This would look a lot different if everyone was opening this post on their own home server instead of chaos.social.

Unfortunately there's no way to construct a link that references the post but opens where it belongs for you. I think there needs to be a fediverse URL protocol to solve for this, ie this HN post would link to `fedi://@jonty@chaos.social/110307532009155432`, then when people clicked it they wouldn't have to talk to chaos.social, because it would be opened at their home server.

Another option could be a 'copy link for public access' that generates a static page for the purpose of sharing widely.

Journalists and media could also run their own server which is scaled for the traffic they expect, and mirror the post there. The main problem is linking to the source of the post instead of linking to a federated representation of it.

Re: So this guy is now S3. All of S3

#266

Post by uptownfunk »

There is something really endearing about this. It takes me back to those days where we were building something new and bugs just popped up and we had fun with them, doing silly things and then fixing them. Morale was high, team was fun, we were all learning and building something new.

Re: So this guy is now S3. All of S3

#267

Post by Aeolun »

jeroenhd wrote: post #59
NavinF wrote: post #50

> 429 Too Many Requests Aight, level with me: Is every mastodon server running on a Raspberry Pi?

The server itself seems to work fine. It only seems to be this specific post that's being 429'd. I'm guessing it's some kind of anti-DDoS setup kicking in. Mastodon is also quite heavy to host, my single user instance will easily gobble up several gigabytes of memory if you let it. There are more efficient ActivityPub servers but specifically Mastodon seems to be written for running efficiently on huge servers.

Or running efficiently never maybe?

Re: So this guy is now S3. All of S3

#268

Post by Aeolun »

yreg wrote: post #240
jszymborski wrote: post #136

Earlier quoted context omitted.

This post is on the front of HN. Many a larger website have succumbed to HN's warm embrace.

Isn't HN pretty small? This post has <400 upvotes over 3 hours. There can't be 1000x that amount of lurkers can there?

I’ve seen other people that posted about the HN embrace talk about 50k extra visitors. I guess this is a single page, so 50k pageviews?

Re: So this guy is now S3. All of S3

#269

Post by jackson1442 »

mikepurvis wrote: post #176
CydeWeys wrote: post #125

Earlier quoted context omitted.

I guess I'm not too surprised in that, unlike domain names, these aren't obviously exposed to end users, so terseness doesn't particularly matter. Verbose and descriptive is honestly better for most names.

And given that bucket names are a giant shared namespace, there's absolutely an incentive toward lots of prefixing to help ensure you get the ones you want.

Yep, when writing IaC I always just give it a prefix like "$project-web" and terraform adds a long string of numbers at the end. It's going through CloudFront anyways, so no one should be referencing the bucket name directly unless they're writing to it (and writers can just do `aws s3 ls` to find the name).
Post reply on HN