Christopher Schmidt
Over the years, I made a handful of maps of various things in Cambridge; I have collected some, but not all of them, on this page about housing things in Cambridge.
This includes things like maps of where you could legally build a fourplex (short answer: not many places!); the distribution of tax paid per parcel (Kendall Square pays a lot!) and more.
Christopher Schmidt
Fun fact: sharing this link on Mastodon caused my server to serve 112,772,802 bytes of data, in 430 requests, over the 60 seconds after I posted it (>7 r/s). Not because humans wanted them, but because of the LinkFetchWorker, which kicks off 1-60 seconds after Mastodon indexes a post (and possibly before it's ever seen by a human).
Every Mastodon instance fetches and stores their own local copy of my 750kb preview image.
(I was inspired by to look by @jwz's post: https://mastodon.social/@jwz/109411593248255294.)
Alex Gleason
Jeff Kaufman
@tw @crschmidt @cshabsin link preview bots all ignore robots.txt, so mastodon is at least following precedent here.
Except that I think Mastodon's implementation is wrong: on a centralized network the preview is created at the 'request' of the person sharing, so robots.txt doesn't apply. But here it's created fully automatically, so it really should apply. The fix would be to capture the site at sharing time and send it along in the post, which is also more efficient (though prone to abuse?)
Christopher Schmidt
@jefftk @tw @cshabsin yeah, the prone to abuse and "hard to standardize across all implementations" are the reasons it was rejected in 2017, and has languished as an untouched feature request since 2020 (respectively). Time to rethink that. (I don't love that a single implementation is 95% of the fediverse, but it is; standardization is frankly secondary to making sure the core implementation works well.
Christopher Schmidt
@cshabsin Don't worry! I just confirmed that Mastodon doesn't respect robots.txt for any of these fetches, so even if it's added to robots.txt, it will have no effect!
Tim W
@crschmidt @cshabsin that definitely seems ... inappropriate.
Chris Shabsin
@crschmidt well, this sounds like a p0 bug. Mastodon is going into robots.txt on many servers once this gets noticed widely.
Alex Gleason
@kroner @crschmidt @tw @cshabsin @jefftk Just use custom Object types. Most servers will drop them if they don’t understand.
kroner
sj_zero
Pater Snape FSSP
Alex Gleason
@PaterSnape @jefftk @crschmidt @tw @cshabsin MIT is blocking me? Lol.
Pater Snape FSSP
@crschmidt @jefftk @tw @cshabsin
There are three people who answered to your post and didn't show up on the public thread of your instance. So I think they are blocked.
Jeff Kaufman
@PaterSnape @crschmidt @tw @cshabsin link to one of the posts that seem blocked?
Pater Snape FSSP
@crschmidt @jefftk @tw @cshabsin
Funny how everybody who pointed out the 95% figure is wrong was blocked in advance.
Christopher Schmidt
@PaterSnape @jefftk @tw @cshabsin I don't really know what you mean here?
Specifically, what I mean is "95% of the servers making these requests are Mastodon servers, so this is largely a Mastodon problem." My understanding is Mastodon is also the home to the overwhelming majority of the Fediverse _users_ (even though it's only bare majority of _servers_). My wording choice was poor, but I don't have anyone intentionally blocked?
pawlicker
Pater Snape FSSP
@crschmidt @jefftk @tw @cshabsin
I don't appear there either, so I don't know what that means.
Development Testing
@alex @PaterSnape No, not MIT; better.boston is (likely because they took the list from Fediblock as a starting point for blocking instances.) https://joinfediverse.wiki/FediBlock
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.