Our motto is »#Linux #OpenSource News & #KnowHow for #Office Tasks.«
Our posts are for #solopreneurs, #trainers, #facilitators, and everybody else who tackles their office tasks using open source software under Linux.
While we appreciate #portability, we're strictly Linux-only. With respect to other operating systems: no bashing, no praise, no comparisons. We've already made our choice.
Formerly @social.tchncs.de, 2021-09-01 to 2024-06-15; then @mastodon.de until 2025-04-17
@GossiTheDog "Mastodon" really needs to get cracking on full data portability, IMHO.
It's a shame this hasn't been pushed higher up on the list of things to do.
I think many people have invested quite a bit of time and effort into their posts and profiles, and moving all that data, or somehow managing a switch-over doesn't seem to be that simple, if at all possible.
[Перевод] Переносимый код: Fighting the Lemmings
Сергей Каличев, старший разработчик, Angie Software Однажды, давным-давно, я наткнулся на одну хорошую статью по разработке переносимого кода и решил её перевести. Когда же это было... ё-моё, в 2008 году, 17 лет назад! Обалдеть, как время летит. Статья называлась "Fighting the Lemmings", автор Martin Husemann. Выложил перевод на LOR . С тех пор много воды утекло и, когда я попытался поискать статью в Интернете, то обнаружил, что ни оригинальной статьи, ни перевода, найти практически невозможно. Перевод ещё сохранился в глубоких закромах OpenNet , а оригинал только в архиве Интернета . Ссылки на PDF-ки тоже протухли и больше не работают. Обидно, это ведь такая нетленка для системщиков. Понятно, что переносимость уже сто раз пережёвана в других статьях и книгах, но тут всё было сконцентрировано и написано доходчиво. При этом актуальность до сих пор не потеряна. Ну а что, собственно, кардинально поменялось в разработке переносимого кода на C с тех пор? Если не обращать внимание на упоминания некоторых архитектур и ОС, которые сейчас, да и во времена перевода, звучат, как придания старины глубокой, то в остальном, обо всех особенностях разработки переносимого кода, описанных в статье, надо помнить и сегодня. Выкладываю текст, как он есть, без каких-либо современных правок. Для тех, кому удобнее читать в PDF, вот ссылки: PDF оригинальной статьи PDF перевода А теперь сама статья.
Big question, Why ATProtocol from #BlueSkySocial #PBC’s mouth instead of Mastodon and ActivityPub?:
“Why not use ActivityPub? #ActivityPub is a federated social networking technology popularized by #Mastodon.
Account #portability is a major reason why we chose to build a separate protocol. We consider portability to be crucial because it protects #users from sudden bans, server shutdowns, and policy disagreements. Our #solution for portability requires both signed data repositories and #DIDs, neither of which are easy to retrofit into ActivityPub. The migration #tools for ActivityPub are comparatively limited; they require the original server to provide a redirect and cannot migrate the user's previous data.
Another major reason is #scalability. #ActivityPub depends heavily on delivering messages between a wide network of small-to-medium sized nodes, which can cause individual #nodes to be flooded with traffic and generally struggles to provide global views of #activity.”
Short version, WE CANT CONTROL YOU.
At Artinis, we believe neuroscience research should go beyond the lab, which is why our devices are designed to deliver exceptional performance wherever it's needed—even at home.
Elderly Rehabilitation: A recent study by Klop et al. showcased the diagnostic potential of using the PortaLite MKII to monitor brain activity during rehabilitation for orthostatic hypotension —right in patients’ homes.
https://publications.artinis.com/publication/klop-home-based-2024/
4b. Some companies or PR people may answer that data #portability is on their roadmap. Ask where the roadmap can be checked out
Something I hadn’t considered about account #portability …
It will simplify initial user onboarding. Interested in XYZ software? Cool. Sign up now on xyz.social. You can move your account in a week or two once you have a lay of the land…
From what I've read when they first went public about it, it was because of #portability which don't exist in the #ActivityPub protocol. When I informed them about the #NomadicIdentity powering #Hubzilla (and #Streams today), they said they weren't aware of it (at least from what I can recall), so they'll look into it.
The second reason is moderation. Which, if we only look at AP protocol it's pretty much basic, if any. But if they were only aware of Hubzilla's #Zot protocol before they started their project, they probably would've used it since moderation and permissions are awesome in Zot (far better than what #Bluesky / #ATproto currently have today).
And well, they already started their own project and set up their goals, so they pushed for it.
At least that's how I understood it. Not necessarily accurate.
I wonder when we'll see custom domain #WebFinger in the #Fediverse / #ActivityPub ?
For example, I want to use:
* @-live.youronly.one for my #Streams account
* @-sns.youronly.one for my #Firefish account
* @-photos.youronly.one for my #Pixelfed account
* @-mblog.youronly.one for my #Mastodon account
* @-reading.youronly.one for my #BookWyrm account
Ideally, even if I move to a new host/service, I can use the same WebFinger.
♬ 
