Notices tagged with gnusocial, page 199
-
cc !gs !gnusocial !sn !statusnet
-
I'd be happy to donate admin time/money/bandwidth/storage/CPU/whatever to give @EFF their own #GNUSocial site at eff.org if it helps.
-
I'd be happy to donate admin time/money/bandwidth/storage/CPU/whatever to give @EFF their own #GNUSocial site at eff.org if it helps.
-
see http://skilledtests.com/wiki/XMPP_MUCs_for_GNU_social !xmpp !gs !gnusocial !sn !statusnet
-
I see !gnusocial more as an open discussion forum rather than a private messaging service at least. It will disseminate information well, but that also implies not bothering very much about protecting the content. cc: @hannes2peer @mxj
(but I understand that your point is to _make_ it protect private message content for example, and that'd probably be best accomplished by adhering to the Diaspora* protocol)
-
I host a !GNUsocial !XMPP Multi User Chat room at xmpp:gnusocial@chat.sobac.com
-
Also, as mentioned, metadata is there. So there's no need to actually run a modified !gnusocial codebase. Just implementing a #GreaseMonkey script or something to replace the relative timestamp with the absolute one should be trivial.
-
Aye. But that's pretty unusual. Also, given that you can much more quickly get a sense of how recent a post is - or how heated a discussion is (rather than parsing numbers in your head) there is a clear usability improvement by presenting relative timestamps as opposed to absolute timestamps. But you're of course free to modify and run your own implementation of !gnuso…
-
No longer sending GNU social posts to Twitter, which I hope will make me use GNU social more. There is a logo for !gnusocial though.
-
Please post that you are using #GNUSocial #pump or #diaspora at http://saloon.sixgun.org/t/so-where-is-everyone-hanging-out-these-days/978 so people don’t think the communities are dead.
-
Finally no remote hotlinking to creativecommons.org (over #InsecureHTTP!) !gnusocial https://gitorious.org/social/mainline/commit/5981b5c8d9df24ff9ff4d2db287906470e914115
-
PS. written from my local nightly branch where I removed the requirement of Javascript to post notices in !gnusocial in a somewhat ugly but efficient manner.
-
I think the best !gnusocial patch I made last year was the one stitching together notices with their respective incomplete conversations.
The best ones all-in-all were probably from @rozzin fixing my !ostatus fuckups ;)
-
In (at least nightly) !gnusocial the "about x hours ago" link goes directly to the conversation. To the single notice, there is instead a "[permalink]". @erkan's problem is that both are always visible - so there's no way to tell if there actually _are_ more posts in the conversation.
-
@kris La vraie question est, pourquoi les libristes informaticiens utilisent !GNUsocial?
-
@maliktunga@quitter.is why should !gnusocial be on github? We like decentralization, not centralization, remember? .)
(git itself is decentralized to the core, so I have a hard time seeing a problem with not using the proprietary service "github")
-
I hope "That will be enough !GNUsocial for the moment" doesn't mean you're leaving us! Just because we're an argumentative bunch doesn't mean we don't appreciate the feedback. In fact, your feedback has opened some really good discussion. I'm not a !GNUsocial developer, I just follow them online. http://memegenerator.net/instance/57667777
-
@maliktunga I completely disagree about the Qvitter UI — I find it completely unusable, even on a browser (Midori) with Javascript completely enabled that I can use perfectly well on other #Javascrippled sites. As a !FreeSoftware project, I appreciate that !GNUsocial continues to respect my freedom by giving me choice. Merging the Qvitter UI would be a step backwards. Software Fr…
groupie
Joshua Judson Rosen
Erkan Yılmaz
MMN-o ✅⃠
Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca
Matt Lee
Doug Whitfield
All Hacker Poesy content and data are available under the