Is anyone collecting all these disparate #OStatus and !GNUsocial documentation items in one location? Is there one location available for collecting all these things?
@limer I read your article on http://status.hackerposse.com/url/14954 and as a proponent of an open web, However: * You assume that [any !OStatus instance] has the responsibility to verify its users. The fact is that each user has their own responsibility to verify their accounts. Say, for example, that you are you. Then you have a personal website or work account. At…
@HerraBRE What all good e-mail clients (and even Outlook) have is a feed reader. With a feed reader, you can subscribe to !OStatus profiles and groups. ;)
@sylvhem !OStatus falls back on Atom which doesn't care.
@Gargron If anyone who cares enough happened to have time and energy maybe it would be so that AS 'note' types are single paragraphs of text and AS 'blog' are more freely designed multi-paragraph. This is however not a suggestion and I'm really just happy with how things work now.
@crecca Yes they can. Subscriptions are on a per-instance basis. So if two people from one !OStatus instance subscribe to you, and you block one of them, that instance will still receive the updates and thus the one you blocked will still get the same info as the one you haven't blocked.
+ you can always follow #Atom feeds from a feedreader.
@dredmorbius I'm not sure if we're discussing the same thing here. People who publish stuff publicly will always be targeted, they have a certain set of precautions to take. They're not what I'm talking about. The news article you linked was related to (identifiable) _subscribers_ to this information. They _would_ be safe simply by using Tor and anonymous RSS/Atom fee…
@dredmorbius Well, with !OStatus you can subscribe (using the Atom feed in an ordinary feed reader) to people through Tor without having to identify yourself as a supporter. Or you can create pseudonymic accounts through Tor (even if the target profile doesn't support it, because you only ever interact with the instance you trust). As long as you don't give away your …
@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 implem…
@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
@eileenb Me too! Though I'd like to point out that the obvious answer to "own the name everywhere!" discussion is: Why don't #CocaCola etc. have a social.cocacola.com domain with !OStatus? Then they own their !fediverse presence and can distribute information via proper Atom feeds etc. so sheeple can subscribe....wait why would anyone subscribe to a news feed from Coca Cola?!
@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…
Oh boy, Evan Prodromou (of #StatusNet / #Pump / #OStatus fame) showed up on #Diaspora's GitHub Issue tracker and asked that we support #ActivityPubIt's a nice thought, and hopefully we can do that in the long term. But some part of me is apprehensive about the spec and the leg work it will take to support it. There are certain unanswered questions, such a…