Earlier quoted context omitted.
Not in an economy that demands rapid, scalable, and infinite growth.
[flagged]
Doesn't capitalism demand infinite growth? If you don't have >= 2% YoY, the market thinks you're dead
So this guy is now S3. All of S3
301–310 of 522 posts
Re: So this guy is now S3. All of S3
#302Earlier quoted context omitted.
If they decide not to, then they get all the capabilities, responsibilities, and level of participation that come with not following a standard that others are expecting. You've effectively described what happens when people don't agree.
There's already a strong precedent for something like .well-known being disregarded — the ~/.config directory. It's the same idea, a special directory starting with a dot, and the objection seems to be similar, that it's awkward. In the case of the config directory it's that the storage for an app is spread between multiple directories like ~/.local/share and ~/.cache instead of one directory like ~/.vim https://wiki…
~/.config is an interesting contrast. The difference is .well-known has different producers and consumers, webmasters and web clients, respectively. Whereas the thing that uses an application's config files is the same as the thing that created it.
Re: So this guy is now S3. All of S3
#303Earlier quoted context omitted.
There's already a strong precedent for something like .well-known being disregarded — the ~/.config directory. It's the same idea, a special directory starting with a dot, and the objection seems to be similar, that it's awkward. In the case of the config directory it's that the storage for an app is spread between multiple directories like ~/.local/share and ~/.cache instead of one directory like ~/.vim https://wiki…
~/.config is an interesting contrast. The difference is .well-known has different producers and consumers, webmasters and web clients, respectively. Whereas the thing that uses an application's config files is the same as the thing that created it.
With .well-known they're sometimes different components of the same tool, like with letsencrypt. That's a good observation though. I hadn't noticed that.
Re: So this guy is now S3. All of S3
#304Earlier quoted context omitted.
Path based bucket addressing isn't supported anymore, so this must be a legacy bucket: https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-...
No, they indefinitely delayed that deprecation. It's still delayed. I bet[1] it never happens. They haven't figured out what to do with S3 VPC endpoints and buckets with dots in the name, which both to this day require path-based addressing and are both completely legitimate uses. They just stopped talking about this plan entirely and it's been years; I think it's dead. [1] If they ever actually turn off path-style a…
[deleted]
Re: So this guy is now S3. All of S3
#305Earlier quoted context omitted.
Path based bucket addressing isn't supported anymore, so this must be a legacy bucket: https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-...
The person who did it is in this thread, and apparently you are not correct. It was created yesterday: https://news.ycombinator.com/item?id=35821113 (I don't know anything about this personally, but since a lot of people are indicating an interest in this detail of the story, figured I'd try and surface that link better!)
Thanks!
Re: So this guy is now S3. All of S3
#306Here'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…
Thank you!
Re: So this guy is now S3. All of S3
#307Earlier quoted context omitted.
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.
Lol this is great.
Try making a link to your email address without knowing which email provider your audience is using and you'll understand the utility.
Re: So this guy is now S3. All of S3
#308Earlier quoted context omitted.
What about serving the challenge file from the root or a near-root of the fully qualified url? Like www.domain.com/mastodon.txt or abc.freehost.com/mastodon.txt? Maybe I'm old but what are some popular use cases for webfinger? (I'm just learning about it now)
s3 supports my-bucket.s3-us-west-2.amazonaws.com style URLs as well
In fact the path method is deprecated, but I don't know if support will ever be removed, because some (old) buckets have periods in their names, and therefore don't work with the subdomain format.
Re: So this guy is now S3. All of S3
#309Earlier quoted context omitted.
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!
You’re welcome. :)
Re: So this guy is now S3. All of S3
#310Earlier quoted context omitted.
The person who did it is in this thread, and apparently you are not correct. It was created yesterday: https://news.ycombinator.com/item?id=35821113 (I don't know anything about this personally, but since a lot of people are indicating an interest in this detail of the story, figured I'd try and surface that link better!)
Thanks!
Any time! I was curious about this too.