tombh

37 ms·

1. 451.▲
   by tombh 8y ago

   This should be fixed in version 1.3.2
2. 452.▲
   by tombh 8y ago

   If you leave an issue on the Github repo with some debug logs and some info about the server I can look into it.
3. 453.▲
   by tombh 8y ago

   I haven't made it clear enough on the homepage or the docs, but Browsh isn't designed to run on your own local device, be it a laptop or smartphone. Browsh is best run remotely and then connected to through either SSH/Mosh or
4. 454.▲
   by tombh 8y ago

   This should be fix, let me know if you try again and it works.
5. 455.▲
   by tombh 8y ago

   Ha, you're the first person to mention that. It's probably one of the hardest things I've ever done in my life, both technically and in terms of stamina. So I very much appreciate that someone else can understand that.
6. 456.▲
   by tombh 8y ago

   The bitcoin one! Woaah, thank you so much :)
7. 457.▲
   by tombh 8y ago

   Since launch I've had just under £100 in donations.
8. 458.▲
   by tombh 8y ago

   Does it look related to this? https://github.com/browsh-org/browsh/issues/73
9. 459.▲
   by tombh 8y ago

   You can! It can just be hard sometimes to find where to click the mouse :/ I need to find a better way to provide visual cues for input boxes. Thanks :)
10. 460.▲
    by tombh 8y ago

    Just researching this now. Looks like I need to use `GOARM=7` during build. I have no idea if that would put out all those that were relying on `GOARM=6`?
11. 461.▲
    by tombh 8y ago

    For sure, I totally agree with this. The fact is I don't even use Browsh that much as I have the luxury of fast and cheap Internet. But I have certainly experienced bad internet and felt that craving to be connected to the modern web,
12. 462.▲
    by tombh 8y ago

    Embarrassingly, I need to remove WebGL from Browsh's features, as WebGL doesn't work in Firefox's headless mode. I certainly saw it working in the early days when I wasn't using Firefox headless in order to debug the inj
13. 463.▲
    by tombh 8y ago

    Can you identify the process that was causing it? What size was your terminal window. And if possible the `./debug.log` file from having run `browsh -debug` could be useful. Thanks.
14. 464.▲
    by tombh 8y ago

    I'm planning to add a 'magnifying glass' feature: https://github.com/browsh-org/browsh/issues/33
15. 465.▲
    by tombh 8y ago

    Hey thanks! :)) Ha ok, then I should have just not mentioned, but its good to know Browsh actually coped well.
16. 466.▲
    by tombh 8y ago

    Yes, I know :/ I'm pretty sure it's related to the issues the terminal client has here: https://github.com/browsh-org/browsh/issues/42 At least with the terminal client successive frame updates
17. 467.▲
    by tombh 8y ago

    This is really the perfect use case for Browsh. I first had the idea for it when I was in the deserts of Ladakh where you'd get around 3kb/s speeds. So what you need to do is install Browsh on a remote server along with Mosh. Then
18. 468.▲
    by tombh 8y ago

    I've been watching this: https://www.virustotal.com/#/url/54ab74be93601eb2f252364829c... Because yesterday Google Safe Browsing considered this URL: https://html.brow.sh/mail.google.com a phi
19. 469.▲
    by tombh 8y ago

    Browsh is really aimed at people with slow and/or expensive Internet that would benefit with having the main browser engine running remotely. You then access the output of Browsh via either SSH/Mosh or HTML serivice. But neverthel
20. 470.▲
    by tombh 8y ago

    Thanks for the suggestion. I'm already using Kubernetes/Docker for the `ssh brow.sh` service. What advantages would your approach have?
21. 471.▲
    by tombh 8y ago

    Now that you describe it, yes indeed I can see the problems. I can't think of any other precedent, as most other proxies are least protected by HTTPS, wheres a Browsh service is literally reading every character on a page in plain text
22. 472.▲
    by tombh 8y ago

    That's a great idea about the `alt` metadata, thank you. Have you got an example URL for a page that would benefit from those filled boxes you mention?
23. 473.▲
    by tombh 8y ago

    The html.brow.sh service is quite far behind the terminal client in terms of features. Besides there's big hurdles over privacy if html.brow.sh starts letting users log into sites.
24. 474.▲
    by tombh 8y ago

    I mean for example one of the big problems Browsh has is not rendering text that web developers have hidden in the DOM to be displayed on some kind of mouse interaction. So Browsh has to ask JS to query the `display: hidden`, `z-index`, etc
25. 475.▲
    by tombh 8y ago

    Fantastic resource, thanks
26. 476.▲
    by tombh 8y ago

    For sure that's definitely an option, for both the SSH service and the html.brow.sh service. As people get to learn about Browsh let's see if there are any takers.
27. 477.▲
    by tombh 8y ago

    I've had the idea to make a webextension that transparently proxies all top-level URL bar requests to html.brow.sh, that way you can click on links in other applications that open in your browser and instantly get the Browsh version. I
28. 478.▲
    by tombh 8y ago

    It's be great if html.brow.sh could become a sophisticated proxy that stripped the web down to an absolute bare minimum. Yes I think travelers are the most likely to pay for it, but I think the poorer people of less developed nations w
29. 479.▲
    by tombh 8y ago

    I've thought about this too, because https://text.brow.sh certainly does make scraping websites easy, you just need to `curl` and `grep`. But the trouble is, as I mentioned elsewhere in the thread, Browsh's text render
30. 480.▲
    by tombh 8y ago

    This approach has already crossed my mind, and its not my favourite either. But if it enables me to make Browsh my job then I'd be open to it. I actually already self-advertise Browsh at the bottom of every https://html.brow