Show Navigation
Notices tagged with mastodon, page 3
-
The author's explanation of expectation of "security" or "privacy" in #Mastodon is concerning. Knowing that !OStatus provides no privacy or security at all, bolting privacy and security features onto #Mastodon isn't going to work. This is not the fault of #OStatus, nor is it a shortcoming of #GNUsocial that it doesn't implement security or privacy with #OStatus, but recognizes that constraint.
-
The article attributes lots of statements to the authors of both #GNUsocial and #Mastodon, things that I've never heard either state online (nothing that reached my timeline, anyway). The whole article seems to make the difference between #GNUsocial and #Mastodon much more acrimonious than I've experienced.
-
I would have mentioned the author, Trysdyn, but his #GNUsocial or #Mastodon userID is strangely absent from his website
-
@Gargron I really think you should impose a default license to #Mastodon creations. A libre CC license supposedly. Otherwise copyright says noone is allowed to redistribute neither posts nor other media. Formality may suck but it would suck more if ysers start harassing other instances with takedown requests because they didn't understand that posting on the web means copying and distributing by nature.
-
I am slightly uneased by the extreme increase of #Patreon advertisement in the !fediverse recently (since #Mastodon). What is this, a feudalverse?
-
@kaniini Seems you have an attitude problem to solve before you can get your point across to people. At least that may be a blocking issue causing your great suggestions to bounce. If you fix the attitude bug, maybe @Gargron and you can communicate without information loss.
If people who pay him money are dissatisfied with "his leadership" then they can withdraw the _donations_ and see if that changes anything. My hopes are that made-up currency doesn't dictate #Mastodon development and project management.
-
Oh @marxistvegan you _are_ alive! And on a #Mastodon instance!
-
@herrabre Aliases via #webfinger works with #mastodon as well afaik, try .@mmn@hethane.se
-
@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).
-
@espectalll @realramnit I haven't tried using the "Remote follow" link on a #Mastodon instance yet, no. But that's just a redirect to /main/ostatussub which works great. I just subscribed to @ekaitzzarraga for example.
-
@maloki It'd be neat if #Mastodon could offer #FOAF profiles ;)
-
I tried using #Mastodon in a secure web browser (no javascript). After registration and log in, this is what I got: https://social.umeahackerspace.se/attachment/158309
-
@HerraBRE though I see now that you complained about #Mastodon not respecting the Accept: header... Yeah, that's obviously a bad bug and should be reported as such.
Unfortunately I can't create or discuss Mastodon issues as I'm not a customer with #GitHub...
-
@dvs Maybe it should explain that #Mastodon is part of a network using the !OStatus protocol...
One reason is that it's easier to explain "instances". Maybe someone starts an instance of #Mastodon financed _with_ advertisement, then your FAQ answer here will be incorrect: http://mastoguide.info/Pages/funding.html
-
@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).
-
@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).
-
@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)
-
@pan Well, you're reasonably private if you use Tor and only want to protect your original identity. So you have a perfect privacy setup for leaking sensitive information in a broadcast fashion to subscribers since (afaik) all !ostatus federating instances allow Tor connections.
But no, neither !GNUsocial nor #Mastodon have any real privacy for hiding content.
There's always that question about which tool to use for what purpose: What's your threat model?
-
@rysiek @lambadalambda My hope is that #FOAF gets implemented in #Mastodon. Then any FOAF crawler can generate a good overview of the social graph.
(I can't add issues or requests since I'm not a customer with #GitHub, so cc: @gargron)
-
#Mastodon added: http://sobac.com/wiki/index.php/List_of_Free_Software_Social_Media_platforms Could really use some help with the Connectivity Matrix, tho.