Please enable javascript to use this site.
Quitter.no closing 5th September 2018. Please read this notice. -A.
· OpenID

Message to users of quitter.no. I've decided to close this site on it's 4th birthday, that is 5th September -18. I do not have the energy and capacity to host the site anymore. Please "migrate" or find a new GNU Social home. I've decided to not handover the maintenance or data to anyone else - so please do not ask to get the data to host this site further. Thank you all for using Quitter this period and for following it's users. -A.

  1. @mcscx2@quitter.no (mcscx2@quitter.no)'s status on Thursday, 07-Jun-2018 19:35:08 CEST @mcscx2@quitter.no @mcscx2@quitter.no
    in reply to
    @knuthollund hi, I think the situation with IPv4 has not improved yet. Also https://fediverse.network/quitter.no still reports 65% availability.

    OTOH I can confirm that quitter.no has been working very well during my whole testing period of almost a week over my # socks #

    In case other IPv4 !quitterno users want to try: I just did
    ssh -D 5555 username@some-host-with-ipv6-connectivity
    and set the socks proxy settings in firefox to localhost:5555.

    Maybe there are still some little oddities even with IPv6, because every few minutes the ssh client logs a message like:
    "channel 13: open failed: connect failed: No route to host"
    but one doesn't notice anything of that in firefox.

    For comparison I also tried a socks-proxy-over-ssh connection to an IPv4-only host and, as expected, firefox will give the same "cannot connect to quitter.no" error pages as via a direct IPv4 connection.