Tag: social networking

Posted on
by

Popped over to Twitter to delete the last handful of posts I left there when I deleted most of them back in December. Decided to leave two for now, though I might still delete them before the new TOS takes effect.

Oct 2008:

If only the super high-tech jet fighters had identified, clarified & classified, they’d have seen the attack for what it really was.

Nov 2022:

Weird, it’s almost like the needs of a “town square” for people to communicate and exchange ideas aren’t compatible with the incentives for a single for-profit entity to maintain it.

Posted on
by

I think there’s been a lot of talking past each other on privacy lately because there are so many layers to it.

Google or Dropbox keeping your cloud files from showing up on someone else’s drive or a public share is one layer. Keeping your data from leaking in a data breach is another. Protecting messages in transit from your device to their service. Google and Meta (Facebook, Instagram, and now Threads) are good at those.

But then there’s ensuring that Google or Meta doesn’t misuse it themselves, or sell it to someone who will.

And, well, to put it mildly, they’re not so big on that aspect!

Continue reading →

Posted on
by

Twitter Blue is what happens when you start treating a tool as a status symbol, so you throw the tools away and start selling gold-plated hammers made out of thin plastic.

As anticipated, they’re getting rid of “legacy” verification in favor of charging people $8/month for the privilege of having a blue checkmark next to their name.

Not that verification was perfect before, but most of the complaints I heard prior to the enmuskification were “wait, that person got verified but this person didn’t?”…essentially treating it as a status symbol, indicating who’s worthy of being verified, rather than one tool in the toolbox to indicate that the account really does belong to who it says it does.

Posted on
by

Not that I’ve been particularly active on Twitter for quite a while now, but the way things have gotten, especially under its new owner, I decided it was finally time to go. I haven’t deleted my main account (yet), but I’ve deleted most of my tweet history, and the accounts I used for side projects, and I don’t plan on returning.

Mastodon has filled Twitter’s niche for me over the last few years (obviously different people have different use cases, so it may not fit yours), and you can still find me there at @KelsonV@Wandering.shop.

As for the archive, I’m slowly going through and looking for threads (and occasional single posts) that I think are worth keeping, importing them where they seem to fit best on this website, whether on the blog or another section.

It may be time to do the same with Facebook and Instagram* too. I haven’t been active on either of them in ages, and I’d rather own my data IndieWeb style than wait for Meta to go the way of LiveJournal.

*I’ve already trimmed a lot of my Instagram history.

Posted on
by

The Twitter-to-Mastodon migration is like going from beta testing the Fediverse to production. Just like a public beta always turns up issues that were missed during development, when going to production you suddenly have a *huge* pool of new users who are going to use the system in ways you didn’t anticipate and haven’t already accustomed themselves to its quirks.

And that turns up a lot more things you need to fix!

Some thoughts on features/user experience for Mastodon and other Fediverse software, based on usage and discussions I’ve seen lately:

1. Missing replies aren’t just an inconvenience, they’re a big problem. Instances really do need to reach out and check for additional replies when someone views a post. I’m not sure how to balance the extra network traffic. Maybe just have a manual “check for more replies” button.

2. Quoting is better than screenshotting. I can read quotes on any size screen. So can screen readers.

3. Lack of quoting hasn’t prevented flame wars or dogpiling, and it there’s no indication it reduced them either. If you don’t want to embed an entire post, at least generate a preview like you would to a website with suitable metadata. And let any third-party clients know they can fetch the message themselves and not hand it off to the web browser.

4. If you really want to keep some friction in the quoting process, don’t add a button, but add the preview/embed on display.

5. Link previews should be generated and displayed during composition, without interrupting typing. Whether the preview gets federated along with the post or re-generated at the destination is another debate.

6. User discovery on third party clients needs work, and autocompletion really needs to be part of the composition UI.

7. Remote interactions on posts that aren’t in the app *really* need work.

8. Basic interactions (profile, follow, like, boost, reply) should Just Work(tm) between different federated software, even if they don’t recognize all the same post types or display them nicely. You can always fall back to displaying a link to the source, like Mastodon does with Article types.

9. Mastodon ought to at least *try* to display Articles as long as the formatting isn’t too complex or the length too long.

10. Mastodon’s “Your admin can read your DMs” notice should make it clear that *most* messaging software has this issue, not just Mastodon.

11. Federated hashtag searching is also more important than the inconvenience I used to think it was.

12. I’ve seen several mentions of the need for local-only posts (which some platforms have) and mutual-followers-only posts, and I totally agree with both.

13. (Added 1/23/23) I want to be able to bookmark profiles, so I can mark people/groups that I want to occasionally interact with, but don’t want to follow all the time – but when I do want to look them up or mention them, I can be sure I got the name right.