Internet

Juni 20, 2016

GNU social: quitter.is and quitter.es

(This post is part of a series about GNU social servers).

Server: quitter.is, quitter.es

I want to write an article about some gnusocial instances and would like to ask you some interview questions. The article will be an english article on my (mostly) german blog https://blog.laxu.de about some popular gnusocial instances.

Awesome! Thanks for showing an interest in GNU social :)

I'll note first that I'm the lead developer of the GNU social software.

These are answers that would apply to both quitter.is and quitter.es

Gnusocial configuration

  • How many characters per queet are possible on your instance?

1000

  • Which plugins are installed on your instance?

  • Qvitter (the Twitter-like front-end)
  • StoreRemoteMedia (to avoid hotlinking to remote servers)
  • VideoThumbnails (makes upload your own video files better)

  • Do you keep up with the most recent version or are you testing new versions for a while before using them?

I try the new versions before they're even available! ;) (as I'm a developer myself)

Users, Stability & Money

Users would like a service, which lasts forever and runs fast and reliable. Can you tell something about how your service tries to achieve this?

  • How many users does your service have?

I haven't checked, but I don't think the number of users is important. If anything, I generally recommend running multiple small instances.

  • For how long does it exist?

It's been around a little more than a year now, since the Spanish invasion.

  • How do you pay for the service? Do you get enough donations, do you have sponsors or do you pay for it yourself?

I have extremely cheap hardware, internet and electricity costs. Thus I don't currently need any financial donations for upkeep.

quitter.is is however hosted on a VPS run by (and donated by) Tranquillity, tranquillity.se whose owner is an active member of Umeå Hackerspace (which I usually refer to as being the organisation I develop GNU social through), https://social.umeahackerspace.se/mikael

  • What do you need to pay for hardware / hosting?
  • Are there costs for moderating / maintaining the site?

Only time. Not anything financially relevant. As long as I still have my low electricity costs etc.

  • How do you want to ensure, the service will last (That it can be payed for and there are enough people, who keep it running)?
  • How can your users support you? Do you accept donations? Are there other ways to say thank you, like a amazon wishlist or flattr?

I've promoted some of the users of the site to moderators, those that have been around for some time and I have come to trust.

Abuse Handling

The larger the site, the more abusive users will come. How do you handle the moderation on your site?

  • How can users report abusive Queets / private Messages?
  • How fast can the moderation handle such requests?
  • Are you actively moderating the site or just handling reports?
  • Do you have specific policies how to react on which type of incident?

Some of the more active users are also moderators.

I have zero tolerance for offensive behaviour and will silence anyone who acts unrespectfully towards other users (or hateful to various groups of the population at large).

  • Is there a page with the rules for your instance or do you rely on common sense and notify users, when they are going too far?

Mainly common sense. There is the standard Qvitter Terms of Use, which states that no sexism, racism, ableism, etc. etc. is allowed. Which is just putting words describing what "common sense" means ;)

  • Can you tell something about the possible consequences for breaking the rules?

Generally just silencing. Users who email and explain themselves tend to get a second chance. But my general idea is that if users misbehave so seriously that they get reprimanded, they should not be on any of the instances I run.

Users can always, if they want to, start their own instances and thus I think it is better to ban bad users and let them put an effort to it if they really want to continue doing what they were banned for (racial slur, aggressive behaviour...)

  • Do you notify authorities for serious incidents or do you just ban the users and let the victim report it to the police themself?

There have been cases of annoyed, silenced users who have returned with new accounts and posted (relatively mild) child pornography. These have just been continually silenced and a temporary stop in registrations has been enabled on the sites to prevent them from creating new accounts.

Since they are probably just copypasting images from some darkweb site, I haven't bothered notifying any authorities since they're just - even though it's serious matters - playing around.

Moderation

Moderation to prevent abuse is important, but too much moderation can hurt a site. Moderating legal but possibly offensive posts may create chilling effects, where people censor themself to avoid being moderated or even banned for unpopular opinions.

I don't think the "chilling effects" are as pervasive in the federated networks as in centralised ones like Twitter. Since anyone can start their own, fully anonymous node to spread offensive (even illegal) material, the only chilling effect that you get on a public instance is a better communication climate.

It's a good thing that people think twice about what they write. If they still want to write something offensive and inappropriate, they are free to do so on a platform they take legal and moral responsibility for themselves.

  • When do you delete possibly offensive tweets?

queets ;)

I delete them when they portray typical sexist or racist in an overly simplified way that is not in a context of humour etc. As an example, the "nigga stole my bike" GIFs would be allowed, but an image stating "this nigga is a bike stealer" (possibly even portraying a real person, who is probably totally unrelated) would likely be removed.

  • When do you warn users?
  • When do you temporarily ban users?
  • When do you permanently ban users?

When it totally arbitrarily feels appropriate. ;)

  • Do your moderators discuss decisions among themselfes or are they acting on their own?

I've asked them to only silence when it's pretty obvious that something's really bad about it.

  • Do you discuss the moderation with the users?
  • How do you avoid, that moderators are biased to their own opinion in the discussion, which they are moderating?

I ask moderators to ask me if they're unsure in any way. And we can all join group discussions to get better points of view. Sometimes maybe there's just some cultural thing that someone hasn't understood, maybe someone overreacting to certain phrases (which may arise just due to poor language skills etc.).

  • Do you think your users need to think about being moderated before writing a queet?
  • Do you have any rules, which require the users to think beyond common sense before posting, like avoiding tv spoilers?

No such rules, but there are some memes going around that would probably require users to think twice before publishing them.

  • Where does inacceptable behaviour start on your instance? (bad opinions expressed in a serious manner / flame wars / trolling / insults / haressment / serious threats)

As soon as personal insults show up, I think it's gone too far. It's better to just shut up and ignore someone instead of calling them names.

  • What are your moderators doing with reports for queets in heated discussions, which are strictly speaking not breaking a rule, but offending other users in the discussion?

Offensive, derogatory queets are against the rules :)

  • How are you moderating queets from other gnusocial instances?

Silencing, but I will probably implement some sort of mute functionality or some better kind of "sandboxing".

Backup & Privacy

Some instances have plugins for backup, others don't have this option. What options do you provide for your users? How do you handle the privacy of your users?

  • Can your users export their data (queets, private messages)?

Yeah, the GNU social API lets users traverse the timeline to download queets. Private messages aren't easily downloadable but will probably be removed (and XMPP promoted for that instead).

  • Is there a way to import this data or data from other gnusocial instances?

Not to my instance. I don't support the liberal idea of an identity that can move around. I think the instances should be democratically run as an organisation and you can either join or not, not join and then threaten to move the account.

(just posting a message "I'm over here now" and pointing to another instance is good enough I think).

  • Do you have backups for your server, i.e. in case of hardware failure?

Yes, for at least once every 24 hours or something.

  • Can your users delete their account?

Yes, but only if they request it. I will have to make the deletion process a bit more interactive before I want to allow users to be able to delete themselves. (something like verifying through email or other things that can't as easily be done by someone who just sat down at your unlocked computer).

  • How long does it take for the data to be deleted completely (i.e. disappear from any backups)?

Generally a matter of seconds, minutes for larger accounts. Extremely large (previously active) accounts might take even longer.

  • Do you retain any data after deletion, i.e. to as proof for abusive behaviour, to enable recovery of the deleted account or to prevent others from reregistering the account name?

Just the ordinary backups, which are deleted sequentially. I think there's backed up data for about a week back or something. I wouldn't bother recovering an accidentally deleted account though.

  • Do you ever read private messages? Under which circumstances would you do so and would you inform the users afterwards?

Yeah. But I recommend XMPP and have enabled everyone to be able to log in using their GNU social credentials with an XMPP client to user@quitter.is and user@quitter.es respectively. They can then add my accounts hundur@quitter.is and perro@quitter.es (or my human account mmn@hethane.se) to talk more privately.

Security

  • How are you protecting the data (i.e. is the server hard disk encrypted)?

No, but as with all GNU social instances the passwords stored are salted hashes with, from the top of my head, SHA-512 ($6$ for crypt()).

  • Does your site use HTTPS?

Yes, required.

  • Did you configure more security options like a HSTS header?

Yes.

Legal Issues

It is pretty common that people post copyrighted images on social media, which can get them into trouble*. A smaller site may have problems to get accused of the violation itself instead of the user. How do you handle copyrighted content and law enforcement requests?

  • Do you inform your users about rules for posting copyrighted images / texts?

No, unless it's in the Terms of Use. I assume that anyone who doesn't already care about that wouldn't care if I stated it in rules. I mean, the law is the law and not related to the instance itself.

  • Do you try to actively moderate copyright violations or do you take down content only on request?

Only on request, but that hasn't happened yet.

  • What would you do, when you receive a DMCA notice or a similiar request in your country?

DMCA notices are irrelevant in Sweden.

I'd probably remove it if it wasn't actually licensed freely. But the request would have to be extremely well defined and I would only remove content if I was absolutely sure that the request sender actually has that right.

I'd probably start off with sending an email back demanding a handling fee though, so I can put time into investigating the matter at hand. If they don't reply to that, I'll assume they're just copytrolling :P

  • What do you do about images violating personality rights of people in the image?

This is much more serious than copyright. If the material is not already widespread I would immediately take action against spreading personally identifiable material where the individual is assumed not to want that information being spread.

  • How would you handle requests for the EU "right to be forgotten" law?

Accounts can be deleted, but federated notices of course can't. If the request is sent in regard to a user's notice content rather than about a user account itself, I'd refer to contacting that user instead of me as a service provider.

  • Did you think about getting a national security letter?

I'm not sure what this would mean? :)

Technical Information

Can you tell something about how you run the website?

  • What hardware are you using?

  • quitter.es: Old hardware from a super computer cluster. Nothing fancy.
  • quitter.is: Baseline VPS on https://tranquillity.se

  • What software (i.e. operation system, etc.) are you using?

Debian GNU/Linux, lighttpd, MariaDB, PHP-FPM.

  • Does the server just run gnusocial or are you using it for other things as well?

A couple of wikis, some minor owncloud instance etc. Nothing being used even nearly as much as the GNU social instances.

  • Is your server very busy with the instance?

When thousands of new users show up, yes :)

Final thoughts

  • Why should users choose your instance?

They shouldn't! They should start their own. But if they would, it's because I want a climate that doesn't create any aggression, even if it's perhaps at the expense of limiting what people can write.

  • Do you want to tell anything else?

Thanks for doing this kind of survey! It's good to make administrators think twice about what and how they run servers.

* https://www.washingtonpost.com/news/the-intersect/wp/2015/09/08/how-copyright-is-killing-your-favorie-memes

Copyright is also an issue btw, we just haven't had to deal with it yet. Everything is licensed CC:by on my instances, so it's a direct copyright violation to post anything that's not already that liberally licensed (unless you hold the rights yourself).

Kategorien Internet OpenSource
Tagged GNUSocial GNU social quitter.is quitter.es
Mobil qrcode zeigen

0 Kommentare

März 24, 2016

GNU social: gnusocial.de

(This post is part of a series about GNU social servers).

Server: gnusocial.de
(vinzv blogged the answers on his own blog as well)

GNU social configuration

- How many characters per queet are possible on your instance?
1024 chars.

- Which plugins are installed on your instance?

Activity, Autocomplete, ClientSideShorten, ChooseTheme, EmailReminder, ExtendedProfile, FeedPoller, GroupPrivateMessage, LRDD, ModPlus, OStatus, OpenExternalLinkTarget, Qvitter, StaleAccounts, Statistics, StoreRemoteMedia, TabFocus, TwitterBridge (posting only, no import due to ressource overusage), WebFinger

- Do you keep up with the most recent version or are you testing new versions for a while before using them?

I'm quite close to current nightly status. All code comes from Git so if anything goes wrong I'm moving back some commits.

Users, Stability & Money

Users would like a service, which lasts forever and runs fast and reliable. Can you tell something about how your service tries to achieve this?

I recently got a similar question and told the people asking that I have no intention to close the node. But I can't (and don't want to) promise things I can't do with a good conscience. There's no guarantee - not for gnusocial.de as well as for any service around. The only thing I can promise is that in case of closing gnusocial.de I will do my very best to get a successing admin and/or to help people migrate to another node.

To make financial issues more open I have a page on the wiki: http://wiki.gnusocial.de/gnusocialde:finanzierung

- How many users does your service have?

Registered accounts currently: 917 Actively posting users (can only be estimated): ~20-30

- For how long does it exist?

The domain was registered in February 2014, the complete instance launched on July 22nd, 2014.

- How do you pay for the service? Do you get enough donations, do you have sponsors or do you pay for it yourself?

I mostly pay the monthly fees and annualy domain fees myself. From time to time someone donates a few bucks.

- What do you need to pay for hardware / hosting?

Monthly fees 18,99€ plus .de Domain plus SSL cert (both annually paid).

- Are there costs for moderating / maintaining the site?

There are no costs in money but of course maintaining "costs" spare time.

- How do you want to ensure, the service will last (That it can be payed for and there are enough people, who keep it running)? - How can your users support you? Do you accept donations? Are there other ways to say thank you, like a amazon wishlist or flattr?

Yes, after some people asking I added donation information at the wiki. But there's no Amazon wishlist or special Flattr thing. The local community is not too big and I keep in touch with most users. So if someone wants do give me a present, he or she just can drop me a line.

Abuse Handling

The larger the site, the more abusive users will come. How do you handle the moderation on your site?

- How can users report abusive Queets / private Messages?

Just @-mention me.

- How fast can the moderation handle such requests?

As soon as I see the @-mention I will look into the issue. Furthermore they can simply send me an email: https://gnusocial.de/doc/contact

- Are you actively moderating the site or just handling reports?

Until now I never had a really severe problem so active moderation wasn't necessary. During the rush within the past 2-3 weeks there registered some companies. I wrote to them in advance pointing to the terms of service, not because they did anything wrong but to avoid disappointment.

- Do you have specific policies how to react on which type of incident?

No. As long as there's no need I try to talk to people and explain problems. Nevertheless there's the terms of service page and a quick round up during the registration process. A copy of this text is available on the wiki: https://gnusocial.de/doc/tos http://wiki.gnusocial.de/gnusocialde:tos

- Is there a page with the rules for your instance or do you rely on common sense and notify users, when they are going too far?

Both. See previous question.

- Can you tell something about the possible consequences for breaking the rules?

It's quite simple: Three steps. First, the user gets advice. Second, he get's a serious warning. Third, I will delete (yes, *delete*) the account.

- Do you notify authorities for serious incidents or do you just ban the users and let the victim report it to the police themself?

Luckily I never got into such a situation so I can only guess, that it would depend. For sure I would support the victim but at first I would talk to a lawyer what to do.

Moderation

Moderation to prevent abuse is important, but too much moderation can hurt a site. Moderating legal but possibly offensive posts may create chilling effects, where people censor themself to avoid being moderated or even banned for unpopular opinions.

- When do you delete possibly offensive tweets?

Never. But I'm under German jurisdiction so I have to I try to talk to the people that something (e.g. porn) ain't welcome on this node. There are other nodes specialised on such topics. So users don't have to leave.

- When do you warn users?

If they: - post commercial advertisments. - post content forbidden by German law

- When do you temporarily ban users?

Never.

- When do you permanently ban users?

Never.

- Do your moderators discuss decisions among themselfes or are they acting on their own?

I'm the only moderator but for things I'm unsure I try to contact admins of other nodes and long-term users of my node to get a well-based decision.

- Do you discuss the moderation with the users?

See previous question.

- How do you avoid, that moderators are biased to their own opinion in the discussion, which they are moderating?

If things are getting too hot I guess I would change communication from public to private emails, chats or whatever.

- Do you think your users need to think about being moderated before writing a queet?

No, absolutely not. As said before I will *always* contact users if they post things which are a problem. I strongly believe in solving problems by talking at first.

- Do you have any rules, which require the users to think beyond common sense before posting, like avoiding tv spoilers?

No. If users post things others don't want to read they will be told so by the people affected.

- Where does inacceptable behaviour start on your instance? (bad opinions expressed in a serious manner / flame wars / trolling / insults / haressment / serious threats)

The inacceptable behaviour for me is when someone tells you about your misbehaviour and still you don't stop. On gnusocial.de you can say anything sticking to the terms of service, as long as nobody has a problem with that.

- What are your moderators doing with reports for queets in heated discussions, which are strictly speaking not breaking a rule, but offending other users in the discussion?

I don't have any moderators, so: see previous question.

- How are you moderating queets from other gnusocial instances?

I am not yet. Currently I'm waiting for this feature to be implemented in GNU Social so I can filter out adult-only content from other instances to appear on public timelines. To avoid misunderstandings: users following accounts from these instances will still get the contents. I'm not a nanny judging on anyone for being naughty..

Backup & Privacy

Some instances have plugins for backup, others don't have this option. What options do you provide for your users? How do you handle the privacy of your users?

In terms of microblogging I think there is no privacy at all. It counteracts the idea of posting things public online. Microblogging ain't made for private communications. Nevertheless, posting anon- and pseudonymously on gnusocial.de is of course possible: - users can register whatever username they like - there is no clear name policy and there will never be - webserver logfiles are anonymized: all users' IP adress is 127.0.0.1 - a working email address is *needed* only for signup and password resets - access via TOR is welcome, no Cloudflare or similar captcha crap

- Can your users export their data (queets, private messages)?

Yes, sort of. The data migration feature is broken in GNU Social generally, not only on my node. So exporting the data will need an admin's hand. I'm absolutely willing to do my very best to let users get their data.

- Is there a way to import this data or data from other gnusocial instances?

See question above and: I never had this case yet so I can't tell how good it works.

- Do you have backups for your server, i.e. in case of hardware failure?

Of course. The server is a VPS so hardware failure is not on my watch but on the provider's. Nevertheless I keep backups of both the database and the uploaded files for a short time to avoid problems e.g. due to update on GNU Social's software.

- Can your users delete their account?

Of course. The server is a VPS so hardware failure is not on my watch but on the provider's. Nevertheless I keep backups of both the database and the uploaded files for a short time to avoid problems e.g. due to update on GNU Social's software.

- How long does it take for the data to be deleted completely (i.e. disappear from any backups)?

Depending on the amount of data 1-10 minutes.

- Do you retain any data after deletion, i.e. to as proof for abusive behaviour, to enable recovery of the deleted account or to prevent others from reregistering the account name?

Both: No. And to be honest I'm not willing to pull back accidentily deleted accounts from a recent backup.

- Do you ever read private messages? Under which circumstances would you do so and would you inform the users afterwards?

No. I wouldn't under any circumstances. Even if I was forced to hand over the server's data I would not read private messages.

Security

- How are you protecting the data (i.e. is the server hard disk encrypted)?

No. The server is secured by a strong SSH password, no root login in via SSH and fail2ban. Security updates are installed very quickly (normally within 1-2 hours from being available)

- Does your site use HTTPS?

Yes. HTTP requests are forwarded to HTTPS.

- Did you configure more security options like a HSTS header?

Yes. HSTS and HTKP is enabled.

Legal Issues

It is pretty common that people post copyrighted images on social media, which can get them into trouble. A smaller site may have problems to get accused of the vialogation itself instead of the user. How do you handle copyrighted content and law enforcement requests?

Posting copyrighted content is prohibited by the terms of service. But I'm not monitoring what people post so I can't act proactively on such things. Though if it comes to my knowledge I have to act and would try to contact the user to take content down.

- Do you inform your users about rules for posting copyrighted images / texts?

Yes, it's in the terms of service.

- Do you try to actively moderate copyright violations or do you take down content only on request?

Only on request.

- What would you do, when you receive a DMCA notice or a similiar request in your country?

I would try to contact the user to inform him and ask to delete the content. If he doesn't do or ain't responding I would comply to the DMCA notice.

- What do you do about images violating personality rights of people in the image?

If I get a request: see question above. Otherwise I'm not monitoring what people post so I can't act on such things.

- How would you handle requests for the EU "right to be forgotten" law?

To be honest: I think this law is ridiculous and useless. I never thought about what to do when I recieve such a request. I guess I would contact a lawyer before doing anything.

- Did you think about getting a national security letter?

Yes, but as I'm not under U.S. juristdiction I hardly care. Nevertheless getting a warant canary is on my to do list.

Technical Information

Can you tell something about how you run the website?

- What hardware are you using?

The server is VPS at Netcup Hosting (https://www.netcup.de) with 12 GB RAM and 4 vCPUs

- What software (i.e. operation system, etc.) are you using?

Debian stable.

- Does the server just run gnusocial or are you using it for other things as well?

The server hosts GNU social, a small wiki (Dokuwiki) and some scripts for automated posts to GNU Social.

- Is your server very busy with the instance?

No. 8 out of 12 GB RAM are used, the 4 vCPUs are at about 10% load.

Final thoughts

- Why should users choose your instance?

I don't care. If users choose my instance I'm happy. If they choose another one I'm happy as well. The good thing with GNU Social is that no matter where users are everyone can communicate with everyone. Aside that it would be good if users choose smaller instances in favor to the big ones (e.g. quitter.se) to spread the ressource load over all nodes and to avoid single points of failure.

- Do you want to tell anything else?

If any information is missing within all these questions I'm very happy to give answers, either via GNU Social or directly via email.

Kategorien OpenSource Internet
Tagged GNUSocial GNU social gnusocial.de
Mobil qrcode zeigen

0 Kommentare

März 10, 2016

GNUSocial / Quitter and choosing a server

When twitter tried to make itself unpopular again (last time they upset their users with the prospect to allow 10,000 character tweets) by introducing an algorithmic timeline, the Hashtag #RIPTwitter started to trend and people started looking at alternatives again.

One of the alternatives is GNU social, often called Quitter after a popular GNU social server. Here is an article how to get started, once you decided for a server.

GNU social is a federated system like Jabber/XMPP, which means there is no central server. Each user can choose from a lot of servers, but reach people on other servers. This is a great thing, as everybody can run his own server and having more different servers adds redundancy and diversity. No one can control or censor the whole network.

On the other hand, without a central website, you have to choose a server you want to use for your account. Which server should you use? The one with the nicest name (i.e. quitter has a nice ring for twitter users), the one with the most users, or should you use some other criteria?

Of course, self hosting may be an option for some of us, but others cannot or do not want to host an own server. I host most of my stuff by myself, but unlike an e-mail server it would be hard to move to an hosted service, when i decide i do not want to host my instance on my own at a later time. So i started to think about which criteria are useful to choose an GNUSocial server for my account.

Some of the main aspects include:

  • Reliability: You do not want your E-Mails to be lost, probably you do not want your queets (messages on GNUSocial) to be lost as well.
  • Privacy and Security: Neither should the data be lost on a harddrive failure, nor do you want your private messages or password in a leak.
  • Moderation: On the big sites like Twitter there are sometimes problems with harassment. So when a new social network grows, it will need some moderation to stop people from harassing others. On the other hand could too much moderation hurt the idea of an free alternative, which may even provide more freedom than the commercial ones.

As i asked myself these questions, i thought others may ask themself the same. So i decided to survey some of the server administrators about these things. I sent a mail with some questions to these instances (taken from this list of instances):

(I will link them to follow up posts, as i get answers and have time to blog them)

The Questions:

Gnusocial configuration
=======================

- How many characters per queet are possible on your instance? - Which plugins are installed on your instance? - Do you keep up with the most recent version or are you testing new versions for a while before using them?

Users, Stability & Money ========================

Users would like a service, which lasts forever and runs fast and reliable. Can you tell something about how your service tries to achieve this?

- How many users does your service have? - For how long does it exist? - How do you pay for the service? Do you get enough donations, do you have sponsors or do you pay for it yourself? - What do you need to pay for hardware / hosting? - Are there costs for moderating / maintaining the site? - How do you want to ensure, the service will last (That it can be payed for and there are enough people, who keep it running)? - How can your users support you? Do you accept donations? Are there other ways to say thank you, like a amazon wishlist or flattr?

Abuse Handling ==============

The larger the site, the more abusive users will come. How do you handle the moderation on your site?

- How can users report abusive Queets / private Messages? - How fast can the moderation handle such requests? - Are you actively moderating the site or just handling reports?

- Do you have specific policies how to react on which type of incident? - Is there a page with the rules for your instance or do you rely on common sense and notify users, when they are going too far?

- Can you tell something about the possible consequences for breaking the rules? - Do you notify authorities for serious incidents or do you just ban the users and let the victim report it to the police themself?

Moderation ==========

Moderation to prevent abuse is important, but too much moderation can hurt a site. Moderating legal but possibly offensive posts may create chilling effects, where people censor themself to avoid being moderated or even banned for unpopular opinions.

- When do you delete possibly offensive tweets? - When do you warn users? - When do you temporarily ban users? - When do you permanently ban users?

- Do your moderators discuss decisions among themselfes or are they acting on their own? - Do you discuss the moderation with the users? - How do you avoid, that moderators are biased to their own opinion in the discussion, which they are moderating?

- Do you think your users need to think about being moderated before writing a queet? - Do you have any rules, which require the users to think beyond common sense before posting, like avoiding tv spoilers?

- Where does inacceptable behaviour start on your instance? (bad opinions expressed in a serious manner / flame wars / trolling / insults / haressment / serious threats) - What are your moderators doing with reports for queets in heated discussions, which are strictly speaking not breaking a rule, but offending other users in the discussion?

- How are you moderating queets from other gnusocial instances?

Backup & Privacy ================

Some instances have plugins for backup, others don't have this option. What options do you provide for your users? How do you handle the privacy of your users?

- Can your users export their data (queets, private messages)? - Is there a way to import this data or data from other gnusocial instances? - Do you have backups for your server, i.e. in case of hardware failure? - Can your users delete their account? - How long does it take for the data to be deleted completely (i.e. disappear from any backups)? - Do you retain any data after deletion, i.e. to as proof for abusive behaviour, to enable recovery of the deleted account or to prevent others from reregistering the account name? - Do you ever read private messages? Under which circumstances would you do so and would you inform the users afterwards?

Security ========

- How are you protecting the data (i.e. is the server hard disk encrypted)? - Does your site use HTTPS? - Did you configure more security options like a HSTS header?

Legal Issues ============

It is pretty common that people post copyrighted images on social media, which can get them into trouble. A smaller site may have problems to get accused of the violation itself instead of the user. How do you handle copyrighted content and law enforcement requests?

- Do you inform your users about rules for posting copyrighted images / texts? - Do you try to actively moderate copyright violations or do you take down content only on request? - What would you do, when you receive a DMCA notice or a similiar request in your country?

- What do you do about images violating personality rights of people in the image? - How would you handle requests for the EU "right to be forgotten" law? - Did you think about getting a national security letter?

Technical Information =====================

Can you tell something about how you run the website?

- What hardware are you using? - What software (i.e. operation system, etc.) are you using? - Does the server just run gnusocial or are you using it for other things as well? - Is your server very busy with the instance?

Final thoughts ==============

- Why should users choose your instance? - Do you want to tell anything else?

Kategorien OpenSource Internet Medien Software english
Tagged GNUSocial Quitter StatusNet twitter RIPTwitter
Mobil qrcode zeigen

0 Kommentare

Dez. 26, 2013

30C3 IRC-Statistiken

Für den 30C3 gibt es wieder Chat-Statistiken. Diesmal mit etwas anderem Stil, dank neuem Munin 2.0.

Die Zahlen wurden von einem OTFBot durch das "statistics"-Plugins erfasst und durch Munin gesammelt und zu Graphen aufbereitet.

Die Graphen sind auf 30c3.ircstats.laxu.de zu finden und wurden alle 5 Minuten aktualisiert.

Die archivierten Graphen der letzten Jahre sind verfügbar unter:

Alles nötige um selber solche Statistiken für einen IRC-Kanal zu erstellen, findet man im Sourcecode des OTFBot.

Die nötigen Plugins sind ircClient.statistics (Sammeln der Daten) und webServer.count (HTTP-API zum Abfragen der Daten). Die benutzten Munin-Plugins finden sich im "helpers/munin-plugins" Ordner.

Für die *C3-Statistiken wurde das ircusers-Plugin zweigeteilt, damit die Kurve der aktiven Nutzer besser erkennbar ist.

Kategorien Software Veranstaltungen Internet CCC
Tagged 30C3 Chat IRC OTFBot Statistik
Mobil qrcode zeigen

0 Kommentare

Dez. 27, 2012

29C3 IRC-Statistiken

Auch dieses Jahr gibt es hier wieder Chat-Statistiken zum Chaos Communication Congress:

Die Zahlen werden von einem OTFBot durch das "statistics"-Plugins erfasst und mit Munin gesammelt und zu Graphen aufbereitet.

Die aktuellen Graphen sind auf 29c3.laxu.de zu finden und werden alle 5 Minuten aktualisiert. Ein Archiv der Graphen von letztem Jahr ist auf 28c3.laxu.de verfügbar.

Nach dem Ende des 29C3 werden die Live-Graphen ebenfalls durch eine Archiv-Version ersetzt.

Wer auch gerne selber solche Statistiken für einen IRC-Channel erstellen möchte, findet alles Nötige im OTFBot-Sourcecode.

Die nötigen Plugins sind ircClient.statistics (Sammeln der Daten) und webServer.count (HTTP-API zum Abfragen der Daten). Die benutzten Munin-Plugins finden sich im "helpers/munin-plugins" Ordner.

Für die 29C3-Statistik wurde das ircusers-Plugin zweigeteilt, da der große Unterschied zwischen der Zahl aller Nutzer und der Zahl aktiver Nutzer ansonsten zu einer geringen Auflösung der Kurve für die aktiven Nutzer geführt hätte.

Update: Die Graphen vom 27.12. bis 01.01. sind auf http://29c3.laxu.de archiviert.

Kategorien Software Veranstaltungen Internet CCC
Tagged 29C3 Chat IRC Statistik statistics CCC congress Chaos Communication Congress
Mobil qrcode zeigen

0 Kommentare

Dez. 11, 2011

behaupte.es vs. behaupte-es.de: Lösung gesucht

Es gibt (bald) zwei Seiten für wilde Behauptungen: behaupte.es und behaupte-es.de.

Wir stehen miteinander in Kontakt und suchen eine Lösung, wie man die Seiten vereinen oder zusammen betreiben kann.

Hintergrund

Früher gab es einmal eine tolle Seite für wilde Behauptungen und absurde Thesen: behaupte.es. Die Seite hat mir viel Spass gemacht, ich finde die Idee gut.

Das ganze lief einige Zeit, dann wurde die Seite offline genommen und jahrelang wurde auf der Domain nur angekündigt "Wir kommen bald zurück". Ich habe mir das lange angesehen und bedauert dass es die Seite nicht mehr gibt.

Der nächste Schritt war dann, dass ich mir gedacht habe "Warum nicht selber machen?!". Im September 2011 war es dann soweit, behaupte-es.de wurde geboren.

Ich habe die Seite von Grund auf neu gebaut, einfach damit es wieder eine Seite für tolle Behauptungen gibt und weil es mir Spass macht. Erst eine ganz einfache Seite, dann Schritt für Schritt immer mehr Funktionen. Jetzt ist sie seit September in Betrieb.

Unter den neuen Funktionen war auch eine Twitter-Integration und dabei bin ich plötzlich über Tweets gestolpert, dass behaupte.es jetzt wirklich einen Relaunch plant. Nach dem neuestem Stand soll es schon am 15. Dezember soweit sein.

Inzwischen habe ich auch noch einen Blogpost gefunden, der erklärt warum die ursprüngliche Seite nicht weiter betrieben wurde.

Zwei solche Seiten parallel sind meiner Meinung nach aber eher ungünstig. Das Konzept der Seite ist etwas, das am besten funktioniert, wenn es eine zentrale Seite gibt auf der alle Nutzer gemeinsam behaupten und abstimmen. Eine Aufteilung auf mehrere Seiten bremst beide Seiten aus.

Also habe ich einfach mal mit den Leuten hinter dem Relaunch von behaupte.es Kontakt aufgenommen, in der Hoffnung dass wir eine gute Lösung finden können.

Zusammenarbeit?

Das Ergebnis des Kontakts: Ja, sie bringen die Seite bald wieder online. Sie sind vor kurzem auch über meine Seite gestolpert, ich bin aber der erste, der den Kontakt aufnimmt. Eine Kooperation wäre aus den oben genannten Gründen auch für sie wünschenswert.

Die Frage ist nur, wie kann eine solche Kooperation aussehen? Technisch ist das schwer, da wir auf zwei sehr unterschiedliche Techniken setzen. Die behaupte.es-Leute haben das alte Wordpress-Plugin wiederbelebt, ich hingegen habe das Konzept von Grund auf neu und sauber mit python Django umgesetzt. Der Code der beiden Projekte ist also weitgehend inkompatibel.

Das heißt man kann nicht z.B. die Mobilversion von meiner Seite in die andere Seite integrieren ohne weite Teile neuschreiben zu müssen.

Motive und Befürchtungen

Es scheint, dass zumindest unsere Motive die gleichen sind:

  • Die Seite soll es wieder geben, weil das Konzept gut ist
  • Es macht einfach Spass die Seite zu bauen und zu sehen wie Nutzer sie benutzen
  • Die Seite soll unkommerziell bleiben

Leider aber auch die Befürchtungen:

  • Wer weiß, wie lange das jeweils andere Team seine Seite jetzt betreibt?!
  • Bei einer möglichen Zusammenarbeit wäre es ungut für die Pflege der Codebasis komplett auf die anderen angewiesen zu sein.

Lösungen?

Zusammen haben wir noch keine Idee für eine Lösung bekommen, ich habe von verschiedenen Leuten auch ganz verschiedene Meinungen gehört:

Einfach parallel betreiben

Die offensichtliche Lösung, die vor allem keine weiteren Schritte erfordert: Wir betreiben die Seiten parallel.

Ich habe gesagt bekommen "Lass es einfach laufen, dann wird sich am Ende die bessere Seite durchsetzen".

Meine Bedenken: Für die Nutzer ist das eine blöde Situation. Wo stelle ich meine Behauptung ein? Auf der einen Seite? Auf der anderen? Auf beiden? Wie bekomme ich die Stimmen von zwei verschiedenen Seiten zusammengerechnet?

Hör auf, das ist deren Idee

Ich soll aufhören, schließlich hatten die anderen die Idee zuerst.

Das stimmt natürlich, aber ich habe jetzt viel Energie in eine schöne Seite gesteckt, und hätte normalerweise auch Lust gehabt die Seite noch weiter zu entwickeln, bis sie alle Funktionen hat die man sich von so einer Seite wünschen würde. Es wäre also wirklich schade sie jetzt einzumotten.

Die sollen dir die Domain geben

Das ist genau die Gegenposition zum vorherigem Abschnitt.

"Die haben drei Jahre lang die Seite offline gelassen, du hast etwas neues gebaut, wenn sie fair wären, dann sollten sie dir die gute Domain geben und dir die Seite überlassen."

Hier gilt mein Argument vom Abschnitt zuvor genau umgedreht. Die behaupte.es-Leute haben jetzt für den Relaunch ebenfalls viel Energie in ihre Sofware gesteckt, und möchten sie jetzt auch betreiben.

Lösung gesucht!

Nach wie vor weiß bisher keiner von uns eine Lösung, die wirklich für beide Seiten das Problem löst.

Vielleicht hat ja einer der Leser eine Idee? Vorschläge gerne in den Kommentaren oder per Mail (Adressen in der Seitenleiste hier oder auf behaupte-es.de).

Updates

19.12.2011
behaupte.es ist immernoch im "Kurz vor Start der Beta Phase"-Zustand, obwohl der Relaunch ja für den 15. Dezember angekündigt war. Und ich habe auch noch keine Reaktion bekommen auf die E-Mail mit der ich die Zuständigen dort über diesen Blogpost informiert habe.

28.12.2011
Ich habe gerade eine E-Mail bekommen, dass bei behaupte.es doch seit dem 15. Dezember in der Beta-Phase ist, allerdings in einer geschlossenen Beta. Die Seite wird wohl bald in eine offene Beta-Phase wechseln.
21.01.2012
Die behaupte.es-Seite zeigt immernoch "kurz vor Start der Beta-Phase" an, während auf Twitter heute angekündigt wurde dass weitere Beta-Accounts vergeben werden. Behaupte-es.de läuft immernoch offen nebenher.
02.05.2012
Letzter Stand an dem behaupte.es immer noch nur eine Hinweisseite zeigt. (Ich werde diesen Timestamp immer mal wieder aktualisieren, solange die Seite noch nicht aus der geschlossenen Beta heraus ist.)
10.06.2012
behaupte.es ist auch öffentlich online.
03.10.2012
Beide Seiten sind online, auf beiden ist nicht sehr viel los.

Kategorien Fun Software Internet
Tagged Abstimmung behaupte.es behaupte-es.de behaupte es behauptungen django wordpress Php Problem Lösung vote Kooperation Beta
Mobil qrcode zeigen

0 Kommentare

Sept. 18, 2011

Neues Behaupte es!

Nachdem www.behaupte.es (Artikel zur Seite) schon seit Jahren ankündigt baldmöglichst neu zu erscheinen und sich immernoch nichts geändert hat, gibt es jetzt eine neue Behauptungen-Seite.

Hiermit präsentiere ich stolz: www.behaupte-es.de


Bildschirmfoto der Seite

Eventuell könnte die Seite noch ein paar mehr Kategorien gebrauchen, falls also jemand eine wichtige Kategorie weiß, einfach mal hier kommentieren.

Oder einfach mal behaupten dass die Kategorie nötig ist ;).

Kategorien Ankuendigung Internet
Tagged behaupte es behauptungen vote abstimmen
Mobil qrcode zeigen

0 Kommentare

März 23, 2011

Anonymous-Twitter Bookmarklet

Bookmarklet: Anonymous-Twitter

how to use it

  • drag the Bookmarklet above to your bookmarks-toolbar.
  • visit twitter
  • click the Bookmarklet
  • ???
  • PROFIT!

what does it do?

When you click the bookmarklet, every tweet will have "Anonymous" as author, so you can judge the tweets by the message and not by the author.

how does it work?

the bookmarklet runs a tiny piece of javascript on the twitter-page to insert some CSS-Code, which hides the user-images and usernames from twitter and adds "Anonymous" as username and a picture of Anonymous as user-image.

thanks to ...

@paniq, who tweeted the idea and also makes good music.

Stylish / Userscript

you can use the userstyle for twitter, if you want the change to be permanent. the userstyles site has also an option to install the style as userscript.

Kategorien Anonymität Internet Fun english Software
Tagged Anonymous twitter JavaScript Bookmarklet
Mobil qrcode zeigen

0 Kommentare

Aug. 5, 2010

Das Internet neustarten

Eben im Radio gehört:
Es gib jetzt sieben Experten die im Falle eines Terroranschlags das Internet neustarten können.

Ähm, was? Der Sender (1-Live) hat dann etwas weiter ausgeholt und erzählt, es geht um DNSSEC.
Trotzdem, was genau kann man neustarten, sodass es im Falle von Terror etwas bringt? Auch wurde die Nachricht in den Kontext des geforderten Reset-Knopfes für das Internet gesetzt.

Online findet man zum Beispiel im Tagesanzeiger eine entsprechende Meldung. Hier wird auch schön eingeleitet mit:

Es klingt wie der Plot eines Actionfilms mit Tom Cruise oder Matt Damon in der Hauptrolle. Oder wie die Geschichte aus «Herr der Ringe», in der ein Herrscher des Bösen mit einem einzigen Ring die Welt beherrschen will. [...]

weiter gehts dann mit

Im Fall der Fälle müssen sich mindestens fünf der sieben Schlüsselträger an einem geheimen Ort in den USA treffen. Dort würden sie mit ihren Smart Keys, die jeweils einen Teil des Freischaltcodes tragen, gemeinsam das Internet neu starten. Quasi «Control, Alt und Delete» für Fortgeschrittene.

Das ist natürlich purer Unsinn in dieser Form.

Ja, die Herren können DNSSEC neustarten.
Aber nicht im Sinne von abschalten und später neustarten oder im Sinne von "Reset" im Terrorfall, sondern "neu starten" im Sinne von (wieder) starten nachdem es ausgefallen war.
Sie können im Fall dass die Rootserver durch einen Terroranschlag oder anderen Notfall beschädigt oder nicht erreichbar sind einen neuen Rootserver aufsetzen, der gültige Signaturen hat.

Also geht es nicht darum das Internet abschalten zu können, sondern darum im Zweifelsfall einen Ausfall schnell abfangen zu können. Klingt schon ganz anders, nicht?

Einen seriösen Artikel findet man bei silicon.de, wo auch von der Lizenz zur Rettung des Internets geredet wird und nicht von Reset-Schaltern und ""Strg+Alt+Entf." fürs Internet.

Kategorien Internet
Tagged WTF reboot reset neustarten Neustart Terror DNSSEC Ctrl-Alt-Del Rootserver DNS Schlüssel
Mobil qrcode zeigen

0 Kommentare

Nov. 2, 2007

Demokratie 2.0? (Seite)

Da diese Seite etwas veraltet ist, verweise ich auf das AK-Vorrat Linksystem für aktuellere Links.

Demokratie 2.0 Eine Linksammlung zum Thema "Demokratie 2.0". Dabei geht es um Links zum neuem Demokratieverständnis einiger Politiker, die trotz Kritik etwas "jetzt machen" wollen, sowie um die Aushöhlung der Bürgerrechte und ausufernde Überwachung.

Der Inhalt der Seite darf als "public domain" frei verwendet werden. Mirror dieser Seite: im Wiki von Vorratsdatenspeicherung.de

Die Liste wird immernoch weiter ergänzt. Neue Links bitte als Kommentar posten. [letztes Update: 14.12.2007]

Kategorien Anonymität Datenschutz Sicherheit Demokratie Internet Vorratsdatenspeicherung Spionage
Tagged Demokratie2.0 Web2.0
Mobil qrcode zeigen

2 Kommentare