Notices tagged with gnusocial, page 108
-
aaaand success with #xmpp !gnusocial /cc @n2admin
it was a combination of a rather stupid ypot on my part, but mostly, certificate permissions, order of cert in the bundle (backwards from the "pem" format). in any event, xmpp@crosstalk.co came online and said 'hey you..verify!'
-
Groups are a tough nut to crack. At present, a group moderator can ban users, and they can control membership by making the group private and having to approve every member, but what I'd really love to see in !GNUsocial is the ability to do Usenet-style moderated groups, where membership is open and public, but posts to the group are queued until they've been approved by a mod. That's…
-
!gnusocial #xmpp as soon as I enable the xmpp plugin, console starts spitting out this error: http://pastebin.com/LTGYnMeZ
it's not an authenticationn issue, as far as the user/host/server are concerned -- it connects with a client, etc. Any pointers, suggestions?
-
@hundur hmm no love there :(. I'll try other things while I'm dinking around with it #xmpp !gnusocial
-
@hundur the use case is being ablel to use a quitter for identity verification, both as an impersonation prevention mechanism (eg you could py a 'verified' badge on urls in profiles that link back, in the way the !gnusocial kinda does with OpenID ones) It also means you could use a gnusocial account as an indieauth ID http://status.hackerposse.com/url/9772 which has other benefits. …
-
why does Quitter strip out the rel="me" markup from !gnusocial ? Being able to do bidirectional id verification this way is very hand for distributed systems.
-
Because the statefull twitter api gives me a lot of problems with it's rate-limits I am now switching to a database and pulling tweets from the steaming api. This offers better options to populate information into my !gnusocial instance.
-
@pipistrellum no. Una de las cosas que más me ha gustado de !gnusocial es la ampliación del texto disponible.
En el mensaje corto se obliga a suprimir demasiadas cosas y hace los debates más pobres y confusos.
Mi impresión es que Tuiter se ha convertido en un concurso de frases originales y que no se profundiza en las cosas. Como los telediarios.
#esmiopinión
-
xmpp is alive and kicking, i just cant get !gnusocial to use the account I created for it, per the xmpp plugin readme. :/
-
sometimes bangtags to offsite groups such as !fediverse or !sn are showing up as hyperlinks automatically and other times not #newinterface ... also i wish that following said links would keep me onsite and gather #network mentions by query, which may be something i can set in preferences but is probably something to do with the !gnusocial source #qvitter .. said @nydel to zeself in a publicly-viewable test queet.
-
@antisocialjustice It's only a matter of time until !GNUsocial reaches the same number of users. #NetworkEffect
-
@antisocialjustice From that article: "What if I was a business owner and my livelihood depended on this [Twitter]?" Well then, you have a bad business model for relying on a free (gratis) service without a business contract. And if you do have a business contract with Twitter and they ban you then you have grounds for a breach of contract suit and can claim damages. But all in a…
-
@taknamay Unfortunately none of them talked about the #libre #freedom aspect of !gnusocial which is, you know, the key of the whole thing
-
!XMPP !gnusocial join moes_tavern@conf.netlab.cz for chat
-
Does anyone know how to get rid of a stale notification marker? It won't go away... !gnusocial https://gnusocial.de/attachment/2699647
-
New note by nebuk
-
About a year ago, soon after joining gnusocial, I wrote this: "Conversations in !gnusocial sometimes look like Picasso paintings: they are decomposed and reassembled so as to never look the same from two random viewpoints in the !fediverse"
I think that still holds, unless you can prove that the above conversation only implies remote users that are known to _both_ instances.
-
@singpolyma interesting, you seem to have posted this from Github as if it where an !ostatus instance. !gnusocial
-
@andstatus Recent versions of !GNUsocial will always prefer the full webfinger ID before the local part. It will then transform the full webfinger ID to only the local part, but put the profile's URI in href="".
-
!gnusocial Predictions on what might happen if I downgrade from 1.2 beta 4 to 1.2 beta 3? Or should I bite the bullet and switch to Master? I'm having a ton of problems since upgrade.