❤️ web dev, design, data viz, tools for thought, ML + novel uis
📗 Data Visualization course & book http://fullstack.io/fullstack-d3
✨ R&D @GitHubNext, views my very own
| home | wattenberger.com |
| 🐦 | twitter.com/wattenberger |
@nrchtct @darth_mall @kristinHenry right! I was limiting my list to only instances who choose to have publicly available timelines, although I can see how that might not be mutually exclusive with instances that don't want to be found.
It seems like the best way is to have a solely opt-in site that makes it easy to understand the options, although the trick there is the usual: a lot of work needs to go into going and getting enough opts-in for it to be helpful
@darth_mall @kristinHenry perhaps it would be helpful to make it clear that I was only using public endpoints and not using any information private only to members. I have been working with data for a long time and do have _some_ idea of privacy 🙂
thank you for the info and especially for that last point - I can finally understand how blocking an instance might be a logical response.
@kristinHenry @darth_mall that's definitely not something I want and I'm not going to pursue this, as I mentioned before.
Maybe I'm misinterpreting the word "scraping" - I was only using data from publicly available endpoints (eg https://vis.social/api/v1/instance/peers).
I would love some more detail on the specific actions that are not allowed - the last thing I want is to make anyone uncomfortable!
@darth_mall that makes total sense, and I very much want to respect everyone's wishes for privacy.
In this case, I don't really see a good path that makes it easy for people to find the best home for themselves on Mastodon. for a side project, I couldn't get enough data by only mapping instances that opt in. Thanks for the info & perspective!
I very much believe that true collaboration involves way more than just the code, and I'm really excited to explore the space more.
Check out the write-up for more detail:
What if we could embed the figma design and google docs spec? What if we could do some light task management within the workspace? Quick & easy - list out the sub-tasks, self-assign one, divide & conquer.
Could we comment on & react to edits right in the workspace, or reference specific lines of code?
And if we can layer on top a rich community of plugins, could we include other things in this collaboration? What about a set of shared snippets or a shared clipboard?
if we can have a coding environment that includes all of this context, we open the door to true collaboration.
And a fun extra: this extends to collaboration with myself and others in the future!
In this exploration, we prototyped an interface that allowed you to create a "workspace" for any thread of work (fixing an issue, adding a feature, etc).
You could share that workspace (live!) with others and layer "plugins" on top of that space
