🌈 Social 📸 Photography 🌈

Profoundly NerdyWhat makes NetBSD more portable than its counterparts?<a href="https://bitbang.social/tags/netbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#netbsd</a> <a href="https://bitbang.social/tags/openbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#openbsd</a> <a href="https://bitbang.social/tags/freebsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#freebsd</a> <a href="https://bitbang.social/tags/portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#portability</a> <a href="https://bitbang.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://bitbang.social/tags/askfedi" class="mention hashtag" rel="nofollow noopener" target="_blank">#askfedi</a>

Johannes ErnstSooo ... do data <a href="https://j12t.social/tags/portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#portability</a> laws require that you can port your <a href="https://j12t.social/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a> girlfriend?"So, how's your girl?" -- "Oh, fine, but I recently made her move house, from OpenAI to Meta."

Kevin Karhan :verified:Also didn't <a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener" target="_blank">@EUCommission</a> mandate <a href="https://infosec.space/tags/Compatibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#Compatibility</a> & <a href="https://infosec.space/tags/Portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#Portability</a> between these <a href="https://infosec.space/tags/Platforms" class="mention hashtag" rel="nofollow noopener" target="_blank">#Platforms</a>?<ul><li>Like wasn't that one of the points behind <a href="https://infosec.space/tags/DigitalMarketsAct" class="mention hashtag" rel="nofollow noopener" target="_blank">#DigitalMarketsAct</a>?</li></ul><a href="https://infosec.space/@kkarhan/114862595629371002" translate="no" rel="nofollow noopener" target="_blank">https://infosec.space/@kkarhan/114862595629371002</a><a href="https://infosec.space/tags/DMA" class="mention hashtag" rel="nofollow noopener" target="_blank">#DMA</a>

Jan PenfratHaha really! Google was allowed to invite an "independent" app developer who builds on <a href="https://eupolicy.social/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a>'s data <a href="https://eupolicy.social/tags/portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#portability</a> <a href="https://eupolicy.social/tags/API" class="mention hashtag" rel="nofollow noopener" target="_blank">#API</a> in order to celebrate how great Google is. This is slightly ridiculous.Now we're watching an <a href="https://eupolicy.social/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a>-voiced film showing off the API functionality. Is this the moment I should go home?

Kevin Karhan :verified:<a href="https://mstdn.social/@fabiscafe" class="u-url mention" rel="nofollow noopener" target="_blank">@fabiscafe</a> <a href="https://fosstodon.org/@okapi" class="u-url mention" rel="nofollow noopener" target="_blank">@okapi</a> OFC <a href="https://mastodon.bsd.cafe/@chesheer" class="u-url mention" rel="nofollow noopener" target="_blank">@chesheer</a> 's <a href="https://mastodon.bsd.cafe/@chesheer/114665737941231945" rel="nofollow noopener" target="_blank">criticism</a> is understandable on <a href="https://infosec.space/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> given that <a href="https://infosec.space/tags/SystemD" class="mention hashtag" rel="nofollow noopener" target="_blank">#SystemD</a> is inherenty focussed and intertwined with <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> (just as it's Inspiration, <a href="https://infosec.space/tags/LaunchD" class="mention hashtag" rel="nofollow noopener" target="_blank">#LaunchD</a>, is intertwined with <a href="https://infosec.space/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#macOS</a>'s Darwin/NeXTstep kernel).<ul><li>The problem is after some hefty "init wars" with like <a href="https://infosec.space/tags/Upstart" class="mention hashtag" rel="nofollow noopener" target="_blank">#Upstart</a> and others SystemD became the de-facto standard, and the "(statistical) rounding errors" of <a href="https://infosec.space/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSD</a> users got sidelined, in part because BSDs looked at that mess and went like "Nyet, SysVinit is fine!" and continued their fiddling around...</li></ul>And sadly there's nothing they (or anyone else) could've done unless they had multiplied suddenly and being able to keepcthe old tech stack maintainable.<ul><li>Similarly <a href="https://infosec.space/tags/Xorg" class="mention hashtag" rel="nofollow noopener" target="_blank">#Xorg</a> is dying and there are already GPUs that only support <a href="https://infosec.space/tags/Wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wayland</a> and <a href="https://infosec.space/tags/X11" class="mention hashtag" rel="nofollow noopener" target="_blank">#X11</a> apps get run using <a href="https://infosec.space/tags/XWayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#XWayland</a>. </li></ul>OFC I wish for more diversity in solutions, but <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> being <a href="https://infosec.space/tags/streamlined" class="mention hashtag" rel="nofollow noopener" target="_blank">#streamlined</a> is what makes <a href="https://infosec.space/tags/portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#portability</a> across distros easier and boosted adoption as well as providing massive gains in solutions like <a href="https://infosec.space/tags/DXVK" class="mention hashtag" rel="nofollow noopener" target="_blank">#DXVK</a>, <a href="https://infosec.space/tags/Proton" class="mention hashtag" rel="nofollow noopener" target="_blank">#Proton</a> and <a href="https://infosec.space/tags/Wine" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wine</a> in general.<ul><li>And TBH most "<a href="https://infosec.space/tags/TechIlliterates" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechIlliterates</a>" aka. "<a href="https://infosec.space/tags/Normies" class="mention hashtag" rel="nofollow noopener" target="_blank">#Normies</a>" frankly don't give a shit what OS they use. All it needs to do is serve them their eMails and allow them to 'consoom themselbes happy' as in watching YouTube, Play games, etc.</li></ul>

tuxwise<a href="https://infosec.exchange/tags/introduction" class="mention hashtag" rel="nofollow noopener" target="_blank">#introduction</a>Our motto is »<a href="https://infosec.exchange/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://infosec.exchange/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> News & <a href="https://infosec.exchange/tags/KnowHow" class="mention hashtag" rel="nofollow noopener" target="_blank">#KnowHow</a> for <a href="https://infosec.exchange/tags/Office" class="mention hashtag" rel="nofollow noopener" target="_blank">#Office</a> Tasks.«Our posts are for <a href="https://infosec.exchange/tags/solopreneurs" class="mention hashtag" rel="nofollow noopener" target="_blank">#solopreneurs</a>, <a href="https://infosec.exchange/tags/trainers" class="mention hashtag" rel="nofollow noopener" target="_blank">#trainers</a>, <a href="https://infosec.exchange/tags/facilitators" class="mention hashtag" rel="nofollow noopener" target="_blank">#facilitators</a>, and everybody else who tackles their office tasks using open source software under Linux.While we appreciate <a href="https://infosec.exchange/tags/portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#portability</a>, 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

☮ ♥ ♬ 🧑‍💻Big question, Why ATProtocol from <a href="https://ioc.exchange/tags/BlueSkySocial" class="mention hashtag" rel="nofollow noopener" target="_blank">#BlueSkySocial</a> <a href="https://ioc.exchange/tags/PBC" class="mention hashtag" rel="nofollow noopener" target="_blank">#PBC</a>’s mouth instead of Mastodon and ActivityPub?: “Why not use ActivityPub? <a href="https://ioc.exchange/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a> is a federated social networking technology popularized by <a href="https://ioc.exchange/tags/Mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mastodon</a>.Account <a href="https://ioc.exchange/tags/portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#portability</a> is a major reason why we chose to build a separate protocol. We consider portability to be crucial because it protects <a href="https://ioc.exchange/tags/users" class="mention hashtag" rel="nofollow noopener" target="_blank">#users</a> from sudden bans, server shutdowns, and policy disagreements. Our <a href="https://ioc.exchange/tags/solution" class="mention hashtag" rel="nofollow noopener" target="_blank">#solution</a> for portability requires both signed data repositories and <a href="https://ioc.exchange/tags/DIDs" class="mention hashtag" rel="nofollow noopener" target="_blank">#DIDs</a>, neither of which are easy to retrofit into ActivityPub. The migration <a href="https://ioc.exchange/tags/tools" class="mention hashtag" rel="nofollow noopener" target="_blank">#tools</a> 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 <a href="https://ioc.exchange/tags/scalability" class="mention hashtag" rel="nofollow noopener" target="_blank">#scalability</a>. <a href="https://ioc.exchange/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a> depends heavily on delivering messages between a wide network of small-to-medium sized nodes, which can cause individual <a href="https://ioc.exchange/tags/nodes" class="mention hashtag" rel="nofollow noopener" target="_blank">#nodes</a> to be flooded with traffic and generally struggles to provide global views of <a href="https://ioc.exchange/tags/activity" class="mention hashtag" rel="nofollow noopener" target="_blank">#activity</a>.”Short version, WE CANT CONTROL YOU. <<a href="https://atproto.com/guides/faq" rel="nofollow noopener" translate="no" target="_blank">https://atproto.com/guides/faq</a>>

Kevin Karhan :verified:<a href="https://mastodon.social/@reichenstein" class="u-url mention" rel="nofollow noopener" target="_blank">@reichenstein</a> Consider filing an <a href="https://infosec.space/tags/antitrust" class="mention hashtag" rel="nofollow noopener" target="_blank">#antitrust</a> <a href="https://infosec.space/tags/complaint" class="mention hashtag" rel="nofollow noopener" target="_blank">#complaint</a>.woth <a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener" target="_blank">@EUCommission</a> and your local <a href="https://infosec.space/tags/AntiCartelWatchdog" class="mention hashtag" rel="nofollow noopener" target="_blank">#AntiCartelWatchdog</a> to enforce <a href="https://infosec.space/tags/EU" class="mention hashtag" rel="nofollow noopener" target="_blank">#EU</a> <a href="https://infosec.space/tags/Cloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cloud</a> <a href="https://infosec.space/tags/Portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#Portability</a> legislation...

JunoIntroducing tori, a tool to track your system's configuration and replicate it.I've been simultaneously using and developing it personally for the past 5 months, and now I would like to teach it to fly so it can break out from our nest.This version still has very few of the features I enjoy in my personally-hardcoded version. If it sounds interesting, just stay tuned.I wrote a blog post with a more in-depth description of what it is, how it works and why I built it:<a href="https://blog.jutty.dev/posts/introducing-tori.html" rel="nofollow noopener" translate="no" target="_blank">https://blog.jutty.dev/posts/introducing-tori.html</a><a href="https://mastodon.bsd.cafe/tags/OperatingSystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#OperatingSystems</a> <a href="https://mastodon.bsd.cafe/tags/portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#portability</a> <a href="https://mastodon.bsd.cafe/tags/SysAdmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#SysAdmin</a> <a href="https://mastodon.bsd.cafe/tags/shell" class="mention hashtag" rel="nofollow noopener" target="_blank">#shell</a> <a href="https://mastodon.bsd.cafe/tags/POSIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#POSIX</a> <a href="https://mastodon.bsd.cafe/tags/ash" class="mention hashtag" rel="nofollow noopener" target="_blank">#ash</a> <a href="https://mastodon.bsd.cafe/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSD</a> <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://mastodon.bsd.cafe/tags/VoidLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoidLinux</a> <a href="https://mastodon.bsd.cafe/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> <a href="https://mastodon.bsd.cafe/tags/ConfigurationManagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#ConfigurationManagement</a>

tuxwise<a href="https://mastodon.de/tags/introduction" class="mention hashtag" rel="nofollow noopener" target="_blank">#introduction</a>Our motto is »<a href="https://mastodon.de/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://mastodon.de/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> News & <a href="https://mastodon.de/tags/KnowHow" class="mention hashtag" rel="nofollow noopener" target="_blank">#KnowHow</a> for <a href="https://mastodon.de/tags/Office" class="mention hashtag" rel="nofollow noopener" target="_blank">#Office</a> Tasks.«Our content is for <a href="https://mastodon.de/tags/solopreneurs" class="mention hashtag" rel="nofollow noopener" target="_blank">#solopreneurs</a>, <a href="https://mastodon.de/tags/trainers" class="mention hashtag" rel="nofollow noopener" target="_blank">#trainers</a>, <a href="https://mastodon.de/tags/facilitators" class="mention hashtag" rel="nofollow noopener" target="_blank">#facilitators</a>, and everybody else who tackles their office tasks using open source software under Linux. Tasks over tech!While we appreciate <a href="https://mastodon.de/tags/portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#portability</a>, we're strictly Linux-only. With respect to other operating systems: no bashing, no praise, no comparisons. We've already made our choice!

Andrew Chouseemingly out of nowhere I've somehow found myself delving deeper into technologies that could be classified as "permacomputing"-friendly or adjacent. I've recently been doing a lot of reading and exploration on things like around redbean, lua, tcl/tk, c, portability, longevity, and "old" tech and can't help but get excited or overly curious about them.<a href="https://toot.cafe/tags/permacomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#permacomputing</a> <a href="https://toot.cafe/tags/lua" class="mention hashtag" rel="nofollow noopener" target="_blank">#lua</a> <a href="https://toot.cafe/tags/redbean" class="mention hashtag" rel="nofollow noopener" target="_blank">#redbean</a> <a href="https://toot.cafe/tags/tcl" class="mention hashtag" rel="nofollow noopener" target="_blank">#tcl</a> <a href="https://toot.cafe/tags/tk" class="mention hashtag" rel="nofollow noopener" target="_blank">#tk</a> <a href="https://toot.cafe/tags/c" class="mention hashtag" rel="nofollow noopener" target="_blank">#c</a> <a href="https://toot.cafe/tags/portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#portability</a>

Robert Riemann 🇪🇺<a href="https://loma.ml/profile/z428" class="u-url mention" rel="nofollow noopener" target="_blank">@z428</a> For perfect <a href="https://chaos.social/tags/portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#portability</a> in the Fediverse: Instances involved in a move would need to trust each other, e.g. when importing time-stamped content from the past. People could fake their past easily. <a href="https://chaos.social/tags/activitypub" class="mention hashtag" rel="nofollow noopener" target="_blank">#activitypub</a>

Jan Penfrat<a href="https://indieweb.social/@tchambers" class="u-url mention" rel="nofollow noopener" target="_blank">@tchambers</a> <a href="https://venera.social/profile/fediversenews" class="u-url mention" rel="nofollow noopener" target="_blank">@fediversenews</a> Maybe <a href="https://eupolicy.social/tags/Meta" class="mention hashtag" rel="nofollow noopener" target="_blank">#Meta</a> is smart enough to comply with its <a href="https://eupolicy.social/tags/DigitalMarketsAct" class="mention hashtag" rel="nofollow noopener" target="_blank">#DigitalMarketsAct</a> obligations in the <a href="https://eupolicy.social/tags/EU" class="mention hashtag" rel="nofollow noopener" target="_blank">#EU</a> early (should <a href="https://eupolicy.social/tags/Threads" class="mention hashtag" rel="nofollow noopener" target="_blank">#Threads</a> ever be launched there).Art 6(9) <a href="https://eupolicy.social/tags/DMA" class="mention hashtag" rel="nofollow noopener" target="_blank">#DMA</a>: "The <a href="https://eupolicy.social/tags/gatekeeper" class="mention hashtag" rel="nofollow noopener" target="_blank">#gatekeeper</a> shall provide end users and third parties authorised by an end user, at their request and free of charge, with effective <a href="https://eupolicy.social/tags/portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#portability</a> of data provided by the end user or generated through the activity of the end user in the context of the use of the relevant core platform service [...]."

Ian Brown (@1br0wn) 🇮🇨🚨 My new open access article: The UK’s <a href="https://social.masto.host/tags/Midata" class="mention hashtag" rel="nofollow noopener" target="_blank">#Midata</a> and <a href="https://social.masto.host/tags/OpenBanking" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenBanking</a> programmes: A case study in data <a href="https://social.masto.host/tags/portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#portability</a> and <a href="https://social.masto.host/tags/interoperability" class="mention hashtag" rel="nofollow noopener" target="_blank">#interoperability</a> requirements, Technology and Regulation (2022) <a href="https://techreg.org/article/view/11539" rel="nofollow noopener" target="_blank">https://techreg.org/article/view/11539</a>

Recent searches

Search options

Administered by:

Server stats:

#portability