Elementi taggati con: Friendica
Federation Statistics, List of Servers, Fediverse
Just some links for looking at statistics, list of pods, etc. First one lists Federation statistics:
There are also statistics for separate networks, e.g.:
(Does someone maybe know why was there a sudden drop in the number of total users in the middle of '15?)
List of servers on podupti.me:
List of Hubzilla public servers:
This site helps to choose a Mastodon instance (and also shows statistics):
List of Friendica public servers:
#federation #fediverse #statistics #hubzilla #friendica #diaspora #mastodon #pleroma #gnusocial #linux #gnu #gnulinux #network #socialnetwork
A symbolic donation challenge
Since you are reading this post I guess you are directly interested in the improvement of Diaspora*. As you probably know Diaspora* couldn't improve without the hard and enthusiastic work of the developers. That is why
I challenge you to give at least a symbolic â‚¬0.01/week amount to the Diaspora* developers
â‚¬0.01/week is not much. It just â‚¬0.52/year so probably you can easily afford that. I guess you throw away much more to buy some fancy junk you don't even need at all
Isn't â‚¬0.01/week too little?
Yes, it is symbolic, but it is much more than nothing.
Also it can be a lot if most of us are willing to join (especially if some of us are willing to give a bit more).
For example, imagine if just 1% of the currently registered users of the federation have been taking this challenge. That would mean about â‚¬65/week for the developers. Just 15% of the users that were active in the past 6 month could give â‚¬75/week this way. 70% of the monthly active users could give â‚¬105/week for the developers by this "symbolic" donation.
Of course, you are free and encouraged to give more. (I also do so.)
How to participate?
- Create an account at https://liberapay.com.
- Add some money to your wallet.
- Start directly donating the developers.
Please, also encourage others to join this cause by spreading the message and voting on the poll below.
#diaspora #developer #donation #liberapay #crowdfunding #freesoftware #free-software #opensource #open-source #foss #floss #gnu #freedom #privacy #poll #hubzilla #gnusocial #friendica #federation
I posted this on my #Facebook. Since Iâ€™m a newbie, Iâ€™m not certain I got all the information correct. However, I do believe I stayed true to the concept. I'll work with any critique you care to give. Be kind, please. Iâ€™m #newhere.
If anyone is interested in an open-sourced, and de-centralized, algorithm-free #socialnetwork where you own your information and it goes nowhere you donâ€™t allow, I have been taking four of the best for a test run these last two weeksâ€”I have nothing but praise for them all. They are:I am 98% certain none of my friends care about any of this. But, on the off chance Iâ€™m wrong, the Fediverse could use more people like us who do care. Thanks for listening.
#diaspora* (lowercase and stylized with the asterisk)
The first three are more akin to Facebook while Mastodon is Twitter-like microblogging network whose popularity has been growing quickly. Hereâ€™s the truly great part aside from what is mentioned above: it doesnâ€™t matter which one you choose (minor exception with diaspora*), because they are all federated. Meaning, though I use Friendica, I can see and interact with people on each of the other networks without being a part of them. Huzzah! Itâ€™s like adding #Twitter friends to your Facebook with full access from your FB profile. You can even post on their walls or send them private messages
Decentralized means that the networks run on individual servers anyone can set up (the #Federation), but still works like a social network. You choose which server you want to live on, or make your own. Each of these networks have a federation of servers which are part of the larger #Fediverse. In other words, the federations are federated, and no one person or entity owns the network.
I highly recommend Mastodon as a Twitter replacement. I would recommend the others individually depending on your needs and your level of skill.
I have not yet chosen a favorite. But when I do, I will cancel the others, because they are part of the Fediverse and multiple accounts are not necessary. However, if multiple profiles is what you need, two of them offer that capability. Unlike Twitter, where you can use different accounts within the app, here you can have one or more individual and separate profiles on one account. Easy peasy!
See you in the Fediverse!
Converse.js is a web based XMPP/Jabber instant messaging client.Converse.js can be integrated into Ruby on Rails, Django, Plone, Roundcube, Wordpress, Alfresco, Friendica and many more.
It enables you to add chat functionality to your website, independent of any specific backend. You will however need an XMPP server to connect to, either your own, or a public one.
Look at the changelog - there are many new features and bug fixes!
What's in the release?(I would not enjoy working too much in the "JS ecosystem". Ecosystem? Is this the new term for hazardous waste site?)
No more jQuery
The last straw for me was when jQuery 3 came out, and half of Converse.js's ~240 tests failed once I plugged it in.
After spending some time trying to figure out what backward incompatible changes they made and how I should update the code, I decided to instead rip jQuery out entirely.
#mozilla #opensource #firefox #nonprofit #profit #privacy
Meine Vorstellungen eines #Open-Source Browsers :
SchÃ¶n wÃ¤re es doch, wenn z.B. Mozilla.org ebenfalls auch andere Open Source Projekte wie #diaspora #friendica #gnusocial usw. unterstÃ¼tzen wÃ¼rde und sich tatsÃ¤chlich an ihre eigenen Versprechungen halten wÃ¼rde.
AuÃŸerdem : Was ich bis heute nicht so recht nachvollziehen kann, sind die BeweggrÃ¼nde, weshalb ausgerechnet sehr viele LINUX !!! Distributionen immer noch die Firma Google als Default Search-enginge ihren Usern zumuten wollen.
Social-Relay version 1.2.0
New version of the public content #relay server software. This version brings support for passing through also #Diaspora protocol Retraction messages (ie deletions of content). This is important since otherwise a post later deleted that the relay originally delivered would not be delivered. Issues exist in #Diaspora, #Friendica and #Hubzilla issue trackers to get retractions to be sent to the relays.
Next for the relay system I intend to separate the relay system documentation to it's own repository, since it's not really a part of Social-Relay which is just the server implementing it. Would love to get some opinions on various subjects there then, regarding how to proceed with things like decentralizing the relays and getting rid of the reliance on the-federation.info as a way to bootstrap lists of nodes. Preferably opinions from project admins since the decision on how to decentralize the relays has to be done the way the projects are fine implementing it.
Ping @DavÃ¬d M and @Jeremy Pope . Additionally please note the change in the requirement files. I simplified them a bit, changelog has details.
[1.2.0] - 2016-10-25
- Expose NodeInfo to allow registering relays to pod lists. Unfortunately, NodeInfo schema doesn't contain the relay software key so this NodeInfo document cannot be validated by consumers.
- Network calls now use a custom user agent
Social-Relay/<version> - https://github.com/jaywink/social-relay. Thanks @bmanojlovic for the patch.
- Relay also Diaspora
retractionand photoentities. The former follows the same way likeand commententities are relayed, ie the targets are the same as where the status_messageor photowere relayed. photofollows same rules as status_messageentities, ie according to subscriber wishes.
- Replaced custom payload sending with the new helper from
federation. This will not try to deliver to httptargets at all. This means nodes that are not using https will not get deliveries. Really, these days, there is no reason to run a public website with http.
- Removed suggestion to use
pip-toolsand convert requirements files to standard Python project requirements files. Didn't dig the workflow after all. To install dev dependencies use requirements/development.txt. For production, use requirements/production.txt, which also contains uWSGI. If you don't deploy using uWSGI, you can just use requirements/requirements.txt.