Clicking on any "quote" off of a profile page gets the 503 also... it feels a little rough.
In my case, it doesn't show any error, but the loading bar gets stuck at around 95% so nothing appears on the screen.
I was able to 503 the site in a few different ways. Like adding limit=1000 to a big thread.
Edit: somewhat related to async loading issue mentioned below, it seems to show a 503 error if I hit F5 when the page or part of the page is still rendering. I think the 503 error page is wired incorrectly, I don't think an actual server error is happening at that time, it's just client side showing that error page whenever it's not feeling well.
Edit2: recent threads on the front page seem to be reloading on a timer, so if you accidentally hit F5 while it's doing that it will 503 too. I should say that F5 reloads the page anyway so the error is shown only briefly but still weird and annoying.
Edit3: I left a tab open and it did a 503 on its own after a while. I don't recall what page was in it. Unfortunately it redirects to the home page on error so I can't see the original URL and back button doesn't work either.
Edit4: Wall Observer seems to fail sometimes but not always with a 500 error in the API call:
https://api.demo.epochtalk.com/api/posts?limit=10&page=1&thread_id=178336However the UI sometimes throws a 503 error before even getting the API response. Seems like there is a shorter timeout in the UI than the backend, and loading a big thread (even one page of it) sometimes exceeds both.
A few notes that I can't be bothered to report as bugs.
- Breadcrumbs at the top should not be capitalized or truncated. I don't understand what the possible reason for this could be. The last breadcrumb should be a link. Again, no plausible reason for it to not be.
- Same with thread titles of recent threads on the front page. The blobs have a massive top margin and then a truncated thread title. Why? And the recent threads block itself should be collapsible. Not everyone will like it taking up most of the front page.
- No merits
on user profile in threads. - Not a fan of squished and rounded avatars in thread lists etc. They're unreadable/unrecognizable. Just don't show anything.
- Full-size avatars in threads seem to be smaller than on Bitcointalk, causing some to be mangled when scaled down.
- Asynchronous loads should be more obvious, especially because browser rendering is very slow in some cases. You click something, indicator at the top stops spinning and nothing is happening for a while. It should be indicating something until it stops rendering. Ideally blanking out the area of the page it is reloading.
- There is something odd going on with line breaks. Some posts are rendering differently between bitcointalk and epochtalk. I don't have an example right now but I've seen words squished together as if there was a line break missing between them.
- Quotes should be spaced out bit better in posts. I know boxed quotes are "old school" but there was nothing wrong with that, easy to read and understand who said what. If we're not doing boxes then it should have at least some vertical separation.
- Board links don't have board id in them. This could break links if the board name is ever changed.
e.g. https://demo.epochtalk.com/boards/Development-&-Technical-Discussion - Unicode mildly broken:
And just an illustration on how uncooked the whole thing is in general and why it shouldn't have been made public in this condition. Just opening any random thread you see this:
The user is "user" and... "User". Why?
Default avatar... may be a matter of opinion, but I think it should just show nothing instead.
Missing date in quote - I reported that one.
Mangled signatures mentioned earlier.
That literally takes seconds to notice. Am I the only one seeing it?
And that's before you start clicking on things and quote links are broken, thread sorting is broken, etc. And that's before opening other pages and seeing duplicated username on user profile page, mangled upper/lower case texts etc.
Not sure why theymos is allergic to doing this the right way but this is a waste of time for everyone involved. Users will report the same bugs multiple times. Shit, I may report the same bug multiple times myself because I will forget which ones I already reported and I can't see what I reported. This should be sorted out internally. Then put out a public test when you can't find any bugs to fix anymore in an internal alpha.
Sorry for ranting, I've spent too many years dealing with stuff like that in my day job and it raises my blood pressure
Edit #7573 - error in
https://demo.epochtalk.com/threads/5525744?page=3 (only happened once, can't reproduce)
At least the site has a sense of humor: