Nutomic
Again all these arguments make sense for mobile, but not for large screens. Its good to improve the UX for mobile but that shouldnt negatively affect desktop UX. So when...
Not sure about that. But I thought it would be useful to have an overall concept laid out. But feel free to close if you see it as a duplicate.
How about this: - a link format that contains a device id and a folder id (eg `syncthing://add/*device-id*/*folder-id*`) - a way to generate such links in syncthing - a way...
Right, my idea was to have seperate stats for every wrapper. Having the same ones doesn't really make sense.
It should probably be a key:value map, but otherwise it sounds good. Also, we should probably update the urAccepted value whenever these "external feature" keys change.
@calmh I misunderstood your reply, disregard what I said about urAccepted. As for the data, boolean values should be fine (at least for now). Still, I would prefer to have...
Like I said, boolean values would be totally fine. I'm just disagreeing how the JSON should be formatted :p Things like cpu architecture or number of folders are included in...
Just like the backend, its better to use an env var for this (with the same name, eg `VERSION` or `LEMMY_VERSION`).
Confirmed
This problem is caused by the url cleaner added in https://github.com/LemmyNet/lemmy/pull/5018. It needs to ignore text inside of code blocks, probably by converting it to a markdown-it plugin and working...