Nice. There were a few comics that I followed on Twitter due to lack of them posting other places. But it is nice to know that if I find another account that I am actually interested in I will be able to get a feed.
It would be wasteful to upload the full size image only to throw most of it away. JPEG compression is very cheap, especially at low resolutions (I assume that image search uses a pretty low-resolution source image). Doing it this way is actually what I would do for best user experience. (Not saying that they aren't doing other malicious things, but doing the resizing on the client is actually a good idea)
In fact the top one has more crop.
This is my strategy. If I can't bank on the website I find a new bank.
It would be nice if there was a shortcut to go "back to previous site". Because on one hand using back to navigate around map moves is often very convenient, but sometimes I want to go to the site before the map. Having a two-level history with page and site would be super useful.
This is a case of the streetlight effect. Evaluating the skills needed to do the job is very difficult in an interview setting, so most of the focus going on evaluating skills that are easy to evaluate in an interview (such as people skills).
It isn't wrong, as all else being equal it is still better to hire the person with better skills that you can measure but obviously is not a strong evaluation of candidate quality.
#1 items should be backups. (Well maybe #2 so that you have something to back up, but don't delete the source data until the backups are running.)
You need offsite backups, and ideally multiple locations.
That isn't what that document says. It says that they can impersonate you in non-E2EE scenarios. The clients I use warn me when a message isn't properly encrypted so someone without E2EE keys can't impersonate someone in an E2EE room.
That being said the general concept is a problem. I would love to see progress where all events from a user are signed by a device key and non-forgable. There is some thinking about this with portable identities (such as MSC2787) where you server is basically just storing and forwarding events but the root of trust is your identity and keys that you control. But none of this will land soon, not for many years.
Probably yes, it depends on your threat model.
If you are using E2EE on a matrix.org account then your message content, attachments (images) and most other traffic isn't accessible to anyone but the people in the chat. However Matrix isn't the most private option, it has a number of leaks such as reactions and chat topics (these are being worked on but aren't close to happening).
For most people Matrix is a very private and secure option and the fact that it is federated is a huge plus. If you want something more secure you are probably looking at Signal (which you don't want to use and isn't federated) or Simplex Chat (which doesn't have multi-device support).
There are local readers, that fetch the feed directly from your device, but many use backend servers for the feed fetching. There are a handful of possible reasons:
- Cross-device syncronization.
- Save battery by checking on the server and only waking the device with a push notification when there are actually new items.
- Obey platform background activity restrictions (especially on iOS)
- Privacy by hiding your IP from the feed operators.
- Avoid missing items on busy feeds when your client goes offline by checking constantly from the server.
Yup, first-past-the-post strongly pushes two primary parties polarizing politics to just the right and left with no nuance on individual issues. Then both sides end up being corrupt anyways and doing what they want, but no reasonable parties can make their way up the ranks due to strategic voting to avoid the spoiler effect. So the crap just festers.
You can sue anyone in Canada as well. That doesn't mean you will win, or that the judge won't throw out your case before it starts.