Skip to content
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

Open
mixmix opened this issue Sep 7, 2019 · 4 comments
Open

Junkyard? #5

mixmix opened this issue Sep 7, 2019 · 4 comments

Comments

@mixmix
Copy link
Member

mixmix commented Sep 7, 2019

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?

@dominictarr
Copy link

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.

@mmckegg
Copy link
Contributor

mmckegg commented Sep 8, 2019

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.

@stale
Copy link

stale bot commented Dec 7, 2019

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

@stale stale bot added the stale label Dec 7, 2019
@mixmix
Copy link
Member Author

mixmix commented Dec 7, 2019 via email

@stale stale bot removed the stale label Dec 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants