131–140 of 148 posts
Earlier quoted context omitted.
I upvoted not because I agreed (I found the naming conventions distracting and inconsistent) but because why the fuck was your perfectly innocuous comment downvoted?
I'm not sure, but it made me sad. I don't think we are supposed to talk about downvotes, so I just grinned and bared it. Thanks for offsetting that vote for me.
Earlier quoted context omitted.
I'm from Europe and on one occasion Youtube was broken on Firefox but not on Chrome. It was fixed in the day or two.
In my experience, YouTube in-video links (those that e.g. show thumbnails of videos and are pointed at by vloggers with their fingers) have been broken in Firefox for years. Not that I complain, I've always been annoyed by those. I think it took me 2 years to realize that after seeing vloggers point at invisible things. I had to double-check in Chrome. (I just assumed that they forgot to add the links when editing.)
Love the opinionated swearing rant that is the sample website! (See screenshots at bottom). Yes, simple vanilla HTML is inherently responsive. And much of the modern web is rubbish.
Not only a rant, there is a whole opinoated swearing discussion! [0]: http://motherfuckingwebsite.com/ [1]: http://bettermotherfuckingwebsite.com/ [2a]: https://evenbettermotherfucking.website/ [2b]: https://bestmotherfucking.website/
Earlier quoted context omitted.
The idea of "minimal browsers" is a popular one and there are thriving communities based on this idea: Gopher is a dead simple text-based protocol: https://en.wikipedia.org/wiki/Gopher_(protocol) Project Gemini is a slightly more powerful protocol for the small web: https://gemini.circumlunar.space/ The tilde (~) community, which makes the small web social: https://tilde.club/ I recommend you have a look at James Tom…
Neither Gopher nor Gemini are remotely close to being a replacement for the web, as neither support anything close to rich text or media. Gemini doesn't allow for embedding images in web pages - which makes it vastly inferior to the web for any kind of interesting documents. Imagine reading a research paper where, in order to view figures and equations, you had to follow a link to a separate object . No font control.…
This statement is incorrect. Gemini clients can absolutely display inline images.
The difference is that default behavior is to require a user action to load a resource. An image can be a link, but when a user clicks that link it can turn into an inline image. This is how clients like Lagrange work. In other words, inline images can have delayed loading.
If a user understands the consequences (tracking, network usage) of doing so, this behavior can be changed to load images by default; however, authors should not expect users to do this and should write their documents accordingly.
Personally, I prefer a document to not have inline images; my gemini client opens images in my default image viewer instead. My window manager makes my age viewer float above other windows by default. This way, images "pop out" into a separate window that I can keep viewing as I scroll down in a document; I never have to scroll up to look at the last image.
> Imagine reading a research paper where, in order to view figures and equations, you had to follow a link to a separate object. No font control. No two-column layout. No anchors to allow you to jump to sections of the document.
These are all client-side features. Half the point of Gemini is for the user agent to determine presentation and leave semantic markup to authors. I don't want weird fonts or multi-column views, but you do; Gemini lets us both get what we want instead of having everyone see a one-size-fits-all presentation. Clients like Kristall even give you a TOC in the sidebar.
> Gemini and Gemtext actively inhibit learning and knowledge dissemination by obsessing over pure plain text, which is bad at those things.
Text is the only form of communication that can be understood by the sighted, blind, deaf, and machine (translation, etc) while being stored and transmitted without information loss. Text is good at knowledge dissemination.
i thought it was related to the old hotdog code editor. think i used that to learn html back in the early noughties.. better, simpler days - i really miss them.
What an odd name to hit twice in the browser world.
Then again, there's Viola, Cello, and Vivaldi though ... so who knows, maybe the population size is way larger than I pretend it is.
Earlier quoted context omitted.
Youtube and gmail will mysteriously break for people on Firefox too, so it's not that much worse. /sarcasm (sort of...)
Regular Firefox user here with a YouTube Premium account. I use it all the time and have never had any issues.
Written in Go. This is presumably good for security. Curious that the components are named ketchup, mayo, mustard, sauce, bun, and gg. There's an obvious omission here, although it has the advantage of being vegan friendly. Also, somewhat related: it's a pity the Servo project is going nowhere. I don't mean to put this project down, but Servo was the only realistic shot at a truly new, truly usable Free Software brow…
Servo was primarily a test bed for Firefox and all the components that they wanted to get into Firefox eventually made it.
Earlier quoted context omitted.
I feel ya. I'm refactoring my CSS parser the third time now, because I needed to support nested media queries (and therefore the logical condition "spec"). It's amazing how complex even CSS has gotten. And implementing HTML without the ISO SGML spec and the SGML handbook is close to impossible. So many edge cases, so much layouting overhead, and so much damned flow root types. Honestly in the beginning I thought "how…
This is exactly it. I looked at doing something like this, ok, I looked at doing this and decided early to forgo CSS because it's so very very complicated. Truthfully, if my skillset had better matched the task I might have been lured into giving it a go. On another project I considered using CSS as a styling technology and got down to really understand it in detail. I then realized how good my 1,000 yard vision real…
Well, I actually tried to start a movement for that [1].
The idea is to offload as much as possible to trusted peers, and to refine the web with a trust model where the user has to trust a website specifically to deliver expected things from the user's side (e.g. a news website should have no right to shove videos down your throat).
I also think that a lot of web browsers tackle the privacy problem wrong. "User Privacy" is not sending a user-agent to a server, or downloading a resource from it in a statistically easily detectable manner.
Real privacy is not having to download anything from the web server at all, by offloading requests to its peers. In my Browser [2] I'm trying to have every metadata, configuration or observation (and extraction) federated. I believe that the real strength of peer-to-peer is not decentralization; it is federation and liberation.
It's great to see yet another attempt at writing a web browser --- and I say this as someone who has been (slowly) working on one myself. The browser is far from stable, spec-compliant, or even really useful, but, I'm slowly working on bringing more features and supporting more sites. When the specs are constantly churning in order to keep one gigantic company's browser an effective monopoly, maybe it isn't really th…