@pasture @Nonetrix Oh shoot is that the source who keeps leaking bad stuff about #Trump to the #NewYorkTimes and #BuzzFeed?
I know a guy that knows a guy that knows a guy that knows a guy that knows a guy that knows a guy that knows a guy that knows a guy that knows a guy that knows a guy that knows a guy that knows a guy that knows a guy that knows a guy that knows a guy that knows a guy that knows a guy that knows a guy that knows a guy that knows a guy that knows a guy
go follow @blitzed
Re A police officer’s shield is covered...they’re still standing in front of the courthouse. More rioters have gathered https://twitter.com/ShelbyTalcott/status/1287322365706133504
--
Full-List of bots: https://joejoe.github.io/mastodon
NBA, Nike, Apple Pressured To Distance Themselves From China https://www.oann.com/nba-nike-apple-pressured-to-distance-themselves-from-china/ https://twitter.com/OANN/status/1287472225503731712 #News #China
--
Full-List of bots: https://joejoe.github.io/mastodon
@shpuld why not, it works for me
@realcaseyrollins right. Once you've built the group infrastructure, creating UI candy to make certain use cases (e.g. DM, followers-only) more accessible would be straightforward. But having already implemented the special cases independently, retrofitting groups into the standard, in a way that's compatible with existing servers and clients, seems to be quite a pain.
@khird Or DMs would just be two-person, invite-only groups. Then you could name your chat, like I do with my brother in #Facebook #Messenger.
@realcaseyrollins I think this is backwards actually. Groups should've been the underlying addressing mechanism, with DM conversations (a group of two people) and follower-only posts (a group where only the admin has send privileges) as special cases.
I've moved over to @realcaseyrollins for my private account
This is literally just here to archive my old posts now