DEPRECATED
For now, I might still be active here on occasion, but for timely interaction (@mentions, answers, or private messages) please use my main feed instead.
❤️ | 😡
%v94nUmPPiYoMYR00+02HbbeWW9UkNIFBqfN9jUDTvfQ=.sha256{
"type": "about",
"about": "%Jg9QUXtWXQQHgGNUvnkBzulHl6XflXU74I/z8Ino9yE=.sha256",
"attendee": {
"link": "@Bk5uzkFxdMJnJR+rKVd+X4LO/u+8VV+lA14e+XLabXQ=.ed25519",
"remove": true
}
}%/HgRi28+6xWKKWrQHkblvmn1Z4RSE1PhL5tspZVYtVE=.sha256%SjTyEwh5ASRu2g9T4I5+9V5TfNFDdEHW+pZglaHwpE8=.sha256%kfrDAd6Q2/2Jc52tMPAGuTz+7xCtIBZqeZ08yFMaZ4Q=.sha256{
"type": "about",
"about": "@Bk5uzkFxdMJnJR+rKVd+X4LO/u+8VV+lA14e+XLabXQ=.ed25519",
"name": "Daan (deprecated)",
"description": "**DEPRECATED**\n\nFor now, I might still be active here on occasion, but for timely interaction (@mentions, answers, or private messages) please use [my main feed](@MRiJ+CvDnD9ZjqunY1oy6tsk0IdbMDC4Q3tTC8riS3s=.ed25519) instead.\n\n❤️ | 😡"
}%tetW+r8UwSPJ47tCI4BryPF4Ulr2MOAckUW/RpgX1Gs=.sha256{
"type": "about",
"about": "@Bk5uzkFxdMJnJR+rKVd+X4LO/u+8VV+lA14e+XLabXQ=.ed25519",
"image": "&/xdDoI1qrE5eV2hmBZzOz1Am6yewPP3HklsVFSjKRU0=.sha256"
}%m//FmczyTLm9oXEpO7ZSmDjKu/fyu9j7rC3uJhs4+2k=.sha256Deprecating This Feed
All passengers please leave the ship.
TL;DR: use my main feed for contact from now on.
Dear all,
as previously announced I will be terminating this feed in the near future. For now, I will not formally terminate it, since I will still have access to the machine hosting it and the protocol for termination has not yet been decided on.
I will be waiting to see if any new input to this emerges out of the currently ongoing discussions of feed formats, tangles, etc. In the meantime, please be advised that @mentioning this feed, or sending private messages to it, will likely not result in a timely response.
If you want to be reasonably sure that I see your response, mention, or private message, please address it to my main feed!
%X46nEoAovbJ3VR6mc8gmOi+/IdpAQGiqBu0Epeun6S0=.sha256On the one hand I want to ask for that to become a use case. On the other hand.... That just encourages risky behaviour :D
%G32IzpsnNlaF4zz16tL0nHxQ+eWcpYu5DfGAt3Aw/+E=.sha256there is a thing called ssb-lan?
I'm not sure how #ssb-conn handles the case where there is a local peer with the same feed id. I launched a different identity for debugging and it showed my laptop on the local net just fine, and I had to click "connect" in the sidebar to gossip. I don't see that now that they're both running the same ID again. Maybe that's a special case?
%DhqL+oaINuSY4EtbNrg9FVrCZFo4Dowl9Q1FYLwPRxo=.sha256Show whole feed