Live data from Hacker News

So this guy is now S3. All of S3

chaos.social

281–290 of 522 posts

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

#281

Earlier quoted context omitted.

How does Bluesky compare to Mastodon? (Other than letting you register S3 as your user handle)

Here's how I think about it: * ActivityPub -> AT Protocol ( https://atproto.com/ ) * Mastadon -> Bluesky ( https://blueskyweb.xyz/ ) Right now, federation is not turned on for the Bluesky instance. There are differences in both, however. I'm not going to speak about my impressions of the Mastadon vs Bluesky teams because frankly, Mastadon never really caught on with me, so they're probably biased. ('they' being my im…

Thank you for the overview!

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

#282
post #3

For those not getting the context(like me), this seems to be about the Bluesky Social( https://bsky.app/ ), a twitter alternative.

Sometimes it feels like companies fund weak competitors to discourage / drown out competition.

Microsoft funded Apple to keep another OS vendor alive, so it's not about discouragement. It's probably a lot cheaper to fund a competitor than paying the gov't and getting tagged as a recognized monopoly

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

#283

Earlier quoted context omitted.

Sometimes it feels like companies fund weak competitors to discourage / drown out competition.

Microsoft funded Apple to keep another OS vendor alive, so it's not about discouragement. It's probably a lot cheaper to fund a competitor than paying the gov't and getting tagged as a recognized monopoly

Not true at all.

https://www.zdnet.com/article/stop-the-lies-the-day-that-mic...

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

#285
post #50

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

This was both funny and ironic at the same time.

Upon clicking reply fastidiously, i got the hn 429

"Sorry, we're not able to serve your requests this quickly."

Wow.

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

#286
post #134

Earlier quoted context omitted.

Aren’t federated services grand?

[flagged]

yah that's fine, but the replication to other domains does no good for the typical user on the web who only has a link to the original URL, clicks it, sees an error page, and then clicks away

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

#287

Earlier quoted context omitted.

> I'm sure just because of its age and principals involved it's been heavily influenced by the crypto crowd. It builds off of several specifications that came from the crypto crowd. It does not use a proof of stake or proof of work blockchain, though, so depending on how you use the words "crypto" and "blockchain," it either is or is not those things.

> > I'm sure just because of its age and principals involved it's been heavily influenced by the crypto crowd. > It builds off of several specifications that came from the crypto crowd. It does not use a proof of stake or proof of work blockchain, though, so depending on how you use the words "crypto" and "blockchain," it either is or is not those things. From the protocol's FAQ docs itself: > Is ATP a blockchain? >…

Yes. I agree with the FAQ. But I have heard decent arguments (that I disagree with) regarding what "blockchain" means by people I respect, and so I want to be respectful of that.

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

#288
post #240

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 can provide some statistics myself.

One of my blog posts was submitted to HN that had 194 points and 149 comments[1]. All dates are in UTC.

  1 - Unique visitors per day - Including spiders
  Hits       h%  Vis.     v%  Tx. Amount Data
  ------ ------ ----- ------ ----------- ----
   14439  1.49%  1148  1.19%  106.42 MiB 21/Jan/2023
   17043  1.75%  1754  1.81%  184.69 MiB 20/Jan/2023
   33560  3.45%  3267  3.37%  491.32 MiB 19/Jan/2023
   46568  4.79%  5816  6.01%  637.54 MiB 18/Jan/2023
  323797 33.32% 28928 29.88%    4.06 GiB 17/Jan/2023  
[1]: https://news.ycombinator.com/item?id=34388533

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

#289
post #134

Earlier quoted context omitted.

[flagged]

yah that's fine, but the replication to other domains does no good for the typical user on the web who only has a link to the original URL, clicks it, sees an error page, and then clicks away

I understand. In my view it will be important to have a fediverse URL protocol so that these links are not aimed at the original domain, and instead open at your home server, or in a mobile app connected to the home server.

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

#290

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.

A while back I made one with a name like "postgresbackups" and was floored to realise later it was a global name.
Post reply on HN