#portability

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>

Ian Brown 👨🏻‍💻Well! Look what <a href="https://eupolicy.social/tags/Twitter" class="mention hashtag" rel="tag">#Twitter</a> founder and <a href="https://eupolicy.social/tags/Bluesky" class="mention hashtag" rel="tag">#Bluesky</a> / <a href="https://eupolicy.social/tags/Nostr" class="mention hashtag" rel="tag">#Nostr</a> co-founder Jack <a href="https://eupolicy.social/tags/Dorsey" class="mention hashtag" rel="tag">#Dorsey</a> just gave $10m to... 'The team at “and Other Stuff” is also working on a social media “Bill of Rights”…which spells out what social media platforms need to provide in areas like <a href="https://eupolicy.social/tags/privacy" class="mention hashtag" rel="tag">#privacy</a>, <a href="https://eupolicy.social/tags/security" class="mention hashtag" rel="tag">#security</a>, <a href="https://eupolicy.social/tags/interoperability" class="mention hashtag" rel="tag">#interoperability</a>, <a href="https://eupolicy.social/tags/transparency" class="mention hashtag" rel="tag">#transparency</a>, <a href="https://eupolicy.social/tags/identity" class="mention hashtag" rel="tag">#identity</a>, self-governance, and <a href="https://eupolicy.social/tags/portability" class="mention hashtag" rel="tag">#portability</a>.' 👏 <a href="https://eupolicy.social/tags/DMA" class="mention hashtag" rel="tag">#DMA</a> <a href="https://eupolicy.social/tags/DMCCA" class="mention hashtag" rel="tag">#DMCCA</a> <a href="https://techcrunch.com/2025/07/16/jack-dorsey-pumps-10m-into-a-nonprofit-focused-on-open-source-social-media/" target="_blank" rel="nofollow noopener" translate="no">https://techcrunch.com/2025/07/16/jack-dorsey-pumps-10m-into-a-nonprofit-focused-on-open-source-social-media/</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="tag">#Google</a>'s data <a href="https://eupolicy.social/tags/portability" class="mention hashtag" rel="tag">#portability</a> <a href="https://eupolicy.social/tags/API" class="mention hashtag" rel="tag">#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="tag">#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>

Ian Brown 👨🏻‍💻Time to add office suites as a Core Platform Service to the <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23DMA" target="_blank">#DMA</a> (and consider whether additional Art. 5/6/7 obligations should apply, too)… <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23Google" target="_blank">#Google</a> <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23Workplace" target="_blank">#Workplace</a> <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23Microsoft" target="_blank">#Microsoft</a> <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23Office" target="_blank">#Office</a> <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23StrategicAutonomy" target="_blank">#StrategicAutonomy</a> <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23DataSovereignty" target="_blank">#DataSovereignty</a> <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23portability" target="_blank">#portability</a> <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23interoperability" target="_blank">#interoperability</a> /cc <a class="mention" href="https://bsky.app/profile/aschwab.bsky.social" rel="nofollow noopener" target="_blank">@aschwab.bsky.social</a> <a class="mention" href="https://bsky.app/profile/filomenac.bsky.social" rel="nofollow noopener" target="_blank">@filomenac.bsky.social</a> RE: <a href="https://bsky.app/profile/did:plc:qc6xzgctorfsm35w6i3vdebx/post/3lracwk3ha22o" rel="nofollow noopener" target="_blank">https://bsky.app/profile/did:plc:qc6xzgctorfsm35w6i3vdebx/post/3lracwk3ha22o</a>

Felix Palmen :freebsd: :c64:Getting somewhat closer to releasing a new version of <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener" target="_blank">#swad</a>. I now improved the functionality to execute something on a different worker thread: Use an in-memory queue, providing a <a href="https://mastodon.bsd.cafe/tags/lockfree" class="mention hashtag" rel="nofollow noopener" target="_blank">#lockfree</a> version. This gives me a consistent reliable throughput of 3000 requests/s (with outliers up to 4500 r/s) at an average response time of 350 - 400 ms (with TLS enabled). For waking up worker threads, I implemented different backends as well: kqueue, eventfd and event-ports, the fallback is still a self-pipe.So, <a href="https://mastodon.bsd.cafe/tags/portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#portability</a> here really means implement lots of different flavors of the same thing.Looking at these startup logs, you can see that <a href="https://mastodon.bsd.cafe/tags/kqueue" class="mention hashtag" rel="nofollow noopener" target="_blank">#kqueue</a> (<a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> and other BSDs) is really a "jack of all trades", being used for "everything" if available (and that's pretty awesome, it means one single <a href="https://mastodon.bsd.cafe/tags/syscall" class="mention hashtag" rel="nofollow noopener" target="_blank">#syscall</a> per event loop iteration in the generic case). <a href="https://mastodon.bsd.cafe/tags/illumos" class="mention hashtag" rel="nofollow noopener" target="_blank">#illumos</a>' (<a href="https://mastodon.bsd.cafe/tags/Solaris" class="mention hashtag" rel="nofollow noopener" target="_blank">#Solaris</a>) <a href="https://mastodon.bsd.cafe/tags/eventports" class="mention hashtag" rel="nofollow noopener" target="_blank">#eventports</a> come somewhat close (but need a lot more syscalls as there's no "batch registering" and certain event types need to be re-registered every time they fired), they just can't do signals, but illumos offers Linux-compatible signalfd. Looking at <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>, there's a "special case fd" for everything. 🙈 Plus <a href="https://mastodon.bsd.cafe/tags/epoll" class="mention hashtag" rel="nofollow noopener" target="_blank">#epoll</a> also needs one syscall for each event to be registered. The "generic <a href="https://mastodon.bsd.cafe/tags/POSIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#POSIX</a>" case without any of these interfaces is just added for completeness 😆

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

Joaquim Homrighausen<a href="https://cyberplace.social/@GossiTheDog" class="u-url mention" rel="nofollow noopener" target="_blank">@GossiTheDog</a> "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.<a href="https://mastodon.online/tags/mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#mastodon</a> <a href="https://mastodon.online/tags/portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#portability</a> <a href="https://mastodon.online/tags/dataportability" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataportability</a> <a href="https://mastodon.online/tags/fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#fediverse</a>

☮ ♥ ♬ 🧑‍💻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>>

André Machado :debian:Resumed Technical Comparison: Linux vs. BSDLinux and BSD are two influential families of open-source operating systems with distinct philosophies, architectures, and use cases. Although they share UNIX roots, their development paths, licensing models, and system design set them apart.Read More: <a href="https://machaddr.substack.com/p/resumed-technical-comparison-linux" rel="nofollow noopener" target="_blank">https://machaddr.substack.com/p/resumed-technical-comparison-linux</a><a href="https://mastodon.sdf.org/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSD</a> <a href="https://mastodon.sdf.org/tags/RUNBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#RUNBSD</a> <a href="https://mastodon.sdf.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://mastodon.sdf.org/tags/Comparison" class="mention hashtag" rel="nofollow noopener" target="_blank">#Comparison</a> <a href="https://mastodon.sdf.org/tags/Use" class="mention hashtag" rel="nofollow noopener" target="_blank">#Use</a> <a href="https://mastodon.sdf.org/tags/Cases" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cases</a> <a href="https://mastodon.sdf.org/tags/Operating" class="mention hashtag" rel="nofollow noopener" target="_blank">#Operating</a> <a href="https://mastodon.sdf.org/tags/Systems" class="mention hashtag" rel="nofollow noopener" target="_blank">#Systems</a> <a href="https://mastodon.sdf.org/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://mastodon.sdf.org/tags/Portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#Portability</a> <a href="https://mastodon.sdf.org/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#Security</a> <a href="https://mastodon.sdf.org/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenBSD</a> <a href="https://mastodon.sdf.org/tags/NetBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#NetBSD</a> <a href="https://mastodon.sdf.org/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> <a href="https://mastodon.sdf.org/tags/Technical" class="mention hashtag" rel="nofollow noopener" target="_blank">#Technical</a> <a href="https://mastodon.sdf.org/tags/Review" class="mention hashtag" rel="nofollow noopener" target="_blank">#Review</a> <a href="https://mastodon.sdf.org/tags/Computer" class="mention hashtag" rel="nofollow noopener" target="_blank">#Computer</a> <a href="https://mastodon.sdf.org/tags/Science" class="mention hashtag" rel="nofollow noopener" target="_blank">#Science</a>

Aral Balkan:kitten: Kitten¹ updateDomain migrations are now live for your Kitten apps.You can now point any custom domain to a deployed Kitten app. When the first Domain² instance goes live at small-web.org later this year, you’ll be able to deploy Kitten apps in ~10 seconds at <your domain>.small-web.org. Then, if you want to, you can point any domain to it using any registrar.¹ <a href="https://kitten.small-web.org" rel="nofollow noopener" translate="no" target="_blank">https://kitten.small-web.org</a> ² <a href="https://codeberg.org/domain/app" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/domain/app</a><a href="https://mastodon.ar.al/tags/Kitten" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kitten</a> <a href="https://mastodon.ar.al/tags/SmallWeb" class="mention hashtag" rel="nofollow noopener" target="_blank">#SmallWeb</a> <a href="https://mastodon.ar.al/tags/Domain" class="mention hashtag" rel="nofollow noopener" target="_blank">#Domain</a> <a href="https://mastodon.ar.al/tags/interoperability" class="mention hashtag" rel="nofollow noopener" target="_blank">#interoperability</a> <a href="https://mastodon.ar.al/tags/portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#portability</a> <a href="https://mastodon.ar.al/tags/web" class="mention hashtag" rel="nofollow noopener" target="_blank">#web</a> <a href="https://mastodon.ar.al/tags/dev" class="mention hashtag" rel="nofollow noopener" target="_blank">#dev</a>

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>

mgorny-nyan (he) :autism:🙀🚂🐧Today is the day I've used <a href="https://social.treehouse.systems/tags/GDB" class="mention hashtag" rel="nofollow noopener" target="_blank">#GDB</a>. With a <a href="https://social.treehouse.systems/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> <a href="https://social.treehouse.systems/tags/C" class="mention hashtag" rel="nofollow noopener" target="_blank">#C</a> extension. On <a href="https://social.treehouse.systems/tags/SPARC" class="mention hashtag" rel="nofollow noopener" target="_blank">#SPARC</a>.What could it be if the package fails on some integer math on SPARC, but works on PPC64 (big endian)? Well, it turns out that it's because `char` is signed on SPARC.And the author decided to cast a `const unsigned char *` parameter into a `const char *` variable, for no apparent reason. Sigh.<a href="https://github.com/ICRAR/crc32c/pull/44" rel="nofollow noopener" translate="no" target="_blank">https://github.com/ICRAR/crc32c/pull/44</a><a href="https://social.treehouse.systems/tags/portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#portability</a> <a href="https://social.treehouse.systems/tags/Gentoo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gentoo</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!

Francesco Yoshi Gobbo :linux:<a href="https://mastodontech.de/@ChristianKrebel" class="u-url mention" rel="nofollow noopener" target="_blank">@ChristianKrebel</a> for <a href="https://qoto.org/tags/tenting" class="mention hashtag" rel="nofollow noopener" target="_blank">#tenting</a>, you can always build on them <a href="https://www.reddit.com/media?url=https%3A%2F%2Fpreview.redd.it%2Fan3y45x0emob1.jpg%3Fwidth%3D4032%26format%3Dpjpg%26auto%3Dwebp%26s%3D55ab06258409c46726d9439c8e529123703f11ce" rel="nofollow noopener" target="_blank">as this person</a> have!The ‘problem’ of the <a href="https://qoto.org/tags/Moonlander" class="mention hashtag" rel="nofollow noopener" target="_blank">#Moonlander</a>, and also of the <a href="https://qoto.org/tags/Glove80" class="mention hashtag" rel="nofollow noopener" target="_blank">#Glove80</a>, is that they take a good amount of space on the <a href="https://qoto.org/tags/backpack" class="mention hashtag" rel="nofollow noopener" target="_blank">#backpack</a>.. now, if that is a problem, only depends on you… but if <a href="https://qoto.org/tags/portability" class="mention hashtag" rel="nofollow noopener" target="_blank">#portability</a> is on top of the list, the <a href="https://qoto.org/tags/Voyager" class="mention hashtag" rel="nofollow noopener" target="_blank">#Voyager</a> can only be beaten by custom ones… ^^The problem for me, is the only 2 thumb keys, I think 3 would have been perfect! :blobaviator: <a href="https://qoto.org/tags/ZSA" class="mention hashtag" rel="nofollow noopener" target="_blank">#ZSA</a> do you hear me? XD

tuxwise<a href="https://social.tchncs.de/tags/introduction" class="mention hashtag" rel="nofollow noopener" target="_blank">#introduction</a>Our motto is »<a href="https://social.tchncs.de/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://social.tchncs.de/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> News & <a href="https://social.tchncs.de/tags/KnowHow" class="mention hashtag" rel="nofollow noopener" target="_blank">#KnowHow</a> for <a href="https://social.tchncs.de/tags/Office" class="mention hashtag" rel="nofollow noopener" target="_blank">#Office</a> Tasks.«Our content is for <a href="https://social.tchncs.de/tags/solopreneurs" class="mention hashtag" rel="nofollow noopener" target="_blank">#solopreneurs</a>, <a href="https://social.tchncs.de/tags/trainers" class="mention hashtag" rel="nofollow noopener" target="_blank">#trainers</a>, <a href="https://social.tchncs.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://social.tchncs.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!

Jan Penfrat<a href="https://indieweb.social/@tchambers" class="u-url mention">@tchambers</a> <a href="https://venera.social/profile/fediversenews" class="u-url mention">@fediversenews</a> Maybe <a href="https://eupolicy.social/tags/Meta" class="mention hashtag" rel="tag">#Meta</a> is smart enough to comply with its <a href="https://eupolicy.social/tags/DigitalMarketsAct" class="mention hashtag" rel="tag">#DigitalMarketsAct</a> obligations in the <a href="https://eupolicy.social/tags/EU" class="mention hashtag" rel="tag">#EU</a> early (should <a href="https://eupolicy.social/tags/Threads" class="mention hashtag" rel="tag">#Threads</a> ever be launched there).Art 6(9) <a href="https://eupolicy.social/tags/DMA" class="mention hashtag" rel="tag">#DMA</a>: "The <a href="https://eupolicy.social/tags/gatekeeper" class="mention hashtag" rel="tag">#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="tag">#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 [...]."

Paul Nemitz„<a href="https://eupolicy.social/tags/Google" class="mention hashtag" rel="tag">#Google</a>'s conduct could compress the right to <a href="https://eupolicy.social/tags/portability" class="mention hashtag" rel="tag">#portability</a> of <a href="https://eupolicy.social/tags/personaldata" class="mention hashtag" rel="tag">#personaldata</a>, established by Article 20 of the <a href="https://eupolicy.social/tags/GDPR" class="mention hashtag" rel="tag">#GDPR</a>, and could constrain the economic benefits that consumers can derive from their <a href="https://eupolicy.social/tags/data" class="mention hashtag" rel="tag">#data</a>. <a href="https://eupolicy.social/tags/DSGVO" class="mention hashtag" rel="tag">#DSGVO</a> <a href="https://eupolicy.social/tags/Privacy" class="mention hashtag" rel="tag">#Privacy</a> <a href="https://eupolicy.social/tags/Antitrust" class="mention hashtag" rel="tag">#Antitrust</a> <a href="https://eupolicy.social/tags/Competition" class="mention hashtag" rel="tag">#Competition</a> <a href="https://eupolicy.social/tags/GAFAM" class="mention hashtag" rel="tag">#GAFAM</a> <a href="https://eupolicy.social/tags/Datenschutz" class="mention hashtag" rel="tag">#Datenschutz</a> <a href="https://eupolicy.social/tags/Wettbewerb" class="mention hashtag" rel="tag">#Wettbewerb</a>RT @antitrust_it@twitter.comItalian Competition Authority, investigation opened against <a href="https://eupolicy.social/tags/Google" class="mention hashtag" rel="tag">#Google</a> for abuse of dominant position in <a href="https://eupolicy.social/tags/dataportability" class="mention hashtag" rel="tag">#dataportability</a> <a href="https://eupolicy.social/tags/ICA" class="mention hashtag" rel="tag">#ICA</a> <a href="https://eupolicy.social/tags/Antitrust" class="mention hashtag" rel="tag">#Antitrust</a> <a href="https://en.agcm.it/en/media/press-releases/2022/7/A552" target="_blank" rel="nofollow noopener" translate="no">https://en.agcm.it/en/media/press-releases/2022/7/A552</a>🐦🔗: <a href="https://twitter.com/antitrust_it/status/1547474478975926272" target="_blank" rel="nofollow noopener" translate="no">https://twitter.com/antitrust_it/status/1547474478975926272</a>

Recent searches

Search options

Administered by:

Server stats: