Notices by MMN-o ✅⃠ (mmn@social.umeahackerspace.se), page 7
-
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Wednesday, 26-Apr-2017 10:07:14 UTC MMN-o ✅⃠
@herrabre That's exactly the idea of the spec methinks ;) (and even possibly email server configuratiom discovery though that's best solved with SRV records.
Google were, as you probably know, on the webfinger train when it started out. But bailed on it, as with everything else open and good.
webfinger -> profile page -> rel=me works pretty good today à la !indieweb with !GNUsocial at least. -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Tuesday, 25-Apr-2017 06:35:08 UTC MMN-o ✅⃠
@pettter It's a !GNUsocial thing to get some context for a new subscription. The weird part is because of 'ORDER BY created'. -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Monday, 24-Apr-2017 16:39:32 UTC MMN-o ✅⃠
@kevinmarks Btw, !qvitter counts unread mentions, not !GNUsocial. -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Monday, 24-Apr-2017 14:27:26 UTC MMN-o ✅⃠
@junglestrike Oh, the !fediverse "stands foe" something? It has an opinion? We have given it lifw apparently. Yet again, we witness the miracle of life. (I want to see @rw do some graphics on giving birth to the fediverse) -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Monday, 24-Apr-2017 14:22:31 UTC MMN-o ✅⃠
@pskosinski Yeah, we need to do some remote fetching for !GNUsocial. I've been putting it off for too long. -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Monday, 24-Apr-2017 05:58:54 UTC MMN-o ✅⃠
M[astod]onday! -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Monday, 24-Apr-2017 05:55:33 UTC MMN-o ✅⃠
@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 farsi).
My desire is to implement unicode support for nicknames. I don't know about the best strategy for homoglyph attacks etc, but I bet the !xmpp community has lots to share there. There you can have at least a large set of Unicode in your user part of the XMPP ID. Maybe #Prosody developer @zash knows more about unicode in XMPP usernames etc?
cc: @munin @nightpool -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Monday, 24-Apr-2017 05:33:23 UTC MMN-o ✅⃠
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 think are despicable and don't agree with. But they are only a problem if you lack moderation.
Instead of "web-scale" we should think "human-scale". -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Sunday, 23-Apr-2017 16:53:39 UTC MMN-o ✅⃠
*injects !GNUsocial needles in @pskosinski* -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Sunday, 23-Apr-2017 11:56:56 UTC MMN-o ✅⃠
@celesteh Not currently at least. I've got a branch for a "filtered timeline" patch but nothing working. !GNUsocial -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Sunday, 23-Apr-2017 06:13:38 UTC MMN-o ✅⃠
@lohang It's due to using #Docker and then relying on third parties to store (or storing on the Docker image itself, which it isn't designed for).
I can't believe this many people have managed to setup a Ruby on Rails application properly on their own machines. -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Saturday, 22-Apr-2017 11:56:11 UTC MMN-o ✅⃠
@japananon GNU social is more of a continuation (name changes, change of direction, developer switches etc.) of the other works - not "incorporates" (though that's technically correct too of course).
Also, we're not all communists like @hannes2peer. I, for one, am a space communist. Big difference. -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Saturday, 22-Apr-2017 10:32:07 UTC MMN-o ✅⃠
@tomas ...or even better (if !GNUsocial regex handles it?) just @härdin.se -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Saturday, 22-Apr-2017 09:20:27 UTC MMN-o ✅⃠
@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: '/(?:^|\s+)@((?:\w+[\w\-\_\.]?)*(?:[\w\-\_\.]*\w+)@(?:(?!-)[A-Za-z0-9\-]{1,63}(?<!-)\.)+[A-Za-z]{2,10})/'
where the interesting part is the domain name regular expression. I have now, in !GNUsocial, put the fixes in the nightly branch and will also see if I can push to master. -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Saturday, 22-Apr-2017 07:11:16 UTC MMN-o ✅⃠
@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 gets shortened automagically, so visually this is a bad example, but here I wrote the full .@anotheruser@social.umeahackerspace.se: @anotheruser
cc: @maiyannah -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Friday, 21-Apr-2017 22:33:36 UTC MMN-o ✅⃠
@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="https://social.umeahackerspace.se/conversation/690842"/>
<ostatus:conversation href="https://social.umeahackerspace.se/conversation/690842" local_id="690842" ref="https://community.highlandarrow.com/conversation/429650">https://community.highlandarrow.com/conversation/429650</ostatus:conversation>
Which is an incomprehensible mess that I fully understand if @Gargron hasn't bothered trying to understand. (though I have a vague memory of him asking me about it, or someone else, and I couldn't give an answer. Maybe if I have enough sleep tonight I'll give a go at clearing the mess up tomorrow). -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Friday, 21-Apr-2017 22:31:36 UTC MMN-o ✅⃠
@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 never stored or distributed from #Mastodon (which relies entirely on thr:in-reply-to)
What we have is however a bit of a mess and I don't remember which part is what we actually use and which part just comes along from #StatusNet (where none of this worked and conversations were even more broken). -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Friday, 21-Apr-2017 21:59:08 UTC MMN-o ✅⃠
@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. -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Friday, 21-Apr-2017 21:55:27 UTC MMN-o ✅⃠
@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. -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Friday, 21-Apr-2017 06:00:02 UTC MMN-o ✅⃠
Well, that was one hour of !GNUsocial browsing in the morning to wake up. Now the sun is acting up and causing a bunch of light radiating through the curtains. Better get up and do something less productive.