Activity, over time
Daily observations from the public event archive.
Attention
Daily stars & forks
Star accumulation
Cumulative stars
Pull requests
Daily opens & merges
Conversations
Daily issues & comments
Community
Daily accounts & reviews
Releases
Daily releases
Trending history
Daily top 10 · last 90 days · UTC
Mentions
Stars
Forks
Contributors
Latest stargazers
The last 10 distinct accounts we observed this year.
Most active participants
PR, issue, comment & review events in the past year.
Packages
Scan pending.
README badges
Embed a badge in your README or website.
Live mentions · last 30 days
Mentions
Or this case we encountered, where on iOS Signal apparently corrupts its sqlite DB, leading to loss of all messages. Signal-iOS#5813 Interestingly here, the sqlite DB would be trivially fixable, and messages restorable, with the `sqlite3` CLI. But there's no way to get at that sqlite DB file. Even if you change Signal's code to add a feature to export the DB, it apparently cannot see your DB, because iOS sandboxes that so that it is only visible to Signal builds signed with the Signal developers' keys. So that means your messages are all there, on your device, running open-source software, and yet you cannot get them. This cannot have been the intention of Signal being Free Software. Where is "change it to make it do what you wish (freedom 1)"? (I do not use iOS myself but have friends suffering this issue. Everybody involved is programmers and yet we seem to be able to do nothing about it.) So it seems that even though the messages are on the user's device, it really is the Signal developers who "own" that data, and have the exclusive and ultimate control over it. Makes me wonder: Does this mean users suffering this need to GDPR-request their data out from Signal?