Notices by made out of flesh or wood (nightpool@cybre.space), page 18

@HTHR that's an xkcd quote

@ajdunevent very few people are saying that email is a relic because they *want* it to be a relic—they're just being practical.

noone under the age of 30 uses email for anything—except if they have a white collar job, in which case they use it solely for work.

@chr everyone loves his beats

@doggeaux really just some stunning posts august. keep up the good work.

@pea wow, I HATE this

@bunnysay_ebooks @gargron if you rate limit by hour, the spam bots will just follow exactly that many, every hour, without stopping until they're caught, and it'll probably be just as bad.

@darius @puckipedia i don't think the reason people have problems with crossposters is because they think non-mastodon content is wrong. i think people have problems with crossposters because they're non-interactive—people turn them on and then go back to twitter.

they're not posts made by "real users", they're posts that have nothing to do with this network, reflections of people who half the time don't even know they're being cross-posted.

@darius @puckipedia

ultimately—i can't read anyone's mind. Maybe mastodon could be a good feed reader. so far https://bots.tinysubversions.com/u/nightpool has been pretty disappointing, although i think part of that is tumblr's lackluster RSS feeds. I don't really think feed readers are what people want out of it, but maybe they are. people seem to be annoyed enough at cross-posters that it doesn't seem obvious that "add more types of even less interactive cross-posters" is going to have a good reception.

@darius @puckipedia

right now the way reading Weird content in mastodon works is that *mastodon* will try to convert it into a Note (in this case, that would work pretty well for RSS—it would show title and link).

i think it's also going to be useful if mastodon let the *sender* specify a "fallback" format, but right now that doesn't exist (and it's maybe hard to see what AS property we should use for that, we might want to invent one)

@darius mastodon supports converting articles into notes but I don't know a good way in the spec to have two representations for the SAME object.

@darius like, broadly, having multiple content types/representation in a single Object

why is it a bad idea to care about software versions, rather then feature support? because that way lies Mozilla/5.0 (Linux; Android 8.1.0;) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Mobile Safari/537.36

@darius @jalcine @sivy @pixeldev

not sure how that fits into the current spec though, since it only seems to account for language-tagged values, not contentType ones. (except for the source property, but it feels weird to use that here)

@darius @jalcine @sivy @pixeldev

i think that's a really bad idea. i would be much more happy trying to do something like contentMap'ing into plain text and html representations

@gaditb the former but damn now i'm thinkin about the latter