Notices by MMN-o ✅⃠ (mmn@social.umeahackerspace.se), page 8
-
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Friday, 21-Apr-2017 05:32:51 UTC 
MMN-o ✅⃠
It's unfortunate that HN doesn't federate, as I can't join the discussion without becoming a customer and giving away data to some random capitalist "incubator" with nothing but an interest to make money off from me rather than give me a platform to discuss news on. Then maybe I could've replied to some illiterate crap there. -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Friday, 21-Apr-2017 05:21:54 UTC
MMN-o ✅⃠
@bobjonkman As if HN has ever had a sane and informed discussion on any topic. -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Thursday, 20-Apr-2017 21:31:42 UTC
MMN-o ✅⃠
@espectalll I fixed that in master and nightly. The acct: URI is normalised and remote subscribes work for anyone who has updated that. Maybe @hannes2peer wants to merge this on #quitter.se: https://git.gnu.io/gnu/gnu-social/commit/388655d19b29524f7f501b092e56ece6bd05d19c and https://git.gnu.io/gnu/gnu-social/commit/2744bdcdb76e5d8affa7c54a583effadb7b1430d
@Gargron I never understood underscore filtering either (but that's not the issue in this thread). But then again #Gmail ignores (at least) dots in their usernames, so there's obviously some sort of use to it (less confusion for example: a_____b vs a____b <- who is who?).
cc: @thefaico -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Thursday, 20-Apr-2017 08:42:11 UTC
MMN-o ✅⃠
@PeterCxy We've had this discussion on !GNUsocial too - even whether the !fediverse tag should have a Spanish equivalent or not.
Depending on how much a profile posts, there could of course be practical issues with varying languages. It's not like you start talking Japanese in a (real, physical) room full of Swedes, right? But you rather reserve that persona for another situation, where the ones who hear you are more receptable.
As long as we haven't implemented language tagging (which is simple to do, less simple to handle well in a UI fashion unless trusting crappy automagics) it might be worth considering multiple accounts for different personas. (see .@hannes2peer@quitter.se and .@oemplojerad@quitter.se for example) -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Thursday, 20-Apr-2017 08:25:04 UTC
MMN-o ✅⃠
@shnoulle I've heard about this !GNUsocial, what is it? Doesn't sound !vegan - are you sure it's great anyway? -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Wednesday, 19-Apr-2017 22:41:40 UTC
MMN-o ✅⃠
@gargron I think the only reason !GNUsocial doesn't generate <p> is because I'd have to write a parsing routine instead of using PHP's nl2br or whatever does the work today. ;) -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Wednesday, 19-Apr-2017 09:45:53 UTC
MMN-o ✅⃠
@vinzv The recent push to !GNUsocial source fixing the 'acct:' normalization apparently broke the "+Remote" button in the classic interface (and /main/ostatussub without a ?profile_uri= argument). So I pushed some fixes for that now to nightly and master. -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Wednesday, 19-Apr-2017 08:56:31 UTC
MMN-o ✅⃠
@HerraBRE !GNUsocial calls it "mute" for the per-profile blocking, which makes the muted profile disappear from your feeds (while logged in of course). Or at least should, I think it's still buggy because it's not been such a big problem for me at least thanks to active moderators.
Then we have "silence" which is a moderator-level ban from the site in general. New posts are not received. -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Wednesday, 19-Apr-2017 07:57:21 UTC
MMN-o ✅⃠
@maloki In the current state of code, !GNUsocial at least wouldn't accept the update (no duplicates) because the post would still, if I read the Atom spec correctly, have the same URI. -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Wednesday, 19-Apr-2017 07:55:37 UTC
MMN-o ✅⃠
@maloki No it wouldn't cause a lot of Federation issues necessarily. It could perhaps cause duplicates, but since #Atom has the "atom:updated" element then - just as with any feed reader - !OStatus implementations can see that it is updated.
However, it should only be possible to update atom:content and not mentions. Categories etc. is debatable.
Why we haven't implemented updates in !GNUsocial is mainly because we solve it the social way, by just saying "oops, made an error" or accept that we are not all perfect and thus can live with spelling errors etc. If it's something really, really bad we just delete the post.
Also, updates are not implemented because I work too much and if I did implement it, I'd want it to have a complete revision history - which would probably be cause enough for people who want to edit their post to choose "delete" instead anyway. ;) -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Tuesday, 18-Apr-2017 20:55:51 UTC
MMN-o ✅⃠
@HerraBRE #Mastodon works with !GNUsocial as it is pretty well. There were some issues that @gargron raised with me, some of which I believe I fixed and some that I couldn't really figure out (some profile avatar update thing for example?)
Regarding RFC7033 (#WebFinger) it - since standardisation - only _requires_ a JRD (application/jrd+json). application/xrd+xml is just a bonus from !GNUsocial (voluntary according to spec).
The host-meta XRD is XML that because it was standardised before people who reinvent everything (JSON fanpeeps) started developing standards: https://tools.ietf.org/html/rfc6415
But since JRD and XRD are easily translatable between each other it doesn't really matter. And while #Mastodon doesn't use it, the /.well-known/host-meta endpoint is good for discovery unrelated to profiles, such as #OAuth endpoints etc. (so clients can auto-configure them). -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Tuesday, 18-Apr-2017 13:32:11 UTC
MMN-o ✅⃠
I imported your feed to my !GNUsocial instance and am trying to reply so I can see whether the notice appears on your site. -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Monday, 17-Apr-2017 22:32:43 UTC
MMN-o ✅⃠
First GIF, now MP3. Let's relive the '90s and forget about all the new, improved and libre-from-the-start technologies!!! -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Monday, 17-Apr-2017 15:45:10 UTC
MMN-o ✅⃠
@brunodias I'm gonna make a Megalodon implementation and crush the puny Mastodon! Any GNU in the way will be obliterated. https://upload.wikimedia.org/wikipedia/commons/9/97/Stenoshark.jpg -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Sunday, 16-Apr-2017 22:08:44 UTC
MMN-o ✅⃠
@Elizafox @Gargron Delete functionality for profiles ought to be _profile_ deletion as suggested in that thread. It would be up to each federated remote instance whether to delete the profile and/or data.
The possibility to delete an account's data should be obvious. But essentially that could be accomplished by just having the user edit their profile data, deleting avatar removing the given e-mail address and such.
Given that the user can already do all those things (I assume in #Mastodon too), I don't see any point in rushing a "profile delete" functionality.
This discussion is also relevant to !fediverse and !GNUsocial (where delete functionality is disabled by default due to account hackability and no delay in deletion). -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Friday, 14-Apr-2017 10:51:44 UTC
MMN-o ✅⃠
@kevinmarks I'm not entirely sure why you'd want a template URL in the Link rel. The way a !GNUsocial profile is presented currently with a Link header is (a URL to the webfinger endpoint but can be any endpoint of course):
Link: <https://social.umeahackerspace.se/url/154243>; rel="lrdd"; type="application/jrd+json" -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Friday, 14-Apr-2017 10:45:32 UTC
MMN-o ✅⃠
@kevinmarks Oh right, maybe #Mastodon doesn't publish public timelines as feeds yet without authorization. It's been requested by some of the new users though, and i've previously expressed its usefulness to @Gargron before. So my hopes are that it'll show up at least in the form of a public Atom feed via some API, if not also as HTML.
I think the argument against having it as HTML was that "the expectancy from users is that not all communication is immediately public" or something (i.e. it's all public but you'd have to crawl to get the data, which I've expressed should be called privacy through obscurity) -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Friday, 14-Apr-2017 09:25:26 UTC
MMN-o ✅⃠
@aw I'm not sure what you were trying to get across here. Can you or can you not access?
Either way, !GNUsocial is meant to be 100% usable without javascript. -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Thursday, 13-Apr-2017 19:49:29 UTC
MMN-o ✅⃠
@deadsuperhero Well, the info's gonna be there whether you like it or not. The data's there and profiles in a standards compatible !fediverse preferrably have a #FOAF transcription which means graphing of who knows who is available openly.
I do encourage keeping follower count low-key though (like calling them 'subscribers' as in !GNUsocial). -
MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Thursday, 13-Apr-2017 16:33:01 UTC
MMN-o ✅⃠
@pan My issue with mixing public and private communication inside the same tool is that some day you're going to make a mistake (or as with Facebook, the definition of private gets redefined regularly). Better to use different tools for sensitive communication, those are my two fiddy.
All Bobinas P4G content and data are available under the 