Pretty much same thing. I want niche creators to see that their content is appreciated (in lack of paid subscription), and Piped with a bunch of other frontends are simply not a way for this.
vintprox
joined 1 year ago
I think some people don't give any room to breathe to projects that just want major contributors be paid, even when, as you rightfully say, XMPP had the same compatibility struggles in its infancy as Matrix implementations now have.
So far, there is a lot of FUD around newer protocol and that it lacks in openness. But if you look again, it recognizes versions and differences between them in the specification. Every MSC proposal covers the context of change and recommendations to implement, while keeping backwards-compatibility with older software in mind. If you make a proposal, it will be reviewed. If you need someone else besides Spec Core Team members to move it forward, flag to you - fork. But I rather prefer this model in upstream than beating around the bush and electing someone who might have lost an idea of why they are still in the project.
This is terrible news. :( Sorry to hear that work makes you download from proprietary store front. I suppose, expecting phones with LineageOS, CalyxOS, GrapheneOS, etc given for work purposes is a bit much at this moment, but at least side-loading should be provided if we're to avoid monopoly. To me, it's never healthy if organization is fixated on using only the single app kit for everything.
What you guys call "swipe typing" is actually a glide typing, right?
Sadly, not yet. (Also missing this feature.)
I hope to impose a better question: why would it not cost the developer? $25 may be a steal for some, but I don't think a proprietary store really deserves so much attention from primarily FOSS developer.
Haha, well... It's a Samsung Galaxy from Android 10 era and, apparently, it has terrible Settings. Whenever I try to say "Don't optimize" on any app, it changes the label, but only for a brief moment, which effectively does not turn off any optimization.
It will just keep reactivating battery optimization, at least it's what I see on Samsung.
A fun story: I was curating my magazine on Melroy's instance and didn't butt heads with any regression when he switched from Kbin to Mbin. Nice to see priorities set straight on migration!
In retrospective, it's a practical decision to move away from downtimes, especially seeing as development is so rapid now.
We might do a mirror to Codeberg to avoid a complete dependency on GitHub, while accepting PRs on the side. Priorities tell us to postpone this idea in favor of long-awaited changes and fixes, though! 😉
view more: next ›
What about "We Fedicast"?