home.social

#edbrowse — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #edbrowse, aggregated by home.social.

  1. I'm going to be blind for a bit in March (the phrase "bandage contacts" has come up in the surgery docs). Any OpenBSD accessibility advice people have?

    #openbsd #edbrowse #accessibility #a11y

  2. I'm going to be blind for a bit in March (the phrase "bandage contacts" has come up in the surgery docs). Any OpenBSD accessibility advice people have?

    #openbsd #edbrowse #accessibility #a11y

  3. I'm going to be blind for a bit in March (the phrase "bandage contacts" has come up in the surgery docs). Any OpenBSD accessibility advice people have?

    #openbsd #edbrowse #accessibility #a11y

  4. I'm going to be blind for a bit in March (the phrase "bandage contacts" has come up in the surgery docs). Any OpenBSD accessibility advice people have?

    #openbsd #edbrowse #accessibility #a11y

  5. I'm going to be blind for a bit in March (the phrase "bandage contacts" has come up in the surgery docs). Any OpenBSD accessibility advice people have?

    #openbsd #edbrowse #accessibility #a11y

  6. Okay...how do other folks decide between different terminal-based web browsers?

    Lynx is the one that gets mentioned the most on fedi. It also has by far the highest popcon on Debian.

    It seems Lynx is part of the same family tree as links, links2, and elinks. Trying all of them, I really don't see much difference between Lynx and Links: the only differences I notice are that they use different default colors for text, and links has a smaller file size.

    Links2 can run in either graphical or terminal mode. I can't use the graphical mode due to a lack of dark mode. The terminal version of link2 seems identical to links: is there even a difference?

    Elinks, when used as a web browser, seems nearly identical to the other three, aside from a different color scheme. Its website claims it supports CSS and JS, but I haven't seen those actually make a difference on a real website. Elinks can also work as a gemini and gopher browser, which is a nice perk.

    Outside of the links/lynx/elinks family, Debian has a few more terminal browsers.

    Edbrowse can let you load the text of a website and then edit it? It also works with geminispace.

    Netrik does not appear to work with https: it works fine with plain http.

    w3m, with the image extension, can display images inline in the terminal, which looks weird. Without the image extension, I don't notice much difference between w3m any the links family, aside from again a different color scheme.

    Overall, I don't see what makes Lynx stand out from all the other terminal browsers. Yet both fedi and Debian users seem to strongly prefer it. What criteria are other fedicreatures using to compare terminal web browsers?


    #WebBrowsers #TerminalBrowsers #Lynx #Links #Links2 #Elinks #Netrik #Edbrowse #W3m #geminiprotocol #gopher

  7. Okay...how do other folks decide between different terminal-based web browsers?

    Lynx is the one that gets mentioned the most on fedi. It also has by far the highest popcon on Debian.

    It seems Lynx is part of the same family tree as links, links2, and elinks. Trying all of them, I really don't see much difference between Lynx and Links: the only differences I notice are that they use different default colors for text, and links has a smaller file size.

    Links2 can run in either graphical or terminal mode. I can't use the graphical mode due to a lack of dark mode. The terminal version of link2 seems identical to links: is there even a difference?

    Elinks, when used as a web browser, seems nearly identical to the other three, aside from a different color scheme. Its website claims it supports CSS and JS, but I haven't seen those actually make a difference on a real website. Elinks can also work as a gemini and gopher browser, which is a nice perk.

    Outside of the links/lynx/elinks family, Debian has a few more terminal browsers.

    Edbrowse can let you load the text of a website and then edit it? It also works with geminispace.

    Netrik does not appear to work with https: it works fine with plain http.

    w3m, with the image extension, can display images inline in the terminal, which looks weird. Without the image extension, I don't notice much difference between w3m any the links family, aside from again a different color scheme.

    Overall, I don't see what makes Lynx stand out from all the other terminal browsers. Yet both fedi and Debian users seem to strongly prefer it. What criteria are other fedicreatures using to compare terminal web browsers?


    #WebBrowsers #TerminalBrowsers #Lynx #Links #Links2 #Elinks #Netrik #Edbrowse #W3m #geminiprotocol #gopher

  8. Okay...how do other folks decide between different terminal-based web browsers?

    Lynx is the one that gets mentioned the most on fedi. It also has by far the highest popcon on Debian.

    It seems Lynx is part of the same family tree as links, links2, and elinks. Trying all of them, I really don't see much difference between Lynx and Links: the only differences I notice are that they use different default colors for text, and links has a smaller file size.

    Links2 can run in either graphical or terminal mode. I can't use the graphical mode due to a lack of dark mode. The terminal version of link2 seems identical to links: is there even a difference?

    Elinks, when used as a web browser, seems nearly identical to the other three, aside from a different color scheme. Its website claims it supports CSS and JS, but I haven't seen those actually make a difference on a real website. Elinks can also work as a gemini and gopher browser, which is a nice perk.

    Outside of the links/lynx/elinks family, Debian has a few more terminal browsers.

    Edbrowse can let you load the text of a website and then edit it? It also works with geminispace.

    Netrik does not appear to work with https: it works fine with plain http.

    w3m, with the image extension, can display images inline in the terminal, which looks weird. Without the image extension, I don't notice much difference between w3m any the links family, aside from again a different color scheme.

    Overall, I don't see what makes Lynx stand out from all the other terminal browsers. Yet both fedi and Debian users seem to strongly prefer it. What criteria are other fedicreatures using to compare terminal web browsers?


    #WebBrowsers #TerminalBrowsers #Lynx #Links #Links2 #Elinks #Netrik #Edbrowse #W3m #geminiprotocol #gopher

  9. Okay...how do other folks decide between different terminal-based web browsers?

    Lynx is the one that gets mentioned the most on fedi. It also has by far the highest popcon on Debian.

    It seems Lynx is part of the same family tree as links, links2, and elinks. Trying all of them, I really don't see much difference between Lynx and Links: the only differences I notice are that they use different default colors for text, and links has a smaller file size.

    Links2 can run in either graphical or terminal mode. I can't use the graphical mode due to a lack of dark mode. The terminal version of link2 seems identical to links: is there even a difference?

    Elinks, when used as a web browser, seems nearly identical to the other three, aside from a different color scheme. Its website claims it supports CSS and JS, but I haven't seen those actually make a difference on a real website. Elinks can also work as a gemini and gopher browser, which is a nice perk.

    Outside of the links/lynx/elinks family, Debian has a few more terminal browsers.

    Edbrowse can let you load the text of a website and then edit it? It also works with geminispace.

    Netrik does not appear to work with https: it works fine with plain http.

    w3m, with the image extension, can display images inline in the terminal, which looks weird. Without the image extension, I don't notice much difference between w3m any the links family, aside from again a different color scheme.

    Overall, I don't see what makes Lynx stand out from all the other terminal browsers. Yet both fedi and Debian users seem to strongly prefer it. What criteria are other fedicreatures using to compare terminal web browsers?


    #WebBrowsers #TerminalBrowsers #Lynx #Links #Links2 #Elinks #Netrik #Edbrowse #W3m #geminiprotocol #gopher

  10. Okay...how do other folks decide between different terminal-based web browsers?

    Lynx is the one that gets mentioned the most on fedi. It also has by far the highest popcon on Debian.

    It seems Lynx is part of the same family tree as links, links2, and elinks. Trying all of them, I really don't see much difference between Lynx and Links: the only differences I notice are that they use different default colors for text, and links has a smaller file size.

    Links2 can run in either graphical or terminal mode. I can't use the graphical mode due to a lack of dark mode. The terminal version of link2 seems identical to links: is there even a difference?

    Elinks, when used as a web browser, seems nearly identical to the other three, aside from a different color scheme. Its website claims it supports CSS and JS, but I haven't seen those actually make a difference on a real website. Elinks can also work as a gemini and gopher browser, which is a nice perk.

    Outside of the links/lynx/elinks family, Debian has a few more terminal browsers.

    Edbrowse can let you load the text of a website and then edit it? It also works with geminispace.

    Netrik does not appear to work with https: it works fine with plain http.

    w3m, with the image extension, can display images inline in the terminal, which looks weird. Without the image extension, I don't notice much difference between w3m any the links family, aside from again a different color scheme.

    Overall, I don't see what makes Lynx stand out from all the other terminal browsers. Yet both fedi and Debian users seem to strongly prefer it. What criteria are other fedicreatures using to compare terminal web browsers?


    #WebBrowsers #TerminalBrowsers #Lynx #Links #Links2 #Elinks #Netrik #Edbrowse #W3m #geminiprotocol #gopher

  11. @4bz i liked #ploum's essay about the two webs:
    ploum.net/2023-08-01-splitting

    i think it makes sense to resort tl a shitty web browser for the shitty JS-powered capitalist web; and whenever possible use #ytdlp or #tubular for hostile sites like #youtube;

    and then use other web browsers (or rss readers, or ...) for the enjoyable web. those web browsers might not even need JS. these include #offpunk, #lynx, #netsurf, #dillo, #links, #edbrowse, #librera, #eww.

  12. @4bz i liked #ploum's essay about the two webs:
    ploum.net/2023-08-01-splitting

    i think it makes sense to resort tl a shitty web browser for the shitty JS-powered capitalist web; and whenever possible use #ytdlp or #tubular for hostile sites like #youtube;

    and then use other web browsers (or rss readers, or ...) for the enjoyable web. those web browsers might not even need JS. these include #offpunk, #lynx, #netsurf, #dillo, #links, #edbrowse, #librera, #eww.

  13. @4bz i liked #ploum's essay about the two webs:
    ploum.net/2023-08-01-splitting

    i think it makes sense to resort tl a shitty web browser for the shitty JS-powered capitalist web; and whenever possible use #ytdlp or #tubular for hostile sites like #youtube;

    and then use other web browsers (or rss readers, or ...) for the enjoyable web. those web browsers might not even need JS. these include #offpunk, #lynx, #netsurf, #dillo, #links, #edbrowse, #librera, #eww.

  14. @4bz i liked #ploum's essay about the two webs:
    ploum.net/2023-08-01-splitting

    i think it makes sense to resort tl a shitty web browser for the shitty JS-powered capitalist web; and whenever possible use #ytdlp or #tubular for hostile sites like #youtube;

    and then use other web browsers (or rss readers, or ...) for the enjoyable web. those web browsers might not even need JS. these include #offpunk, #lynx, #netsurf, #dillo, #links, #edbrowse, #librera, #eww.

  15. Re-learning how to use #edbrowse, and I am very much glad I'm doing so. The possibilities for automation are endless, and I actually like browsing the internet this way.

  16. Re-learning how to use #edbrowse, and I am very much glad I'm doing so. The possibilities for automation are endless, and I actually like browsing the internet this way.

  17. Re-learning how to use #edbrowse, and I am very much glad I'm doing so. The possibilities for automation are endless, and I actually like browsing the internet this way.

  18. Re-learning how to use #edbrowse, and I am very much glad I'm doing so. The possibilities for automation are endless, and I actually like browsing the internet this way.

  19. Re-learning how to use #edbrowse, and I am very much glad I'm doing so. The possibilities for automation are endless, and I actually like browsing the internet this way.

  20. 3/3
    "The distinguishing factors are the sizes of the pieces.
    If you turn a face 90 degrees from start, it looks off kilter.
    Some pieces are longer, wider, taller, than others.
    It only makes a cube when solved, otherwise it looks like a jumble of
    plastic rectangles stuck together.
    The sighted person has almost no advantage here.
    And there's nothing to wear off, so I can play with it for years to
    come.
    It's COOL!

    Feel free to repost this in other forums.

    Karl Dahlke"

    #accessability #edbrowse

  21. 3/3
    "The distinguishing factors are the sizes of the pieces.
    If you turn a face 90 degrees from start, it looks off kilter.
    Some pieces are longer, wider, taller, than others.
    It only makes a cube when solved, otherwise it looks like a jumble of
    plastic rectangles stuck together.
    The sighted person has almost no advantage here.
    And there's nothing to wear off, so I can play with it for years to
    come.
    It's COOL!

    Feel free to repost this in other forums.

    Karl Dahlke"

  22. 3/3
    "The distinguishing factors are the sizes of the pieces.
    If you turn a face 90 degrees from start, it looks off kilter.
    Some pieces are longer, wider, taller, than others.
    It only makes a cube when solved, otherwise it looks like a jumble of
    plastic rectangles stuck together.
    The sighted person has almost no advantage here.
    And there's nothing to wear off, so I can play with it for years to
    come.
    It's COOL!

    Feel free to repost this in other forums.

    Karl Dahlke"

    #accessability #edbrowse

  23. 3/3
    "The distinguishing factors are the sizes of the pieces.
    If you turn a face 90 degrees from start, it looks off kilter.
    Some pieces are longer, wider, taller, than others.
    It only makes a cube when solved, otherwise it looks like a jumble of
    plastic rectangles stuck together.
    The sighted person has almost no advantage here.
    And there's nothing to wear off, so I can play with it for years to
    come.
    It's COOL!

    Feel free to repost this in other forums.

    Karl Dahlke"

    #accessability #edbrowse