kixik

joined 3 years ago
[–] kixik@lemmy.ml 4 points 1 week ago* (last edited 1 week ago) (1 children)
[–] kixik@lemmy.ml 3 points 1 week ago
[–] kixik@lemmy.ml 2 points 1 week ago

What's the error you get? Perhaps someone has dealt with it before. What overrides have you tried?

There are several things that might affect some sites and are more troublesome than others, for example:

  • security.OCSP.require
  • webgl.disabled (if changed to false it's recommended to use the CanvasBlocker extension)

ublockOrigin can give trouble to some sites, a quick test is to temporarily disable it and see if the site works. It can be investigated further what specific filter might be affecting the site.

[–] kixik@lemmy.ml 29 points 1 week ago* (last edited 1 week ago) (2 children)

Librewolf is a privacy oriented fork of Firefox, it grabs some setting from arkenfox. Betterbird is not a privacy oriented fork of Thunderbird as far as I remember. When I tried it the only thing I was attracted to was its tray support, but as I use non DE compositors, so far wayfire, labwc and sway (tabbed layout), and as there's currently a Firefox bug, I didn't see any reason to keep trying it, and now on sway with tabbed layout I see no reason for a tray any ways...

[–] kixik@lemmy.ml 1 points 1 week ago* (last edited 1 week ago)

Well there's already a browser on the works, verso, and it also attempts to make servo "embeddable":

We aim to explore embedding solutions for Servo

Hopefully both project reach 1.0 sooner rather than later. Meanwhile there's Librewolf at least, and there was Mull, but instead currently there's IronFox and also FrozenFennec on the works as well, all forks of Firefox oriented to privacy.

[–] kixik@lemmy.ml 2 points 1 week ago

Have you tried enabling webgl, which by default is disable on Librewolf? You can do that by overwriting the corresponding setting, as it can be done for any Librewolf setting, in particular the webgl override needed is:

defaultPref("webgl.disabled", false);

If you do, Librewolf recommend using the extension "CanvasBlocker" given the fingerprinting allowed by webgl. There's a settings doc BTW..

[–] kixik@lemmy.ml 8 points 1 week ago

Corps are for profit, and Mozilla is a Corp... Really sad times indeed.

[–] kixik@lemmy.ml 4 points 2 weeks ago (4 children)

see this other post: https://lemmy.ml/post/26518180/16957376

Hint, look at the date this gets pushed, :)

[–] kixik@lemmy.ml 17 points 2 weeks ago

do you mean you use a more privacy oriented fork like Librewolf, or instead some chrome/chromium derivative or fork?

[–] kixik@lemmy.ml 1 points 2 weeks ago* (last edited 2 weeks ago)

I don't agree with what is written in that blog BTW, 1st I like that there's a repo that at least tries as best as it can to protect the free software aspect of the apps, which many disregard but are pretty important to me, that's one of the main values from f-droid for me. Proprietary binary components can include many invasive "features" one is not aware of. As requirement the source code and building from it is required. If you build from source, removing proprietary dependencies for example you'll get a different binary, and that requires a new signature on the final package. F-droid has improved a lot on reproducible builds. And I've read in several places magnifying the issue of apks from official f-droid being moths later compared to original developer release, my own experience is different, and when I've written, I immediately get a reaction from someone which doesn't agree with me (I never reply back). I've read about the single entity signature, but that alone should not be an issue, otherwise we would be distrusting packages from debian, arch, and so on, which use a set of signatures to sign all of their packages, particularly when the build and signing process is automated, in some distros most packages come signed by the same bot. The issue about using a VM with a LTS distro about to expire or already expired is a valid one, but can you blame them when migrating breaks their flows and they don't have enough hands, and that got overcome any ways. Now a days things are working fine AFAIK. That the clients support multiple repos violate an android policy, oh well, I don't care much about android policies, and google for that matter, which collects a ton of data from users and people forgets about what that means, but what a bad practice not to follow those policies.

I believe some people really dislike free software, which is not the same as open source, one really need to value the four basic freedoms it procures, and if one doesn't give a dumb for whatever reason then one doesn't really appreciate free software, perhaps all one wants is not paid software, which is not the same. Free has two meanings and people often gets confused, and f-droid is about free software. It's true they can't guarantee every single bit of their content, but they trying through their policies and a few scripts has value to me, and taking a look at what free software meaning and the basic freedoms it looks to preserve is important to be understood before complaining about an organization trying to offer free software. It would be more appropriate if the terminology changes to use the spanish "libre" word instead, but it is what it is, that why sometimes FOSS is instead referred as FLOS (free/libre or free and libre). And true, as a result developers who want to provide apks through f-droid and also through non free software app stores or repos (whatever makes more sense) need to have in place something to account for the differences, and that's not optimal, but there's a good reason for it, but some developers just don't want to do it and even less not depending on android proprietary stuff or other proprietary stuff for that matter, which is their prerogative any ways.

A little rant of mine, not we all have to agree over the same arguments I guess.

[–] kixik@lemmy.ml 2 points 2 weeks ago (1 children)

That was so long ago, haha, it's governed by these:

// disable captive portal
pref("network.captive-portal-service.enabled", false);
pref("captivedetect.canonicalURL", "");

The first can be easily changed to true in ~/.librewolf/librewolf.overrides.cfg or equivalent. The 2nd can be overwritten as well, but whether you look at FF to see what it has by default, or you use any more private site of choice for Librewolf to try to connect to, to test captive-portal. So yes, one can overwrite anything as long as you know what you're doing...

[–] kixik@lemmy.ml 4 points 3 weeks ago* (last edited 3 weeks ago) (4 children)

Well, it is available on the IzzyOnDroid separate f-droid repo, so if using the f-droid client, you can still grab freetubeAndroid with it.

Never tried it though, and not sure how bloated for a phone, but it's easy to install/update with any f-droid client.

9
submitted 4 months ago* (last edited 4 months ago) by kixik@lemmy.ml to c/archlinux@lemmy.ml
 

cross-posted from: https://lemmy.ml/post/21673875

Cross posting so that the OP realizes this community is alive. I have no issues with qemu, which is installed on my system with no issues.

Posting here as there doesn't seem to be an active Arch Linux community.

I noticed while updating my system today that I have a bunch of qemu packages I don't recall installing. So I took a look at why they were there and found this:

Name            : qemu-base
Required By     : qemu-desktop
Install Reason  : Installed as a dependency for another package

Name            : qemu-desktop
Required By     : None
Optional For    : qemu-base
Install Reason  : Installed as a dependency for another package

It seems like qemu-desktop was a dependency for something I later removed and pulled in qemu-base. However, because of the dependency cycle, they aren't showing up as orphans and has just been hanging around in my system along with 150mb of other dependencies.

Correct?

Edit: Adding clarification on why this was cross posted, and no I'm not the OP.

 

cross-posted from: https://lemmy.ml/post/21522958

(cross-posted from: https://lemmy.ml/post/21522265)

A group of people including Drew DeVault are trying to cancel RMS again, basing their claims on ancient misinterpreted quotes. Stallman may be controversial, but these activists are just acid for the entire Free Software movement.

 

Darn, and I just got Librewolf upgraded to 131.0, meaning needing to wait further for 131.0.2.

 

Is this total cookie protection something embedded, not requiring any user intervention? I know with librewolf we get the strict enhanced cookie protection mode, but I don't know if for this total protection there's something required, if not turned on by default...

Greetings !

 

Hello !

I'm wondering if there's some blogging mechanism which would allow some sort of unique digital signature (PGP perhaps) to prevent personification, but which allows non traceable and fully anonymous author. Not looking for blockchain like stuff (apart from the layer Monero adds, blockchains are totally transparent, traceable and non anonymous). Not looking for bigotry, attacking people or anything like that.

The idea is to be able to share ideas, even corporate related, without being afraid of retaliations whether at work, corporations or governments. Expressing something at pubic might bring unexpected consequences, particularly if not aligned by the corporation one works on if that's the case, or might provoke AI, bots, or paid/unpaid people looking around, to include anyone in a particular list, without even warning the writer about it.

So I was looking if such thing is possible, and if it exists. Social networks of course wouldn't be an option, they're not anonymous, and at contrary can be used to cross-reference and trace people.

If such solution doesn't exist, I'm wondering if something based on gnuNet might get close, although gnuNet is not meant to make users anonymous. Or perhaps something based on i2p.

Of course the digital signature should be used exclusively for the blog posting, and can't be associated to any real email, host, or whatever...

Feedback on the blog posts should also be allowed to anonymous people with their own unique digital signatures. But this is harder, since depending on the technology, not sure if moderation would be allowed, or even if it would make sense, in which case, no blog feedback should be allowed, though no feedback is really a down side for blog posts. Maybe allowing just the original post to remove feedback. Some other down side, but that's unavoidable, is the lack of non on thread feedback, meaning giving feedback through email or any other medium, since if that was available would make the writer non anonymous...

If such thing is not available, and eventually based on something like gnuNet or i2p, most probably clients would be needed to write blogs but another one that would offer some sort of RSS/atom functionality for the blog to be accessible from current RSS/atom readers.

 

This blog post, and some of its comments are pretty interesting and concerning at the same time. Not really sure if in the end that means that nothing other than centralized controlled messaging can be as cryptography safe.

Any comments?

1
Changes to dinit-rc (forum.artixlinux.org)
14
submitted 9 months ago* (last edited 9 months ago) by kixik@lemmy.ml to c/lemmy_support@lemmy.ml
 

Hello, !xmpp@lemmy.ml was locked by my mods, and continued on !xmpp@slrpnk.net which is entirely fine given federation, so I guessed I could follow it on the lemmy sort of synced space/community, !xmpp@slrpnk.net, where I can post to the slrpnk community without having an account there. But for some reason recent posts on slrpnk real xmpp community are not showing on !xmpp@slrpnk.net, like if they're not syncing anymore.

Any way to remediate it?

 

Hi !

As I have account on lemmy.ml, I look into the lemmy community created on slrpnk.net through the federated lemmy community, but its contents don't match the ones on the original slrpnk community. There are some messages missing.

Not sure if this is something someone would care, but I was planning to look at the contents through the lemmy instance, where I do have my account...

Greetings !

view more: ‹ prev next ›