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
- Making an image file from an SD card on Windows
- AirPlay on Raspberry Pi the easy way
- Using Overlay file system with Docker on Ubuntu
- Raspberry Pi GPIO Joystick
- Raspberry Pi TV/PVR
- Gen8 Microservers
- Boot2Docker on Hyper-V
- Raspberry Pi Satellite TV
- Connecting Docker containers between VMs with VXLAN
- Using Amazon EC2 as a web proxy
Chris Swan on Why my X230 might be my last L… Vish on Why my X230 might be my last L… Docker Networking |… on Container Networking Tutorial Running Docker on Hy… on Boot2Docker on Hyper-V Chris Swan on Gen8 Microservers
- Web security is totally, totally broken.
- Pity the Poor Stormtroopers: Baby Bou-Bou Ambushed Them
- Cold sore virus 'treats skin cancer'
- Security and Compliance on the Google Cloud Platform
- Cryptographic Right Answers
- Organizational Debt is like Technical debt – but worse
- Multipath routing on a Raspberry Pi 2
- BMW 3.0 CSL Hommage
- TrueRNG V2
- RT @icecrime: Docker Bench for Security, nice auditing tool by @diogomonica blog.docker.com/2015/05/docker… 17 minutes ago
- RT @rj_gallagher: NSA analyst: "We are drowning in information. And yet we know nothing." firstlook.org/theintercept/2… 7 hours ago
- @jpetazzo did you see my question yesterday about building a graph of FROM imports to see how vuln image taints cascade across Docker Hub? 7 hours ago
- Great stuff from @jpetazzo "Someone said that 30% of the images on the Docker Registry contain vulnerabilities" jpetazzo.github.io/2015/05/27/doc… 7 hours ago
- I'd forgotten how thoroughly obnoxious iTunes is 11 hours ago