Aspects of federation

From I ask questions

aspect	pro	contra
features	you can use additional features e.g. able to use more/other Status.net plugins adapt features to your needs e.g. modify code	you've to be careful with new features/upgrade to new software version since they may break things so it's wise to make a backup of the DB + the files on HD
statistics / regulation	identify: who reads what? or: restrict access -> e.g. makes also scraping info harder (e.g. slower? since not all on one server?)	in case thinking about inviting one of your relatives, friends: think about if they wonder: "Do I like spying of a large corporation on me or you?"
safety	own backup intervals e.g. data safe when all burns at centralized server	it's now: you vs. machines (spammers) (this was actually no problem since I set registration on server so that I had to review them)
people	getting to know other like minded persons you (have to) decide more from now on I think that may help that people get more aware of things in general (federation, federation) (dev) teams: StatusNet + Friendica teams were helpful, though I preferred StatusNet due to their activity in IRC making people (that use centralized services) puzzled (by mdim) -> so they start asking questions
resources		increased resources for: - spam control - server resources (e.g. backup) - for my Friendica actually these 2 above were not the problem, what got me disappointed was that some things I wanted did not work + cost me in the end too much time to investigate (see also context here) - import contacts from existing networks: it costs time to do this, unfortunately not all offer this, in such a case importing rss feeds of the time line is a nice approach - you have to find yourself people (which can take time) -> one system which helps here is identi.ca though recent system downs made again clear people should NOT create an account at identi.ca, better set up an own server, so you get still contact with people even if a major system fails
copyright, licences		you've to be aware of copyright when you copy + paste things in any case but: at the centralized server admins can delete (faster?) inappropriate content did you think already what licence you want to distribute your content? Let's say you know the answer, so now the question: what happens when others redistribute your content under another licence + actually do not know what they do? (father forgive them, for they do not know what they do: a dent/tweet is retweeted very quickly) or: the software's licence model does not allow this, read this thread until end
when you stop federating in the future		-size: do not underestimate the amount of data saved in the database: depending on your future export place or the tools offered by your current provider this may give you some headache (time needed to im-/export, fails due to software problems, ...). Here's some data on the mysql DB size of friendika after ca. 2 weeks. Here's some info about identi.ca's shutdown for 4 days - they had to handle 75M-row table - e.g. your identi.ca dents are saved only in your database (or the users who are subscribed to you) example: 1. I use own StatusNet (SN) server 2. my dents are in my DB only 3. after a few weeks: I decide to stop using SN on my server 4. I just want to dent on identi.ca again 5. the dents from step2 are lost? I could write a small tool to import them to e.g. identi.ca again, but those dents won't have original date due to identi.ca's streaming nature :-( :solution: broadcast them, e.g. with: brdcst.it to identi.ca ?

Aspects of federation

Contents

see also

Views

Personal tools

Search

experimenting

special data

Erkan Yılmaz

Toolbox

? / HELP