Notices tagged with gnusocial, page 36
-
Hi all new #Mastodon based followers! Glad you traversed across the #OSocial !fediverse all the way to this !gnusocial !qvitter instance =)
-
@gargron Either way, I don't think there would be a problem for !GNUsocial with remote #Unicode (non-ASCII) characters. Nicknames are normalised as-is (for example removal of underscores which was another discussion). I don't remember if transliteration of nicknames is done, but we do that for #håshtägs (which has also sparked controversy due to incompatibility with…
-
I think you're right in that some soul is lost. Anything which grows too much will fail as a community. However, as this is all !fs the important thing to remember is that these are mere tools to create our own, new and balanced communities. I for one have seen many Twitter users come and go in floods to the !fediverse, some staying to create instances of #GNUsocial I…
-
@stitchxd @shel I think this is a known issue, but people have different and varying opinions from "how to fix it" to "should it be fixed at all". Some posts do not federate :-(
!gnusocial
-
@sarahjeong I suggest finding some good old !GNUsocial'ists too, I think most appreciate the new animal in the herd. Though as a precaution you could probably stay away from the "free speech" servers .]
-
Is anyone collecting all these disparate #OStatus and !GNUsocial documentation items in one location? Is there one location available for collecting all these things?
-
*injects !GNUsocial needles in @pskosinski*
-
@mmn Is this something that could be done via the plugin architecture? !gnusocial
-
!gnusocial If you're a GNU social server sysadmin, don't disable TLSv1.0 support and earlier on your webserver or Andstatus and Twidere won't work on Android versions prior to 4.4.2.
I just lost like a fucking month until I figured this out.
-
@celesteh Not currently at least. I've got a branch for a "filtered timeline" patch but nothing working. !GNUsocial
-
Is there a way to suppress some classes of notifications from the !gnusocial timeline? I'd like to stop displaying who my users are following and what they are liking, so the timeline can focus on more interesting content.
I read the helpfile for the config options an it doesn't seem to be there.
-
@mattl Is there a way to donate to the !gnusocial dev?
-
Buenas!!... !gnusocial !fediverse !tzag
-
@tomas ...or even better (if !GNUsocial regex handles it?) just @härdin.se
-
@maiyannah Apparently that was a bug that only domains like the one @thelovebug@s.wefamlee.be has experience! The dealbreaker was the single 's' in the domain name and the regular expression which couldn't catch the full domain name because of that: This: '!(?:^|\s+)@((?:\w+[\w\-\_\.]?)*(?:[\w\-\_\.]*\w+)@(?:\w+\-?\w+\.)*\w+(?:\w+\-\w+)*\.\w+)!' changed to this: '/(?:…
-
@thelovebug@s.wefamlee.be I scrolled through the list of issues for #postActiv and found this about full acct URI mentioning for local IDs:https://git.postactiv.com/postActiv/postActiv/issues/90 As a matter of fact, it works great in !GNUsocial (at least in the nightly branch, which is the one I probably recommend for everyone and will "soon" merge into master). It ge…
-
@maloki The part of the federated Atom feed that tells !GNUsocial which conversation (if the in-reply-to is unknown) it should be stitched into looks like this: The part of the <link rel="ostatus:conversation" href="http://status.hackerposse.com/url/14849"/> <ostatus:conversation href="http://status.hackerposse.com/url/14849" local_id="690842" ref="http://status.hack…
-
@maloki Right, that thing could probably be fixed by doing a remote-fetch of parent (which I believe #Mastodon does for replies to unknown posts, right?). I haven't checked whether the feed is fixed yet (@Gargron mentions the Suprrrfeedrrrrr "sanitation" with thr:in-reply-to) We stitch together instances in !GNUsocial based on the conversation URI though, which is nev…
-
@maloki I read the above discussion and just want to let you know that I'm always ready to know if something on our side should be improved or fixed. I've noticed already that the underscore-in-nick thing causes some confusion and I'm surely going to see if I can take care of the confusing UX around it on !GNUsocial's side.
-
@realramnit Yes, which is confusing because if you do the whole nick + URL it will do the same lookup as /main/ostatussub which will fail if it's not properly formatted (with underscores). Clearly a !GNUsocial bug.