Skip Navigation

User banner
Posts
8
Comments
311
Joined
2 yr. ago

  • My main search engine is Mojeek, and my secondary search engine is Kagi. I've paid for Kagi for over a year, and it gets good results. I think it's great that every part of both search engines work without Javascript, and that Kagi's results pages are very light. It's also cool that it returns results for pages in the Internet Archive, which can be useful for certain esoteric topics. I'm de-ranking certain sites so they're pushed to the bottom of results, like quora, twitter, w3schools, and reddit.

    There are also no ads! At all! I used Duckduckgo in a VM today and it was dreadful how far you have to scroll just to get past the ads and see the actual results.

    Kagi gets great results. My only problem is that, just like Duckduckgo, they use the Bing API. Now, Kagi actually uses their own non-commercial index Teclis, combined with their news index Tinygem, as well as calling Google's API and many other search engine APIs (including Mojeek). My main search engine is Mojeek because they use their own index.

    I've found Kagi great for technical/日本語 queries, which is something Mojeek doesn't handle well. If I want to learn about a certain topic, I search Wikipedia directly. I think Kagi is the nicest and fanciest Bing/Google proxy around, with easily the best user experience of any search engine.

  • Yes, I like the default workflow. I always have particular applications on the same workspaces, and I close them as I need to. Sometimes I have multiple, usually a maximum of two on one workspace, because I can ALT+TAB through them. I like that the top bar is uncluttered. I don't use the dock at all, but Activity Overview is sometimes useful. I can operate the desktop completely with my keyboard. It's also very minimal without too many options, and it looks pretty. I find it very usable.

    The only annoying thing was needing to manually create shortcuts inside of dconf for workspaces 5-10. I really don't know why they force you to do that...

  • Yay. It's fixed for my NVIDIA computer, too. All of the bizarre scaling issues and other nonsense is fixed.

    • The package manager.
    • New releases make it to the repositories quickly.
    • The software is as vanilla as possible; no changes made by the distribution except to get it working.
    • The wiki.
    • +/- No nagging graphical updater.
    • +/- Users can share build scripts for building software from source very easily
    • +/- No particular stance on free software licenses.
  • Oh, I didn't know that! All I've ever seen when this question gets asked in the BBS is "it'll be done when it's done :)" which is fair enough. If they're waiting for the .1 release as an indicator of stability, then that explains why it feels like a while.

  • I usually don't mind when most packages get behind, but the one I always notice is GNOME. It's been taking longer than I would generally expect for Arch to ship a new major update for GNOME. Fedora seems to have more up-to-date packages in most areas and ships them vanilla like Arch, as well as coming with a host of other sane defaults, so I've been thinking of making the switch...soon.

  • This document talks briefly about unauthorized redistribution of RHEL sources: https://www.redhat.com/licenses/Appendix_1_Global_English_20230309.pdf

    Unauthorized Use of Subscription Services. Any unauthorized use of the Subscription Services is a material breach of the Agreement. Unauthorized use of the Subscription Services includes: (a) only purchasing or renewing Subscription Services based on some of the total number of Units, (b) splitting or applying one Software Subscription to two or more Units, (c) providing Subscription Services (in whole or in part) to third parties, (d) using Subscription Services in connection with any redistribution of Software or (e) using Subscription Services to support or maintain any non-Red Hat Software products without purchasing Subscription Services for each such instance (collectively, “Unauthorized Subscription Services Uses”).

    Page for all agreements with Red Hat: https://www.redhat.com/en/about/agreements

    These documents appear to be written in Microsoft Word, not that this is of any consequence.

  • You can build visual novels in Ren'Py, which uses only Python, but that might not be what you're looking for.

  • but browser should not crash what ever some website does.

    Sometimes crashing would be better than trying to beat wonky code into shape: https://samy.pl/myspace/tech.html

    1. Sweet! Now we can do javascript with single quotes. However, myspace strips out the word "javascript" from ANYWHERE. To get around this, some browsers will actually interpret "java\nscript" as "javascript" (that's java

      <NEWLINE>

      script). Example:

      <div id="mycode" expr="alert('hah!')" style="background:url('java script:eval(document.all.mycode.expr)')">

    But on principle I agree. I can't say whether Google Images works or not on my Firefox browser, because I'm using Mojeek.

  • It is interesting though that we find ourselves working around a bug we did not introduce triggered by code we do not control.

    I imagine a lot of a browser's codebase looks like this. From what I understand, browsers expect webmasters to screw up their markup and make allowances for it.