I'd disagree with "most messengers" doing that, in my experience, most don't do it by default. Signal is a pretty rare exception to do so by default.
What messenger doesn't? Signal, WhatsApp, Matrix, Snapchat, Discord, Telegram, etc. I'd say "most" is pretty accurate. No idea what Wechat does, but that's a whole different story.
If you get a push notification on your phone, everything you see in that notification must by definition pass through the push notification service.
Also not true. What you "see" could have been retrieved post-notification, as described in the message you responded to. What you see has nothing to do with what goes through the push service and is a full technical inacurracy.
The push notification for most messengers is a ping with little to no data in it, telling the app to grab messages directly via TLS. That's how e2e works with push.
The ones you speak of don't regret their vote, and never will, so I have no need to address them as it relates to the statistic. Also, ignorant doesn't mean dumb. Lastly, I'm glad you feel your third-party vote had an impact, vs voting in primaries to push the right candidate that could succeed. (if one happens).
Read that, then look at how small election splits are. This is a good thing.
Do we get frustrated and angry as we wish everyone who defaulted to voting right because their parents did and they don't know better and can't be bothered to read real news? Yes.
Should we be happy when enough people show change to be visible on the horizon? Also yes.
No, it's not. That just means a birthdate field next to name, address, etc, is coming.
Just because systemd said "Guess we will roll over and add this in" doesn't mean Debian has to use an extra demographic field, of which they didn't use all of them to begin with.
On a good note, this was expected. It was part of a plea deal where he only had to serve 6 months of 10 years, the rest as probation. This was also just the criminal result, the civil suit is still ongoing, and so far the victim seems pleased with the overall outcome.
If a snap is bundled with it's own dependencies (the point of snap), those dependency libraries are not loaded into shared memory. Multiple apps that would typically share a loaded dependency must now each load them into RAM.
Yea, I run Gitea for my personal work and we run our for our business, mainly because I started before the Forgejo fork. At some point I'll migrate over.
I have been debating on making a home page out of my core service bookmarks. Have you explored many options? At one point I just considered making an HA dash
This is from a third-party tracker, who took the downtime of every GitHub hosted service and added them together. So a bunch of stuff that was down 0.5% of time and/or some beta+new release services down for longer make it look way worse than the core service uptime actually is.
At its core is MEMORY.md, a lightweight index of pointers (~150 characters per line) that is perpetually loaded into the context. This index does not store data; it stores locations.
Actual project knowledge is distributed across "topic files" fetched on-demand, while raw transcripts are never fully read back into the context, but merely "grep’d" for specific identifiers.
This "Strict Write Discipline"—where the agent must update its index only after a successful file write—prevents the model from polluting its context with failed attempts.
For competitors, the "blueprint" is clear: build a skeptical memory. The code confirms that Anthropic’s agents are instructed to treat their own memory as a "hint," requiring the model to verify facts against the actual codebase before proceeding.
Interesting to see if continue.dev takes advantage of this methodology. My only complaint has been context with it.
Feels about the same but bigger, niche communities have a bit more content. If you feel like the uniqueness disappeared in a few months, social aggregators are not for you.
What messenger doesn't? Signal, WhatsApp, Matrix, Snapchat, Discord, Telegram, etc. I'd say "most" is pretty accurate. No idea what Wechat does, but that's a whole different story.
Also not true. What you "see" could have been retrieved post-notification, as described in the message you responded to. What you see has nothing to do with what goes through the push service and is a full technical inacurracy.