W.Sadowski | 24 Jun 12:59 2015
Picon

unsubsribe



2015-06-24 12:45 GMT+02:00 Melvin Carvalho <melvincarvalho <at> gmail.com>:


On 10 June 2015 at 13:32, Wouter Miltenburg <wouter.miltenburg-B7ZOObYzTCQ@public.gmane.org> wrote:
Hi all,

I am a student and currently doing research in decentralised social
networks. For my research I've some questions about GNU social and I
hope the mailing list is the appropriate place for these questions.

You may be interested in :

https://linkeddata.github.io/SoLiD/

It's a new social decentralization protocol developed over 20 years at Tim Berners-Lee's lab at MIT.  It tries to invent very little, and just use existing web standards that are put together in a certain way to achieve decentralization.

I've run GNU social in the past, but now I've implemented this, and am very pleased with the results.

There is also a social web working group at the W3C which is hoping to standardize decentralized interaction between social networks.  GNU Social and SoLiD are two of the inputs, tho I think it is slightly behind on its deliverables.
 

The most important question about GNU-social is its current status. On
Wikipedia it is noted that 1.1.2 is still an Alpha release and that
1.1.1 is the stable release. Let's assume that 1.1.1 is the current
stable release and 1.1.2 is the "future" of GNU social. What will be the
aim for GNU-social and how is privacy dealt with? With other
implementations like Friendica/RedMatrix effort was put in the privacy
of the users. That's why I was wondering what GNU-social will provide
for it's users. Will private/direct messages be encrypted in some form
(or do we rely on SSL/TLS if supported by the other end)?

Will there be more advancements in federation support between different
nodes? As far as I can see you can only message someone directly, from
another node, when he/she is added to a group. Couldn't find the option
to directly post to someone's "wall" when I visited his/her profile.
More like the idea how Friendica/RedMatrix support seamless "roaming" of
the profiles across nodes.

What kind of advancements will be made to the user's profile? Will
support be added to share your photos and conveniently access it from
one place for example.

How is performance and scalability be dealt with? Do we currently queue
the messages and remove them if a node is considered "death" or when a
user's profile is removed? Do we synchronise information every once in a
while? How is consistency guaranteed when a node was down for
maintenance and we want to keep information synchronised. Is there some
kind of polling mechanism.

If this isn't the appropriate place to discuss this please let me know.
Although this information might be useful to be put in a document or
something (i.e. FAQ).

With kind regards,
Wouter Miltenburg.



Wouter Miltenburg | 10 Jun 13:32 2015
Picon

GNU-social features

Hi all,

I am a student and currently doing research in decentralised social
networks. For my research I've some questions about GNU social and I
hope the mailing list is the appropriate place for these questions.

The most important question about GNU-social is its current status. On
Wikipedia it is noted that 1.1.2 is still an Alpha release and that
1.1.1 is the stable release. Let's assume that 1.1.1 is the current
stable release and 1.1.2 is the "future" of GNU social. What will be the
aim for GNU-social and how is privacy dealt with? With other
implementations like Friendica/RedMatrix effort was put in the privacy
of the users. That's why I was wondering what GNU-social will provide
for it's users. Will private/direct messages be encrypted in some form
(or do we rely on SSL/TLS if supported by the other end)?

Will there be more advancements in federation support between different
nodes? As far as I can see you can only message someone directly, from
another node, when he/she is added to a group. Couldn't find the option
to directly post to someone's "wall" when I visited his/her profile.
More like the idea how Friendica/RedMatrix support seamless "roaming" of
the profiles across nodes.

What kind of advancements will be made to the user's profile? Will
support be added to share your photos and conveniently access it from
one place for example.

How is performance and scalability be dealt with? Do we currently queue
the messages and remove them if a node is considered "death" or when a
user's profile is removed? Do we synchronise information every once in a
while? How is consistency guaranteed when a node was down for
maintenance and we want to keep information synchronised. Is there some
kind of polling mechanism.

If this isn't the appropriate place to discuss this please let me know.
Although this information might be useful to be put in a document or
something (i.e. FAQ).

With kind regards,
Wouter Miltenburg.

Ged Quayle | 12 May 22:10 2015
Picon

Pear problem



On Tuesday, 12 May 2015, 21:08, Ged Quayle <gedq-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> wrote:


I'm trying to run gnu social on an NGinx / fpm stack and it's bombing. Error log tells me


2015/05/12 15:57:02 [error] 21885#0: *291936 FastCGI sent in stderr: "PHP Strict Standards:  Non-static method PEAR::getStaticProperty() should not be called statically, assuming $this from incompatible context in /srv/www/html/circleofpagans/extlib/DB/DataObject.php on line 4673
PHP Strict Standards:  Non-static method PEAR::getStaticProperty() should not be called statically, assuming $this from incompatible context in /srv/www/html/circleofpagans/extlib/DB/DataObject.php on line 2450
PHP Strict Standards:  Non-static method DB::connect() should not be called statically, assuming $this from incompatible context in /srv/www/html/circleofpagans/extlib/DB/DataObject.php on line 2455
PHP Strict Standards:  Non-static method DB::parseDSN() should not be called statically, assuming $this from incompatible context in /srv/www/html/circleofpagans/extlib/DB.php on line 520

and so on.  I don't want to loosen reporting.  Is there a fix for this?

thanks


Paulo Henrique Santana | 8 May 19:21 2015

Re: New server


----- Mensagem original -----
> De: "Daniel Pimentel" <d4n1@...>

> Hi Paulo and FSF team. I'm from Brazil, and I'd like help about it.

Hi Daniel, 

I'm talking to ASL to host a GNU social instance. Probably something like "social.sofwtarelivre.org"
But they asked me about hardware and bandwidth.

Best regards,

--

-- 
Paulo Henrique de Lima Santana
Curador de Software Livre da Campus Party Brasil
Tim:  (41) 9638-1897
Vivo: (41) 9198-1897
Site: http://www.phls.com.br
Jabber: phls@...
Twitter: http://www.twitter.com/phls00
GNU/Linux user: 228719  GPG ID: 0443C450

Paulo Henrique Santana | 8 May 19:12 2015

New server

Hi, 

I'm planning start a new GNU Social server in Brazil.
Can you give tips about hardware and bandwidth to start a server?

Tnanks

--

-- 
Paulo Henrique de Lima Santana
Curador de Software Livre da Campus Party Brasil
Tim:  (41) 9638-1897
Vivo: (41) 9198-1897
Site: http://www.phls.com.br
Jabber: phls@...
Twitter: http://www.twitter.com/phls00
GNU/Linux user: 228719  GPG ID: 0443C450

Adam Lake | 27 Apr 05:20 2015
Picon

Wordpress/Buddypress integration with GNU social

I am wondering how integrating buddypress(wordpress) with GNU Social would work?  I am thinking the person administrating the Buddypress community(like an ning comunity site) would essentially own that community, although there could be a variety of ownership structures, and that GNU Users could join buddypress Communities, as many as they want and that they approved(unless open enrollment) for by each Communities admin.  Perhaps there could be a drop-down Communities section in the timeline filtering already going on in the left section of GNU social where users could put a check next to which communities notification they want filtering into their timeline.  Perhaps the user could respond right from this page with notices that get sent to the appropriate section of the community site they are responding to, or if the user wants to engage in some functionality that is more complex they could click on the community so that that community opens up in a frame within GNU social--perhaps just an icon on the top of the screen that links the user back to their GNU Social timeline is all that is needed to exit the specific community and go back to their GNU timeline.  I don't have the technical understanding to know exactly how this would be accomplished but it seems to me the essential idea is to get a Buddypress instance to be a node in the GNU network such that it recognizes approved members of GNU Social as members of their buddypess site. The notifications from each buddypress community site the user is a member of would feed into their notifications on GNU Social.  

I hope this makes sense.  If this is achievable I think it would create far more value than the sum of GNU social and worpdress/buddypress.  Wordpress is open source and powerful and has a massive and growing number of plugins as well as a tremendous amount of human capital behind it. But, we need all this to exist on a distributed layer for reasons that I assume I don't have to enumerate for you all., Also, what buddypress offers is another way for GNU Social to grow--I think affinity communities make a lot of sense because people will feel the more tangible use of them in the earlier stages while the network is growing.  

Any clarifying questions would be helpful.  I

My interest is part of a larger plan help facilitate a social movement.  The required technology layer does not seem like its quite there yet, but a distributed layer is essential and I'm thankful you all are developing it. 

Any thoughts?  

--
Adam Lake
540-585-4444
Cyttorak | 23 Feb 20:37 2015
Picon

timeline api get wrongs id

Thanks
Erkan Yilmaz | 31 Jan 15:40 2015
Picon

translations for GNU social: help, suggestions, ideas...

Hello,

ideas, suggestions so far:

1. <at> catmidia suggested to update/review the EN translation first, it's from 2010 (1), then all other language teams can start their work on correcting/adding. 

2. which software to use? and where?
we could host it at translatewiki (2), or if there's already something for the various GNU projects: then there; or host a software-translation system ourselves; ...? (3)

3. what to translate? priorize?
<at> simsa0 So it's about translations of menus, headers etc. that users can see & do interact with, or about the software manuals/texts, or both ... ?
see also (4)

Please also join the group: !gstranslate (5)

Erkan



**********************************************************************************************
This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail.
Any unauthorised copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.

Diese eMail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese eMail irrtuemlich erhalten
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht
gestattet.
**********************************************************************************************
Morgan McMillian | 18 Jan 23:23 2015

Client API for social

Hello, I'd like to take a stab at doing some client development for GNU
social. Looking at the source code and other references I've found on
the internet there is mention of using a Twitter like API but all of the
links are referencing documents on status.net which no longer exist.
Particularly what I'm interested in are the API differences between
Twitter and social. Has this been documented or is it a matter of
pulling apart the source to figure it out? Thanks in advance.

--

-- 
END OF LINE

Adam Moore | 11 Jan 11:10 2015

"GNU social" sucks.

Not the project!  I'm actually quite enthusiastic about the project.  I
think it's great; I use the software every day.  I want the fediverse to
grow, and thrive, and obviate the big, closed, commercial services.

But the name sucks.

Sticking "GNU" in front of the name of piece of software buys you some
interest with a small group of computer users who happen to share a
particular set of values, but the wider world couldn't be made to care
less.  So, take the GNU away and you're left with what?  "Social."  Ugh.

"Social media" is a noxious catch-phrase.  Naming projects/products
after noxious catch-phrases makes you look *really lame*.  Imagine a
TCP/IP stack released under the name Superhighway.  Yeah.  It would only
be worse if you named it Superhighway '95.  Worse still, it's an ~old~
catch-phrase (Twitter exploded in, what, 2007?).  The term might stick
around indefinitely, but right now it's been overused, overhyped, and is
rapidly becoming quite passé.  That's not good for attracting new users,
new interest, and growing the network.

Furthermore, GNU projects have a long history of humorous, whimsical,
and punny names.  'GNU social' is boring as shit.

I'm gonna make a bold proposition, here: the name should be changed to
GNU Herds.

Now, Herds isn't the most inventive name in the universe, I know. But
it's got some strengths that "social" does not:

* It's homophonous with "heard".  As in, stand up and be herd!  Or,
   more simply, BE HERD.  That's not only a solid tag-line, but it's a 
dual
   reflection of what we want GNU social to be about: herd to signify 
unity
   in opposition to proprietary corporate media, and heard to signify 
free
   expression through free software.

* It's an animal metaphor for what the software actually does: it
   globally unifies the communications of a panoply of *local herds* 
(what
   we now call instances).

* It invites a thematically unified set of system jargon, and that
   reinforces community.  Right now we have people talking about
   "statuses", "notices", and "dents" interchangeably, all of which are
   artifacts of various incarnations of StatusNet.  All are also 
inadequate
   terms.  "Notices" and "statuses" are inaccurate -- *conversations* 
take
   place on GNU social, not just notifications and status updates -- and
   "dents" is ...incoherent.  A more general term is needed: bleats.  
(Yes,
   it's like "tweets" only less humiliating to say aloud.  And, yes, I 
know
   that wildebeest do not "bleat", but the unifying theme isn't "herds of
   gnu", it's simply "herds".)  So, a GNU Herds user might be ~grazing~ 
the
   public feed of their local ~herd~, see a ~bleat~ they like, and
   ~rebleat~ it...  you get the idea.

Also, "Herds" should be an acronym.  Better yet, it should be multiple
acronyms, because I love when the names of projects are understood to be
acronyms, but no consensus has been reached about what the acronym
actually is.  Here are some starters:

     Heterogeneous Exchange of Remote Data Subscriptions
     Humane Ecosystem of Reticulate Data Stores
     Human Expression Relayed via Distributed Servers

You might be thinking, ah, but we don't want to confuse people by
calling it Herds when there's a 25-year-old GNU project that's never
going to be completed called Hurd.  Listen -- NOBODY is going to confuse
Herds with Hurd.  Of the billion GNU/Linux (and derivatives) users on
the planet, how many of them have ever heard of the Hurd project?
Probably no more than point-one percent of them, and that's being
generous.  Moreover, those who ~have~ heard of it know that a Hurd is a
Hird of Unix-Replacing Daemons and is nothing to do with herds. It's a
non-issue.

Alright, that's my rant/proposal concluded.  Let's hear the yays and
nays and their rationales, shall we?  STAND UP AND BE HERD!

Or remain seated, whatever's more comfortable.

Erkan Yilmaz | 11 Jan 09:04 2015
Picon

if this gets sent to mailing list

checking (1), with another email adress.

Erkan
--
Find me at: 

**********************************************************************************************
This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail.
Any unauthorised copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.

Diese eMail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese eMail irrtuemlich erhalten
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht
gestattet.
**********************************************************************************************

Gmane