Event JSON
{
"id": "8674c78826581d75bbca48960fce404ae75d3a377878066e0c2a65bd5e227260",
"pubkey": "4d8f55e60182873c271f69742433c5c3824cc40c6f13dfaeb9baa599d59dd6a7",
"created_at": 1775685499,
"kind": 1,
"tags": [
[
"t",
"veracrypt"
],
[
"t",
"windscribe"
],
[
"t",
"wireguard"
],
[
"proxy",
"https://social.tchncs.de/@gborn/116371324882346259",
"web"
],
[
"proxy",
"https://social.tchncs.de/users/gborn/statuses/116371324882346259",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://social.tchncs.de/users/gborn/statuses/116371324882346259",
"pink.momostr"
],
[
"-"
]
],
"content": "Microsoft hat Konten von #VeraCrypt, #WireGuard, und #WindScribe Entwicklern geschlossen. Die können keine Kerneltreiber mehr signieren - scheint ein System dahinter zu stecken.\n\nhttps://borncity.com/blog/2026/04/08/microsoft-kontensperren-fuer-veracrypt-und-wireguard-entwicklern/",
"sig": "814e3feca350bad2d71cd8f12b4c468b790a74359088565ee9c6285a41220c6d0c38479eb454cbe9a5cd4cd30f19e29e2b32924253987d17c019689a2da401b1"
}