kixik

joined 3 years ago
[–] kixik@lemmy.ml 2 points 1 hour ago

What they're saying there is that when trying to auto detect the server configurations, there are unexpected connections to cloudfare IPs, which didn't usually happen with K9. Who posted the concern associated this to telemetry, but the answers are pointing a different direction. But at this point it just guesses, :(

I guess some more formal traffic inspection needs to happen to understand if truly there's unexpected traffic, where it is directed to, and hopefully infer somehow its purpose. The guesses about what's happening suggest it's just about the auto connection, but again, just guesses.

I explored the configurations, and I didn't find anything about telemetry, and so neither how to disable it. K9 does not have an about:config advanced configuration like desktop Thunderbird does, so if there's truly telemetry or some other sort of information leakage, then after proving it, perhaps developers realize they can do better. But so far nothing really proving telemetry or information leakage.

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

What telemetry is enabled? Is there a way to disable it?

[–] kixik@lemmy.ml 3 points 6 hours ago

F-Droid produces its own builds, with its own signatures, so to get f-droid going, you'll need to install from F-Droid. However the import mechanism seems really nice. Perhaps you can install from F-Droid the official release, which can co-exist with your upstream installed beta release, import from it from the F-Droid app, then remove the upstream installed beta release, and if you wan to keep on beta, then install the beta release from F-DRoid (be careful right now, given a bug made K9 show up as beta release as well, but the app ID is clear, just being careful is enough), and then import from the official release, then remove the official release and you're all set. The idea is not to reconfigure a thing by doing those steps, and perhaps you wouldn't like to go to beta, and remain on the official release, which is not that behind, and perhaps better tested.

[–] kixik@lemmy.ml 3 points 15 hours ago

Did that, thunderbird release no beta, and no issues since I don't have google account. For people with google account requiring to re-sign in, and who don't often do so, signing in is really hard if they don't registered their phone number to google. It's sad, I commented about it in some other post. Understandable in reality they are different apps, but in the end it should be the same user ID, but nevertheless it's a PITA if people don't have a device permanently logged in, :( For them it's better to stay on K9,and hope K9 doesn't go away, or else find out how the heck to login to google once again.

[–] kixik@lemmy.ml 2 points 15 hours ago

correct, that's the official release, the other is beta for testers...

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

Sadly, when having a gmail account, the migration is not possible, if the user doesn't keep permanently logged in somewhere. TB is not taking the current K9 OATH, and tries to establish it's own authentication, which on a K9 + desktop TB user not logging often to google at all, it's really almost impossible to login to gmail, since it ask as security the user 1st phone number, which could have never been registered to google, and beyond that it requests to use a different device which is already logged in, but it you go to the desktop, and attempt to login, it does exactly the same thing, the same stupid question or requesting for another device. So it gets into a loop of devices which can't be resolved. And for this other user I tried to setup TB for, they don't authenticate near often to google, but they use both desktop TB and K9 quite well.

For now, for such users, until they figure out how the hell to login to their google account again, they better don't try migrating to Thunderbird, since the import functionality is not quite enough to get google mail working fine, again if the user doesn't login to google often. A bit sad, though it makes sort of sense, since the apps registered to google would be different. Sad in the sense that an already working setup for gmail on K9 can not just be imported as is to TB, and keep just working.

While K9 remains working, there's no issue for such users though. Hopefully that doesn't happen,

It works great when not having a google/gmail account, :)

[–] kixik@lemmy.ml 1 points 16 hours ago (1 children)

Ohh, it needs to import though. I was afraid in case there would be sort of two different directories over the same data, or that on TB dir it would be to start fetching stuff. But it seems it literally copies over the directory contents, which is fine, since the then the other app could easily been removed.

And it works with TB non beta, I guess it works with beta for testers a well (though I like the release, and see how it goes). I'll be using non beta for now, a bit behind, I prefer to use releases rather than beta releases, and on f-droid I enabled unstable upgrades...

Anyone played with push vs. pull on TB? On K9, I ended up having both. With the last years changes, it removed the push option selecting from the fetching configs, but the push could be selected/deselected from each folder, and I keep them both. Pulling makes the requirement of not having restrictions on battery usage though.

Not sure if that's getting any better with TB (non beta or beta), and if push has gotten any better. In the end, imap push/idle pretty much depend on the server, and not so much on the client I'd guess...

Thanks !

[–] kixik@lemmy.ml 1 points 17 hours ago (4 children)

Thunderbird beta for testers?

[–] kixik@lemmy.ml 3 points 17 hours ago (6 children)

OK, many thanks !

I'll just do nothing for now then. I hope if at some point a migration is required, it's sort of automatic, f-droid just starts using the Thunderbird app rather than the K9, without user intervention other than performing the f-droid upgrade, one and that would be it. But we'll see.

If you ask, knowing it's the same thing, I would have gone with just one app, replacing the other one, and that would be easier and clearer, :)

Thanks a lot again !

31
submitted 20 hours ago* (last edited 5 hours ago) by kixik@lemmy.ml to c/fdroid@lemmy.ml
 

I'm long K9 user, and I was aware of it becoming Thunderbird, but I need to clarify what should I do to easy eventual transition, hopefully without having the deal with all my K9 settings...

Today K9 turned into Thunderbird Beta for Testers, however there's already an app called that way Thunderbird Beta for Testers showing up on f-droid. Thoug the actual ID of each differ (com.fsck.k9 vs. net.thunderbird.android.beta).

What should K9 users do, to avoid losing its current settings (accounts, folder settings, encryption and so on)? Should we remain using the K9 app, and hope that when it goes away then the thunderbird app replaces it somehow automatically and pick all accounts and settings? Should this period when the two apps with the same name coexist be used to install thunderbird beta for testers, hope that it pick all settings from K9 up, and then remove K9?

It's somehow confusing, I was originally hoping at some point K9 just turned into thunderbird, but at once, automatically, without still having two apps, so I'm wondering what's next. For now I'm just still using the K9 app with thunderbird name...

Thanks !

Edit 1: Many thanks for those who replied, at least I don't have a google account, and no need to inherit the OAuth to google, or any other of such account for that matter, although I could remain to K9 I migrated to Thunderbird official release (no beta) without issues. It sounds like a good opportunity to migrate to Thunderbird.

Edit 2: It's sad that the OAuth can not be inherited, though understandable. For those who were just using TB or K9 for a long time with gmail, and the account gets into the infinite dependency loop of requiring a device already logged in, given the stupid security question has no answer, then perhaps it's time to ditch google and look for an alternative, I haven't found anything useful to help around there. Google actually sent a message indicated it has protected the user from herself, and inhibited her attempt to reach her own account. Meanwhile, just staying with K9 seems OK, since it's still there (just a metadata name corrupted but the app ID remained K9 still).

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

good idea, thanks !

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

Cool, many thanks ! I'll just wait a littloe longer then...

[–] kixik@lemmy.ml 4 points 1 week ago (4 children)

Oh, you mean using divestos-fdroid-repo? Well, before it became part of official f-droid I used to do that. I'm not sure how long it'll take to fix the official f-droid.org builds though, since I'd like to go back to it. The sad thing is that to move from one repo to another one loses all configurations/settings, :( But perhaps it's truly unsafe to wait until the build on f-droid.org gets fixed, if it ever does it.

Anyone aware if there are efforts to get it back building for f-droid.org? Does it depend on the Fennec issue getting resolved?

 

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.

 

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

Anyone aware of a conversations fork with support for unified push notifications? Or a similar xmpp android app with omemo (just the same as conversations' support) and unified push notifications support, available through the official f-droid repor or a f-droid repo if not available from the official ones?

BTW, I noticed !xmpp@lemmy.ml community was locked. Any particular reason for that?

Also, Converstions requests to set unrestricted use of battery, to use battery under background without restrictions. So it seems unified push notifications would help, though this github issue sort of indicates unified push notifications wouldn't help, so it just tells me there's no intention to include support for it on Conversations, but not that it wouldn't help save battery.

 

Anyone aware of a conversations fork with support for unified push notifications? Or a similar xmpp android app with omemo (just the same as conversations' support) and unified push notifications support, available through the official f-droid repor or a f-droid repo if not available from the official ones?

BTW, I noticed !xmpp@lemmy.ml community was locked. Any particular reason for that?

Also, Converstions requests to set unrestricted use of battery, to use battery under background without restrictions. So it seems unified push notifications would help, though this github issue sort of indicates unified push notifications wouldn't help, so it just tells me there's no intention to include support for it on Conversations, but not that it wouldn't help save battery.

13
submitted 8 months ago* (last edited 8 months ago) by kixik@lemmy.ml to c/fediverse@lemmy.ml
 

https://disroot.org provides several decentralized federated services, as email and xmpp, besides other cloud services as well... But not sure if asking here is right or not, but don't know anywhere to ask either...

Is it having a license issue, does anyone know about it? Any status updates?

Websites prove their identity via certificates. LibreWolf does not trust this site because it uses a certificate that is not valid for disroot.org. The certificate is only valid for p1lg502277.dc01.its.hpecorp.net.
 
Error code: SSL_ERROR_BAD_CERT_DOMAIN

But also:

disroot.org has a security policy called HTTP Strict Transport Security (HSTS), which means that LibreWolf can only connect to it securely. You can’t add an exception to visit this site.

The issue is most likely with the website, and there is nothing you can do to resolve it. You can notify the website’s administrator about the problem.

I also tested with ungoogled chromium and pretty similar thing...

Anyonea aware, and also about disroot saying on this?

Edit (sort of understood already, no issue with disroot at all): The issue only shows up under the office VPN. It seems like disroot is not recognizing the office's cert...

Edit: Solved. Yes it's the office replacing the original cert with its own, as someone suggested. Thanks to all.

23
submitted 8 months ago* (last edited 8 months ago) by kixik@lemmy.ml to c/linux@lemmy.ml
 

Hello !

As Mint is based on Ubuntu, I’m wondering if it will follow the missteps (to me at least) Ubuntu is doing to demote *.deb packages in favor of snaps?

Well that based on Ubuntu 23.10’s New Software App Will Demote DEBs (Apparently) post, and its lemmy.ml discussion.

From all ubuntu based distros, Mint seems not to follow those missteps, but I'm wondering if Rhino will do the same. Actually I don't like Rhino created a wrapper package manager which actually gets snap support as well as apt on the same bucket. But who knows, it might be they won't follow ubuntu on this.

Does anyone know?

My interest on Rhino comes from it being rolling release. But I don't want snap to become the source of common/important packages.

Thanks !

 

I started some time ago using a teddit frontend with local subscriptions, and at some point it was hard for the one I picked to keep up, then I moved to libreddit, at that time libredd.it, then it stopped working and moved to libreddit.spike.codes, but it seems it stopped working as well, and finally I moved to libreddit .mha.fi, but some time back there was too much rate limiting, making it unusable, and since yesterday it seems totally down, giving the error "502 Bad Gateway". I also have the libRedirect extension on Librewolf configure to choose among several libreddit instances (so when searching for something any is picked), and most of them seem out of service, or being rate limited as well.

So, are frontends for reddit finally coming to an end?

Edit: Indeed, it seems at least non self-hosted front-end instances are way rate limited or down

 

Any thought on DOH, which is the base for this ECH? I remember in the end cloudfare and some others, providing the service to services, were the ones gathering the information instead of the ISPs... Librewolf still has DOH disabled by default, and although it can be easily change, perhaps that default is overall the sounder way.

Do Librewolf guys have different thoughts on DOH now, specially with the possibilities of ECH?

view more: next ›