Could you pick an unassigned value from the astral plane, or something not popular in the private use block? Or even send NUL as the separator?

/

The very similarly named Medicaid might apply, though?

/

Yeah. It’s annoying and overbearing. So, typical Twitter.

Their Developer Policy [developer.twitter.com] clauses C3 and C4 do clarify the permission asking bits for me, though. So, that puts this to rest for me.

And yeah, sounds like backfeed done Indie-style needs explicit permission through opt-in.

/

Point 1 regarding permission is in an interesting gray area with Tweets. Twitter’s contracts seem to say you’d be fine backfeeding as long as you preserve their display guidelines - developers are one of the parties they sublicense content to at their discretion, as the original author agreed to.

But then their display policies throw in a parenthetical hemhaw about how you maybe need permission in some cases, with zero further elaboration.

Searching for that contradictory line led me to a summary of all I worked out [media.gn.apc.org], but no further clarity. :\

Zombie Severability Clause ?

/

Oh yes, Chicago puts the pie in “pizza pie.” And pierogis…

/

I had local post office mark a prescription package as “undeliverable address” the day it was to be delivered, only to deliver it the next day. Inscrutable.

Nah. Seems that’s a pretty common age for that to come up.

That “blocking” issue shows up elsewhere, too. You can circumvent a Twitter block by just logging out, unless the person’s tweets are protected - which would be the same as requiring auth to access an RSS feed.

/

That “waffling on” is why I didn’t pick up any podcasts for a long time. Now I’m just choosy. Sometimes topic or interviewee overcome poor production and editing; often they don’t.

Rising intonation tends to get skewered by US speakers, too. Vocal fry, I can’t say - either I never encounter it, or I don’t notice it.