vintprox

What about "We Fedicast"?

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.

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.

@melroy This is stupid YouTube... Anyway, if you're on the legs, try Grayjay for Android. 😉👍

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.

@ernest, please. All they need is commits, PRs and comments that add something. True, dev work is full of cool updates and reporting, but it crosses roads with other mundane activities. Devlog is probably going to drain you more than it's worth, so I hope you'll build your priorities straight.

Let's be open: I'm only making a press-kit for Mbin recently (and nothing much) just after being introduced to the fork as a result of @melroy migrating. It's a crazy amount of reviewed and merged pull requests, which I couldn't dream of committing nor reviewing in detail. There is simply a lot that can be done with community harnessing the project. No way this fork would be considered serious if it were to feed everyone with blog updates. At this point, your words set up a head start. It's a matter of whether it will start: will these old habits offer something that was not served already? (Big downtimes happen to be one of those things...)

No idea if any competition will take place - again, introduction to a fork was ever so sudden, making me wonder if it didn't have to come to this. In any case, whatever we continue doing I hope remains healthy for the wider community of contributors and users. Thank you for returning! 🤝

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!