# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 10
# self = https://watcher.sour.is/conv/5sdjyvq
@prologic @abucci Oh, I totally get your point of view. 😅 (“90% of the web sucks anyway” etc.)
The thing is … we must use the “sucky part” of the web anyway, don’t we? At least I do. There is absolutely no way (anymore) for me to use a WebKit2GTK browser at work – I did that for a while, long ago. (We’re now forced to do 2FA with some USB key and WebKit doesn’t support that anyway …)
Even in my private life, I do want to use YouTube or even Netflix. I want to search something on DuckDuckGo (or whatever), open a link and it should open that page – instead, it works only ~50-70% of the time. Yes, those might be shitty web pages, but if they contain the information that I’m looking for, then I’d rather be able to visit them.
Every time a web page that I wanted to visit didn’t work, I opened Firefox. Over time, I noticed that I usually have two browsers running *at all times* – my WebKit2GTK one and Firefox. Firefox for all the web sites that didn’t work in WebKit.
Which web sites don’t work? Mostly those with a gazillion JS frameworks and twenty billion CSS effects. (Btw, “is really slow” is the same as “doesn’t work” for me.) It has nothing to do with ads. 😅 It’s just shitty shitty bloated web sites – and more web sites become like that every day.
With all that said, it *is* possible to use WebKit2GTK as a (main) daily driver. You should just expect a *very* bumpy ride and you need a lot of patience. 😅~
@prologic @abucci Oh, I totally get your point of view. 😅 (“90% of the web sucks anyway” etc.)
The thing is … we must use the “sucky part” of the web anyway, don’t we? At least I do. There is absolutely no way (anymore) for me to use a WebKit2GTK browser at work – I did that for a while, long ago. (We’re now forced to do 2FA with some USB key and WebKit doesn’t support that anyway …)
Even in my private life, I do want to use YouTube or even Netflix. I want to search something on DuckDuckGo (or whatever), open a link and it should open that page – instead, it works only ~50-70% of the time. Yes, those might be shitty web pages, but if they contain the information that I’m looking for, then I’d rather be able to visit them.
Every time a web page that I wanted to visit didn’t work, I opened Firefox. Over time, I noticed that I usually have two browsers running *at all times* – my WebKit2GTK one and Firefox. Firefox for all the web sites that didn’t work in WebKit.
Which web sites don’t work? Mostly those with a gazillion JS frameworks and twenty billion CSS effects. (Btw, “is really slow” is the same as “doesn’t work” for me.) It has nothing to do with ads. 😅 It’s just shitty shitty bloated web sites – and more web sites become like that every day.
With all that said, it *is* possible to use WebKit2GTK as a (main) daily driver. You should just expect a *very* bumpy ride and you need a lot of patience. 😅~
@prologic @abucci Oh, I totally get your point of view. 😅 (“90% of the web sucks anyway” etc.)
The thing is … we must use the “sucky part” of the web anyway, don’t we? At least I do. There is absolutely no way (anymore) for me to use a WebKit2GTK browser at work – I did that for a while, long ago. (We’re now forced to do 2FA with some USB key and WebKit doesn’t support that anyway …)
Even in my private life, I do want to use YouTube or even Netflix. I want to search something on DuckDuckGo (or whatever), open a link and it should open that page – instead, it works only ~50-70% of the time. Yes, those might be shitty web pages, but if they contain the information that I’m looking for, then I’d rather be able to visit them.
Every time a web page that I wanted to visit didn’t work, I opened Firefox. Over time, I noticed that I usually have two browsers running *at all times* – my WebKit2GTK one and Firefox. Firefox for all the web sites that didn’t work in WebKit.
Which web sites don’t work? Mostly those with a gazillion JS frameworks and twenty billion CSS effects. (Btw, “is really slow” is the same as “doesn’t work” for me.) It has nothing to do with ads. 😅 It’s just shitty shitty bloated web sites – and more web sites become like that every day.
With all that said, it *is* possible to use WebKit2GTK as a (main) daily driver. You should just expect a *very* bumpy ride and you need a lot of patience. 😅~
This discussion reminds me a bit of self-hosting e-mail. I *hate* when people give up on that. 😅 And now *I’m the one* who gave up on non-mainstream browsers. Hmm.
This discussion reminds me a bit of self-hosting e-mail. I *hate* when people give up on that. 😅 And now *I’m the one* who gave up on non-mainstream browsers. Hmm.
This discussion reminds me a bit of self-hosting e-mail. I *hate* when people give up on that. 😅 And now *I’m the one* who gave up on non-mainstream browsers. Hmm.
This discussion reminds me a bit of self-hosting e-mail. I *hate* when people give up on that. 😅 And now *I’m the one* who gave up on non-mainstream browsers. Hmm.
@movq See... 😅 Come join the dark side with me and build a Webview-based Browser in Go 🤣
@movq See... 😅 Come join the dark side with me and build a Webview-based Browser in Go 🤣