Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Posts by ArtOfCode
Thank you for this. You're absolutely right - we don't currently do enough in terms of providing guidance for users when something goes wrong. It's part of our vision for the platform that we'll pr...
This is something we either can't fix, or can't fix without significant effort. It's been a little while since I last checked what browser tooltips can do, but one thing they can't do is render HTM...
Fix pushed. When you save a post, we don't take what you typed into the textbox and convert it to markdown on the server, if we can avoid it (we still have to if the client has JS disabled). There...
Unfortunately, this isn't something we have control over. It's down to the MathJax library and how it renders the math. If you look at the page HTML, by default it renders math by putting every cha...
I surprise myself, but the answer is "yes you can". There's a new Hierarchical sort button on tag list pages. You won't see much difference right now because not many tags have been made hierarchi...
Done - should be going live with the next deploy.
Fixed - tabs on the user profile have been unified, rolling out in the next build.
This has now been implemented - watch out for it in the next deploy.
Fixed and rolling out in the next build.
I'm assuming you mean forum.codidact.org, rather than just codidact.org? The former is a discussion forum; the latter is just a static site with nowhere that you could report anything. If that's t...
These may well all be things we do when reviews are implemented. At the moment, reviews don't exist, so I'm marking this [status-deferred].
Fixed; rolling out in the next build.
This has taken a little while to get to while I did some research into how feasible it is. For the moment, I'm putting a [status-deferred] on this - I know that's not the answer you were hoping for...
Having had a look into this, the cost of doing this in terms of database and page load time is prohibitive. Perhaps it's doable with some caching here and there, but at that point we're investing w...
There's a difference: your user account & profile is network-wide, whereas your email subscriptions are per-site. I can see the use of having a single network-wide page to manage your emails, b...
We support browser widths down to 360px, which is the smallest common browser width on most modern mobile devices. At that width, I see this: Even going smaller than that, I can't reproduce what y...
I thought we did this already, so I had a look. Turns out we were using the wrong link to check for duplicates, which I've updated. You should find you only get one notification per comment thread ...
Inline footnotes aren't supported: you'll need to use full footnote syntax instead, i.e.: here are some words[^1] [^1]: example footnote
These bugs are related but slightly different. Both should now be fixed.
It's not the network sign-in that's created accounts for you - it's visiting the sites. When you visit a site and are signed in elsewhere, an profile is created for you on that site. So, with netwo...
Should also be fixed with the next deploy.
This is by design. The users you're seeing created before the site... well, they were - they're user accounts that were created elsewhere before EE launched (like mine - which is one of those on De...
[status-norepro] If you use your browser's Inspect Element feature, you should be able to find the computed font sizes on each. On all browsers on my end I see h1 as 27.2px and h2 as 25px. Admitte...
All categories are treated equally; voting in any category affects reputation. This is different to how it works on Stack Exchange, but that's just one of those differences - neither approach is n...
I've declined this, for the same reason that I've declined other similar Unicode-related "bugs" before. They're not really bugs, just a product of how easy Unicode is to abuse. The solution: don't...
