Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)KI
Posts
72
Comments
281
Joined
4 yr. ago

  • It does have a "All articles" view, :) I'll go for it. On Arch it depends on webkitgtk, which some time back was considered insecure, and webkit2gtk was supposed to be the only one to use. Perhaps that changed...

    Thanks !

  • akregator is unfortunately part of the kde-pim, requiring akonadi, and a bunch of kde deps, see for example:

     
        
    % pacman -S akregator
    resolving dependencies...
    looking for conflicting packages...
    
    Packages (92) accounts-qml-module-0.7-4  akonadi-contacts-23.08.0-1  akonadi-mime-23.08.0-1  akonadi-search-23.08.0-1  attica-5.109.0-1  grantlee-5.3.1-1
                  grantleetheme-23.08.0-1  kaccounts-integration-23.08.0-1  kactivities-5.109.0-1  karchive-5.109.0-1  kauth-5.109.0-1  kbookmarks-5.109.0-1
                  kcalendarcore-5.109.0-1  kcmutils-5.109.0-1  kcodecs-5.109.0-1  kcompletion-5.109.0-1  kconfig-5.109.0-1  kconfigwidgets-5.109.0-1
                  kcontacts-1:5.109.0-1  kcoreaddons-5.109.0-1  kcrash-5.109.0-1  kdbusaddons-5.109.0-1  kdeclarative-5.109.0-1  kded-5.109.0-1
                  kglobalaccel-5.109.0-1  kguiaddons-5.109.0-1  ki18n-5.109.0-1  kiconthemes-5.109.0-1  kidentitymanagement-23.08.0-1  kimap-23.08.0-1
                  kio-5.109.0-2  kirigami2-5.109.0-1  kitemmodels-5.109.0-1  kitemviews-5.109.0-1  kjobwidgets-5.109.0-1  kldap-23.08.0-1  kmailtransport-23.08.0-1
                  kmbox-23.08.0-1  kmime-23.08.0-1  knewstuff-5.109.0-1  knotifications-5.109.0-1  knotifyconfig-5.109.0-1  kontactinterface-23.08.0-1
                  kpackage-5.109.0-1  kparts-5.109.0-1  kpimtextedit-23.08.0-1  krunner-5.109.0-1  kservice-5.109.0-1  ksmtp-23.08.0-1  ktextaddons-1.4.1-1
                  ktextwidgets-5.109.0-1  kuserfeedback-1.2.0-1  kwallet-5.109.0-1  kwayland-5.109.0-1  kwidgetsaddons-5.109.0-1  kxmlgui-5.109.0-1
                  libaccounts-glib-1.26-2  libaccounts-qt-1.16-3  libakonadi-23.08.0-1  libdbusmenu-qt5-0.9.3+16.04.20160218-6  libdmtx-0.7.7-1
                  libgravatar-23.08.0-1  libkdepim-23.08.0-1  libkgapi-23.08.0-1  libkleo-23.08.0-1  messagelib-23.08.0-1  pimcommon-23.08.0-1
                  plasma-framework-5.109.0-1  polkit-qt5-0.114.0-1  prison-5.109.0-1  purpose-5.109.0-1  qca-qt5-2.3.7-1  qt5-graphicaleffects-5.15.10-1
                  qt5-location-5.15.10+kde+r4-2  qt5-quickcontrols-5.15.10-1  qt5-quickcontrols2-5.15.10+kde+r6-1  qt5-speech-5.15.10+kde+r1-1
                  qt5-wayland-5.15.10+kde+r57-1  qt5-webchannel-5.15.10+kde+r3-1  qt5-webengine-5.15.14-5  qtkeychain-qt5-0.14.1-1
                  signon-kwallet-extension-23.08.0-1  signon-plugin-oauth2-0.25-1  signon-ui-0.17+20171022-3  signond-8.61-1  solid-5.109.0-1  sonnet-5.109.0-1
                  syndication-5.109.0-1  syntax-highlighting-5.109.0-1  threadweaver-5.109.0-1  xapian-core-1:1.4.23-1  akregator-23.08.0-1
    
      

    I was hoping there's something which way less dependencies, hopefully GTK rather than Qt... At some point I wanted to use kmail and korganizer, also part of kde-pim, but besides korganizer never fixing a pretty old bug, the amount of deps I needed, plus the akonadi DB, made go back on that attempt. The same goes for akregator unfortunately...

  • Pretty interesting. I was not counting on a rss sort of reader extension, but it might work... I'll explore it, though if lemmy already support rss seeds, perhaps I can get a more generic rss reader doing it... Thanks !

  • It might achieve it, but I'm not looking into having a lemmy instance, but rather being able to sort of browse and keep up to date with some communities, just as it was possible to do with reddit (no need to host anything)...

  • Yeah, I was afraid so... I'm OK with Arch, and I actually use Artix (to avoid systemd), but I know there are people who don't want, neither can do configs, nor maintain them on upgrades, as it's a typical thing on Arch, and most distros based on it... So I'm afraid there's really no Arch based distribution for those kind of users, and EndeavourOS seems no exception. Actually if one really wants typical Arch after installation, there are alternatives to the Arch ISO, no need for other distribution for that I'd suggest...

    It'd be nice to have an Arch based distribution equivalent to Mint, so maintenance is really minimal on new users, and users with no tech abilities. Something rolling release is actually something welcome for such users, since having to upgrade on major versions is not always as clean, even for people with some experience.

    At any rate, thanks for the clarification.

  • One thing I don't know about any Arch based distributions is how about configurations. On Arch, the default configurations for some packages, whether do not work out of the box, or are not the safest configs. Whether while installing new SW, or while updating, there's a good level of involvement particularly with configurations.

    Apart from installation, which in rolling release distributions it might be about a one time thing per device, configuration might become a burden for new users.

    I believe Manjaro (I've never used it) comes with some sort of sane configs that work out of the box for most users, unless when looking for particular tweaks, or so I read in the past. But Manjaro has fallen really down on people's preferences. If EndeavourOS uses Arch repos, I'm wondering if there's any difference, once installed, between maintaining Arch and maintaining EndeavourOS. Just by how it sounds, it's the same thing, a lot of wikies readings (particularly when not familiar with the SW and how to make it work, there's SW that works without particular configs, but there are some that don't really work nicely out of the box on Arch), having to config lots of things to install stuff and make it work, and then be careful on upgrades about configs changes. It doesn't look like EndeavourOS makes this any simpler, and just having some extra stuff, but not having their own repos, where they package SW with curated configs, then I see no purpose other than to make the Arch install easier, which now a days have alternative ways to do so.

    Can some one please clarify on configs, and maintenance in general, for EndeavourOS? Is there an Arch based distribution really making this easier on new gnu+linux users, who are are really not used to deal with any of that? TBH, depending on Arch packages repositories sounds hard to achieve any of that...

  • it's not just osm instead of gmaps for the FOSS version. It's NOT using google push notificationss neither gapps at all. Using sockets instead of push notifications. It makes molly FOSS being more battery hungry, but at least it's not using google stuff. Not sure if the dev would be willing to integrate suipport for unified push for the FOSS version, that'd be even better...

  • For those using tbsync with TB, and any companion extension, like its provided for exchange (office 365 and the like), TB broke tbsync and its companion extensions.. That said, there's an issue, and apparently some developer releases for those wanting to try....

    It's been several times TB breaks extensions with such changes. TB devs don't have to care, but that means for the users, to be extra careful, and to avoid upgrading until finding out required extensions have caught up...

  • The env var works fine on Xorg though. And yeap, several applications need to catch up. That's what I meant when I said it's not wayland fault itself. However it's been years things have been trying to catch up. Every now and then I try, but a couple of months back I couldn't routinely use wayland, given all missing functionality plus additional nuances... The hard part is that if not using gnome, or plasma for that matter, getting things working take a lot of time, just to find out some things, I depend on for work, don't work yet. At any rate, I still pay attention as well, to forums like this, to see if there's some news that might trigger another retrial...

  • What I'm missing from wayland, it's not really something from wayland itself. Examples are several needed electron based applications, which some will refuse to properly work (for meetings, desktop sharing, etc), wine, gtk4 applications not respecting GDK_DPI_SCALE (not sure if already addressed) when not using gnome (wayfire being used as compositor), no proper support for conky (or eventually equivalent wayland functionality) yet, and several nuances with waybar, and some other tools. Major issue is my work dependency over some non floss electron binary blobs, like teams, slack, and so on, which particularly for desktop sharing and meetings don't yet work properly, no matter the electron options one can use for them, and some floss I use like signal, freetube, jitsi. Wine has a horrible hack, which I might live with, but it's horrible...

    So I'll have to wait further for non wayland stuff to truly support wayland, and it has taken ages for that to happen, :(

    I haven't tried labwc, andit sounds interesting, though I don't like openbox configs, and I really love fluxbox ways, which are also text files, but I never got used to openbox configs, perhaps just because I got way too familiar with fluxbox, which is what I use with Xorg (fluxbox + picom + tint2 + conky).

  • searx and searxng are not search engines, and searx is more private (searxng collects info from users, which searx never wanted to). AFAIK duckduckgo is neither a search engine on its own, it uses blink...