Is the desktop app native?
332 karma · joined January 25, 2017
(you can still see it in the url)
But the main difference is that DGG chooses ads based only on search term, as opposed to tracking you and collecting your data across the entire net.
> Are these stories personalized to me?
> For the most part, no. Most recommendations on your new tab come from a general list of the best of stories on the web. But Pocket is actively exploring ways to deliver personalized recommendations in a way that vigorously protects users’ privacy. Importantly, neither Mozilla nor Pocket ever receives a copy of your browser history. When personalization does occur, recommendations rely on a process of story sorting and filtering that happens locally in your personal copy of Firefox.
Unfortunately it's proprietary, but there's another native client called gtkcord3 [0] that seems to be progressing well.
Why? Not trying to be snarky, just genuinely curious, I'd expect that those people would generally be less susceptible to advertising.
Are you talking about this page? https://sourcehut.org/
It seems like the opposite to me, each feature has a big heading that you can quickly read to get an overview of all the features, with smaller, more detailed descriptions below.
Imagine what these massive companies could do if they made their own native clients.
Unfortunately, it looks like it's not open-source, their Github repo is only for bug reports: https://github.com/pipes-digital/pipes
If you’re using Linux and Pulseaudio, look into echo cancellation, it’s easy to enable and can help improve your voice quality a little bit.
While I thought dropping the "no build-step" requirement wouldn't be a big deal nowadays, they later say:
> We should still explore introducing a full build step in the future (including full support for module bundling, ES6+ transpilation via Babel, etc), but this is a non-trivial change to the architecture of MediaWiki.
I can see why going with something that doesn't need a build-step could be appealing.
There's also the other factor (mentioned below) about community. If MediaWiki chose Svelte, they would definitely have to invest a lot into the framework and it's community, and I'm not sure if that's something they want to or are capable of doing. The biggest pain point with Svelte right now (at least for me) is the tooling, it's real bad.
This is the only mention about Svelte:
> Svelte, Inferno, and Preact are aggressively optimized for performance but have much smaller communities of users (Preact suffers from this issue to a lesser extent, but only as long as it maintains a very high level of compatibility with mainstream React, which may not be the case forever).
I'd be interested in seeing a bit more discussion about it.
I also don't understand this. What makes it even worse is that someone has already done this. I've been using Ripcord [0] for a few months for Discord and Slack, and it performs way better (it's native, written in Qt 5), and supports nearly all of those platform's features [1]. It is unfortunately proprietary (although I think the dev has open sourced the theming engine).
it doesn't look as beautiful (if you care about that), but it has most of the features. This is all done by 1 guy. Imagine what Slack and Discord could do themselves.
The real solution is to drop these proprietary solutions that don't respect their users. Unfortunately, while I love Matrix and Signal, the large majority of my social circle would never move to those.
Edit: I should also add, there's a very promising, open-source Discord client being developed called gtkcord3 [2], it's still very early in development, but it looks great and already supports the essential features, excluding voice chat.
[0] https://cancel.fm/ripcord/ [1] https://dev.cancel.fm/service_features [2] https://github.com/diamondburned/gtkcord3
I agree. It's also very minor, but one feature I miss from the old Firefox is being able to scroll the address horizontally. Now you have to tap on it, which opens the keyboard.
- Extensions are not supported...
Edit: maybe I misread the article. Do they mean that they're going to replace the old Firefox with Preview in it's current state? It would definitely be horrible if they pushed a downgrade that removes extension support (even if they plan to add more support later).
AFAIK they're adding the extensions API used by all extensions, but they're going incrementally by trying to support APIs used by popular extensions first. They even said they plan to add more extensions soon. Ideally, once the extension API is solid they'll allow you to install from the addon store (like old Firefox). It would be awful if they only allowed you to install they're recommended extensions.
> The thumbnails are removed from the tab list...
That was a nice feature. The icon beside tab names is pretty big, maybe they could add an option to make it even bigger and show a tab thumbnail.
> Popups each time you close a tab use up unnecessary screen space...
Agreed, although I like being able to undo if I accidentally close one. I much prefer the way the old Firefox did it (basically the same thing, but a slimmer banner touching the bottom of the screen). Hopefully they improve this somehow.
> The address bar is now at the bottom...
As someone with a large phone I appreciate this, but if you don't like it you can change it back to the top in settings.
cheat () {
curl "cheat.sh/$1"
}