@oreolek @eloisa @poetgrant So yes, I've just started Memex. I've already got an XHTML parser working well on one particular page!

Have no illusions - it won't be able to compete with Blink or even WebKit and Gecko. There'll be way too many broken pages.

What it can do is establish a strong alternative vision for the web, get that vision taken more seriously, and hopefully push others to take it further.

I will be begging for help with it.

@ekaitz_zarraga @ada https://git.sr.ht/~alcinnz/memex

Though I've barely started.

And now I'm announcing the second and final project I'm starting today: "Memex", a new and hopefully more hackable, less crackable browser engine.

It won't support JavaScript, and instead try out some alternative ideas that aren't Turing Complete. Because I want to show The Web can be better that way.

I'll only be able to implement the absolute basics of Memex, so if any of you want it to actually be something please, please contribute!

https://git.sr.ht/~alcinnz/memex

I've said this before, but I'm tooted to say it again.

Browsers were originally designed to layout and render documents. To handle all the various writing systems, cultural legacy, etc it takes extra effort upfront to do so, but it remains efficient because documents rarely change.

Interactive apps on the other hand tend to be easier to layout and yet change all the time.

Combining the two just gives the worst of both worlds. In terms of performance, and I also think UX.

@aral GNOME Web does rely heavily on (100% free software) code provided by Apple, so take that as you will.

And if you don't look GNOME Web's UI, Midori and my own Odysseus share these qualities and it's backend.

@Wolf480pl @danyspin97 @Shamar An interesting example of this caching: Debian repositories.

They have an extensive volunteer mirror network how they want to prevent from altering packages when you fetch them. So they cryptographically sign all their packages.

Combine that with the fact that just the file sizes (which is not obscured by HTTPS) are enough to determine which packages you're downloading, and there's no benefit to them HTTPS.

It only costs them recruitment of these proxies.

@bob @puffinux @jeffcliff I'd much quicker sign @aral 's Indie Manifesto. It's much more clear by what is meant by "privacy" and how to achieve it.

@bob @puffinux @jeffcliff Wow that contract doesn't say much more than "governments and companies will work together to protect privacy and ensure everyone can get online. Oh and we need strong public discourse."

I can't see anyone disagreeing with that. The question is how do people interpret it?

If anyone wants Odysseus in the Debian (or others') repositories, please tell them so. If you don't know the procedure for doing so feel free to ask me.

I think for the moment though I'll focus on delivering more value and give you guys a chance to let them know it's desired. However if you don't I probably still will offer it to them somewhat soon.

I won't say when because I always say "whenever it's ready".

Just published a new blogpost describing everything I've been doing on Odysseus.

https://alcinnz.github.io/Odysseus/dev/2018/08/31/webfeed-previewer.html

I think there's people here would enjoy it.

@aral I felt exactly the same way about submitting to developer.elementary.io!

@aral @aadilayub On all these desktops app icons are expected to be installed to:
/usr{/local?}/share/icons/$theme/$size/apps/$reversedns.png

/local is optional, $theme is the icon theme it caters to, $size is how many pixels it is tall & wide, & $reversedns identifies your app. A variety of image formats are supported, though I usually see PNG or SVG.

Any "Linux" app will install an icon to the "hicolor" theme which is the standardized fallback, though it recently doesn't have to be that.