Ærion

@cobalt123 I replaced Pocket with Wallabag, and #Evernote with @joplinapp, and use both separately. @wallabag

@daniel@gultsch.social I appreciate that. I meant the term loosely. In general, I'd love to see more Android apps 'ported' to alternative mobile OSs. The pending changes to Android later this year make it clear that it's more important than ever to have other options than the choice between Android and iOS.

@daniel@gultsch.social Time to port Conversations to mobile Linux and Sailfish OS?

@metin Change post visibility? 😃🙏🏻 Tap photo to open it? 😃🙏🏻 Pinch zoom that stays zoomed in when released? 😃🙏🏻 @dansup

@unifiedpush@fosstodon.org Congratulations! It's a shame that #Paralino isn't open source, which makes it hard to trust its #e2ee credentials, but still a nice boost for UnifiedPush. It really should be adopted as the standard for notifications, as it demonstrates that Google's infrastructure is not necessary. As I've understood it, there's zero need for developers to use Firebase, at least for notifications. Now let's hope Paralino also opens up the servers, and goes FULLY open source.

@wallabag 🥂🥳 Congratulations!! I've been with you for about half of that! I didn't know of your existence at first, and was a Pocket user for a while, but I discovered Wallabag when I went on a mission to replace everything I use with #FOSS software and services. I've not looked back since.

@organicmaps Instead of shifting the blame onto @fdroidorg, you could *easily* fix this 'problem' yourself by ensuring no AF apply to your app. @CoMaps has *zero* AF. Furthermore, several people have attested here that they're not seeing the issue at all, and that the default settings only exclude the NSFW AF. One more reason why I'm glad to have replaced Organic Maps with CoMaps. Edit: typo @fennek

@CoMaps Is there a way to install this without using Flatpak? I avoid Flatpak like the plague.

@CoMaps@floss.social 🎉🎊🎈 Congratulations!! I've been with you since the beginning, having left Organic Maps after several years of using that.

@zoneghost@theforkiverse.com To be fair, many of those places didn't start out like that. Probably didn't even intend to turn into what they've become now. Investors happened, and with that enshitification followed. Just look at the origins of Facebook, that didn't start as a disguised advertising company driven by a mass corporate surveillance machine. @evacide@hachyderm.io

@dansup@mastodon.social AMAZING!! @pixelfed@mastodon.social

@davidculley We should be 'glad' that they still bother posting any disclaimer, however teeny tiny, whatsoever. The next step is to just post AI generated content without disclaimers. We live in an age where it's becoming harder and harder to tell truth from fiction, thanks to AI and people are willingly embracing it. @wakame

@IzzyOnDroid Done! With a scathing message for ~them~ the AI bot to enjoy. I can't WAIT to turn my back on #Android, literally my last and only tie to #Google. We can only hope that this attack on 3rd party app stores, and #FOSS in general, leads to accelerated development of #mobilelinux and motivate devs to start porting their apps to it. It's HIGH TIME to end this duopoly of iOS and Android as our only choices for our mobile phones and tablets. @postmarketOS @ubports #mobian @jolla

@beyondmachines1@infosec.exchange **Or better: close your LinkedIn account and be done with it. I'm so fucking sick of #bigtech taking liberties with our accounts, our data, our hardware, our digital lives, with impunity. We are not their vassals. Fine, so they're being taken to court. They may get fined. There may be new legislation. It won't matter. It amounts to nothing more than a slap on the wrist. They'll (pretend to) comply, while inventing new ways to keep doing what they're doing. Remember #Microsoft being forced to decouple Internet Explorer from XP, and getting fined? Try uninstalling Edge from W10/11… I rest my case. Nothing will change until people actually go to prison, not for 6 months or so, but for a decade or more. We wouldn't accept ANY of this IRL!! People would get locked up for gaining unauthorised access to your house, taking photos of your tools, book collection, etc., and selling them to 3rd parties! How has this become OK, just because it's digital and invisible?!

@cobalt123 The really cool thing that both can be self-hosted too. Just make sure to still support both projects financially, if you go down that route! @somcak Edit: typo correction

@simonriley If that's the point they wanted to draw attention to, then they should've used actual images from the actual event. All they've achieved instead is shifting the focus to the utterly unnecessary use of AI, and the untrustworthiness of their institution. I care infinitely more about that than the 64 injured officers. @wakame @davidculley

@andy_warb@mastodon.social Fab analogy, especially with Google's history of killing off apps and services, leaving users scrambling for alternative solutions; you never see that coming either… @geerlingguy@mastodon.social

@CoMaps@floss.social Wow, that really is an amazing development!! 🥳

@wallabag While I'm not affected by this, it is very sad news for iOS users. 😢 I appreciate that this is not down to the Wallabag project, but there's a risk that this will make Wallabag less attractive as a viable alternative to Pocket and other read-it-later services. Not every iOS user is financially able to pay for apps, so where does this leave them? And even those who can afford to may balk at the idea of suddenly having to pay for an app. Aside from this, it always feels like betrayal, a stab in the back, when #FOSS developers decide to make their apps closed source. It's never a good sign. There's nothing wrong, of course, with wanting/needing to make money with an app, but there was no need for this step. He could have chosen to charge for the app, but leave it open source. There are *plenty* of open source projects that are libre but not gratis, such as Wallabag itself. Let's hope someone will want to pick up the mantle… 🤞🏼

@dansup While strictly speaking not part of the Fediverse, @snikket_im firmly belongs on this list for significantly lowering the bar of entry for #XMPP @aral @gazaverified @quillmatiq @anewsocial @silverpill @mitra @julian @nodebb @jesseplusplus @frequency @jaz @teamtoot @iftas @thisismissem @benpate @koen

@Papaexmatrikulatus@mastodon.social Well, you asked a 'quick' question as to why I avoid Flatpak. I gave you my reasons, and they still stand. If Flatpak, or even Snap (known to have been a source of spyware, BTW) works for you, then great! I'm not trying to convince you, or anyone, to not use it. I don't really care whether it's one or the other that becomes the standard, as long as the current issues are addressed. Until such time, I'm not interested, and will stick to native packages that don't bloat my system, and can be installed and updated from a single source. @bas_spr@digitalcourage.social @LookWhatTheCatDraggedIn@mastodon.social

@Papaexmatrikulatus This blog post explains my reasons perfectly. https://machaddr.substack.com/p/snap-or-flatpak-on-linux-why-you Pretty much the same reasons why I hate Electron apps.

@dansup@mastodon.social

• • I know signal isn't federated, consider @matrix or @xmpp alternatively

How about pointing to https://quicksy.im/ rather than Signal? And @snikket_im@fosstodon.org for those who prefer #selfhosting ?

#Quicksy is by far the easiest way to get into #XMPP, and it behaves like WhatsApp (and Signal) users expect, with automatic contact discovery.

We need truly open instant messaging, not more walled gardens. However much good Signal has done for privacy in IM, it is not the golden answer to WhatsApp, Telegram, and all the other monolithic platforms.

@daniel@gultsch.social @matrix@mastodon.matrix.org @xmpp@fosstodon.org

@catisabetterdog@troet.cafe Of course, being able to use Android apps on Sailfish OS is great, but ultimately we need native apps. Relying on compatibility with another OS's apps is a risky strategy. What if Android app support gets dropped? What if Google changes Android to the point where this no longer works? And what about apps that depend on SafetyNet or Play Integrity, or whatever Google calls it these days? @daniel@gultsch.social

@dansup@mastodon.social 🥳

@Papaexmatrikulatus@mastodon.social System integration, or rather the lack thereof, is only one of the issues with Flatpak/Snap. Even if a package doesn't need it, the other issues mentioned in the article I posted, still apply. @bas_spr@digitalcourage.social

@CoMaps Thanks, I'll give it a try when I get a moment.

@freedominternet En als gebruiker kun, nee, MOET je zelf ook wat doen:

• Vul niet meer in dan nodig: laat optionele velden leeg.
• Sla je creditcard/debitcard nooit (indien mogelijk) op bij de aanbieder, maar laat het invullen door je wachtwoordbeheerder.
• Gebruik een uniek wachtwoord voor elke site/service.
• Gebruik een uniek e-mailadres, bijv. via #SimpleLogin, indien nodig zelfs een wegwerpadres voor eenmalig gebruik.

De combinatie van die laatste twee zorgt ervoor dat geen enkel ander account gevaar loopt bij een lek.

En unieke e-mailadressen (aliassen) hebben als positieve bijwerking een gigantische reductie in spam.

Ontvang je spam op een gelekt e-mailadres? Maak een nieuwe alias aan, update het betreffende account, wis de oude alias: geen spam meer! Let wel: zorg ervoor dat je het werkelijke e-mailadres waar de aliassen naar verwijzen NERGENS gebruikt worden; houd dit adres dus geheim!!

@bas_spr@digitalcourage.social Exactly, more fiddling required to achieve (partial) parity with native versions. It should make things easier, not harder. Flatpak, Snap, and AppImage (and Electron) primarily benefit developers, while offering little benefit to users. Furthermore, it scatters packages over multiple installation sources, instead of just one: the native package manager.. And finally, yet again we have multiple, incompatible, approaches trying to solve the same problem. Until there is a single, unified method for package distribution, that addresses all the shortcomings of the current ones, I'm steering clear of all of them. @Papaexmatrikulatus@mastodon.social

@mcbaumwolle@mastodon.social Never mind that, where is the Mastodon link??? @EUCommission@ec.social-network.europa.eu

@saxnot I don't think the advanced features are the main obstacle in switching from MS Office to alternative office suites. Sure, in certain environments this may be a showstopper, but the two key issues are: 1) Having to learn something new. Most people have a huge aversion to anything with a learning curve, anything that's different from what they're used to. The introduction of a ribbon style interface option in LO goes some way towards addressing the issue, but ultimately LO does not work like MSO, and that introduces friction in someone's workflow. 2) People are held hostage by the OpenXML format. MS have done an outstanding job in effectively killing off ODF, by introducing + fast tracking their OpenXML format, while at the same time making sure that ODF support is deliberately crippled. Even if people are able (willing?) to overcome the functional differences, this is what makes people stick to MSO. For the record, I've been using LO since the Star Office days. @tomstoneham

@Papaexmatrikulatus@mastodon.social But that has been my point all along: I don't *want* Flatpak et al. I prefer staying with native packages. *If* there is to be a unified approach at all, it has to address the current issues, the biggest one of which is competing systems. Until then, as I originally stated, I am not interested. They do not solve a problem for me, they *create* problems. Also, as previously stated, they primarily benefit devs, as they only have to package their apps once. Just like Electron apps primarily benefit devs. As for who uses AppImage: https://aur.archlinux.org/packages?O=0&K=Appimage @bas_spr@digitalcourage.social

@vitekorre@mastodon.social 😵 It takes 940 partners for Microsoft to make Outlook work?! Are they THAT incompetent??? 🤣 @Techaltar@mas.to

@KentNavalesi Because it's invisible. Unlike getting burgled, or their car having been broken into, it's not something they feel or witness. Until they do… @uastronomer

@pixelfed@mastodon.social Looking forward to it!

@drunkenmadman@aus.social Good. Fucking. Riddance.

@saxnot That is 𝘱𝘳𝘦𝘤𝘪𝘴𝘦𝘭𝘺 what I was pointing out, and is 𝘱𝘳𝘦𝘤𝘪𝘴𝘦𝘭𝘺 the reason why I reject the notion that switching to Linux is difficult. It's why I call it a 𝘱𝘦𝘳𝘤𝘦𝘪𝘷𝘦𝘥 difficulty, as these issues, as you point out, exist just the same on 𝘢𝘯𝘺 platform. @tomstoneham

@Papaexmatrikulatus@mastodon.social Unified as in: a single, universal method to install packages, as opposed to Flatpak vs Snap vs AppImage, mixed with native packages. They all try to be that, but none of them actually achieves its goal. Take CoMaps, for example. Ubuntu users would, I imagine, prefer a Snap package, but since only a Flatpak (*) is offered, they're either left out or forced to install Flatpak, learn how to use it, and now they have three app sources to maintain: .deb (via apt), Snap, and Flatpak. That's not what I'd call unified. (*) I don't use any of the *buntus, or their derivatives, so I don't know if someone's made a Snap package. It's more to illustrate the problem. @bas_spr@digitalcourage.social

@dansup@mastodon.social @matrix@mastodon.matrix.org @xmpp@fosstodon.org

A Windows user switching to macOS, with no one in their social circle who's familiar with Macs, will suffer just as much as someone switching to Linux without having fellow Linux users they can ask for help. The same goes for macOS users wanting to move to Windows, Android to iOS, etc. The real problem isn't the (perceived) difficulty of Linux, but rather the lack of popular software such as Microsoft Office, Photoshop, combined with the natural resistance to change, and the sheer unwillingness to learn something new. Distros such as Linux Mint, Zorin OS, or Elementary OS, to name but a few, have pretty much eliminated the UI learning curve, thanks to their close resemblance to either Windows or macOS, or their ability to switch layouts at will. 2/2 @saxnot @tomstoneham @neil

@quantumsys Perfect, as I happen to run Arch! @CoMaps

@wallabag Ah, I see. That's great! I wasn't aware of this project at all. It would be good to have this project mentioned in the official announcement of the demise of the official iOS app. It will surely avoid any confusion.