Where is the up-to-date version?

I would get the Google Fiber and use a VPN for nearly everything.
It’s what I do with Comcast.

I get it. It’s still beta, and we’re only like 2% of the market. Makes sense not to worry about us yet.

For the typical “average” person, that’s likely.

But the early adopting power user, looking for alternatives to Google, aren’t those “average” people.

I’m 22 days into my month, and have 688 searches so far. But when unlimited was $15, I had no real trouble staying under 300.

People search so much mainly because they’re used to free unlimited searches.

I fixed the previous link.

They’re supported by user subscriptions. $10 for unlimited searches.

I’m too lazy. And there’s already Kagi

Still an attention based, ad funded business model, that turns it’s users into the product.

They do have ways to manually add to browsers, apps and search tools.

If you want to manually set Kagi as a default search engine, use these settings:
• Kagi Search URL https://kagi.com/search?q=%s
• Kagi auto suggestions URL https://kagi.com/api/autosuggest?q=%s

They don’t have an app.

Kagi is quite good at it. It includes citations even, so you can check if you’d like.

Firefox regular does that. There’s a setting to clear history on close. Then it adds a quit button to the menu. You can pick how much is deleted. History, cookies and anything else.

I just revoked all it’s data permissions. That’s good enough in the mean time.

keeping the main repo full of abandonware isn’t a good idea and will hold fdroid back on being a good app store.

That’s the only thing you wrote that sounds like a reason. It’s really just a speculative assertion.

That’s not to say you’re wrong! I actually do agree with you. In the long term. When their are millions of abandoned apps, and the main repo is hundreds of megabytes, and take several min to update each time, that would be a real problem. Yes. Pruning would be advantageous; And quite trivial to implement. Today though? It’s hardly the most pressing issue to F-Droid adoption. But sure why not.

New things can and should be built.
New things.

Taking something that’s currently good at what it does, and changing it to do something substantially new doesn’t work.

Google would have been better off, if they created a new service to emulate TickTock rather than shoehorn TickTock videos into YouTube.

They created Inbox to try to redesign email, rather than mess with how Gmail worked. That was absolutely the right way to do it.

That’s what your talking about here. Rather than adapt Lemmy to your new idea. Create an entirely new system expressly designed for it. That would really be making something new.

deleted by creator

I don’t know why some people seem to frequently want something to be something else.
When one service tries to incorporate multiple (and very different) modes of interactions, it always suffers.

Lemmy isn’t a chat room. If you want a live discussion you go to Discord or Matrix. Lemmy isn’t that. It shouldn’t be that. I remember when the Lemmy feed would constantly update. Even when It was working properly, it was extremely annoying. Lets let Lemmy be Lemmy. And if you want to engage with people in a different way, go to a service that was designed for it. Specialization is a good thing.

I’m pretty sure all user data is public already.
PMs might be the only thing not everyone can see.

I wouldn’t put a timeline to it. Just a list of features, broad and specific. As time goes on, they can be marked as “in progress” or “included”. New things can be added over time, or made more specific. All without timetables. For now call it a wishlist.

Unless compatibility can be set separately?

I imagine it could. It would be strange need to upload a “new version” of the app, when nothing actually changed accept approving a new OS for that version. Then you need to track which version numbers are real changes, and which aren’t. That would be weird.

There is actual compatibility, and official compatibility.

The updated apps likely didn’t have any code changed. (why they still worked when side loaded) Instead, the Play Store listing updated the compatibility filter to include Android 14, so 14 users could now see them in the Play Store.

It’s not an uncommon practice. Many apps might simply have a compatibility filter like “yes if [OS version > X]”. But that can be a problem if some future OS breaks compatibility. Especially in the case of a benchmark app that’s supposed to give comparable results between OS versions. If the new OS tweaks something that doesn’t fully break the benchmark, but causes inaccurate numbers, that would need to be checked before it gets approved.

I got it too. Sounds great. I frequently miss type and wish I could go back to fix it.