At Sinologic we use different publication formats to match each piece of content to its nature. A 3,000-word technical article is not the same as an interesting link from X or Bluesky. Here we explain how each one works.
Standard article
The main format of the blog. A full article with a title, featured image, structured content with headings, code, images and videos. This is what you will find in most publications about VoIP, Asterisk, Kamailio or IP telecommunications.
Features:
- Automatic table of contents in the sidebar (generated from the article headings)
- Estimated reading time
- Featured image with hero effect
- Related articles at the bottom
- Previous/next navigation between articles
- Chat-style comment system
Mini-post
A quick note, shorter than a standard article. Used to share an idea, a thought or a brief observation that does not require the structure of a full article.
It is displayed with a more compact design in the homepage grid, without a featured image.
Micropost
The shortest format of all. Similar to a social media post: a short text with the author’s avatar and name, in the style of a tweet or a Bluesky post, but hosted on our own server.
It is displayed as a compact card on the homepage with the Sinologic logo and direct actions.
Social (X / Bluesky)
This is a special format for sharing social media posts. Instead of simply linking to a tweet or a Bluesky post, we extract all the content and store it locally on our server:
- Author’s avatar — downloaded and stored on our server
- Name and username of the original author
- Full text of the post
- Images and videos — downloaded locally
- Statistics — likes, reposts, replies and views at the time of extraction
- Date and time of the original post
Why do we do this? Because platforms change. Tweets disappear, accounts get suspended, APIs change overnight. By storing everything locally, the content is preserved even if the original platform decides to delete it or change its rules.
We currently support automatic extraction from:
- X (Twitter) — via the FxTwitter API
- Bluesky — via the public AT Protocol API
What about LinkedIn?
Unlike X and Bluesky, LinkedIn does not offer any public API to access post content without authentication. While X has FxTwitter and Bluesky has its fully open AT Protocol, LinkedIn actively blocks any programmatic attempt to access its posts. For this reason, it is not possible to integrate LinkedIn posts with the same level of independence we achieve with X and Bluesky. If LinkedIn were to open its API in the future, we would add it.