Just a detail, but in a recent game there were an error in the engines move notation as it wrote Nexd4 even though only one knight could take on d4. I experienced this in the most recent iOS version of the Lichess app running on a iPhone 6.
Heres a screenshot of the bug:
https://imgur.com/NflDE6o
I think SF checks for pseudo-legal moves when making notations.
@Solal35 "pseudo-legal moves" / what does that mean, a move is either legal or not IMHO
Pseudo-legal = otherwise legal but you haven't checked if it puts your own king in check. A typical way to generate legal moves is to generate pseudolegal moves, then for each move check if in the position resulting from the move, the opponent can pseudo-legally capture the player's king.
This is not a glitch, even though the knight is pinned.
Ok thank you - I understand now the meaning of "pseudo-legal moves" - at least learned something new today ;)
But still, as a user of Lichess, I should not need to know the technical details regarding algorithms and implementation to not get confused about inconsistency in move notation - therefore I still think this is a bug
Even the mighty Informator (Informant) as well as ChessBase use the extended notation (French Winawer: "4. Nge2").
In fact it is used more often,
@Sarg0n OK I see - then maybe it is not a bug after all, but still think it is strange...
On another site - will not mention it here but it is also a chess committed site - I stumbled on this below, which really shows how much confusion such inconsistency in the rules of chess notation can cause:
https://imgur.com/bFxSjH2
This topic has been archived and can no longer be replied to.