Bitcoin Wiki:Issue Tracker: Difference between revisions
mNo edit summary |
|||
Line 15: | Line 15: | ||
dump.bitcoin.it just goes to the Main Page if accessed with SSL | dump.bitcoin.it just goes to the Main Page if accessed with SSL | ||
// fixed | |||
== Bitc<b></b>oin:* namespace interwiki links broken == | == Bitc<b></b>oin:* namespace interwiki links broken == |
Revision as of 08:27, 9 June 2014
This page serves as the Wiki issue tracker.
To file a new issue, add a second-level heading (==), and describe your issue in detail.
Issue discussion should happen on the Talk page.
Do not delete resolved issues unless you are a wiki administrator, or the creator of the issue.
Presented with SSL cert from another site
A few times on 2014-03-27, non-deterministically across a few pages, I got the typical "wrong SSL cert" warning from Firefox, saying I'd been delivered the cert for kitchensurfing.com, issued the same day.
Backup site broken via HTTPS
dump.bitcoin.it just goes to the Main Page if accessed with SSL
// fixed
Bitcoin:* namespace interwiki links broken
Links to [[Bitcoin:Community portal]] (for example) get turned into broken bitcoin: URI links.
- Looks like someone mistakenly put "bitcoin" in the interwiki table, it's just a namespace and doesn't need an entry there. --Gmaxwell (talk) 15:46, 8 June 2014 (UTC)
Example [[1]] One more example [[2]]
Make the anti-spam payment system more discoverable
I understand that Cryptopay is [being replaced](http://www.reddit.com/r/Bitcoin/comments/27lofu/dear_bitcoin_foundation_please_take_ownership_of/ci20i6t). Can you give us more details on that? The new system should be more discoverable by new users - I suggest a notification for every new user on how to edit. (people still ask me how to edit the damn thing).
Require a fee for new user registration
There is still a big spam problem in the Recent Changes page. As a workaround, can use this link to view recent changes excluding the user namespace.
Use a proper issue tracker
I know you like wikis ... but can't we use something like Zendesk to track issue? Wikis weren't designed to be issue trackers...