Nov. 24, 2016

Links (120)

Kategorien Links
Tagged Raytracker Entropy Sheep Bubcon Gina-Lisa Lohfink Alice Schwarzer Sifftwitter Grundgesetz Amadeu-Antonio Amadeu-Antonio Stiftung Telefonnummern SMS Quietscheenten Tetris TetrOS JavaScript 2016 Bahn WLAN git Pill Empfängnisverhütung Männer Kasperski Microsoft Terry Pratchett Werbung Adblocker AfD
Mobil qrcode zeigen

0 Kommentare

Nov. 6, 2016

Technischer Datenschutz: Anonymes VPN

Wer im Internet unterwegs ist hat eine eindeutige IP-Adresse zugeordnet, an die Webseiten und andere Dienste die Daten schicken. Die Adresse, die sich üblicherweise nur einmal am Tag ändert, kann benutzt werden um einen durchs Web zu verfolgen.
Im Zuge der Vorratsdatenspeicherung sind Internetprovider verpflichtet die Zuordnung der Adresse zu einer Person längere Zeit zu speichern.

Hier hilft ein VPN-Anbieter. Ein typisches Privacy-VPN kostet zwischen 5 und 15 Eur im Monat, wobei es häufig Rabatt gibt wenn man es für einen längeren Zeitraum bucht.

Übersicht
Typ: Dienstleistung, Software
Aufwand: Einmalige Installation
Komplexität: Mittel
Kosten: 5-15 Eur im Monat
Schützt vor: Tracking über die IP, unsichere Netzwerke

Bei einem Privacy-VPN muss man dem Anbieter den man wählt vertrauen, dass er das Versprechen nichts aufzuzeichnen einhält.
Der Anbieter selber hat einen Ruf zu verlieren und auch selber ein Interesse daran bei Anfragen sagen zu können "Wir speichern nichts", aber als Kunde hat man keine Möglichkeit zu prüfen ob es stimmt. Daher werde ich hier auch keinen einzelnen Anbieter empfehlen.

Wogegen hilft ein VPN?
Normalerweise verbindet sich der Computer direkt mit der angesuften Seite. Dabei kann der eigene Internetanbieter alles1 mitlesen und die Seite sieht eine IP-Adresse die zu dem Zeitpunkt dem Internetanschluss fest zugeordnet ist.
Über die IP-Adressen können unterschiedliche Seiten feststellen, dass der gleiche Nutzer sie besucht und wenn sich der Nutzer zum Beispiel ein öffentliches WLAN benutzt können alle Leute im gleichen WLAN seine Daten ebenfalls mitlesen.

Wie funktioniert ein VPN?
Benutzt man ein VPN, werden die Daten zunächst verschlüsselt zum VPN-Anbieter geschickt und von dort aus mit einer Adresse des Anbieter zur angesurften Seite. Der Anbieter verspricht, dass er nicht speichert welche Adresse des Kunden welche Adresse des Anbieters benutzt hat.
Bei den meisten Anbietern teilen sich mehrere Kunden eine Adresse des Anbieters, was die Anonymität weiter erhöht.

Damit ist die Verbindung gegen die Lauscher im WLAN und beim eigenen Internetanbieter geschützt, weil sie bis zum VPN-Anbieter verschlüsselt ist. Ab dort wird sie normal zur Zielseite weitergeleitet.
Da der Anbieter die Daten weiterleitet sehen die Webseiten nur noch die Adresse des Anbieters und nicht mehr die echte Adresse des Nutzers.. Dadurch können sie den Nutzer nur bis zum VPN-Anbieter zurückverfolgen, der wiederum keine Daten gespeichert hat die eine Zuordnung ermöglichen.
Dadurch, dass mehrere Nutzer die gleiche Adresse benutzen wird es außerdem schwierig einen einzelnen Nutzer im Web zu verfolgen.

Wo finde ich ein gutes VPN?
Das wichtigste bei einem VPN ist Vertrauen: Man muss seinem Anbieter vertrauen, dass er wirklich keine Zuordnung von VPN-Adresse zu echter Adresse speichert und dass er selber nicht mitliest2. Außerdem gibt es Unterschiede beim Preis, darin wieviele Geräte gleichzeitig das VPN benutzen können und Spezialfunktionen die nur einige Anbieter haben.

Weil das Vertrauen in den Anbieter der wichtigste Faktor ist, sollte jeder selber entscheiden, welches VPN er benutzt. Um sich ein gutes Bild zu machen führt das Onlinemagazin Torrentfreak einmal im Jahr Interviews mit verschiedenen VPN-Anbietern und es gibt eine Seite mit Vergleich der wichtigsten Eigenschaften, die ich beide als Hilfe zur Wahl des passenden VPNs empfehlen kann:

Als weiteres Entscheidungskriterium empfehle ich die Privatssphärenerklärung des Anbieters genau zu lesen. Im Allgemeinen gilt "je kürzer, desto besser".
Wenn dort 10 verschiedene Fälle stehen unter welchen Umständen sie doch aufzeichnen ist ein schlechtes Zeichen. Wenn dort nur steht "We will never log anything under any circumstances" ist das ein gutes Zeichen.

Wie benutze ich ein VPN?
Die meisten VPN-Anbieter haben eine eigene Software und häufig auch Apps, die nur installiert werden müssen. Diese Zugangssoftwares sind normalerweise sehr leicht zu bedienen.
Mehr Details zur jeweiligen Software sind meistens auf der Homepage des Anbieters den man sich ausgesucht hat zu finden.

Fußnoten

1) Alles was nicht anderweitig vor dem versenden schon verschlüsselt ist.
2) Ein VPN-Anbieter kann so viel mitlesen, wie der eigene Internetanbieter oder jemand im gleichen WLAN mitlesen kann wenn man kein VPN benutzt.

Kategorien Vorratsdatenspeicherung Datenschutz Verschlüsslung Überwachung
Tagged technischer Datenschutz VPN
Mobil qrcode zeigen

0 Kommentare

Okt. 30, 2016

Technischer Datenschutz: 3rd-Party Cookies

Eine einfache Einstellung zum Verhindern von Tracking ist das deaktivieren von Third-Party Cookies.

Third-Party Cookies sind Cookies, die von anderen Seiten als der momentan besuchten Seite kommen. Damit sind sie sehr gut zum Tracking über mehrere Seiten hinweg geeignet und werden auch hauptsächlich dafür benutzt.

Übersicht
Typ: Einstellungen
Aufwand: Einmalig ändern.
Komplexität: Gering
Schützt vor: Seitenübergreifendem Tracking mit Cookies.

Third-Party Cookies deaktivieren in Firefox:

  • Menu
  • Einstellungen
  • Datenschutz
  • "Firefox wird eine Chronik: ..." auf "[nach Benutzerdefinierten Einstellungen anlegen]" ändern.
  • "Cookies von Drittanbietern akzeptieren:" entweder auf "Nur von besuchten Drittanbietern" oder "Nie" ändern.

Third-Party Cookies deaktivieren in Chrome:

  • Menu
  • Einstellungen
  • Unten den Link "Erweiterte Einstellungen anzeigen" anklicken
  • Button "[Inhaltseinstellungen]"
  • Häkchen machen bei: "Drittanbieter-Cookies und Websitedaten blockieren"

Die Einstellung "Nur von besuchten Drittanbietern" bei Firefox ermöglicht es, dass zum Beispiel Facebook Like-Buttons auch außerhalb von Facebook Cookies lesen und setzen dürfen, wenn man selber schon mit Firefox auf Facebook war.

Der Vorteil ist, dass Funktionen wie "X deiner Freunde haben die Seite geliked" weiter funktionieren. Der Nachteil ist, dass Facebook den Nutzer wieder über alle Seiten mit Likebuttons hinweg verfolgen kann. Das gilt für andere Seiten die häufig eingebunden werden wie Twitter, Google und weitere entsprechend auch.

Kategorien Datenschutz
Tagged Cookies 3rd-Party Cookies technischer Datenschutz
Mobil qrcode zeigen

0 Kommentare

Okt. 23, 2016

Technischer Datenschutz: PrivacyBadger

Der Privacy Badger ist ein Browser-Addon, das von der amerikanischen Bürgerrechtsorganisation EFF entwickelt wurde. Das praktische an dem Addon ist, dass es ohne etwas einzustellen sofort funktioniert und beim normalen Surfen kaum wahrgenommen wird.

Übersicht
Typ: Browser-Addon für Chrome und Firefox.
Aufwand: Einmalige Installation.
Komplexität: Keine Pflege oder Einstellungen nötig.
Schützt vor: Seitenübergreifendem Tracking.

Beschreibung

Der Privacy Badger verfolgt, welche Seiten von welchen anderen geladen werden. Wird eine Seite häufig von anderen geladen ohne dass der Nutzer es braucht, ist es wahrscheinlich, dass es sich um Trackingscripte wie Google-Analytics handelt. In einem solchen Fall werden zunächst keine Cookies mehr mitgesendet (Status: gelb) und wenn es sich um offensichtliches Tracking hält wird die ganze Verbindung blockiert (Status: rot).

Damit werden zum Beispiel Cookies die für einen Warenkorb im Onlineshop verwendet werden zugelassen, während Cookies die dazu verwendet werden zu verfolgen auf welchen Seiten der Nutzer nacheinander war abgelehnt werden.

Mit einem Klick auf das Privacy Badger Icon kann man sehen, welche Seiten gerade eingebunden sind und welche davon blockiert wurden. Ein Klick auf den Schieberegler hilft manuell Seiten zu blockieren oder eine Blockade aufzuheben.

Anfangs sollten alle Seiten auf grün stehen, aber je länger der Privacy Badger "mitsurft", desto schneller lernt er, welche Seiten den Nutzer verfolgen und fängt an diese zu blockieren, während er erkennt welche Seiten legitim sind. Damit ist keine Konfiguration nötig und es werden auch keine externen Filterlisten wie zum Beispiel bei Adblockern benötigt.

Werbung wird teilweise mitblockiert, wenn sie gleichzeitig den Nutzer verfolgt. Reine Werbung ohne Tracking wird vom Privacy Badger nicht blockiert.

Fazit
Dafür, dass man nichts weiter tun muss als den Privacy Badger zu installieren leistet er gute Dienste um Nutzertracking zu erschweren. Eine Installation kann nicht schaden.

Kategorien Datenschutz
Tagged technischer Datenschutz PrivacyBadger
Mobil qrcode zeigen

0 Kommentare

Okt. 23, 2016

Technischer Datenschutz

Im Internet sind die eigenen Daten häufig Freiwild. Während inzwischen bekannt ist, was die NSA treibt und die Vorratsdatenspeicherung schon einmal gekippt wurde, geht es politisch leider wenig voran.

Die Vorratsdatenspeicherung ist neu beschlossen worden und noch nicht wieder gekippt, über die Konsequenzen dessen was 2013 über die NSA heraus gekommen ist wird immer noch in Ausschüssen die erst einmal diskutieren ob es überhaupt so schlimm ist beraten. Wer politisch etwas tun möchte: Ja bitte!

Aber die politischen Lösungen dauern und sind schwer durchzusetzen und bis dahin sind eure Daten weiter ungeschützt. Daher werde ich hier einfache Anleitungen sammeln, wie man sich technisch schützt, solange der gesetzliche Schutz fehlt.

  1. Tracking Schutz mit dem PrivacyBadger
  2. Deaktivieren von 3rd-Party Cookies
  3. Ein VPN benutzen
  4. Adblock benutzen
  5. Mehrere Browserprofile
  6. Referer blockieren
  7. Die Firefox Tracking Protection
  8. Sichere Passwörter und Passwortmanager

Kategorien Datenschutz
Tagged technischer Datenschutz
Mobil qrcode zeigen

0 Kommentare

Aug. 20, 2016

Links (119)

Kategorien Links
Tagged Kryptografie Cryptography Emoji Gender Gap Pokemon Pokemon Go Datenschutz Datenweitergabe Gina Lisa statistics Dealer Psychopharmaka Sexualstrafrecht Privacy Snowden Erziehung Privatssphäre WIPP Neural Network voice machine learning Gesichtserkennung Berlin WLAN Tor Tor Projekt #kleinpeng
Mobil qrcode zeigen

0 Kommentare

Juni 26, 2016

Links (118)

Kategorien Links
Tagged WLAN claw maschines Werbung Ads Web infinite Jukebox Stackoverflow RegEx HTML pay gap Gender Math american airlines Flightradar24 Privacy anonymity Vergewaltigung rape culture Maintainer upstream packaging forbes wired WiFi Lichtschalter Owncloud pwncloud April Webcomic fool Emoji miscommunication Kansas map geolocation farm neuronal net Neuronales Netz tensorflow
Mobil qrcode zeigen

0 Kommentare

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

April 16, 2016

Berufe ohne Zukunft #55

Berufe ohne Zukunft #55: Fernbedienung

Kategorien Berufe ohne Zukunft
Tagged Fernbedienung
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