⛤
I think the current logo would work fine as a unicode character. I dislike the three anuses for a logo.
⛤
I think the current logo would work fine as a unicode character. I dislike the three anuses for a logo.
That’s a very specific usecase though that the majority of programmers likely will never have to face.
You’re mixing the definitions of sideloading media and sideloading apps. Sideloading media follows your definition, e.g. transfer via another local device. Sideloading apps refers to the installing of apps outside of the (pre-)installed app store, e.g. by installing an APK directly.
Better rebrand to Clownstrife I guess.
In the Netherlands 112 is fine, most critical systems are. It’s mostly airports that are getting fucked by this it seems.
Banks and PSPs are fine here too.
The PR had some issues regarding files that were pushed that shouldn’t have been, adding refactors that should have been in separate PRs, etc…
Though the main reason is that Signal doesn’t consider this issue a part of their threat model.
Both WhatsApp and Signal show the same amount of chats to me (9 for both). WhatsApp does show a small sliver of a tenth chat, but it’s not really properly visible. There is a compact mode for the navigation bar in Signal, which helps a bit here.
From what I can see there’s slightly more whitespace between chats, and Signal uses the full height for the chat (eg same size as the picture), whereas WhatsApp uses whitespace above and below, pushing the name and message preview together.
In chats the sizes seem about the same to me, but Signal colouring messages might make it appear a bit more bloated perhaps? Not sure.