@matigo Maybe GET /users/mute and GET /users/silence to go with the POST and DELETE flavors?
These are my bullets:
- Bullet one
- Bullet two
Also a list.
- Listings
- Some stuff
- This should wrap lines a bit. Just a smidge. Not too much. You know? OK, maybe more than a bit. Maybe a lottabit. That's a word, right?
#MacchiatoNoise
@matigo Should muted posts continue to come to me, or are those gagged server-side? (I'm not clear on the expected API behavior.)
@matigo Silencing takes a noticeable amount of time to trigger. The embedded account says it's been silenced, but the posts still get sent down.
Muting does send the client the posts, which I think is a good move; I plan to cloak them but let people look if they want.
@matigo No, I was totally reloading the timeline (I'm not storing anything locally, basically), and was getting posts with the youMuted stuff set to yes! It seems like it takes a while before it starts actually suppressing the posts. I'm not sure if it suppressed mutes at all, since I tested mute and silence on the same person.
So, hmm, can I get a list of folks I've muted/silenced to undo that? >.>
@jws Oh wait. Silence just takes a while to take effect server-side. And then the user is dead to you, and the backend doesn't even send silenced posts down.
Mute and silence don't actually do very much without client support. Which probably won't be in the next release.