Why did indymedia project fail and how do we mediate these issues in a reboot

hamishcampbell commented

2020-01-18 09:36:45 +00:00

(Migrated from unite.openworlds.info)

This is a space for new people to talk about these issues.

ajeremias commented

2020-01-18 11:03:11 +00:00

(Migrated from unite.openworlds.info)

why you say it failed? I got so many information from all indymedia websites all over the world, during all this years.. i don't get it.. what failed? can we start on that?

hamishcampbell commented

2020-01-18 11:16:55 +00:00

(Migrated from unite.openworlds.info)

The is background here https://unite.openworlds.info/indymedia/indymedia-reboot/wiki/ether-pad-archive

ajeremias commented

2020-01-18 11:38:29 +00:00

(Migrated from unite.openworlds.info)

For me it becomes every time more clear that what indymedia needs is just small automatic cross-posting and maybe using apis/embbed to connect all different networks in a single place indymedia...

for instance... i create a new node for indymedia.. it installs:

a blog page
a mastodon page
a peertube page
pixelfed?
mobilizon

from the indymedia gui, i would be able to insert blog posts, videos, images, etc... blog posts would be hosted in a blog federated place and taken by an api, to the indymedia website, mastodon would just send a new notification with title a little excerpt of the history, peertube would receive videos, and pixelfed images, mobilizon for the calendar and events... is not this? other approach would be to host everything in a hubzilla page, but i believe this is way more complex, hubzilla is trying to solve too much in a single place.

I don't understand the pleroma-FE approach, need more input :)

For me it becomes every time more clear that what indymedia needs is just small automatic cross-posting and maybe using apis/embbed to connect all different networks in a single place indymedia... for instance... i create a new node for indymedia.. it installs: - a blog page - a mastodon page - a peertube page - pixelfed? - mobilizon from the indymedia gui, i would be able to insert blog posts, videos, images, etc... blog posts would be hosted in a blog federated place and taken by an api, to the indymedia website, mastodon would just send a new notification with title a little excerpt of the history, peertube would receive videos, and pixelfed images, mobilizon for the calendar and events... is not this? other approach would be to host everything in a hubzilla page, but i believe this is way more complex, hubzilla is trying to solve too much in a single place. I don't understand the pleroma-FE approach, need more input :)

❤️ 1

hamishcampbell commented

2020-01-18 12:06:34 +00:00

(Migrated from unite.openworlds.info)

That is kinda the plan, have a look at the images.

With the #OMN we go one stage further and build a distributed shared metadata enriched data soup.

Our apps are a ladel and the internet is a semantic web cauldron.

It's an interesting project built largely with existing tools and open standards #4opens

That is kinda the plan, have a look at the images. With the #OMN we go one stage further and build a distributed shared metadata enriched data soup. Our apps are a ladel and the internet is a semantic web cauldron. It's an interesting project built largely with existing tools and open standards #4opens

ajeremias commented

2020-01-18 13:09:55 +00:00

(Migrated from unite.openworlds.info)

i added this when editing:
"I don’t understand the pleroma-FE approach, need more input :)"

i added this when editing: "I don’t understand the pleroma-FE approach, need more input :)"

Rows
Columns

Why did indymedia project fail and how do we mediate these issues in a reboot #4