1 Persons are tagged with #decentralization

#decentralization

danie10@squeet.me
Danie

The Podcast Index exists to preserve, protect and extend the open, independent podcasting ecosystem by enabling an open, categorized index that will always be available for free

Bild/Foto
A new initiative uses open source to keep podcasting decentralized and add new features. They have a documented API that will allow any app or developer to connect to the index.

The purpose of the project is to offer a sustainable alternative to individual podcast hosters who may come and go, and as an alternative to a Big Tech wanting to commercialise and centralize their offering, and often then losing interest and just shutting it down (remember Google Reader?).

There is an excellent interview with Dave Jones from the project on the podcast Linux Unplugged episode 440: Saving Podcasting from Centralization.

See https://podcastindex.org/

#technology #podcasts #decentralization #opensource
#Blog, ##decentralisation, ##opensource, ##podcasts, ##technology

3 Likes
1 Shares
One person like that
robertbenavides@joindiaspora.com
Rob

It always amazes me when people that claim to be against de-platforming and condemn the actions of anti Free Speech companies like twitter, not only continue to post to it but when I mention Diaspora not only do they have no idea what I'm talking about, but don't even put in effort to find out. This even includes long-time tech-y type dudes.

Then again, look how long its taken bitcoin to catch the public eye compared to when it actually started, and that involves money.

#decentralization #networks #centralization #bitcoin #diaspora #complainers #bigtech #smalltech #littletech #twitter #obvious #theydontlisten #freedom #privacy #freespeech #socialnetworks

danie10@squeet.me
Danie

It's time to decentralize the internet, again: What was distributed is now centralized by Google, Facebook, etc

The idea of decentralization is baked quite firmly into the internet’s architecture. The definitive paper on the internet’s original design is David Clark’s “The Design Philosophy of the DARPA Internet Protocols” published in 1988. Near the top of the list of design goals we find “Internet communication must continue despite loss of networks or gateways,” and “The Internet must permit distributed management of its resources.” The first goal leads directly to the idea that there must not be single points of failure, while the second says more about how network operations must be decentralized.

Central platforms can suddenly change policies to shift users away from the content being provided by a creator. They can also be single points of failure.

It seems that the pendulum swung hard towards centralization with the rise of a few giant internet companies controlling the way billions of people experience the internet, and that pendulum is showing signs of slowing, if not starting to swing the other way. Decentralization is a pillar of the internet’s architecture that has been fundamental to its success, and we’re now seeing a wide range of efforts to return to its decentralized roots. Let’s hope that at least some will be successful.

See It's time to decentralize the internet, again: What was distributed is now centralized by Google, Facebook, etc

#technology #decentralization

Image/photo

The idea was to remove central points of failure, not introduce them

https://gadgeteer.co.za/its-time-decentralize-internet-again-what-was-distributed-now-centralized-google-facebook-etc

6 Likes
5 Comments
1 Shares
anonymiss@despora.de
anonymiss

Disasters I've seen in a #microservices #world

Source: https://world.hey.com/joaoqalves/disasters-i-ve-seen-in-a-microservices-world-a9137a51

Going for significant architectural changes doesn't come for free. Teams started to realize that sharing a database was a single-point-of-failure. Then, they realized that separating their domains created a whole new world: eventual consistency was a thing. What about when a service where you're pulling data off is down? The number of questions and problems started to pile up. The promises of a high-speed development pace were trumped by looking for bugs, incidents, data consistency issues, etc. Another problem was that engineers needed centralized logs and observability solutions to span across tens of services to spot and correct these defects.

#software #development #economy #hype #decentralization #problem #fail #database #architecture

Disasters I've seen in a microservices world

When Martin Fowler's post about microservices came out in 2014, the teams where I worked were already building service-oriented architectures. That post and the subsequent hype made their way into almost every software team in the world. The...

4 Likes
1 Shares
1 Shares
tanakian@spyurk.am
inky, from the tape

this is a russian podcast on history of the fediverse: https://open.tube/videos/watch/db9cc76d-093c-4347-a49a-9af4246a1d92

i have to say they did a comprehensive research, or did know the history very well.
it starts with the early internet, email, then explains situation with messengers, xmpp, xml, rss, tells about aaron schwartz, and goes in to early fediverse projects, starting from identica.

in this podcast, diaspora is a tragic story. near the end of the podcast they mention the ticket to support activitypub, and that the comments were mostly not about whether it should be done, but on how it should be done. and then comes dennis schubert, critisizes the protocol and rejects the wanted proposal. then they say that diaspora is getting weaker - quantity of nodes decreases, while fediverse is getting richer - more and more people are attracted.

mastodon was mentioned as a huge success. well, it is a huge success. but they also mentioned that the project is heavy, slow, not easily deployed, has too many dependencies. most of that can also be said about diaspora. the pleroma was presented as an alternative, which is much faster, easily updated without downtime, thanks to underlying erlang ecosystem. it also supports gopher!

i did not think socialhome will be mentioned. but jason robinson was mentioned several times, as federation activist, diaspora developer, then the-federation.info author, and then they described the socialhome project in details, starting with its history. mentioned that it has very little number of nodes, and expressed the hope that it'll be developed further.

they also were talking about pixelfed, funkwhale, peertube, mobilizon, and the blog engines that support federation: write freely, plume, and that wordpress is able to federate with activitypub nodes via special plugin.

overall, very interesting, for me, listening, and a very good introduction for newcomers. thanks to creators. i am really thankful to creators, i wish the text was published, because i know many prefer to read, not listen, like me, also it would make the text searchable.

#russian #podcast #history #internet #diaspora #mastodon #decentralization #socialhome #pixelfed #funkwhale #peertube #mobilizon, #blog #rss #atom #writefreely #plume #wordpress #activitypub #federation #freedom #freedom_of_speech #freedom-of-speech #freedomofspeech #web #gopher #w3c #standards #protocol #protocols #research #listening

История Fediverse

Пересборка представляет: История Fediverse Полная версия истории социальной сети Fediverse. Ведущий - @drq@mastodon.ml Огромное...