Event JSON
{
"id": "1a45dc077e2c2d01d7fd8b9d0d68876b81d64993d907fc8d51bc4ceeec46d0c4",
"pubkey": "eb5fdbb085d57d03273b8b8ecd3be2016096d89ecee4f596cde0771ac9eee876",
"created_at": 1697830501,
"kind": 1,
"tags": [
[
"p",
"e06c1f25be1e23f1c90a88ce823dd8f2a2c167db37cd429ebc5e85c1c8414d0d",
"wss://relay.mostr.pub"
],
[
"p",
"26cad6f140bf86de9c26b7c15419cab1aebdd7086358d26aa2d750e21cf3bf2e",
"wss://relay.mostr.pub"
],
[
"e",
"d1546ca860202328cebd5977396095d5467fa809483be27f8f21168d909f0ad3",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://layer8.space/users/RyunoKi/statuses/111269019776829588",
"activitypub"
]
],
"content": "nostr:npub1upkp7fd7rc3lrjg23r8gy0wc723vze7mxlx5984ut6zurjzpf5xss4tcwy TIL.\n\nAnother reference that's neither a branch nor a tag could be commits that „got lost“ on a force push.\n\nYou should be able to `git show` them until the next cleanup/garbage collection.\n\nIn a way, that's reassuring because it's hard to break git.\n\nOn the other hand this proved to be a security hole (by downloading a publicly available .git from the Internet of a proprietary codebase - https://blog.gitguardian.com/secrets-credentials-api-git/ is one aspect)",
"sig": "3c49f6c92e73a2e456862deb3d944b90e2825ee32b3e5c5835ad99e41f7fce8ed48e8320c2bbe703c2075a8c8fcaf3b2a20fc56f7bd2d213e42fcdeb253da36d"
}