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
- Raspberry Pi GPIO Joystick
- Three doesn't feel at home on 4G networks
- Raspberry Pi sous vide water bath
- Forwarding DNS queries to AWS VPC resolvers
- Using Overlay file system with Docker on Ubuntu
- AirPlay on Raspberry Pi the easy way
- Howto - Factory Reset iLO 4 on HP Microserver Gen8
- Connecting Docker containers between VMs with VXLAN
- Apache 2.2 on Ubuntu 14.04
Chris Swan on Forwarding DNS queries to AWS… Ramon Snir on Forwarding DNS queries to AWS… BBC Micro:Bit availa… on micro:bit Simon Hugh Grant on Surprisingly Slipshod for… Neil Fagan on Surprisingly Slipshod for…
- Why the Navy Needs Disruption Now
- The Fallacy of Real-Time Analytics in Performance Monitoring
- let’s hear it for the maintainers!
- An Eight Point Brief for LEV (Lesser Evil Voting)
- Bad Moon Rising — Welcome to the Scream Room
- BBC micro:bit as an Eddystone-URL Beacon using Espruino
- Introducing 'Sock Shop': A Cloud Native Reference Application
- Could wearing a suit harm your career?
- Life and death of a container
- mermaid - Generation of diagrams and flowcharts from text in a similar manner as markdown.
- RT @fintanr: Just 700 supporters needed for @LegoLovelace ideas.lego.com/projects/102740 << go on, get on it 1 day ago
- A point I made at London Cloudcamp years ago. Also AWS can't do a price war (supply elasticity of demand) GCP can twitter.com/sparkycollier/… 1 day ago
- RT @samcharrington: Insurance is next big market for #IoT, #ML @timoreilly. + you won't be able to opt out. via @AbeGong. #WrangleConf http… 1 day ago
- RT @nwbrux: An Eight Point Brief for LEV (Lesser Evil Voting) buff.ly/2aguJbk Noam Chomsky endorses Clinton in his own special way.… 1 day ago
- RT @swardley: Is UK Gov trying to return to pre-2010 days of IT cock-ups, massive waste, lacklustre CIOs and consultant gorging? - https://… 1 day ago