# 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 13
# self = https://watcher.sour.is/conv/t4dyocq
A short responses to the browser thing. Now thinking about it, it's sad Opera despite being Chinese owned, linked to scams and overall shitty, still remains the best choice I have, for what I usually need.
Still when I need to test sites at work, I often just use the browser I mede, because it doesn't cache everything and it's not filled with cookies, so one can actually see how the site currently looks and not some old and broken cached version.
It's amazing the competition is so shitty, that despite all their sabotage, one student with not much time was able to make a browser, that may not be able to compete, but is still somehow more useful for webdev.
@thecanine I _think_ the hardest part about making a Browser these days is the rendering engine. This is why most of them are based on WebKit, because it handles all that shit for you. Which isn't necessarily a bad thing, which itself was based on KHTML.
@thecanine I _think_ the hardest part about making a Browser these days is the rendering engine. This is why most of them are based on WebKit, because it handles all that shit for you. Which isn't necessarily a bad thing, which itself was based on KHTML.
@prologic and I'd rather prefer that to chrome or firefox, haha
I wish KHTML wasn't _that_ dead though
@novaburst Isn't it just called WekKit now? QtWebKit, GTKWebKit and friends?
@novaburst Isn't it just called WekKit now? QtWebKit, GTKWebKit and friends?
@prologic I'd say that at this point, most (including mine) are Cromium based, which is giving Google a lot more power than they already have and letting them get away with bending the web standards as well as the direction that most of the Internet is heading.
Chromium is also a security nightmare, with critical vulnerabilities having to be patched on almost weekly basis, so at this point I'd love to see at least one engine starting from scratch and having the funding and team, allowing it to eventually catch up.
@thecanine Would you mind sharing the source code of your (Chromium-based) browser? I know that using WebKitGTK is super easy, because it’s just a GTK widget – but I’ve always refrained from doing anything based on Firefox or Chromium since they’re totally different beasts, much harder to build your own browser on top. 🤔
@thecanine Would you mind sharing the source code of your (Chromium-based) browser? I know that using WebKitGTK is super easy, because it’s just a GTK widget – but I’ve always refrained from doing anything based on Firefox or Chromium since they’re totally different beasts, much harder to build your own browser on top. 🤔
@thecanine Would you mind sharing the source code of your (Chromium-based) browser? I know that using WebKitGTK is super easy, because it’s just a GTK widget – but I’ve always refrained from doing anything based on Firefox or Chromium since they’re totally different beasts, much harder to build your own browser on top. 🤔
@movq I built once Chromium from sources. On my i5 10th Gen with 32GB RAM all Threads on fire, it took 30 Minutes. Crazy!