惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

D
Darknet – Hacking Tools, Hacker News & Cyber Security
T
Threat Research - Cisco Blogs
C
Cyber Attacks, Cyber Crime and Cyber Security
AI
AI
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
H
Hacker News: Front Page
P
Proofpoint News Feed
Know Your Adversary
Know Your Adversary
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
The Hacker News
The Hacker News
腾讯CDC
O
OpenAI News
Vercel News
Vercel News
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
量子位
S
Schneier on Security
T
Tor Project blog
B
Blog
The Register - Security
The Register - Security
宝玉的分享
宝玉的分享
S
Securelist
有赞技术团队
有赞技术团队
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
T
Tailwind CSS Blog
G
GRAHAM CLULEY
Hugging Face - Blog
Hugging Face - Blog
W
WeLiveSecurity
D
DataBreaches.Net
TaoSecurity Blog
TaoSecurity Blog
博客园 - Franky
Latest news
Latest news
I
Intezer
Hacker News: Ask HN
Hacker News: Ask HN
WordPress大学
WordPress大学
PCI Perspectives
PCI Perspectives
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
小众软件
小众软件
GbyAI
GbyAI
F
Full Disclosure
V
V2EX
Project Zero
Project Zero
The Last Watchdog
The Last Watchdog
T
Tenable Blog
Security Latest
Security Latest
Attack and Defense Labs
Attack and Defense Labs
F
Fortinet All Blogs
S
Secure Thoughts
Application and Cybersecurity Blog
Application and Cybersecurity Blog
Google DeepMind News
Google DeepMind News
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint

Henri Sivonen’s pages

Parin vuoden tutkimattomuus crates.io: Rust Package Registry Asiakirjatonta toimintaa It’s not wrong that "🤦🏼‍♂️".length == 7 Koulutartuntojen tilastointimenettely Perusteasiakirjoja hallussapitämättä ikärajoitettu Asiantuntijat ja nukkuva vallan vahtikoira Koronapassilausunto Suppealla tietopohjalla ohimeneväksi väitetty Text Encoding Menu in 2021 The Text Encoding Submenu Is Gone An HTML5 Conformance Checker Not Part of the Technology Stack Browser Technology Stack Bogo-XML Declaration Returns to Gecko A Look at Encoding Detection and Encoding Menu Telemetry from Firefox 86 Why Supporting Unlabeled UTF-8 in HTML on the Web Would Be Problematic Rust Target Names Aren’t Passed to LLVM Toimintamalli Activating Browser Modes with Doctype Johtopäätöksiä mallin rakenteesta Tehtävänmäärittelyä kirjoittamatta ja kuolemia laskematta laumasuojamallinnettu Character Encoding Menu in 2014 Erillissuosituksen tarpeettomuudesta yleissuosituksen poikkeukseksi? STM:n maskiaikajana Rust 2021 Oma-aloitteisesti mallinnettu Kokopinovaatimuksin kilpailutettu chardetng: A More Compact Character Encoding Detector for the Legacy Web Varauksia paisutellen tiedotettu Perusteasiakirjoitta tiedotettu Always Use UTF-8 & Always Label Your HTML Saying So IME Smoke Testing The Validator.nu HTML Parser About the Hiragino Fonts with CSS It’s Time to Stop Adding New Features for Non-Unicode Execution Encodings in C++ Rust 2020 The Last of the Parsing Quirks About about:blank Rust 2019 a Web-Compatible Character Encoding Library in Rust How I Wrote a Modern C++ Library in Rust Using cargo-fuzz to Transfer Code Review of Simple Safe Code to Complex Code that Uses unsafe A Rust Crate that Also Quacks Like a Modern C++ Library #Rust2018 No Namespaces in JSON, Please A Lecture about HTML5 Julkisesti luotettu varmenne ikidomainille TLS:ää (SSL:ää) varten -webkit-HTML5 Lists in Attribute Values The Sad Story of PNG Gamma “Correction” If You Want Software Freedom on Phones, You Should Work on Firefox OS, Custom Hardware and Web App Self-Hostablility HTML5 Parser Improvements ARIA in HTML5 Integration: Document Conformance (Draft, Take Two) Schema.org and Pre-Existing Communities Lowering memory requirements by replacing Schematron HTML5 Parsing in Gecko: A Build Introducing SAX Tree NVDL Support in Validator.nu HOWTO Avoid Being Called a Bozo When Producing XML An Unofficial Q&A about the Discontinuation of the XHTML2 WG Thoughts on HTML5 Becoming a W3C Recommendation Four Finnish Banks Training Users to Give Banking Credentials to Another Site Unimpressed by Leopard Sergeant Semantics The Content Sink Inheritance Diagram – 2006-06-30 What is EME? About Points and Pixels as Units The Performance Cost of the HTML Tree Builder The spacer Element Is Gone Openmind 2006 Performance Mistake XHTML and Mobile Devices WebM-Enabled Browser Usage Share Exceeds H.264-Enabled Browser Usage Share on Desktop (in StatCounter Numbers) HTML5 Parser-Based View Source Syntax Highlighting Vendor Prefixes Are Hurting the Web Accept-Charset Is No More Dualroids Writing Structural Stylable Document in Mozilla Editor ISO-8859-15 on haitallinen Hourglass The Scientific Method According to Hixie Maemo Source Code Karpelan lukkovertaus ontuu Digitaalisesta arkistoinnista ARIA in HTML5 Integration: Document Conformance (Draft) XHTML—What’s the Point? (Draft, incomplete) Mac OS X Browser Comparison HOWTO Spot a Wannabe Web Standards Advocate An Idea About Intermediate Language Trees and Web UI Generation Thoughts on Using SSL/TLS Certificates as the Solution to Phishing Bureaucracy Meets the Web Europe Day HOWTO Establish a 100% Literacy Rate What to Do with All These Photos? Charmod Norm Checking Validator Web Service Interface Ideas DTDs Don’t Work on the Web EFFI’s Day in Court Speaking at XTech
Social Media Impression Management
Henri Sivonen · 2012-09-17 · via Henri Sivonen’s pages

Yesterday, I attended a seminar on Social Media (arranged by University of Tampere but held in Helsinki).

I went there to listen to Herkko Hietanen launch a book Community Created Content (PDF, Amazon) written by him and the other Turre Legal guys. But this isn’t about the book.

There was another presentation by Katri Lietsala, a social media researcher from the Hypermedia laboratory of University of Tampere. She had a slide with the names of the usual suspects: Wikipedia, Flickr, YouTube, del.icio.us, MySpace, Digg, etc.

I observed that there is some overlap in the services provided by different sites but there are also significant differences in the public image of different sites. I asked if they had researched the image formation of social media sites. They hadn’t.

I don’t have answers, but here are some thoughts about the question.

Digg allows you to share links with others. So does del.icio.us. MySpace has social networking features and allows you to post photos of yourself. Flickr is for posting your photos and also has social networking features. Yet, these services are drastically different in terms of public image and associated impressions. Is this something that emerges accidentally or is it something you knowingly design for? Should creators of new services learn something?

Let’s look at the authors whose writing is aggregated at Planet Intertwingly. Many of the Planet Intertwingly authors share interesting URLs using del.icio.us. Not only do they use it, but they would be capable of writing their own link roll software and still choose to use del.icio.us. Clearly, using del.icio.us does not make you look uncool in this group. Digg, on the other hand, is not viewed favorably. In fact, it is viewed unfavorably enough to make an effort to block traffic from there!

The Planet Intertwingly authors tend to maintain control over their online presence by publishing at their own domains. Many even have written their own blogging software. These are not the kind of people who would outsource their online presence and URI space to MySpace. MySpace is where teenage girls post photos of themselves and leave the destiny of their URI space to Rupert Murdoch. However, the Planet Intertwingly kind of crowd is quite OK with outsourcing their photo management to Flickr giving up control of their photo URIs to Yahoo!. It is taken for granted that photos from serious technology events show up on Flickr. The tech cool of Flickr doesn’t seem to get tainted even though there are many users who are effectively using Flickr as a MySpace for 20-somethings and 30-somethings.

Is this all accidental or successful intentional targeting? Do Flickr and del.icio.us have something common in their design that Digg and MySpace don’t have? Should developers of new services design for particular outcomes or just see what happens?

Here are some things that come to mind:

  • del.icio.us and Flickr have a Google-ish no-nonsense graphic design in contrast to MySpace.

  • Flickr does not allow user to modify the graphic design. Many people who want mods have bad taste as witnessed on MySpace.

  • del.icio.us and Flickr have APIs that make developer types feel comfortable.

  • del.icio.us and Flickr solve problems that developer types could solve themselves but del.icio.us and Flickr do it so much better that rolling your own solution is not worth it. On the other hand, MySpace is an awful Web host for people who know how stuff should be done.

  • del.icio.us and Flickr are presented as tools for managing your own stuff (bookmarks, photos) so that they get shared with others. Digg and MySpace are overtly about trolling for attention.

  • In the seminar, a screenshot of Videoni.fi—a Finnish YouTube-wannabe copycat service—got the most laughs. This was due to the tag cloud being dominated by things like “woman”, “boobs”, “music video”, “cat” and “dog”. It appears that Flickr tries hard to avoid a low-brow “boobies!” reputation by manipulating “interestingness” and manually marking individual photos or users as inappropriate to suppress skin photos from public site areas even though the tag clouds elsewhere suggest that people would find those “interesting”. (Cat and dog photos are okay, though.) MySpace is obviously an exhibitionism platform by design and the main concern in limiting it is keeping worried parents and legislators at bay.

  • This is more effect than cause, but Flickr’s partners include Nokia—a company wanting to sell gadgets costing hundreds of dollars/euros to people who are old enough to buy them—whereas MySpace attracts the attention of the kind of old media companies who previously used MTV to manipulate teens into buying stuff.

I have a feeling that I may be missing something profound that is obvious once someone says it.