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?

Hello, [email protected] was locked by my mods, and continued on [email protected] which is entirely fine given federation, so I guessed I could follow it on the lemmy sort of synced space/community, [email protected], 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 [email protected], 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 !

I believe the settings to disable this on Librewolf are set by default...

Hey !

On LOS 21, the app DeviceLockController is there, but it can't be stopped neither disable, at least from my side.

There's another one I don't trust, Android System Intelligence, but I could stop it and disable it.

Those two apps really are scary to be part of LOS. Is anyone aware of bugs on LOS about getting rid of them?

How about DeviceLockController? A reasonable way to disable it without risking too much bricking the phone in the process?

Thanks !

xz-5.6.1-2 from Artix system repo is already available.

Artix corresponding news: The xz package has been backdoored

I'm not self hosting, so I'm depending on what the server admin enables, and the policies they establish.

That said, the server fully supports xep-0313, which perhaps among other things control messages being kept on the server precisely for the purpose of sending them to all registered devices, thus allowing the sync.

But perhaps there's a policy in place removing the messages from the server as soon as some device has gotten it, leaving only online devices with the ability to grab them. I don't know if that's possible...

I experimented getting a device offline for a couple of minutes, and then exchanged messages with another account, and also to my same account. Then eventually I got the device offline, and none of the messages, not even the ones sent to myself, were ever synced on the device just coming online...

This is really sad, since that's precisely one of the benefits of having servers over peer to peer solutions, it's easier to sync devices through the server.

Might this be some sort of policy to keep disk usage on the server low?

I might need to explore some other server if that's the case...

Thanks !

Edit: Communicated with the admin, and they mentioned this was unexpected.

Just wondering, as the reasons to move here are gone, can the community go back to lemmy.ml? There are quite some posts over lemmy.ml, so going back there would be useful I believe, and also moving the few posts here over there would be just great (perhaps not the comments)...

Just an honest question, not to provoke flame wars or anything like it...

Greetings !

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 [email protected] 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 [email protected] 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.