@benwerd my take: use rel=next/prev[ious]
(like inter-post nav) then progressively enhance, make sure you’re not making people play “catch the footer” :)
@benwerd my take: use rel=next/prev[ious]
(like inter-post nav) then progressively enhance, make sure you’re not making people play “catch the footer” :)
@benwerd high expectations asian father microformats geek says:
@fraying woah, when did dotted backslashes replace hyphens? Musta missed the memo :/
@benwerd BALALAIKA
@benwerd you mean like this…?
Erin Richie wot, no hashtag?
Tantek Çelik wow, how many years between feature request and implementation? Must be a record!
Jeremy Keith sure! Will do. Great to see you + @wordridden again, have a safe journey to Germany :)
Tantek Çelik demonstrating replying to a note directly from your site :) #indiewebcamp
.@kevinmarks small correction: I post photos+videos from iPad via email, most notes (like this reply) from my web interface :)
Jovian Salak you lucky guy — Brighton failed utterly to sell me crêpes :( On the plus side, I had toast with some cool people in a café which was playing folk music.
@benwerd will you be on IRC/hangout/etherpad or whatever?
Jovian Salak good god that is hideous. Why do people think this kind of censorship is effective, acceptable or in any way rational? That head appears to be abusing his power and certainly deserves the scrutiny his students put him under.
@helloanselm some of us @indiewebcamp-ers have been working on independent event hosting and cross-site RSVPs, check out indiewebcamp.com/event — potential to manual-POSSE to services like lanyrd too
Aral Balkan there’s some excellent+useful constructive criticism in there! I think you’re still misunderstanding the problem being solved and why indieauth evolved to work the way it does, as the solutions you suggest are in fact a big part of the problem. We wrote up a collaborative point-by-point response to your article here: indiewebcamp.com/On_Evolving_IndieAuth_Followup, which hopefully explains things better than I did previously.
@scottjenson also, without wanting to sound rude, you lecturing me about the quality of my POSSEd notes would be a lot more convincing if you were POSSEing notes (and thus running into these challenges) yourself :)
@scottjenson referring to the truncation? I know what you mean, I made the conscious decision to ignore the length of truncated copies of my content as I didn’t want what felt like an unnecessary limitation of Twitter limiting my self-expression.
Others (Tantek Çelik in particular) care more about the quality of their POSSEd notes, and build UIs which inform them when their notes go over tweet- or retweet-safe lengths. This is one of the places diversity of implementations helps us experiment without having to argue about stuff :)
One interesting alternative is to spread the content of notes which are too long for a tweet over several tweets, but that leads to all sorts of weird directionality changes, potential for them to be interrupted, extra permalinks, etc.
@fraying we saw some being selectively tested, documented them here: http://indiewebcamp.com/reply-context#Twitter_home_page
Personally I dislike the current design more for the changes in directionality without clear delineation, but the blue lines are weird too.
@smarimc @herraBRE you’re coming? You should add yourselves to the guest list indiewebcamp.com/2013/UK — only 8 spots remaining!