mastodon.ie is one of the many independent Mastodon servers you can use to participate in the fediverse.
Irish Mastodon - run from Ireland, we welcome all who respect the community rules and members.

Administered by:

Server stats:

1.6K
active users

#compatibility

0 posts0 participants0 posts today
Continued thread

Also didn't @EUCommission mandate #Compatibility & #Portability between these #Platforms?

infosec.space/@kkarhan/1148625

Infosec.SpaceKevin Karhan :verified: (@kkarhan@infosec.space)One thing that really pisses me off personally is the #regression in terms of #Messenger #Apps. My personal distaste and dislike for #proprietary, #SingleVendor & #SingleProvider #services like #Signal [¹](https://infosec.space/@kkarhan/114234551915193036), #Telegram, #Discord [²](https://infosec.space/@kkarhan/114865723904157014), #WhatsApp [³](https://infosec.space/@kkarhan/114873895410403238), #Slack, #MicrosoftTeams, etc. aside: - *WHY* is there no #CrossProvider #Messenger to handle that shite? - *WHY* does everyone of these shitty providers think people want to download their #bloated #WebApp that takes up triple digit Megabytes if not entire Gigabytes and will gobble up all the #RAM and #CPU each of them can?? This problem ain't new and *already got [solved for corporate social media](https://infosec.space/@kkarhan/114862619013462466) ages ago!* (Not to mention actually good messengers!) - And no, [bridges](https://toots.ch/@dalai/114862754556459439) *[don't](https://swecyb.com/@troed/114862774972645542) count*! - I mean `API 0` - [style](https://digipres.club/@foone/112685423773959519) access because obviously [none of the platforms](https://digipres.club/@foone/112685414638522984) will *allow, endorse or support such an endeavour* and [*actively fight the developers and users*](https://digipres.club/@foone/112685441496803574) ! So yeah, consider this a call for a @gajim@fosstodon.org / #Gajim or @pidgin@fosstodon.org / #Pidgin *for garbage platforms!* - Cuz back in the day we had *way worse messengers* yet people actually made #AIM, #ICQ, #MSN, #QQ, #IRC & #XMPP work just fine from one single *"phat" client*! - Can we please get that back? #api0 #Enshittification

What's your experience with /e/OS 3.0 and apps compatibility, for those of you using it? In particular, with notoriously difficult ones like banking apps or national ID apps (SwissID, I'm frowning at you)?
Have things improved compared to the previous version? Have you found solutions to incompatibilities?

On #fvwm #xorg #windows #compatibility

With all the recent bullsh^H^H^Htalk about #xorg, I realised an interesting historical piece of information. As early as 1999, fvwm (and not twm, from which fvwm is based) supported a raised-over-unmanaged workaround.

Specifically, it was for the following XServer implementations:

"Hummingbird Communications Ltd."
"Network Computing Devices Inc."
"WRQ, Inc."

It looks as though there was a bug in these servers, where a raise of the windows was needed:

github.com/fvwmorg/fvwm3/blob/

From what I can tell:

Hummingbird Communications Ltd were acquired:

en.wikipedia.org/wiki/Hummingb.

Netwrok Computing Devices Inc:

en.wikipedia.org/wiki/Network_

Defunct, but they did purchase some dumb terminals (TekXPress ) from Tektronix

WRQ Inc:

en.wikipedia.org/wiki/The_Atta

I could find no further information other than the paragraph or so mentioned here.

If anyone has any additional information on the #XServer used and its quirks, I'd love to know.

This has been a piece of #fvwm history for over 30 years so I'd love to hear from anyone who has further insight, please. :)

Continued thread

(6/X) Migration update: Moving from Windows to Linux!
After 4 intense days, I’m pausing the move as I’ve run out of time. The biggest hurdle is migrating my research data. As a research librarian working on systematic reviews, I rely on reference managers and qualitative analysis tools, but I am struggling with compatibility issues — for example, EndNote/Atlasti (Windows) vs. Zotero/ Taguette (Linux).
#EndOf10 #Linux #Compatibility #ResearchTools #OpenSource #Technology #AskFedi @zotero

Continued thread

This is awful. I'm backing up my research data from EndNote + Atlas.ti because I can't use them on Linux. I tried switching to Zotero and Taguette, but the data migration process is problematic: I lost groups with Zotero and Taguette doesn't support QDPX file import. 😤
Does anyone know of a QDA tool for Linux that supports QDPX file import (Project Exchange Format for Qualitative Data)?
#EndOf10 #Linux #LinuxMint #ResearchTools #QDA #QDAsoftware #Compatibility #OpenSource #Technology #AskFedi

Interesting & somewhat annoying discovery of the day

Mastodon, for some inexplicable reason, does not support AVIF images

My automated blog posts which use AVIF featured images don't show images when posted here & manually adding the images to the post on mastodon directly doesn't work

I find it odd that the universally accepted web friendly format is not supported here

You'd think anything thats reduces storage & bandwidth pressures would be welcomed

Replied in thread

@wolf480pl So yeah, I think that everything has compromises to some extent.

  • I'm shure #OpenBSD could even up their #security if they were willing to break #POSIX and #compatibility in general for their distro, but that'll only introduce more headaches and pain along the way.

I chose #Linux as basis for @OS1337 because it solves the #driver problem for me and I know it. I'm just complete shit with #NetBSD which may arguably be the better option targeting low-end systems, but that'll again result in more pain and frustration getting other #apps ported over when I can't just say: "Target linux-#i486 and statically compile in all your dependencies" to any 3rd party as starting point.

#Firefox - time to say goodbye, at least for now...

I've been using Firefox for years now, ignoring the fact, that it's objectively the worst performing #browser out there. With lacking #compatibility, outdated #dependencies, multiple unresolved #bugs. All of that was irrelevant, I wanted to support Your goal of making #Internet more #privacy respecting, a safe space.
Sadly, looks like it ends now. The biggest (and only) advantage goes away, and so do I. But I hope I can go back some day...

🕯️

If it's not an API, it's an implementation detail.

A nicely-phrased distinction: “On the technical side, I want to stress that there’s no such thing as an undocumented API (or private API). By definition an API is something that’s meant to be called by apps. Things that aren’t APIs are implementation details. And when you use that term it’s easier to evaluate your choices.” — Quinn “The Eskimo!”

Which is all too reminiscent of a common outcome among apps:

"With a sufficient number of users of an API,
it does not matter what you promise in the contract:
all observable behaviors of your system
will be depended on by somebody.” — Hyrum's Law

Platform providers would usually prefer to follow the model “Everything which is not allowed is forbidden" while developers are fond of "Everything which is not forbidden is allowed”.* The former avoids breaking quite as many apps and can deeply annoy, err, limit app developers, while following the latter makes non-breaking platform changes difficult to impossible, and increases support and testing.

At the intersection of those two models is app instability, angst, and architectural limits.

And yes, there are inevitably cases where API designs are just broken, or where the designs reach their architectural limits, and those then either stymy further work, or might get incompatibly un-broken, or preferably get replaced in parallel with better and more capable designs and the older APIs deprecated and removed.

How you design replacements for your API limits is part of your design too, but a part frequently ignored. As are app upgrades.

Limited API designs I've met have included an eight-byte password hash buffer, and APIs featuring 32-bit addressing for storage and memory.

*I'll leave any discussions of Misters Dillon and Cooley for another time.