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
- Raspberry Pi GPIO Joystick
- Raspberry Pi TV/PVR
- Making an image file from an SD card on Windows
- AirPlay on Raspberry Pi the easy way
- Raspberry Pi Satellite TV
- Howto - fix lip sync on DivX videos
- Making OpenELEC images for Raspberry Pi
- Using Amazon EC2 as a web proxy
- Raspberry Pi Arcade
- Your own VPN in the cloud
Why my X230 might be… on An enterprise Ultrabook Why my X230 might be… on Review – Lenovo X23… Fun with Flocker | C… on Multi tier Docker apps with… Fun with Flocker | C… on Multi tier Docker apps with… Fun with Flocker | C… on Multi tier apps in Docker…
- Revisiting How We Put Together Linux Systems
- DON’T do what you love.
- What do you mean, I have to POST a PHYSICAL CHEQUE to get my gun licence?
- 71 TiB DIY NAS based on ZFS on Linux
- If programming languages were weapons
- Purely Functional Configuration Management with Nix and NixOS
- Declaratively Provision Docker Images Using Nix
- Aspiring for more Fiasco … again
- Containers as a Service (CaaS) Is the Cloud Operating System
- It's Over: The Rise & Fall Of Google Authorship For Search Results
- RT @esdaniel: Revisiting How We Put Together Linux Systems 0pointer.net/blog/revisitin… - "a reinvention how distributions work" #linux #systemd … 3 hours ago
- RT @cardmagic: Don't Do What You Love bit.ly/1qkGvjA 6 hours ago
- @justincormack yeah, Google sat they run GCE KVM VMs inside containers 18 hours ago
- Docker: present and future infoq.com/articles/docke… < my first long form article on @InfoQ 20 hours ago
- RT @swardley: Awful but funny -> RT @janl: If programming languages were weapons: zite.to/1pe3CY4 (via @antumbral) 20 hours ago