Social network modalities
The fuss last week about asymmetric follow got me thinking about communication modalities in social networks. It seems to me that this is yet another case where there’s nothing really new, just fresh perspective. Social networks appear to support the same modalities as data networks, so perhaps it’s worth looking at the old labels and seeing how this applies to emerging use cases:
The classic 1-2-1 pattern. This is what happens with instant messages (IMs), direct messages (DMs) and to an extent good old email (though the use of distribution lists fogs the picture a little there). It’s also what happens with the @name convention in microblogging or something like directed social bookmarking.
In data networks we use multicast groups, and it seems that in social networks the groups concept is the same, so when we post a link, update a status or whatever then it goes by default to a group defined by our immediate social graph (our ‘friends’), or it can be directed at a specific group.
With both unicast and multicast there are clearly ways to have some privacy, with a trade off against the broader collaboration potential. This depends to some extent on whether the defaults are private or public, and whether users normally tinker with those defaults.
This is the uncontrolled, anybody who’s listening option. There’s probably an important distinction between broadcast and public multicast, and this may well be the nub of what asymmetric follow is all about. Frankly I don’t see that much difference between pub/sub asymmetries in regular blogging and microblogging.
Filed under: e2.0 | 3 Comments
Tags: asymetric follow, broadcast, multicast, privacy, social network, unicast
Raspberry Pi Downloads
- AppSecUSA - Docker, DevOps, Security
- Raspberry Pi TV/PVR
- Raspberry Pi GPIO Joystick
- Making an image file from an SD card on Windows
- Raspberry Pi Satellite TV
- Securely accessing your home network with Raspberry Pi - Pt. 1
- Docker Networking
- Using Amazon EC2 as a web proxy
- AirPlay on Raspberry Pi the easy way
- Making OpenELEC images for Raspberry Pi
Technology Short Tak… on Connecting Docker containers b… Chris Swan on Why my X230 might be my last L… @ndy on Why my X230 might be my last L… Why my X230 might be… on An enterprise Ultrabook Why my X230 might be… on Review – Lenovo X23…
- You can be a kernel hacker!
- Keyless SSL: The Nitty Gritty Technical Details
- How CloudFlare promises SSL security—without the key
- Pranking My Roommate With Eerily Targeted Facebook Ads
- The Psychology of Color in Marketing
- Announcing Keyless SSL
- Quick Mesh Project - Experimenting with the WRTnode
- The Four Paths to SDN
- The MSRs of EC2
- Slides of my #AppSecUSA talk yesterday about Docker, DevOps and Security now with added YouTube capture wp.me/palij-Ah 14 hours ago
- RT @justincormack: "firmware development is software development with worse compilers." mjg59.dreamwidth.org/32369.html 15 hours ago
- DEN-SFO anybody around for a beer this evening? 20 hours ago
- @nmacdona yes it matters, scale out == bigger and more power once we're not shrinking. Memristor helps out for RAM (maybe even CPU cache). 1 day ago
- My #AppSecUSA presentation on Docker, DevOps and Security is now up at wp.me/palij-Ah 1 day ago