Event JSON
{
"id": "96c30dd8dac8133f846d1dc4124ffecda9728baeb41d47235b7bc8f32b003dc7",
"pubkey": "a878e3c29369b8c75c10f91dea5341ca900b0c7d77de4c89c575f3401af3e747",
"created_at": 1705491358,
"kind": 1,
"tags": [
[
"p",
"0e90f5fbf4f39c29a80784b05bf0a59f6be9c1d80f8354a50a453b18d2f17b0e",
"wss://relay.mostr.pub"
],
[
"p",
"d5831d273adff61a271c4bc6fb0a4d9ce9ebaffac20c926f2774e32f8b5d3f00",
"wss://relay.mostr.pub"
],
[
"e",
"687be79815b6510bdad688ad1f7468843007d2588a017ea5be4d0c1e54bde67b",
"wss://relay.mostr.pub",
"reply"
],
[
"t",
"debian"
],
[
"t",
"gitlab"
],
[
"proxy",
"https://social.masto.host/users/praveen/statuses/111771081669668079",
"activitypub"
]
],
"content": "nostr:npub1p6g0t7l57wwzn2q8sjc9hu99na47nswcp7p4ffg2g5a335h30v8q520242 So you get security update for any bundled dependency only when gitlab updates that dependency in the bundle. In our case, when these dependency updates are shared across 1000+ #Debian Developers and any security update we make for a #gitlab dependency is also benefiting everyone else. Basically these are two different approaches. What Gitlab Inc provides is an approach that puts each project as the center, whereas our approach puts an entire distribution at the center.",
"sig": "dd4ba4db198f71b9f4a123aba3f10207021a4e6cb3a945dde170775ba15ebe4ea4bf333f3b8c18fe0026db512ebf0e70e6de63eba904a05753d61a88414092b5"
}