Skip to content
TheChatArchiveThe Chat Archive
Perplexitysonar-pro-high· PerplexityHugging Face LMArena Search Arena 24K

wieso wird diese seite nicht in qutebrowser geladen, in chromium aber schon:…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Perplexitysonar-pro’s answer.
  1. User

    wieso wird diese seite nicht in qutebrowser geladen, in chromium aber schon: https://www.thulb.uni-jena.de/

  2. Perplexity Assistant

    Based on the information provided in the search results, there is no specific mention of why the ThULB website (https://www.thulb.uni-jena.de/) is not loading in qutebrowser but works in Chromium. However, we can infer some possible reasons:

    1. Qutebrowser compatibility issues: Qutebrowser is a relatively niche browser compared to Chromium, and it's possible that the ThULB website has some features or scripts that are not fully compatible with qutebrowser[1].

    2. Recent qutebrowser bugs: There have been recent issues reported with qutebrowser, including crashes and rendering problems[1]. It's possible that one of these bugs is affecting the loading of the ThULB website.

    3. Server-side rate limiting: The search results indicate that the ThULB website has implemented rate limiting[7][8]. It's possible that qutebrowser is triggering this rate limiting more easily than Chromium, preventing the page from loading.

    4. JavaScript errors: Some qutebrowser issues have been related to JavaScript errors[10]. The ThULB website might be using JavaScript that is not fully compatible with qutebrowser's rendering engine.

    To troubleshoot this issue, you could try:

    1. Updating qutebrowser to the latest version.
    2. Clearing the browser cache and cookies.
    3. Checking the JavaScript console in qutebrowser for any specific errors.
    4. Trying to load the website with JavaScript disabled in qutebrowser to see if it's a script-related issue.

    If the problem persists, it might be worth reporting the issue to the qutebrowser developers with specific details about the error you're encountering.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.

Identical first prompt