{ "version": "https:\/\/jsonfeed.org\/version\/1.1", "title": "Ilya Birman’s Blog: posts tagged being human", "_rss_description": "Ilya Birman’s blog on design, cities, music, and life", "_rss_language": "en", "_itunes_email": "ilyabirman@ilyabirman.net", "_itunes_categories_xml": "<\/itunes:category>\r\n<\/itunes:category>\r\n\r\n", "_itunes_image": "https:\/\/ilyabirman.net\/meanwhile\/pictures\/userpic\/userpic-square@2x.jpg?1573933764", "_itunes_explicit": "no", "home_page_url": "https:\/\/ilyabirman.net\/meanwhile\/tags\/being-human\/", "feed_url": "https:\/\/ilyabirman.net\/meanwhile\/tags\/being-human\/json\/", "icon": "https:\/\/ilyabirman.net\/meanwhile\/pictures\/userpic\/userpic@2x.jpg?1573933764", "authors": [ { "name": "Ilya Birman", "url": "https:\/\/ilyabirman.net\/meanwhile\/", "avatar": "https:\/\/ilyabirman.net\/meanwhile\/pictures\/userpic\/userpic@2x.jpg?1573933764" } ], "items": [ { "id": "341", "url": "https:\/\/ilyabirman.net\/meanwhile\/all\/how-to-trim-text-the-right-way\/", "title": "How to trim text the right way", "content_html": "

Recently, I wrote about Facebook’s crappy handling of long posts<\/a>: it’s trims the text randomly and loses your reading position when expanded. So how should it be done? Let’s deal with the trimming first.<\/p>\n

Trimming text in a random place is disrespectful to the author and the text, and is a further proof that Facebook doesn’t care what you write. It’s also an example of deep technology dependence: it’s easier for a machine to trim to a certain number of characters, and so it does.<\/p>\n

There could be an aesthetic rationale behind trimming text, i.e. to make it fit into a certain design element. Of course this is also disrespectful to the author and the text, but at least the motives are humanistic. However trimming after a fixed number of characters is not even this: the physical size of lines of equal character length is usually variable: compare “iii” and “WWW”. Even in my Facebook example, a few more words would fit in the same box:<\/p>\n

\n\"\"\n<\/div>\n

Sometimes trimming randomly not only ruins the meaning of the text, but changes its to something indecent:<\/p>\n

\n\"\"\n<\/div>\n

So, if you can’t do without trimming, you have to trim carefully. How does Aegea do it?<\/p>\n

The character limit is considered a rough guideline, not an exact value. If you need to fit in 140 characters, and the text is 143 characters long, then Aegea just won’t touch it. If the text is noticeably over the limit, then Aegea will divide it into sentences and try to take as many full sentences as it can fit. Here, for example, is the snippet of this post:<\/p>\n

\n\"\"\n<\/div>\n

However, if the result is too short (or no whole sentence fits at all), Aegea will look for other signs of safe trim positions: semicolons, dashes, commas, brackets. Only if none of these are present will it trim at a word boundary. And only if there are no word boundaries, will it trim by the number of characters. The absence of word boundaries is a sure sign that the author themselves didn’t care about the meaning, so it’s fine if neither does Aegea.<\/p>\n

In general, Aegea will try to make it as close to the desired length as possible, but so that the meaning does not suffer.<\/p>\n

If I can code this, what would stop Facebook from doing it? I think it’s that it hadn’t even crossed anyone’s mind. Why would Facebook even care about doing anything well? What a nonsense. There is no such metric.<\/p>\n", "summary": "Recently, I wrote about Facebook’s crappy handling of long posts: it’s trims the text randomly and loses your reading position when expanded", "date_published": "2022-10-25T12:50:10+03:00", "date_modified": "2022-10-25T12:49:26+03:00", "tags": [ "Aegea", "being human", "interface", "text" ], "image": "https:\/\/ilyabirman.net\/meanwhile\/pictures\/fb-see-more-3@2x.jpg", "_date_published_rfc2822": "Tue, 25 Oct 2022 12:50:10 +0300", "_rss_guid_is_permalink": "false", "_rss_guid": "341", "_rss_enclosures": [], "_e2_data": { "is_favourite": true, "links_required": [], "og_images": [ "https:\/\/ilyabirman.net\/meanwhile\/pictures\/fb-see-more-3@2x.jpg", "https:\/\/ilyabirman.net\/meanwhile\/pictures\/liz-truss-anal@2x.jpg", "https:\/\/ilyabirman.net\/meanwhile\/pictures\/aegea-snippet-of-this-en@2x.jpg" ] } }, { "id": "331", "url": "https:\/\/ilyabirman.net\/meanwhile\/all\/fuel-low-petrol-stations\/", "title": "Fuel low; here are petrol stations", "content_html": "

\n\"\"\n<\/div>\n

When running out of fuel, not only does my car light an LED, but also offers to show the nearest petrol stations using the built-in navigation.<\/p>\n

Any error or problem message in an interface should not just state it indifferently, but also help you find a solution.<\/p>\n", "summary": "When running out of fuel, not only does my car light an LED, but also offers to show the nearest petrol stations using the built-in navigation", "date_published": "2022-09-13T09:22:08+03:00", "date_modified": "2022-09-13T09:21:51+03:00", "tags": [ "being human", "interface", "photo" ], "image": "https:\/\/ilyabirman.net\/meanwhile\/pictures\/fuellow.jpg", "_date_published_rfc2822": "Tue, 13 Sep 2022 09:22:08 +0300", "_rss_guid_is_permalink": "false", "_rss_guid": "331", "_rss_enclosures": [], "_e2_data": { "is_favourite": false, "links_required": [], "og_images": [ "https:\/\/ilyabirman.net\/meanwhile\/pictures\/fuellow.jpg" ] } }, { "id": "326", "url": "https:\/\/ilyabirman.net\/meanwhile\/all\/remind-of-the-past\/", "title": "Remind me of the past", "content_html": "

Let’s jump right in to the examples. In an online store, you need to select which bank card to use. You’ve been a client for many years, so a whole bunch of cards are already saved. You need to pick the one that you want to use right now:<\/p>\n

\n\"\"\n<\/div>\n

It would be great if the store reminded you, which card you used to make the recent purchase. Even better, specify last purchase date next to each one.<\/p>\n

When you make mistake entering a Google password, it reminds you when you set it:<\/p>\n

\n\"\"\n<\/div>\n

It will only say this if you are entering your old password. If you enter a wrong password that has never been right, it will just say it’s wrong. These “35 days” could be useful, e. g. if they remind you of the circumstances, in which you changed the password, you could remember the password itself.<\/p>\n

More examples:<\/p>\n