-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Junkyard? #5
Comments
it should be moved to the junk yard because it's no longer being maintained. it's theirfore confusing to see it with the stuff that is still actively used. my recollection is that @mmckegg received a grant to work on this but then decided he was more motivated to do general maintenance, and this got left on the back burner. There also has been various discussions since then about other approaches. Is moving something to the junkyard hash? of course there is a certain sadness that something which was potentially cool didn't get used, but it's better to accept that and get on with things. We learnt something from this, so it didn't get shifted to the junkyard in vain. |
I reckon everyone should try to implement same as to find out what a pain it really is 😅 I actually got really close to something that kind of could have worked (combined with the patchwork PR), but it was badly designed, and didn’t handle many edge cases (or the actual user interface for doing the merge). Now I’m a firm believer that the best way to solve sameAs is with virtual feeds built on top of tangles. Merging together multiple feeds without the causal meta data is just too nasty. Meh. This stuff is hard. |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? |
For people reading along check out the module ssb-profile
I think it might good a good basis for gathering identity info for multiple
feeds
…On Sat, Dec 7, 2019, 14:35 stale[bot] ***@***.***> wrote:
Is this still relevant? If so, what is blocking it? Is there anything you
can do to help move it forward?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAUK3HX3WNLG6SW7XOEUWD3QXL4XHANCNFSM4IUPMIPQ>
.
|
sounds harsh ... it's good to know this exists ... but perhaps we also need to know why it didn't work. Is it just that getting it mainstreamed would be hard, or is it fundamentally a problematic solution?
The text was updated successfully, but these errors were encountered: