I would like to suggest understanding failed logins that previously worked as a possible intermediate problem with authorisation from wrong IPs.
As first implementations of libwrap2 are already running nextcloud instances it may well be that a login is rejected by the auth module not because of a password failure but because of an island failure (meaning login request originating from an IP that is not whitelisted). Since this can very likely be an intermediate problem of the client hardware (mobile lost connection to VPN or a WLAN) it is not wanted that all login data (account and password) must be entered again, although they have not changed.
If you are a nextcloud representative and have no idea what I am talking about please contact me by PM.
Thank you
Oh and btw, big bold letters won’t get your request a higher priority, so please don’t use any if you can help it. It doesn’t come across as very nice that way
The bold text was due to Marktown formating, and has been fixed now.
The thing is, I used no formatting at all but simply typed it in, just like this.
… and btw just looked again by editing, and there is no sign of any bold visible for me. Since I am probably one of the last ASCII mailers I never use formatting anyway.
I understand that, but besides being a side note it seems an obvious formatting issue in this forum.
is it possible that its handling of a
“dash dash
Regards”
is broken?
Not sure, but I don’t think there is a general problem, as I have never experienced this in any of my own posts, at least not when typing directly into the online editor.
The only thing I can think of is that when you paste text into the online editor, depending on where you are copying from, some hidden characters or spaces may be copied along that the editor interprets as markdown syntax.
Here you see what happens if you follow the rule to separate the body from the signature by double dash
I’d say this is clearly broken
Check for yourself
I might elaborate that splitting the body and the signature by double-dash is not my invention but used for at least 40 years in mailing-lists, so it is in fact good practice. Only because the authors of this forum are obviously too young to know (internet 2.0 generation it seems) will not make it change.
To generate a formatting effect upwards (i.e. to the beginning) in a text is a very clear sign of a general design bug. This should not be possible at all. All formatting should effect downwards, and if you hit something first that is some kind of a termination sign without a starting format option then it should be expected to be ignored.
Still all has nothing to do with the basic described topic.
Well, I’m not going to spend any more time on this in my eyes minor issue. If it bothers you enough to take action, you could do the following:
First of all, find out if the issue is unique to the Nextcloud forum, or if it exists in other Discourse forums as well. A good place to find out would be here: https://try.discourse.org/
What you are suggesting is really the wrong way round. As I am not really interested in web forums anyway I really don’t care. I try to bring a topic to someones eyes from whom I have no idea who he is and how he can be contacted otherwise (which is not my fault).
You tried to rule me about bad style and I only showed (i.e. proved to) you that I am the wrong addressee for this either.
In the end I probably will end up on the same outcome like so many times before, I tried to help people but they are too busy making money with a buggy forum that only shows bling but no way for a real communication.
I think you are wildly overreacting here. I mean, does this “bug” prevent you from posting on the forums? Obviously not. Yes, you can’t format your posts exactly the way you want, but that’s really all there is to it, and that in no way justifies your exaggerated reaction.
After all, both Nextcloud and Discourse are free and open source projects that are provided to you, respectively in this case to the Nextcloud community, free of charge.
If you don’t like something about a FOSS product, or if you find an issue that you would categorise as a bug, get involved, report it to the appropriate places, and of course constructive criticism is allowed as well, but please do so without basically calling the people who give you their stuff for free idiots.
Stay pracmatic and on topic, and don’t make assumptions about why a bug exists or why certain decisions were made and thereby accuse people acting in bad faith, just because you may have had negative experiences with certain induviduals in the past, or because someone disagreed with you. Things are rarely ever just black or white.
What I am doing is giving a clear feedback and not softening facts just to sound nice.
Fact is: you ruled me for entering ascii text that was/is misinterpreted by a forum software that has obviously no clear design of formatting elements (like e.g. HTML has). Clearly bad programmers made it and you try to soften the fact with the ever-so-nice argument of "it’s free for you to use’‘. Yes, it’s free and it’s bad (but bling, which was obviously the first design goal).
So don’t go and call me the bad boy. Point to the right people that caused the problem. Else it will never be solved.
I write open source software for more than 40 years now and have never used the excuse of “it is free” for stuff that I made bad.
I won’t go on and talk about some major projects that were turned down in all kinds of ways by people whose best excuse is always “it is free”.
You have to have the unbending will to reach a high quality standard, else you only waste peoples’ time with your output.
please lets end it here and waste no more time. Simply don’t blame me, I am the wrong target at this point.
Yes, you found out that a double dash reformats the text above it, I confirmed it, and we established that this is likely a bug. So far so good.
But then you started to rambeling about the internet 2.0 generation, and a buggy forum that only shows bling, but doesn’t provide a way to communicate. I mean common man, don’t you think you’re slightly exaggerating, I mean we are communicating here, aren’t we?
I’ve provided links to the appropriate places and a possible workaround. However, I’m not going to report it for you, because I honestly don’t care enough about this bug, as it doesn’t affect the way I use the forums, and even if I wanted to add a signature, I could easily work around it by adding another line break, and so could you
We both agree to confirm a bug.
We only have to find an agreement now that the “bug” caused us wasting time talking about the bug and not the topic.
And that is my critics on the forum being “bling”, it leads people to talking about the forum more than about the presented topic.
That is not genetic but educated behaviour. Ask yourself why you thought it was necessary to jump on me assuming writing bold/big without thinking about an equally probable assumption of a bug in the forum software.
It makes no sense for me to report such a “bug” as for me it is obvious that the problem is not the showed wrong behaviour but a general design problem within the software and its format language definition. Iow it is broken by design. A bug report is no appropriate way to educate someone in writing better software. Only a majority not using such software will do that.
Yeah, we’re probably not going back to mailing lists and newsgroups with plain text clients.
Also, in this case, it’s not a big deal that we didn’t discuss it here, since feature requests are best placed on GitHub anyway, as I suggested in my very first reply in this thread.
If for some reason you still absolutely want to discuss it here, I’d suggest you repost it, or I could offer to remove my “sidenote” from my first reply, and delete all my following replys.
However, I’m not sure if this is worth the effort, so my suggestion is that we leave this thread as is, and you post your feature request as an issue on GitHub, which is the appropriate place for feature requests in the first place.
I fixed it.
You placed -- direktly under your message, that makes (made) the complete text bold. That is a Markdown syntax feature one should know, since Markdown is used on nextcloud as well
No, it is not broken, since that is email syntax and it works, if you leave one empty line before the two dash.
And btw, to separate signatures in email, the two dashes are not enough, it must be two dashes followed by an empty space, which is something what markdown can not.
So once again, ascii mailing and markdown are two complete different worlds
Then this should probably be re-thought.
Backreferencing format tags are really something thought to be long eliminated.
Don’t call it a “fix” though, what you did is a work-around. Called this way because it is working around an existing problem, nothing really fixed regarding the problem.
Nevertheless I would love to see someone discussing the topic, not the forum software …
