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

221–230 of 522 posts

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

#221

Post by jmccarthy »

bradfitz wrote: post #211

Here's the original email where I proposed .well-known: https://mailarchive.ietf.org/arch/msg/apps-discuss/1_a06NU8z... > 1) I feel that /host-meta is too casual of a name and prone to collisions. It matches /^[\w\-]+$/, which I think is a subset of a fair number of sites' usernames." ... > i.e. put something ugly and weird in there, like a semicolon, to minimize the chance that it interferes with people's existing U…

And later, how the semi became the dot: https://mailarchive.ietf.org/arch/msg/apps-discuss/j6KWTSTVC...

Fun bit of history!

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

#222

Post by eqvinox »

JdeBP wrote: post #220
eqvinox wrote: post #213

Earlier quoted context omitted.

Just FYI, that 429 was explicitly placed on the specific URL HN links to. The remainder of chaos.social is up and running perfectly fine. [Edit: already mentioned above, I just misread it.]

The aforementioned trick wouldn't work if it wasn't. But before the 429 error was put into place the entire site was affected across the board by Hacker News. See https://chaos.social/@ordnung/110312020977014678 .

Ah, yes, sorry, I misunderstood your comment. My bad.

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

#223

Post by bee_rider »

JdeBP wrote: post #189

Things to learn about the FediVerse from the 429 error: * The FediVerse is lots of WWW sites. Some are WWW-hosting companies showing off, with all of the acoutrements of high-end WWW sites, including CloudFlare protection and lots of tweaking of the back end stuff. Others are one-person sites where someone has just set up the vanilla Mastodon/Pleroma/Pixelfed/Friendica/whatever software on a cheap hosted VM somewhere…

Most of us are just browsing for interesting light reading anyway, so blocking us if they can’t serve a Hackernews worth of users seems basically… like an appropriate amount of robustness, for light reading.

Maybe the FediVerse is just not friendly to the idea of a “global top among thousands of users” rating.

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

#224

Post by JdeBP »

jonty wrote: post #204

This is the second time one of my posts has caused issues for the chaos.social admins. I am so, so sorry. The hacker news DDOS is real. Previously: https://news.ycombinator.com/item?id=34691489

The interesting thing to consider is that someone who is popular to read may well be as much of a headache for the local sysop as someone who is a frequent target for attacks. How long until they have a 'bot that just 429s all of your posts on sight, do you think? (-:

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

#225

Post by verdverm »

elijahbenizzy wrote: post #113

OK, this is a very cool method of verification for a social network but they goofed. Everyone goofs. In this thread folks being like "this is a bunch of jokers", yeah, I think they learned their lesson about rolling their own domain verification and everyone had some fun.

It's not just this incident, like not reading your own ToS to know what is in there, they seem to be sloppy

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

#227

Post by rvz »

neoromantique wrote: post #205
shawabawa3 wrote: post #154

Earlier quoted context omitted.

unfortunately this is exactly why mastodon won't work I already don't trust mastodon links because 9 times out of 10 they simply don't work. Everyone's tiny hobby server falls over when one post gets big, and obviously not everyone is going to scale their servers to support the load of a viral post that might happen once every 6 months and will be 100x their base load

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 impression to others that it is not ready for mainstream at all or even ready to onboard on tens or hundreds of millions of users, daily like Twitter.

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

#228

Post by latency-guy2 »

mal-2 wrote: post #165
shawabawa3 wrote: post #158

Earlier quoted context omitted.

> It looks like these links auto-redirect when I access them from here, but when you access them from the homeserver they are served without redirect "Works on my machine" isn't going to cut it for running a popular social network Nobodies going to go around searching for mirrors, they'll just leave and go back to twitter

[flagged]

I can't see it today. I won't remember about looking at your post tomorrow, but I will remember that your website didn't work for a few hours yesterday, so I probably will not visit again.

I don't really care how you implement your fediserve gimmick, I haven't received it. Seems like lots of people will not receive it either.

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

#229

Post by ShadowBanThis01 »

steveklabnik wrote: post #36
ShadowBanThis01 wrote: post #27

Earlier quoted context omitted.

It's ridiculous that this is not in the title.

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 here was, at least, "Bluesky Social allows domain hijacking" or whatever it's actually doing (which I don't have a grasp of, even after following the cryptic link).

Or even just "This guy is now all of S3 on Bluesky Social." But that wouldn't be as click-baity, would it?

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

#230

Post by bee_rider »

shawabawa3 wrote: post #158
mal-2 wrote: post #134

Earlier quoted context omitted.

[flagged]

> It looks like these links auto-redirect when I access them from here, but when you access them from the homeserver they are served without redirect "Works on my machine" isn't going to cut it for running a popular social network Nobodies going to go around searching for mirrors, they'll just leave and go back to twitter

They will just miss out on low-effort posts from sites with semi-technical populations, like this one. It isn’t a big loss really.
Post reply on HN