Anyways im currently trying this one so could you give it a shot and tell me if it works, and what country you are trying from. Thanks.
Spica75 wrote:Though i´ll add that your previous site(not sure which one, if you´ve changed more than once) worked decently for me as well(definitely slower than this one). AH, found the old link i used, it was the 99k.org one(now defunct).
thanks, i'll change that.Té Rowan wrote:Worked for me just now (Iceland). Dates are non-standard, though: Date-month-year order in MM/DD/YY format instead of DD-MM-YY or YYYY-MM-DD. Mind, the Site-That-Must-Not-Be-Named used to err the other way: Month-date-year order in DD-MM-YY format.
cool, last time I tried this im pretty sure it wouldnt work for you. So glad this one is working. If I dont get any negative posts then I can try to get google to show this page in searches instead.Crescent Pulsar S wrote:No problems on my end...
jasonjkay wrote:OK since their seems to be no problems with the new server, I have finally managed to replace all the pages on the old server with a page explaining the move and the new locations. Hope this site is still useful to others. It still helps me find the specific fic I want to read again which is why I still update every so often.
Does it work for you using a pc? also what type of mobile device and what browser? I've tried it with the newest android on a nexus tablet with firefox and chrome which both works. Also tried with my phone which is ancient and is android 2.3 using the old android web browser and firefox which also both worked. If it still doesn't work for you then I need your browser, operating system and country. Im running Chrome on windows 8.1 in the UK.talonhunter wrote:There is a 502 bad gateway error using mobile devices with both sites. Might want to check the settings on that
Cool, glad people find it useful. I only started it to remind me what each story was about and felt it could be good to have my own website.Spica75 wrote:While i don´t remember to use it as often as i might, it IS a very useful site.
jasonjkay wrote:Does it work for you using a pc? also what type of mobile device and what browser? I've tried it with the newest android on a nexus tablet with firefox and chrome which both works. Also tried with my phone which is ancient and is android 2.3 using the old android web browser and firefox which also both worked. If it still doesn't work for you then I need your browser, operating system and country. Im running Chrome on windows 8.1 in the UK.
aww there is no way i can check this out as i dont own any apple products at all and i dont know anyone else with one. I tried safari for windows which worked for me which either means something about apple devices stops the site from working or something to do with your location or internet provider not liking free hosting sites. I have no idea how to fix it to work with your devices so sorry.talonhunter wrote:Using both a iPhone 4S and a iPad Mini both using iOS 7.1.2 and safari browsers in the United States. Haven't tried the laptops lately
jasonjkay wrote:aww there is no way i can check this out as i dont own any apple products at all and i dont know anyone else with one. I tried safari for windows which worked for me which either means something about apple devices stops the site from working or something to do with your location or internet provider not liking free hosting sites. I have no idea how to fix it to work with your devices so sorry.
Avoid Framesets
In general, avoid using complicated framesets that rely on the ability to scroll individual frames because there are no scroll bars on iOS.
On the desktop, frames in a frameset can be independently scrolled as shown on the left in Figure 1-1. On iOS, scrollable frames in a frameset are expanded to fit their content and then a frame is scaled down to fit its region as shown on the right in Figure 1-1. Scrollable full-width inline frames are expanded to fit their content, too. All other scrollable inline frames can be panned using the two-finger gesture. See “Two-Finger Events” for the events generated from the two-finger gesture.
Because there are no scroll bars on the inline frames, this is not an optimal user experience for viewing web content on iOS, so avoid using framesets. Instead use columns as described in “Use Columns and Blocks.”
Don’t Use Unsupported iOS Technologies
In general, Safari on iOS does not support any third-party plug-ins or features that require access to the file system. The following web technologies are not supported on iOS:
Modal dialogs
Don’t use window.showModalDialog() in JavaScript. Read “Use Supported JavaScript Windows and Dialogs” for a list of supported dialogs.
Mouse-over events
The user cannot “mouse-over” a nonclickable element on iOS. The element must be clickable for a mouseover event to occur as described in “One-Finger Events.”
Hover styles
Since a mouseover event is sent only before a mousedown event, hover styles are displayed only if the user touches and holds a clickable element with a hover style. Read “Handling Events” for all the events generated by gestures on iOS.
Tooltips
Similar to hover styles, tooltips are not displayed unless the user touches and holds a clickable element with a tooltip.
Java applets
Flash
Don’t bring up JavaScript alerts that ask users to download Flash.
QuickTime VR (QTVR) movies
Plug-in installation
Custom x.509 certificates
WML
Safari on iOS is not a miniature web browser—it is a full web browser that renders pages as designed—therefore, there is no need for Safari on iOS to support Wireless Markup Language (WML). Alternatively, it does support XHTML mobile profile document types and sites at .mobi domains.
The XHTML mobile document type is:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.1//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic11.dtd">
File uploads and downloads
Safari on iOS supports file uploading—that is, <input type="file"> elements—on iOS 6 and later.
Do not prompt the user to download plug-ins like Flash on iOS. See “Using the Safari User Agent String” for how to detect Safari on iOS.
Know iOS Resource Limits
Your webpage performing well on the desktop is no guarantee that it will perform well on iOS. Keep in mind that iOS uses EDGE (lower bandwidth, higher latency), 3G (higher bandwidth, higher latency), and Wi-Fi (higher bandwidth, lower latency) to connect to the Internet. Therefore, you need to minimize the size of your webpage. Including unused or unnecessary images, CSS, and JavaScript in your webpages adversely affects your site’s performance on iOS.
Because of the memory available on iOS, there are limits on the number of resources it can process:
The maximum size for decoded GIF, PNG, and TIFF images is 3 megapixels for devices with less than 256 MB RAM and 5 megapixels for devices with greater or equal than 256 MB RAM.
That is, ensure that width * height ≤ 3 * 1024 * 1024 for devices with less than 256 MB RAM. Note that the decoded size is far larger than the encoded size of an image.
The maximum decoded image size for JPEG is 32 megapixels using subsampling.
JPEG images can be up to 32 megapixels due to subsampling, which allows JPEG images to decode to a size that has one sixteenth the number of pixels. JPEG images larger than 2 megapixels are subsampled—that is, decoded to a reduced size. JPEG subsampling allows the user to view images from the latest digital cameras.
The maximum size for a canvas element is 3 megapixels for devices with less than 256 MB RAM and 5 megapixels for devices with greater or equal than 256 MB RAM.
The height and width of a canvas object is 150 x 300 pixels if not specified.
JavaScript execution time is limited to 10 seconds for each top-level entry point.
If your script executes for more than 10 seconds, Safari on iOS stops executing the script at a random place in your code, so unintended consequences may result.
This limit is imposed because JavaScript execution may cause the main thread to block, so when scripts are running, the user is not able to interact with the webpage.
See the Safari Web Inspector Guide for how to debug JavaScript on iOS.
The maximum number of documents that can be open at once is eight on iPhone and nine on iPad.
iOS Note: In iOS 1.1.4 and earlier, the JavaScript execution time was limited to 5 seconds and the size of allocations to 10 MB. Also, the limit on the size of canvas elements was the same as Safari on the desktop.
In iOS 2.2.1 and earlier, the sum of all of the frames needs to be less than 2 megapixels—that is, width * height * number of frames ≤ 2 * 1024 * 1024. In iOS 3.0 and later, the limit only applies to one frame at a time.
You also need to size images appropriately. Don’t rely on browser scaling. For example, don’t put a 100 x 100 image in a 10 x 10 <img> element. Tile small backgrounds images; don’t use large background images.
Return to Miscellaneous, Polls, RPGs
Users browsing this forum: No registered users