@gargron You should do it like us in !GNUsocial and !qvitter and just fuck the poooo...liticans' insane legalese law making. Don't let morons put boundaries on your creativity and effectiveness.
Hi !fediverse, does anyone knows a #Friendica public server which offers cross posting with #Diaspora, #GNUSocial and #Pump? And, if possible, with the possibility of reflecting RSS feeds. I'm considering to !selfhost, how difficult is to set up Friendica? Thx
Btw @chimo could I ask of you (and anyone else reading this too!) to do the https://websub.rocks tests for !gnusocial and submit the results as per instructions on the site?
@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 .)
Ooh, yes. Make the #WebMention (LinkBack) plugin work properly in !GNUsocial. _THAT_ is my vacation project. Oh how I've wanted to do this. I will make @kevinmarks proud.
@headcrack !GNUsocial stalls because the underlying HTTPS request never times out, which only happens with PHP sockets as the backend for HTTP_Request2 and not with the CURL backend. This is reproducible outside of the GNUsocial framework as well: http://status.hackerposse.com/url/15690 I am fully aware of the snail-pace type DoS attack and that's why there is a "full…
@sen @headcrack Unless I'm horribly mistaken, that's an entirely separate timeout. I.e. for the daemon->subprocess. The subprocess on its own has its entirely own timeouts for each individual instruction it runs. Also, if this is supposed to relate to the http://status.hackerposse.com/url/15696 ordeal, it doesn't explain why CURL as a backend handles it perfectly fine…
@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 up…