Notices tagged with gnusocial, page 7

  1. @sen Resources don't really matter, what matters is longevity (backups, plan to keeo running the instance...) and preferrably good !GNUsocial experience as issues might arise that might need debugging and investigation. !fediverse

    Sunday, 30-Jul-17 08:54:25 UTC from social.umeahackerspace.se at 63°49'42"N 20°15'34"E
  2. No way to know whether I'll succeed in this, but I'm planning to submit at least one patch each to # and # in 2017. And to try to help create better docs for both projects.

    Sunday, 16-Jul-17 01:40:13 UTC from gs.kawa-kun.com
  3. @hikerus Mastodon had in a previous version (probably still widely in use?) an antifeature that ended push-subscriptions with a slightly too trigger-happy assumption of when a remote server has disappeared.

    While !GNUsocial happily continues several months after initial failures .)

    Wednesday, 12-Jul-17 13:53:04 UTC from social.umeahackerspace.se at 63°49'42"N 20°15'34"E
  4. Verschiedene Admins von Instanzen haben offenbar das Problem mit den Daemons resp. der zu ändernden Route Table noch nicht mitbekommen. !gnusocial

    https://gnusocial.de/notice/10639719

    Sunday, 09-Jul-17 20:12:30 UTC from social.bitcast.info Repeated by mcscx2
  5. Again with the same issue on !gnusocial : remind to kiil manually all daemon afater use stopdameon . Must search for another IP ?

    Sunday, 09-Jul-17 15:27:14 UTC from ostatus.shnoulle.net at 50°41'39"N 3°10'28"E Repeated by mcscx2
  6. @shnoulle 60 is the original default. Nothing should ever take more than 60 seconds to complete for a webserver that remote users can initiate requests for  (i.e. link stuff that gets looked up by your !GNUsocial server). If it was up to me I'd set it to 30 seconds or something.

    oEmbed etc, which in combination with StoreRemoteMedia does remote downloads, has an upper limit anyway on how large files to download (so 30 seconds should be reasonable unless your server is on a really slow connection).

    Monday, 10-Jul-17 13:01:57 UTC from social.umeahackerspace.se at 63°49'42"N 20°15'34"E
  7. Verschiedene Admins von Instanzen haben offenbar das Problem mit den Daemons resp. der zu ändernden Route Table noch nicht mitbekommen. !gnusocial

    https://gnusocial.de/notice/10639719

    Sunday, 09-Jul-17 20:12:30 UTC from social.bitcast.info
  8. Again with the same issue on !gnusocial : remind to kiil manually all daemon afater use stopdameon . Must search for another IP ?

    Sunday, 09-Jul-17 15:27:14 UTC from ostatus.shnoulle.net at 50°41'39"N 3°10'28"E
  9. Reminder for !gnusocial / !postactiv  admins:  It would be a good idea to blackhole requests to/from 91.121.67.58 since it can otherwise mess up your queue and halt federation.

    Linux instructions for doing so: https://www.cyberciti.biz/tips/how-do-i-drop-or-block-attackers-ip-with-null-routes.html

    Saturday, 08-Jul-17 21:44:54 UTC from gs.archae.me in context Repeated by takeshitakenji
  10. Reminder for !gnusocial / !postactiv  admins:  It would be a good idea to blackhole requests to/from 91.121.67.58 since it can otherwise mess up your queue and halt federation.

    Linux instructions for doing so: https://www.cyberciti.biz/tips/how-do-i-drop-or-block-attackers-ip-with-null-routes.html

    Saturday, 08-Jul-17 21:44:54 UTC from gs.archae.me in context Repeated by therubackup
  11. Reminder for !gnusocial / !postactiv  admins:  It would be a good idea to blackhole requests to/from 91.121.67.58 since it can otherwise mess up your queue and halt federation.

    Linux instructions for doing so: https://www.cyberciti.biz/tips/how-do-i-drop-or-block-attackers-ip-with-null-routes.html

    Saturday, 08-Jul-17 21:44:54 UTC from gs.archae.me in context
  12. mastodon.xyz/media/PK1YfzKdgdF

    Friday, 07-Jul-17 19:45:53 UTC from mastodon.xyz in context Repeated by takeshitakenji
  13. mastodon.xyz/media/PK1YfzKdgdF

    Friday, 07-Jul-17 19:45:53 UTC from mastodon.xyz in context
  14. How well known is it amongst # users that their privacy features don't really work outside of their own instance? Perhaps some admins know, but much of the flaming is coming from people angry that # doesn't follow the privacy conventions of # But being angry that the # developer(s) aren't creating the same illusion of privacy is really misdirected anger.

    Wednesday, 05-Jul-17 01:46:06 UTC from sn.jonkman.ca at 43°36'0"N 80°32'58"W Repeated by hfaust
  15. I'm perfectly happy that # exists, and if it implements # in a future version, more power to it. And if it drops # support, well, that's what forks (or reimplementations) like # are for. But don't blame # developers for not following #'s road map for the future.

    Wednesday, 05-Jul-17 01:58:46 UTC from sn.jonkman.ca at 43°36'0"N 80°32'58"W Repeated by dogjaw
  16. How well known is it amongst # users that their privacy features don't really work outside of their own instance? Perhaps some admins know, but much of the flaming is coming from people angry that # doesn't follow the privacy conventions of # But being angry that the # developer(s) aren't creating the same illusion of privacy is really misdirected anger.

    Wednesday, 05-Jul-17 01:46:06 UTC from sn.jonkman.ca at 43°36'0"N 80°32'58"W Repeated by moonman
  17. I'm perfectly happy that # exists, and if it implements # in a future version, more power to it. And if it drops # support, well, that's what forks (or reimplementations) like # are for. But don't blame # developers for not following #'s road map for the future.

    Wednesday, 05-Jul-17 01:58:46 UTC from sn.jonkman.ca at 43°36'0"N 80°32'58"W Repeated by moonman
  18. How well known is it amongst # users that their privacy features don't really work outside of their own instance? Perhaps some admins know, but much of the flaming is coming from people angry that # doesn't follow the privacy conventions of # But being angry that the # developer(s) aren't creating the same illusion of privacy is really misdirected anger.

    Wednesday, 05-Jul-17 01:46:06 UTC from sn.jonkman.ca at 43°36'0"N 80°32'58"W Repeated by guizzy
  19. How well known is it amongst # users that their privacy features don't really work outside of their own instance? Perhaps some admins know, but much of the flaming is coming from people angry that # doesn't follow the privacy conventions of # But being angry that the # developer(s) aren't creating the same illusion of privacy is really misdirected anger.

    Wednesday, 05-Jul-17 01:46:06 UTC from sn.jonkman.ca at 43°36'0"N 80°32'58"W Repeated by sw0rn
  20. How well known is it amongst # users that their privacy features don't really work outside of their own instance? Perhaps some admins know, but much of the flaming is coming from people angry that # doesn't follow the privacy conventions of # But being angry that the # developer(s) aren't creating the same illusion of privacy is really misdirected anger.

    Wednesday, 05-Jul-17 01:46:06 UTC from sn.jonkman.ca at 43°36'0"N 80°32'58"W Repeated by mmn
  21. I'm perfectly happy that # exists, and if it implements # in a future version, more power to it. And if it drops # support, well, that's what forks (or reimplementations) like # are for. But don't blame # developers for not following #'s road map for the future.

    Wednesday, 05-Jul-17 01:58:46 UTC from sn.jonkman.ca at 43°36'0"N 80°32'58"W
  22. How well known is it amongst # users that their privacy features don't really work outside of their own instance? Perhaps some admins know, but much of the flaming is coming from people angry that # doesn't follow the privacy conventions of # But being angry that the # developer(s) aren't creating the same illusion of privacy is really misdirected anger.

    Wednesday, 05-Jul-17 01:46:06 UTC from sn.jonkman.ca at 43°36'0"N 80°32'58"W
  23. @samy Das ist eine grundlegende Frage: willst du dich auf einen Dienst und seine Willkür verlassen - oder nutzt du lieber einen Dienst, der auf Grund seiner technischen Struktur kaum willkürlich handeln kann.

    # (und seine Vorläufer) existieren fast ebenso lange wie Twitter, seit 2008 um genau zu sein. In dieser Zeit wurde ein Netzwerk aufgebaut, das unabhängig von finanziellen Interessen besteht. Alles freiwillig, vieles schlicht aus Überzeugung. Das Netzwerk ist mittlerweile hunderte Server groß und bietet tausenden Nutzern eine Alternative.

    Um auf deine Ausgangsfrage zurück zukommen, eine Analogie:
    Wozu gibt es !Freifunk? Das ist doch nur eine weitere Infrastruktur mit noch mehr Arbeit und den selben Menschen und am Ende bietet es ja doch im Prinzip "das Gleiche".

    Saturday, 01-Jul-17 23:33:36 UTC from gnusocial.de at 48°22'0"N 10°53'55"E Repeated by kzimmermann
  24. @samy Das ist eine grundlegende Frage: willst du dich auf einen Dienst und seine Willkür verlassen - oder nutzt du lieber einen Dienst, der auf Grund seiner technischen Struktur kaum willkürlich handeln kann.

    # (und seine Vorläufer) existieren fast ebenso lange wie Twitter, seit 2008 um genau zu sein. In dieser Zeit wurde ein Netzwerk aufgebaut, das unabhängig von finanziellen Interessen besteht. Alles freiwillig, vieles schlicht aus Überzeugung. Das Netzwerk ist mittlerweile hunderte Server groß und bietet tausenden Nutzern eine Alternative.

    Um auf deine Ausgangsfrage zurück zukommen, eine Analogie:
    Wozu gibt es !Freifunk? Das ist doch nur eine weitere Infrastruktur mit noch mehr Arbeit und den selben Menschen und am Ende bietet es ja doch im Prinzip "das Gleiche".

    Saturday, 01-Jul-17 23:33:36 UTC from gnusocial.de at 48°22'0"N 10°53'55"E
  25. There's the idea of organizing a for .

    Firs location proposal was .

    Who of you would be interested in a ?

    fav. : I'm in
    boost : let's spread it to make it succsed

    Wednesday, 28-Jun-17 11:00:33 UTC from mastodon.social Repeated by ghostdancer
  26. I love #

    Thursday, 29-Jun-17 12:10:11 UTC from gs.kawa-kun.com Repeated by takeshitakenji
  27. I love #

    Thursday, 29-Jun-17 12:10:11 UTC from gs.kawa-kun.com
  28. There's the idea of organizing a for .

    Firs location proposal was .

    Who of you would be interested in a ?

    fav. : I'm in
    boost : let's spread it to make it succsed

    Wednesday, 28-Jun-17 11:00:33 UTC from mastodon.social Repeated by bastianilso
  29. @deadsuperhero what do find more attractive about it than # or #? The lack of full # support (eg !groups) put me off

    Thursday, 29-Jun-17 01:59:40 UTC from quitter.se
  30. There's the idea of organizing a for .

    Firs location proposal was .

    Who of you would be interested in a ?

    fav. : I'm in
    boost : let's spread it to make it succsed

    Wednesday, 28-Jun-17 11:00:33 UTC from mastodon.social Repeated by mmn