339 karma · joined January 12, 2012
If I'm at the computer, I prefer to read and/or scroll an article. If I'm on the move, listening would definitely be better.
* `inlinehashes`[1] - To help build the CSP of websites that I don't control the source/development.
* `worker-ddns` [2] - simple DDNS solution using cloudflare workers
* `kinspect` [3] - a web tool to quickly inspect PGP keys without importing them to my keyring.
[1] https://github.com/dethos/inlinehashes
I also get that feeling. It seems it is now fashionable to take down anything that might change things (I'm not saying that all change is good). Change resistance is something that always existed and we are already used to, but somehow this looks a bit different, more ideological.
It doesn't focus on a single topic, it mostly contains things that I feel I should share.
However, to be sincere, I'm not a huge fan of element and this client look great indeed.
Is there any standard for this integration/interoperability? What about moving from one provider/app to another?
The rest are RSS feeds of blogs and other sources picked by myself.
> this is how Electron auto updater works under the hood (checking for update = downloading it)
Electron auto updater seems too raw, for an app that has a decent size.
> I did change it now to 3 hours.
In my opinion, it is still too frequent. Ideally, the user should be able to set his preference and the app should have a less aggressive default (once a day seem more than enough for most cases).
Given Google's track record, I think it is a sensible evaluation of the situation.
Nowadays I can't stand an environment without the sane defaults and powerful customization capabilities we can find in Plasma/KDE.
A big "thank you" to all KDE contributors.
Email has "instances" that act as gatekeepers. Gmail is one, Outlook is another, Fastmail is...
They are both federated systems and on these systems (email, fediverse, matrix, xmpp...) end users have accounts on servers that then connect between themselves to create the whole network.
The only difference is the underlying protocol and/or the main purpose.
It basically contains a blog and a few pages about other content that I publicly share.