EVIL – At the stinking end you have the #dotcons with full on technicology and privacy nightmare. Facebook messenger, whatsapp (facebook) and telegram (who lies) imessage (just trust us)
NEUTRAL – At the next stage you have the ethical, good technologically working, socially problem apps like signal (king who dose not federate) and matrix (a non-industrial #NGO standard who kinda federates)
GOOD – Then you have the usable, but complex good tech like modern jabber/XMPP that ticks the boxes but still suffers from the #geekproblem
Then you have the #geekproblem with IRC and blockchain spam.
Or for a less “moral” view on the same subject, a post from the #openweb
You could have a chat compass. Centralized/decentralized on one axis, Open/Closed on the other.
What we are pushing at the #OMN is x10 to hard for normal people to use. When we outreach meany people come aboard to try and push onto the project 10x harder to use tools than what we push – this is the #geekproblem expecting people to user tools that are x100 times harder to use than the tools the #dotcons offer them for “free”
This destructive behaver has to stop.To have hope of a #openweb reboot., lets try and be human as we have piles of shit to shovel all ready without adding more.
If you would like to help with moving away from this current world/media mess please create an account: https://unite.openworlds.info this is the organizing space, yes this is to complex and needs to be made simpler and more #KISS but for now it’s what we have and works fine. Have a read through the issues and wikis on each #openweb project.
We have a public chat room here where you can get to know the crew and talk about the projects. Yes we know its complex, but agen it does work – here is a “easy” link for android phones https://firstname.lastname@example.org or you will have to be geeky/ask for help and work it out from here: email@example.com for other platforms.
Sorry about this it’s the #geekproblem that we are working to mediate and with your participation we CAN build useable tools.
If you feel you cannot help with tech/user side then you can support the core project with money here https://opencollective.com or if you don’t have money (we all understand) turn up and make tea at your local protest camp to talk about the #indymediaback#OMN project.
Q. under what circumstances Tor can handle streaming video?
A. What Tor can’t handle is lots of people consuming lots of bandwidth simultaneously. There’s no clean way to load balance and everyone is at the mercy of independent relays.
A. We’ve been saying for years not to run BitTorrent over Tor, because the Tor network can’t handle the load
Interesting most people talk about security/privacy and only respect for the commons as an afterthought – this is clearly a #geekproblem
Q. I2P is run by volunteers and encourages the sharing of videos. The internet is a Commons and depends on trust, not just Tor. ISPs have Fair Use policies etc. If not Tor maybe this person can share over I2P.
A. This one kinda fails one of the #4opens – open “industrial” standards. Only people who went through the process of installing bad UX code could watch the videos so not a good outreach project. The is a resion we are building out a OPEN media network. Worth thinking about this issue “It easy to keep crossing wires with “media” vs. personal. Media should be open, with clear sources, except when protecting them. Whereas personal data should default to private”
1) One of the main ones is co-option by #NGO agender, both, by organizations who push for “common sense” #dotcons paths and individuals who strive to build their careers by trampling over the grassroots horizontality.
2) Second, I know a lot of people who would fuck over the future for petty personal grudges and narrow self subsistence. It’s a problem with rolling out positive grassroots projects like #indymediaback that we need to actively mediate for a good outcome.It’s interesting to think about this at a small personal scale and the wider social issue of #stupidindividualism and the #deathcult that breeds this.
3) Third, let me say something unfashionable, am a fan of liberals, they created meany of the good social things in the world. BUT Intolerant and dogmatic liberals are a constant drain, pushing of “common sense” agender over every issue they touch. This shit smeared problem needs constant mediation.
4) Fourth, the #geekproblem which is looked at in other posts on this blog – click on the hashtag to find them.
5) There are more please comment so i can add them.
In web application development there are 3 groups you can empower and it’s important to understand which group you are empowering.
1) the users
2) the producers
3) the geeks who develop/admin
Most #geekproblem coding is about the 3ed grouping taking all the power to decide. We, tiny, “elite” know what is good for you “passive” masses. This is why most #openweb codebases are unusable, because obviously they simply do not know, good UX in social tech is hard.
Most #dotcons empower capital who pay the geeks to “serve” the producers to enslave the users. In this they are an interesting evil hybrid.
I can’t actually think of an example where the users are actually empowered off the top of my head – ideas please?
Good #openweb projects try to empower the producers/user they are not meany of these. Can anyone think of examples, we need a list.
Obviously we can’t keep repeating the first two shit outcomes as they are already piles of stinking manure everywhere from the last 20 years of this tech mess. You have/need a shovel #OMN
Thinking on the modern UX for the #indymedia reboot. Tabs are a line at the top of the page – metaphor is not buttons. You are switching sheets of paper. The page is the paper. The top banner is the desk under the paper. It’s an interesting challenge to think through metaphors.
Using buttons you are outside the desk/paper metaphor so it’s a whole different thing, to mix them is not KISS and confusing. You are into early computer metaphors with the buttons – think mainframes. We are a “newspaper” so the tabs and table and paper sheets make a feeling for the project. Always echo back if you can for a project that is based on a solid past.
For new stuff “invention” is good and there will be lots of space and growth for this when the #OMN is up and running…
One thing the fediverse taught us is that copying existing successfully projects is a root out of the #geekproblem that #fashernistas embrace. So this up to a point is the right thing to do for social change. We for the first time put a spin on it by rebooting a radical grassroots social tech project. But behind this is something much more radical. The #OMN lets see if we can plant and nurture a seed. Think the soil is a little dry pastime for some compost, get your spades out.
The “newswire” used to be open publishing we now add a switch trust/moderate to this wire. The UK indymedia site did something similar latter in its life. Its up to the “editorial collective” to flip this switch for site/accounts/tags etc
The central “fetures column” is newswire articals promoted to a feature. These are written by the “editorial collective” from text and media resources from newswire posts.
Both are news flows.
In journalistic terms the newswire is “breaking news” that flows past fast. It might or might not be true/accreat in real time but will be relatively accreat over time. Its “citizen journalism” in that horrible liberal term. Grassroots reporting maybe better term.
The “feature column” is more like tredtional journalism. Facts are checked, spelling correct, sound in audio good, videos stable etc its the best of the newswire collected and put into context by a group of “citizen journalists” this moves slowly so articals stick around for days/weeks.
The moderation stream is not visible to non “editorial collective” people.
The value in the OMN idea is a social feedback loop to push federation to a lowest level, grassroots. The 5 functions: link/trust/moderate switch is key to this social outcome.
The OMN use of these 5 functions as a strong political/social protection against political infighting/tribalism and mediating the #geekproblem by removeing the levers of control from the programmers/admins and giving them to the producers.
From my long experience in the delight and mess of grassroots media/tech, with out the last two “social tech” paragraphs the project has zero chance of working.
A sideways look at the death of UK indymedia and things to learn for its reboot.
With federation, we don’t have to go down the path of a “virtual silo” this issue was one of the reasons indymedia was ripped apart. The desire for security, privacy and control of having it all on one server controlled by the “elite” geeks compared to having lots of different servers controlled by different groups. The final rip that killed UK was this very issue.
The fediverse is the reboot of the loose network based on trust and clearly against the centralized silo based on control
Not sure if the is a good history on this, most indymedia history is crap so best to go back to the original source. Think a lot is on archive.org
Q. Should IMC self-hosting be based on something like freedombone – easy to install, maintain, etc
A. Yes… though to seed it as a testing roll out we can host a few before passing um onto the community’s. But the idea is the same as freedombone which is a fab project. BUT as a outreach tool has real imitations due to ISP’s and crap routers in peoples homes, me and me brother tom (who is proper geeky) spent 3 days trying and failing to get it running, a little to do with freedombone and a lot to do with his rooter refusing to do port forwarding reliably.
As with everything OMN we take all paths, for the hyperlocal:
* Home install fab (but likely complex)
Bashrc is likely to add the indymedia server to freedombone so that’s the home install covered
* Community local install, good but could fall for the #geekproblem
Is for the geeks, so they can sought it out for themselves from the sourcecode.
* Easy VPS script – good anufe likely it will work
This one we have to make easy, but this is not a priority till after the test rollout.
* us hosting it on a central server bad but probably the right thing to do for the test rollout.
Is actually the second one just done badly 😉
Todo for the test rollout
* Get the peertube (@RCS currently AWOL) and searx (@jolek78) with @sanders making it happen back online and updated.
* Get a test instill of hyperlocal code to give feedback (@bashrc)
* find small community’s for test rollout, have lifeboats IMC, and a few others in mind (Hamish)
Give us a shout if you have ideas or connections on these.
The project i like to point to as an example. The indymedia project an early alt-media network that spread the use of open source software and #4opens organizing around the world at the turn of the century. In the UK the was a #geekproblem vs #openweb fight that became nasty over what we would now understand as “activertypub” the fedivers vs more centralized silo approach. In the UK you can see this stress point fought as a proxy war over #RSS
The #openweb aggregation side were sold a dud by the #fashernistas being swayed by the #geekproblem It was obvious that the project had to change and move away from central servers to a more aggregation model. BUT the movement was torpedoed by an obviously pointless opensource project instead of implementing a existing standerds based RSS they created there BETTER, BRIGHTER flavor which was of coures incomparable with everyone else.
This is an example of a “better” but obviously pointless open source project and also destructive behaver. The #indymedia project in the UK was ripped apart internally from this same devide in the end. A bad “open source” outcome. You can find similar behaver today in the fedvers if you look.
Its a intresting thing to look at. Actually you can see 3 active sides in the internal uk #indymedia mess and important to see the outcome that they ALL LOST in the end.