Unterhaltung
Nachrichten
-
-
@kuro ouch
-
@mk Lohan was a nice one, true. Very quiet the last weeks. But it's his legitimate decision. Probably his professional or familiar life...
-
@kuro he was quiet because he lost his SN installation, and was unable to resurrect it (I tried to help but he gave up in the middle of that). What is sad is that he's the kind of person SN _should_ work for but maintaining a site is just too difficult for someone who has only a hazy idea what a "database" is, etc. SN needs to be *manageable* (literally) for non-IT people, artists, writers...
-
Also, all the short links @lohang provided are now inaccessible. And he provided *many* links! So there's a case for allowing longer messages that don't need URL shortening (yes, the target link is in the title text of the short URL, but that's less than trivial to extract)
-
@bobjonkman yes, very very true - shorten only when absolutely needed! and IF needed, use a reliable *external* shortener that doeosn't just stop to exist if your node goes belly-up
-
@bobjonkman that said, he has databases - so at least some of those may be recoverable
-
Makes little difference if the URL shortener is an internal service or external; they all go down eventually.
-
@bobjonkman actually, it makes a lot of difference - shorteners with a professional staff or company behind it has a much smaller chance of going under soon than a single-person site by someone who doesn't do full time "shortening".
-
Even so, I'd be sure to choose an URL shortener with a open database, so that when it does go down the links can still be recovered. !fs
-
m♻ @lohang: @bobjonkman I am concerned about the missing links and group data. I can make the database available to anyone who is willing to recover and if needed can give access to my server as well. I cannot do it myself. I am really sorry about the loss. #sn should be distributed with all these warnings included so people like me will not attempt running it :-P
-
@bobjonkman Indeed, what I said yesterday: making GNU/social more admin-user-friendly should be a very high priority for development - without that, the #federation dream will never really take off. And that starts with god documentation - what little there is is not far too technical for many. /cc mattl @mmn
drak gefällt das. -
@bobjonkman @erkanyilmaz I discovered that '!'CC still leads to http://qttr.at/l5 even if Lohan declared it gone. Any idea how to stop it?
-
@kuro Iguess: clean it from the database, before (anyone) joining the new group
-
@mk How could I? I'm not admin at quitter.se where I subscribed. Should I ask @3mp3 to do sth about it? Exactly what?
-
@kuro @bobjonkman @erkanyilmaz I managed to join the (new) !CC group by navigating to the group on quitter.se
-
@kuro, no, only an admin could potentially do that (remove any group record in the database that points to mini.alochana.net). However, I just managed to subscribe and I now see links pointing to the new group - that might happen on quitter.se as well if anyone there joins the new group (maybe after 'leaving' the old one first. /cc @bobjonkman @erkanyilmaz
-
@kuro The wrong group is probably only in your own !SN database. Just leave the !cc group on mini.alochana.net, then SN should recognize your local group. !fedgroups
-
@bobjonkman You're right, I had forgot to readjust that. Good hint, thanks! - Indeed I had expected -> alochana closedown eliminated connex.
-
@mk Some days ago I tried to DL the http://qttr.at/81 database in txt format but only got 33 bytes. I hope @evan can help http://qttr.at/4hl
-