OSP TEST - From Tactic to Strategies

etherpad link: http://pads.osp.kitchen/p/in-betweenmediapads-viktor

Quote

quoteAymeric tells us about this “eurika” moment of his, recently: “what we are going on is not a repeat of 10-15 years ago!”. This is the “Musk-Twitter” moment, which can be described as such: “Lurk is composed of people not so much engaging in sharing infrastructure and software, as it is of a community that wants to participate in an infrastructure of healthy, sensical discussion.”

There are “ethical considerations when using software: such as energy, exploitation of workers, government surveilance, …”. On the other hand, alternatives often remain hypothetical, are often not “production ready”.

Relevance

relevance

We start the last session of the first day as a dive into the more complicated political questions: the how to reclaim the internet,Be differentorganize ourselves collectively in this undertaking. Before giving the mikes to our speakers, Tommaso argues the event to be part of a tentative in building alternative tactics, and raises the preliminary condition for its success: gathering tactical knowledge about platforms, bringing it together. ThisThis is the only way to “move from tactics to strategies”, from the user to the collective misappropriation.

an interesting conference

design sprintDesign Sprints is a methodology developed by Google for iterative design research: quote‘The Design Sprint is a proven methodology for solving problems through designing, prototyping, and testing ideas with users. Design sprints quickly align teams under a shared vision with clearly defined goals and deliverables. Ultimately, it is a tool for developing a hypothesis, prototyping an idea, and testing it rapidly with as little investment as possible in as real an environment as possible.’ Typically, this process of design, prototype, test, and redesign takes place within one intense sprint of five days. However, the Hybrid Pubs group sprint is spread out over 9 days in 9 months, giving more time for in-depth discussion, playfulness, and (productive) failure.

Our approach to prototype development for hybrid publications is work-flow first design, as described by Adam Hyde in Understanding workflowWorkflow-first Design: ‘To get to good technology, it is very important to start the process by not thinking about technology at all. If you frame your thinking through the lens of technology, you will more than likely end up with an expensive failure. What [workflow-first designers] are really interested in are good workflows and, later, designing technology to encapsulate and enable good workflow.’ For this reason, the exercises and outcomes described below do not primarily focus on pub tech. Instead, the goal of the first sprint day was to create a clear problem definition, and the goal of the second day was to get a clear understanding of a regular event report publishing workflow.

test

H1

This is a test?

A List:

• With
• Multiple
• items event

report