seReive 1.02 Adds Timeline And Improves Picture Upload

(English further down)

Letzten Freitag am späten Nachmittag haben wir seReive 1.02 veröffentlicht. Neu kann man jetzt Fotos direkt in ein Facebook Album posten. Bisher wurden sie nur auf den seReive-Server geladen. Weil es bei Facebook nicht möglich ist, einen Post zu branden und gleichzeitig ein Foto in ein Album hochzuladen, haben wir dies nun dadurch verdeutlicht, dass nur eine der beiden Möglichkeiten angewählt werden kann.
Die entscheidende Neuerung jedoch ist die Zeitleiste mit ihren Editier-Möglichkeiten. Sie ersetzt das frühere Archiv. Neben allen bisher verschickten Posts sieht man in der Zeitleiste pendente Nachrichten. Diese können entweder gelöscht oder editiert werden.
Handelt es sich um Gruppen von Nachrichten, die gemeinsam und gleichzeitig zum Versand freigegeben wurden, kann man zwar einzelne Posts löschen, aber wenn man Text, Fotos oder Versand-Zeitpunkt bearbeiten will, geht das nur, wenn man die ganze Gruppe anklickt. Anschliessend öffent sich das Editier-Fenster, das die Nachricht behandelt, als würde sie komplett neu veröffentlicht. Gleichzeitig werden diese Posts aus dem Zwischenspeicher entfernt. Das bedeutet, wenn man nach dem Editieren nicht auf Versenden klickt, werden diese Posts auch nicht verschickt. Sie sind damit faktisch gelöscht. Umgekehrt gewährt diese Methode, getreu unserem Motto, die grösste Flexibilität bei gleichzeitig einfachster Handhabung. Siehe auch Bildergalerie.

English

Last Friday late afternoon we released seReive 1.02. New one can now post photos directly to a Facebook album. Previously they were only uploaded to the seReive server. Because it is not possible on Facebook, to brand a post and simultaneously upload a photo into an album, we have rewritten the software so that only one of two options can be selected.
The key innovation, however, is the Timeline with its editing capabilities. It replaces the previous Archive. In addition to all previously sent posts you can now see pending messages in the Timeline. These can either be deleted or edited.
If there are groups of messages that have been released jointly and simultaneously on sending, you can delete individual posts. But if you want to edit text, photos or sending date, this is only possible when clicking on the whole group. The then opening editing window treats the posts as if they would be released from scratch. The editing window is equal to the Send panel. At the same time, these posts will be removed from the pending posts’ cache. This means that if one does not click to send after editing, these posts will not be sent. They would then in fact be deleted. Conversely, this method, true to our motto, gives users the greatest flexibility with greatest ease of use. See picture gallery in this post.

seReive 0.4 is online with a few improvements and unlimited characters (dt.)

(German translation further down)

This morning seReive 0.4 went online. (Unfortunately there is currently still a problem with posting to MySpace, which does not work. Our developers are working on a solution.)

seReive 0.4  offers you the possibility to post a text of unlimited length. For two reasons we decided to repeal the limitation on text-length. First, via seReive you can post to a WordPress blog. Here a limitation has never made any sense, because WordPress posts can be any length. On the other hand, Facebook recently allowed posts with a length of up to 63’206 characters. So on Facebook, too, it makes no longer sense to limit the number of characters to 420. Other networks have different limits. 700 for LinkedIn and still 140 for Twitter. It is now left to the users to watch that a post is not too long.

With respect to that the second improvement comes in handy. The counting of the number of characters has been improved. So far, it could happen that a post appeared to be shorter than it really was. Some characters that appear as a single character when you type them are HTML-encoded. Code for such characters can actually be up to 5 characters long. For example, an ‘ encodes as %27 – turning a single character into three. Since today seReive will count characters in HTML code, so that it should no longer occur, that a tweet gets split into two, because it only seems to be less than 140 characters long, while in reality it is longer.

What we could not solve is the inclusion of images. Pictures that you post require a – variable – number of characters, too. E.g. twitter creates a URL and includes it into the post. Counting this is not possible, because it happens after the message gets delivered to Twitter. To be on the safe side we recommend to consider pictures as having 25 characters and developed a warning that will warn you when a Tweet with picture is longer than 115 characters.

The last improvement is purely graphical in nature. We found that many new users do not recognise seReive’s buttons on computer screens. On mobile devices buttons are clearly identifiable, but on computer screens until now you could only see the text. Now buttons have a magenta-colored frame. In German: Read more of this post

Congratulations To Cristina d’Ignazio

You may have noticed seReive running at the bottom of your screen while she is busy posting something for you.

It was  therefore very logical for us to sponsor a marathon runner. Cristina d’Ignazio has made the Uetliberglauf 2011 and the Lausanne Halfmarathon 2011 wearing seReive on her shirt. At the Uetliberglauf 2011 she was only third and took seReive up to the podium. We would like to congratulate her at this place for this outstanding performance. (With seReive on her shirt, however, of course we didn’t expect anything less…)

Hooray to Cristina!

Follow

Get every new post delivered to your Inbox.