Notices tagged with admin

markov

Man, i dont like how the #admin aren't reading any of these messages here yet!

markov

Man, i dont like how the #admin aren't reading any of these messages here yet!

markov

At least i know now that the #admin isnt the trouble here anyway.

markov

At least i know now that the #admin isnt the trouble here anyway.

markov

Man, i dont like how the #admin aren't reading any of these messages here yet!

markov

At least i know now that the #admin isnt the trouble here anyway.

nat

If #ADMIN is reading then they must KNOW what the issue is with COVER UPLOAD.

mk

just solved another problem that's been nagging me for nearly ever: my main user on Dennis had a different UID than my same-named main user on Nikola - result: files on external drives owned by main user when plugged into one computer, but inaccessible (non-existent user) when plugged into the other computer. combination of groupmod & usermod on Dennis and chown on the NAS where I temporarily plugged in the drives one by one: suddenly this was easy-peasy! and fun! #NAS #admin

mcscx pztrn , cmhobbs

@cmhobbs I think these issues can be fixed by your #admin. Do you get timeout / slowness problems when trying to send via Web? c/ @pztrn

mcscx lnxw37

..By setting user-agent to string ..roodkcableoj28840ybtide (read #backwards!)anyone can access the #admin web interface w/o authentication

mk Michael Vogel

It's OK if you can *learn* tot maintain it, or if it's been written so it's *easy* to maintain. Yet Lohan was perfectly able to run a WordPress site for years - and unable fix problems with his SN site. SN just doesn't have the kind of 'end-user maturity' yet that WP has. If we want federation to come off the ground (and I do) then SN must become as easy to administer as WordPress. It shouldn't require anything command-line and it shouldn't require any editing of code. Such things are easy to accomplish - they just haven't been done yet. IMO they _should_ be done. #SN #admin

erkanyilmaz mmn , grote

In theory: NO. The problem must be handled by the statusnet #admin where the user has the problem. I say no, but I normally do the #DB cleaning with all parties involved online (e.g. irc) to make sure: both parties have correct new info. btw: the issue was reported 2 years ago in #statusnet bugtracker http://status.net/open-source/issues/3219 by #GNUsocial member @mmn@freesocial.org re: http://oracle.skilledtests.com/conversation/168140#notice-250136

erkanyilmaz tuttle

@tuttle Did the #admin of your SN server change something ? Try also to unsub and #resub to one of those problematic groups, if that fixes it ?

erkanyilmaz tuttle

Did the #admin of your SN server change something ? Try also to unsub and #resub to one of those problematic groups, if that fixes it ?

erkanyilmaz kuro

You, as mere user, can NOT change that, the #admin of your SN instance must change that

Pony Cabal

Good evening. I will be your MOD this evening. #admin