🔁 https://mrshll.uk/post/everyone-s-worried-about-covid-but-i-m-concerned-about-what-happens
Everyone's worried about covid but I'm concerned about what happens when we encounter covego and covsuper-ego... (I'll show myself out now)
🔁 https://mrshll.uk/post/everyone-s-worried-about-covid-but-i-m-concerned-about-what-happens
Everyone's worried about covid but I'm concerned about what happens when we encounter covego and covsuper-ego... (I'll show myself out now)
🔁 https://twitter.com/ringmaster/status/821726978944409600
This is a good tweet, and a good question.
:)
🔁 https://twitter.com/csarven/status/810838130228072448
Amy shared https://twitter.com/csarven/status/810838130228072448
🔁 How to blog about code and give zero fucks
Amy liked http://garann.com/dev/2013/how-to-blog-about-code-and-give-zero-fucks/
This is really quite excellent.
Amy shared https://pandelisperakakis.wordpress.com/2015/09/09/how-to-negotiate-with-publishers-an-example-of-immediate-self-archiving-despite-publishers-embargo-policy/
the problem of restricted access can easily be solved using existing infrastructures and with a small additional effort on behalf of the authors or their librarians - Pandelis
If you are Web savvy, it is a 'small effort' to self-archive your work in a space you control. But not everyone can manage that. And then, feedback, reviews and collaboration also in a space you control is no 'small effort'. Linking to and from specific parts of other research is not trivial when reports and results are missing fine-grained open identifiers. Maintaining your reputation and tracking the effect of your work (so that other researchers and institutions take you seriously) is no 'small effort'. Searchability and guaranteeing long-term persistence is no 'small effort'. There's still a way to go on both the infrastructure and cultural fronts here.
The (Social) Web has most of the pieces. They just need putting together.
That's what we're working towards with #LinkedResearch.
🔁 https://twitter.com/csarven/status/788261926409150464
Amy shared https://twitter.com/csarven/status/788261926409150464
🔁 https://twitter.com/philarcher1/status/778515246109646848
Amy shared https://twitter.com/philarcher1/status/778515246109646848
Vocabulary development and maintenance, W3C namespace control. 15:30 today, room 1.04 at TPAC2016- Phil
🔁 https://twitter.com/lescarr/status/777875047914561536
Amy shared https://twitter.com/lescarr/status/777875047914561536
Post-platform sociality? @w3c working group on Social Web Protocols for decentralised social systems - @lescarr
🔁 https://twitter.com/csarven/status/777488215020306432
Amy shared https://twitter.com/csarven/status/777488215020306432
Heading out to W3C TPAC2016 to fix and break things for the future #WebWeWant . If anything breaks, the person next to me did it.
🔁 https://twitter.com/csarven/status/775368043094573060
Amy shared https://twitter.com/csarven/status/775368043094573060
This is super important and exciting development for decentralising and owning your notes, comments and annotations!
You can use dokieli to publish your posts and articles, which provides a UI to let people annotate and reply. For people with their own personal storage, they can choose to store their notes themselves. But this isn't many people, so you can also provide an Annotation Service and host your respondents notes for them instead (lowering the barrier to annotating, without locking them in to your platform permanently).
"⚙ #UI to 💾 #WebAnnotations @ annotationService & #LDP #Solid personal storage https://github.com/linkeddata/dokieli 🌟 #LinkedData"
- @csarven
🔁 https://twitter.com/RonDeibert/status/769879654769496065
Amy shared https://twitter.com/RonDeibert/status/769879654769496065