cross-posted from: https://lemmings.world/post/12787893

1. SEPARATE MONERO ACCOUNTS - For privacy reason, organize own funds into accounts like “cash”, “work”, “trading”, “mining”, “donations”, etc.. And in order to later combine these individual accounts funds, sweep/withdraw each of the account balance the way, that you do NOT sweep/withdraw multiple accounts balances in a single transaction, but one transaction per account. Feather wallet may do this thanks to its "Coin control" functions? Source: https://getmonero.dev/public-address/subaddress.html ; https://docs.featherwallet.org/guides/features

2. WAIT/AGE XMR AFTER RECEIVING IT - After receiving Monero (XMR) from a 3rd party, wait some time (a few hours to a few days)

3. CHURN/MIX XMR BY SENDING IT TO OTHER OWN ACCOUNT - Churning/mixing means to send your Monero/XMR to a different account/wallet in order to make it harder for others to track you: "So after 1 churn, there is a 1 in 16 chance (6.25%) that this transaction is yours. After 2 churns, it is a 1 in 16x16 = 1/256 = 0.39% chance that the final output of the route is yours. After 3 churns, 1 in 16x16x16 = 1/4096 = 0.0244%".

   A) Send your entire (or part of) your account's balance to a different account/wallet of yours, such secret destination account won't be used for receiving 3rd party XMR (only yours).

   B) Send your entire account's balance to same account (its own address - self). In case you would send partial, you would mix churned outputs with non-churned making your anonymization effort more or less pointless.

4. WAIT/AGE CHURNED/MIXED XMR AGAIN

5. CHURN/MIX AGAIN BY SENDING TO SELF OR 3RD PARTY - In order to decrease chance (from above mentioned 6.25% to 0.39%) of output being attributed to you. When having various Monero accounts for various purposes (e.g. "work", "home"), possibly churn 2x before "merging" XMR from multiple accounts of yours, example: KYC'ed 3rd party -> MyWork -> MyWork2nd ......... 3rd party -> MyHome -> MyHome2nd -> MyHome3rd -> MyWork2nd

------

FAQ: Why it is not pointless to send Monero from/to self, meaning same account? Because sending to same account is effective in decreasing the chance of a transaction being traced (attributed to you), since "there is no way to see the address" and other person says "You can send to yourself as many times as you want, without anyone knowing you're actually doing it. Every such transaction (called "churn") puts you in a bigger crowd of possible senders." and another person claims similar "churn to your own wallet, as it is not possible to link the output to the wallet".

cross-posted from: https://lemmings.world/post/12787871

> 1. SEPARATE MONERO ACCOUNTS - For privacy reason, organize own funds into accounts like “cash”, “work”, “trading”, “mining”, “donations”, etc.. And in order to later combine these individual accounts funds, sweep/withdraw each of the account balance the way, that you do NOT sweep/withdraw multiple accounts balances in a single transaction, but one transaction per account. Feather wallet may do this thanks to its "Coin control" functions? Source: https://getmonero.dev/public-address/subaddress.html ; https://docs.featherwallet.org/guides/features > > 2. WAIT/AGE XMR AFTER RECEIVING IT - After receiving Monero (XMR) from a 3rd party, wait some time (a few hours to a few days) > > 3. CHURN/MIX XMR BY SENDING IT TO OTHER OWN ACCOUNT - Churning/mixing means to send your Monero/XMR to a different account/wallet in order to make it harder for others to track you: > "So after 1 churn, there is a 1 in 16 chance (6.25%) that this transaction is yours. After 2 churns, it is a 1 in 16x16 = 1/256 = 0.39% chance that the final output of the route is yours. After 3 churns, 1 in 16x16x16 = 1/4096 = 0.0244%". > > A) Send your entire (or part of) your account's balance to a different account/wallet of yours, such secret destination account won't be used for receiving 3rd party XMR (only yours). > > B) Send your entire account's balance to same account (its own address - self). In case you would send partial, you would mix churned outputs with non-churned making your anonymization effort more or less pointless. > > 4. WAIT/AGE CHURNED/MIXED XMR AGAIN > > 5. CHURN/MIX AGAIN BY SENDING TO SELF OR 3RD PARTY - In order to decrease chance (from above mentioned 6.25% to 0.39%) of output being attributed to you. > When having various Monero accounts for various purposes (e.g. "work", "home"), possibly churn 2x before "merging" XMR from multiple accounts of yours, example: > KYC'ed 3rd party -> MyWork -> MyWork2nd > ......... 3rd party -> MyHome -> MyHome2nd -> MyHome3rd -> MyWork2nd > > ------ > > FAQ: Why it is not pointless to send Monero from/to self, meaning same account? Because sending to same account is effective in decreasing the chance of a transaction being traced (attributed to you), since "there is no way to see the address" and other person says "You can send to yourself as many times as you want, without anyone knowing you're actually doing it. Every such transaction (called "churn") puts you in a bigger crowd of possible senders." and another person claims similar "churn to your own wallet, as it is not possible to link the output to the wallet".

1. SEPARATE MONERO ACCOUNTS - For privacy reason, organize own funds into accounts like “cash”, “work”, “trading”, “mining”, “donations”, etc.. And in order to later combine these individual accounts funds, sweep/withdraw each of the account balance the way, that you do NOT sweep/withdraw multiple accounts balances in a single transaction, but one transaction per account. Feather wallet may do this thanks to its "Coin control" functions? Source: https://getmonero.dev/public-address/subaddress.html ; https://docs.featherwallet.org/guides/features

2. WAIT/AGE XMR AFTER RECEIVING IT - After receiving Monero (XMR) from a 3rd party, wait some time (a few hours to a few days)

3. CHURN/MIX XMR BY SENDING IT TO OTHER OWN ACCOUNT - Churning/mixing means to send your Monero/XMR to a different account/wallet in order to make it harder for others to track you: "So after 1 churn, there is a 1 in 16 chance (6.25%) that this transaction is yours. After 2 churns, it is a 1 in 16x16 = 1/256 = 0.39% chance that the final output of the route is yours. After 3 churns, 1 in 16x16x16 = 1/4096 = 0.0244%".

   A) Send your entire (or part of) your account's balance to a different account/wallet of yours, such secret destination account won't be used for receiving 3rd party XMR (only yours).

   B) Send your entire account's balance to same account (its own address - self). In case you would send partial, you would mix churned outputs with non-churned making your anonymization effort more or less pointless.

4. WAIT/AGE CHURNED/MIXED XMR AGAIN

5. CHURN/MIX AGAIN BY SENDING TO SELF OR 3RD PARTY - In order to decrease chance (from above mentioned 6.25% to 0.39%) of output being attributed to you. When having various Monero accounts for various purposes (e.g. "work", "home"), possibly churn 2x before "merging" XMR from multiple accounts of yours, example: KYC'ed 3rd party -> MyWork -> MyWork2nd ......... 3rd party -> MyHome -> MyHome2nd -> MyHome3rd -> MyWork2nd

------

FAQ: Why it is not pointless to send Monero from/to self, meaning same account? Because sending to same account is effective in decreasing the chance of a transaction being traced (attributed to you), since "there is no way to see the address" and other person says "You can send to yourself as many times as you want, without anyone knowing you're actually doing it. Every such transaction (called "churn") puts you in a bigger crowd of possible senders." and another person claims similar "churn to your own wallet, as it is not possible to link the output to the wallet".

Some feedback regarding Proton VPN documentation and some confusion regarding Firefox DNS configuration:

https://protonvpn.com/support/browser-extensions#firefox says:

"By default, Firefox does not route DNS queries through the HTTPS connection to our VPN servers" and then is mentioned a workaround to fix it.

That suggest alarming thing, that ProtonVPN Firefox user has to do some custom workaround in order to be private (prevent a DNS leak).

On another hand, https://protonvpn.com/support/dns-leaks-privacy says:

"DNS queries are routed through the VPN tunnel to be resolved on our servers"

these statements are a bit confusing/contradicting (though Proton later explains that this latest statement does not apply on a browser extension VPN apps) and Proton further adds at https://protonvpn.com/support/dns-leaks-privacy/#dns-over-https that the DNS leak can happen also due to enabled DoH feature in web browser.

Solution: ProtonVPN browser extension should (if possible) warn user in case it fails to process DNS and as a result, it is leaked. Vote for this feature request

----

Another "issue" is with the above mentioned/linked workaround (here I am speaking only about Firefox), this workaround: go to "about:config into the URL bar and hit <enter>. At the warning, click Accept the risk and continue → search for network.trr.mode"

In my case I had this set that variable to 5 which means DoH "Off by choice", Proton in said tutorial suggest value 3 instead, which means (According to https://wiki.mozilla.org/Trusted_Recursive_Resolver#DNS-over-HTTPS_Prefs_in_Firefox ) "Only use TRR, never use the native resolver.".

This confuses me since it looks like an opposite to what i have now, while any DNS leak site:

https://www.dnsleaktest.com

https://ipleak.net

does NOT report leak in my case nor in case i set network.trr.mode to 3. A bit weird but i guess no big deal?

Thanks for your feedback in advance.

On my desktop computer, I have tried to use Syncthing WebUI to add my remote headless server (no GUI/display, only CLI), which was established by just running ./syncthing command. I have got the ID from the CLI output.

Yet my WebUI tells me "connection refused" and "context deadline exceeded" and the headless server output shows "rejected: unknown device" next to my connection attempt.

In a "syncthing --help" output, I am unable to find any command which would add mine defined remote machine ID and allow its connections.

I have tried to access http://headless server IP:8384/ but it timeout. I am unable to find any firewall blocking, another service on a different port is accessible.

Any idea how to proceed interconnecting the two devices simplest way?

Hello, when I use following sqlite3 commands, it returns error "cannot commit - no transaction is active" somewhere near the line "WHERE user IN (".... So I wanted to ask what to replace with what in order not to produce said error. I am not a developer and the ChatGPT (1, 2) is unable to provide working code. Can you please help?

said commands: ``` -- Start a transaction BEGIN TRANSACTION;

-- Insert missing user_permission_overrides rows INSERT INTO user_permission_overrides (room, user, write) SELECT DISTINCT ru.room, u.id, TRUE FROM room_users ru JOIN users u ON ru.user = u.id LEFT JOIN user_permission_overrides upo ON u.id = upo.user AND ru.room = upo.room WHERE u.created < strftime('%s', '2024-07-02 00:49:26') AND upo.user IS NULL;

-- Update existing user_permission_overrides rows UPDATE user_permission_overrides SET write = TRUE WHERE user IN ( SELECT id FROM users WHERE created < strftime('%s', '2024-07-02 00:49:26') );

-- Commit the transaction COMMIT;

END; ```

list of tables, schema, pragma I have pasted here please.

Kodi (20.1 (20.1.0) Git:20230316-d8f3f99cc3-dirty). Platform: Linux ARM 32-bit

was not responding after start and the Tvheadend shown no channels at http://192.168.0.2:9981/extjs.html (later I have found the disconnected antena cable).

cat /home/xbian/.kodi/temp/kodi.log (for other OS log paths check here) shown some warnings and errors, which I have all pasted here.

When i have pushed any button on the remote control (control worked and TV led indicated contact), there was no log entry added into a mentioned kodi log.

"dmesg -T" not shown any errors. After rebooting over SSH (reboot now), it started responding after boot (weird that not under first boot and second yes). But it got no reply from TVHeadend HTSP client (no signal, later I have found it is disconnected antena ;). When i went to this addon configuration, it freezed with following errors in said Kodi log:

error <general>: Repository add-on repository.universalscrapers does not have any directory and won't be able to update/serve addons! Please fix the addon.xml definition error <general>: AddOnLog: pvr.hts: Command getDiskSpace failed: Unable to stat path error <general>: GetDriveSpace: Add-on 'pvr.hts' returned an error: server error warning <general>: OnMessage: Suspiciously long time to handle GUI_MSG_PLAYBACK_STARTED (25.942558s) warning <general>: OnMessage: Suspiciously long time to handle GUI_MSG_PLAYBACK_STARTED (6.573358s) error <general>: CCurlFile::Open - <http://127.0.0.1:9981/imagecache/2403> Failed with code 404: ... Then i saw it moved to and stuck on a "stopping kodi" xbian screen. Since I have not updated a few months, i did command "sudo apt update;sudo apt upgrade" via SSH command line remotely.

it updated many packages, no "kodi" package, but "tvheadend" one

at the end of the upgrade process was: initctl: invalid command: try-restart Try `initctl --help' for more information. invoke-rc.d: initscript ntp, action "try-restart" failed. Setting up xbian-package-config-xbmc (20231115) ... Processing triggers for xbian-package-config-xbmc (20231115) ... Errors were encountered while processing: fail2ban (fail2ban has been installed by me previously and it never worked entirely, and removal is not working somehow), system rebooted itself automatically after upgrading.

After reboot, there still has been errors in the mentioned kodi log: ``` Starting Kodi (20.1 (20.1.0) Git:20230316-d8f3f99cc3-dirty). Platform: Linux ARM 32-bit info <general>: Kodi compiled 2023-03-17 by GCC 10.2.1 for Linux ARM 32-bit version 5.18.2 (332290) info <general>: Running on BCM2711 with XBian 12.0 - Bullseye, kernel: Linux ARM 32-bit version 6.1.66+ info <general>: FFmpeg version/source: 4.4.1-Kodi error <general>: GetDirectory - Error getting /home/xbian/.kodi/userdata/addon_data/pvr.nextpvr/ error <general>: GetDirectory - Error getting special://profile/addon_data/pvr.nextpvr/ error <general>: GetDirectory - Error getting /home/xbian/.kodi/userdata/addon_data/pvr.vbox/ error <general>: GetDirectory - Error getting special://profile/addon_data/pvr.vbox/ error <general>: GetDirectory - Error getting /home/xbian/.kodi/userdata/addon_data/pvr.vuplus/ error <general>: GetDirectory - Error getting special://profile/addon_data/pvr.vuplus/ info <general>: PVR Manager: Started error <general>: [2024-07-01 20:08:55,877 pyinotify ERROR] add_watch: cannot watch /run/splash WD=-1, Errno=No such file or directory (ENOENT) error <general>: AddOnLog: pvr.hts: Command getDiskSpace failed: Unable to stat path error <general>: GetDriveSpace: Add-on 'pvr.hts' returned an error: server error

```

and the screen detected no signal. After next reboot, the screen is ok. After next reboot with connected antena cable, these errors and warnings remains.

After researching all that warnings, I have this (highlighted items are unsolved):

Regarding first block of errors (DBus error: org.freedesktop.DBus.Error.InvalidArgs), someone says that there is no issue with it.

Regarding second block of errors ("Repository add-on repository.superrepo.org.gotham.all uses old schema definition for the repository extension point!"), I think i will have to contact repo admin or uninstall that repo/addons.

"POParser: missing msgstr line in entry. Failed entry", I have not found any solution to that.

Third block: (JSONRPC: Could not parse type "Setting.Details.SettingList") - someone says "can also be ignored, not skin related"

Fourth block may be related to PVR addons that i think are disabled and can not be uninstalled and has no updates. Weird.

Fifth block: (pyinotify ERROR] add_watch: cannot watch /run/splash WD=-1, Errno=No such file or directory (ENOENT)) - I have not found any solution.

Sifth/final block of errors is likely related to second block.

Reposted from: https://lemmings.world/post/10865023

> 1. Recognize the common signs > > • Urgent or emotionally appealing language > • Requests to send personal or financial information > • Unexpected attachments > • Untrusted shortened URLs > • Email addresses that do not match the supposed sender > • Poor writing/misspellings (less common) > > 2. Resist and report > Report suspicious messages by using the “report spam” feature. > If the message is designed to resemble an organization you trust, report the message by alerting the organization using their contact information found on their webpage. > > I have found also these phishing reporting pages: > > SITE: https://safebrowsing.google.com/safebrowsing/report_phish/ > > SITE: https://www.ncsc.gov.uk/section/about-this-website/report-scam-website > > SITE: https://www.scamwatcher.com/scam/add?type=fraudulent_website > > SITE/EMAIL: https://report.netcraft.com/report ( scam [\AT\] netcraft [\D0T\] com - for a phishing/fraud mail forwarding ) > > EMAIL: https://www.ncsc.gov.uk/collection/phishing-scams/report-scam-email#section_1 - forward phish mail to report [\AT\] phishing [\D0T\] gov [\D0T\] uk > > EMAIL: https://apwg.org/reportphishing/ ( reportphishing [\AT\] apwg [\D0T\] org - forward phishing mail as attachment if possible ) > > EMAIL: phishing-report [\AT\] us-cert [\D0T\] gov (phishing message should be sent as attachment possibly or its full source code in a message BODY.) > > OTHER: https://www.knowbe4.com/free-phish-alert (email client extension) > > feedback or new additions are welcome > > 3. Delete > Delete the message. Don’t reply or click on any attachment or link, including any “unsubscribe” link. > The unsubscribe button could also carry a link used for phishing. Just delete > > _________________________________________________ > > Source: https://www.cisa.gov/secure-our-world/recognize-and-report-phishing > > Send this to your friends, especially internet beginners.

If anyone wants to check, here is a video showing a Firefox dev. console (F12 key) and errors occured on https://www.openstreetmap.org/search?query=Oslo#map=8/59.973/10.723

I would like to find the causing extension without the need of disabling extensions randomly or by disabling half of extensions, then if issue solved, disable half of that half etc..

Sometimes it helps to hover over the link near the error on dev. console (F12 key), Console tab, to see the moz-extension://somestring and find first characters of the string at page about:debugging#/runtime/this-firefox Though this time, it does not show that IMO (per the linked video).

If I should click something particular in a FF dev. console (F12), please guide me. Thank you.

SPAM companies like DataPacket/DataCamp, 247.ro continuing to SPAM while using IPs from RIPE, which says "RIPE NCC does not have the legal power to investigate these types of issues or take action against ISPs, other organisations or individuals. ... If you require further assistance, we suggest contacting your local law enforcement agency or seeking legal advice." I know that there are many victims of their unsolicited messages, yet why they are allowed to operate for years, law not reaching them? What one can do except submitting their IPs to:

https://www.spamcop.net

https://www.spam.org/report

https://signalants.signal-spam.fr/reportings/new

https://www.abuseipdb.com

https://cleantalk.org/blacklists

I have tried to submit to TrustPilot, but they are protecting SPAMmers.

3 password managers at same time 🧐 :

My older version of a Firefox browser remember most of my passwords (I am ok how it works), but some important passwords are also stored in KEEpass and not in Firefox. Then there is a ProtonPass which can import both Firefox CSV and KeePass XML.

Problem with import and synchronization of these managers is that the

1. Pass is not made to deduplicate the imported data (some imported logins may already be in vaults), which requires user to delete Pass logins prior importing a .csv file (importing because file contains more up to date logins).

2. import does not contain 2FA secrets nor aliases (aliases deleted in Pass can not be restored into Pass at the time of writing - June 2024).

Firefox and Proton Pass - PROS and CONS (as of June 2024):

Quality of suggested logins:

⛔️ Firefox (old ver.) suggests all passwords saved across whole website incl. its subdomains which is messy

✅ Pass: suggests only passwords for a present page (not subdomains) = good

⛔️ Pass: does not automaticaly complete/suggest login when typing into username field and the list of saved logins is not alphabetically sorted by the username.

Speed:

✅ Firefox: shows saved logins instantly

⛔️ Pass: 1 second delay of a Proton Pass drop down menu with login username suggestions comparing to Firefox which loads immediately and gives impression that it loads even before login page finished loading. Both password managers loads at same time on user mouse click into the login field. Delay of a ProtonPass happens only when the suggestion menu should appear automatically upon loading a login page.

Registration form suggestions:

✅ Firefox: suggests previously used usernames/emails when typing, which is fine

🆗 Pass: does suggest anything when i type, as already mentioned. When I click, it suggests main ProtonMail address and allows generating unique alias which is very important key feature

🆗 Pass: password generating box shows non-important confirmation of a successfully copied password, which hides after like 2 seconds, making impossible to read the next form field during that time, which is annoying.

Login form suggestions:

⛔️ Pass: does not offer any login suggestion on a Basic HTTP Auth (.htaccess password protection of a directory) forms (popup) of mine (site: ILF admin, C*A/my)

Other:

⛔️ Pass: in Firefox i think it sometimes gets logged out requring to spend time re-login which may require 2FA auth from other device or other password manager.

✅ Pass: editing, grouping of passwords seems a bit better than Firefox

✅ Pass: Integrated 2FA

✅ Pass: Pass monitor in paid plan, password strength/leak indication

PROS vs CONS. What to do?

ProtonPass is a bit slower than Firefox, yet it has its advantages - email alias generating, 2FA....

SimpleLogin browser extension can be used for Proton aliases and if you do not need 2FA, it may be easier to stay with just Firefox, which is enough safe manager since I am already making backups of a Firefox (incl. passwords - which are also synced E2EE to the Mozilla cloud https://support.mozilla.org/en-US/kb/sync#w_is-it-secure).

Other option is to use Pass only for aliases and 2FA and inside its General settings, disable passwords saving and filling, letting Firefox do this job.

Third manager (for example KeePassXC) can serve as a backup, it can also import exports of Pass and Firefox. I guess it would be good to backup any password manager (incl. Pass) data regularly on schedule.

What are your suggestions/feedback regarding this?

After removing all passwords under three dots/kebab menu in the top corner of the page "about:logins", i wanted to import passwords from a Proton Pass to see how it works. Yet there is no import menu entry. After researching, I have found a solution that I want to share:

go to "about:config" page, and search for "signon.management.page.fileImport.enabled". Set it to true by double clicking on "false". Reload "about:logins" page to see the import menu entry under three dots corner menu.

Firefox 115.12.0esr with Pass 1.17.4

On various pages including https://lemmy.ml/signup when I click 1st time into a email or password field, Pass shows a "suggestion" box, when I click one more time into that form field, the box now fails to hide even i click outside of it. Workaround is to click into different form field.

Anyone is experiencing the same? On which platform/pass version?

Reposted from: https://lemmings.world/post/10530999

> Please what are the easiest and fastest steps in order to find backup of a currently unavailable post thanks to no longer running Lemmy instance? > > Lets say it is this post we are reading, that become offline. I am not asking for the links to instances that hosts it, but for the way on how to discover all the instances myself.

> So far I have found only this way: > 1. open largest instances list: https://lemmyverse.net/?order=posts&open=true > 2. open one after another and under magnifier button, search for the same post ID (number) as your dead link has

A quick look at the https://join-lemmy.org/docs/administration/federation_getting_started.html does not answer that question. Though at least ChatGPT has an opinion (which may be misleading) 😀

> the probability of it (the post) being distributed on multiple instances depends on factors such as the popularity of the post, the number of upvotes and comments it receives, and how widely it is shared across different instances. Posts that generate a lot of engagement and discussion are more likely to be distributed on multiple instances, as they are more likely to be shared and reposted by users. Additionally, posts that are deemed relevant or controversial may also be more likely to be spread across multiple instances.

I am unsure what it means by shared (i assume just posting a link is not enough).

If that is true that reposted (often called cross-posted) post makes a fully "featured" copy/backup on a different Lemmy instance, is there anything else that does it? Thank you

Please what are the easiest and fastest steps in order to find backup of a currently unavailable post thanks to no longer running Lemmy instance?

Lets say it is this post we are reading, that become offline. I am not asking for the links to instances that hosts it, but for the way on how to discover all the instances myself.

So far I have found only this way:

1. open largest instances list: https://lemmyverse.net/?order=posts&open=true

2. open one after another and under magnifier button, search for the same post ID (number) as your dead link has. One can also search for the post title (while making sure that the search scope is everywhere, not local).

Summary: I wanted to see if I can synchronize Firefox and ProtonPass passwords. It works more or less. One just need to pay attention to using only one or another for saving passwords and if later wanted to switch, just delete outdated app passwords database and import other app passwords. NOTE: If you choose to delete ProtonPass logins and import 3rd party logins, it will possibly NOT import your 2FA secret and aliases (you would have to move these to a separate vault before deleting everything else!

Here is exactly written on what i did and what I have faced in July 2024 (maybe later version of the Proton Pass will work better).

After backing up Firefox browser data/profile and exporting its passwords at "about:logins" page (three dots in the top corner), i have deleted all Firefox passwords (from same three dots menu). Then enabled Firefox passwords import (there were no import entry in that three dots menu) by going to "about:config" and searching for "signon.management.page.fileImport.enabled" double-clicking "false" to set it to "true". Reloaded "about:logins" page and then again using three dots menu imported the .csv export file made by the Proton Pass. Result:

New logins added: 1,808 Existing logins updated: 0 Duplicate logins found: 28 (not imported) Errors: 12 (not imported)

Under details, i could see which rows was problematic (only problem type was "Missing url") and after opening .csv file in a Calc editor i could see that the problematic rows were indeed "missing url" (or anything) in "url" row but the "name" field had the domain name. The problematic rows were almost exclusively Proton aliases (and these does not need any fixing and their later import into Proton Pass failed anyway - in the current version of the Pass that I have used), yet not knowing that at the moment, I have fixed all rows with missing url by copying name into url and prefixing with https:// using Linux command:

awk 'BEGIN{FS=OFS=","} $3=="" {$3="https://" $2} 1' "input.csv" > output_tmp && mv output_tmp "output.csv"

For Windows, this may work: for /f "tokens=1-7 delims=," %a in (input.csv) do @echo %a,%b,%c,%d,%e,%f,%g,%h,%i >> output_tmp && move /y output_tmp output.csv

Upon import of the fixed file, there was same number of errors and this time it was "Missing password".

I did insert a random passwords by modifying previous command like this: awk 'BEGIN{FS=OFS=","} $5=="" {$5="ng21@Ak" $9} 1' "input.csv" > tmp && mv tmp "output.csv"

.csv file can be opened inside LibreOffice Calc (or other table processor), where it is visible in easy to read format.

So after all, import from Proton Pass using .csv file was successful (despite a few harmless errors).

Opposite direction - synchronizing from Firefox to ProtonPass may be problematic. At least in my case was. Because Proton Pass did not delete any duplicates. So if Proton Pass is outdated and Firefox has all ProtonPass items(logins) + new items, it can be done as follows, yet please note that deleting Pass logins and importing 3rd party app logins (Firefox) will possibly not import 2FA settings, so if you are using 2FA, make sure you save private keys so you can setup it again later - keys are visible when editing login with 2FA): Export Proton Pass for backup purpose. Create new vault and move to it all email aliases (meaning aliases not regular logins). Delete vault with logins and create new one and fill it with Firefox .csv file.

I have found around 20 search engine pages worth lemmings.world pages, where one search engine page is 10 results, so in total like 200 indexed subpages of the lemmings.world ?

https://www.ecosia.org/search?q=site%3Alemmings.world&p=19

https://duckduckgo.com/?hps=1&q=site%3Alemmings.world&ia=web

Is it too low or too much considering amount of content posted here?

When there is only one vault in Proton Pass, it seems like the option to Delete vault is inactive/disabled and can not be clicked.

After creating second vault, it worked to delete first (main one). It is a bit weird, no explanation why i was unable to delete.

When I am continuously receiving small Monero payments, should I withdraw my Monero account balance (always to the same secondary XMR account of mine) more often or less often in order to ensure lower traceability of the funds?

I have read that withdrawing "account balance more often can lead to lower traceability of the funds". Is it significant? azalty@jlai.lu mentioned that "after 1 churn, there is a 1 in 16 chance (6.25%) that this transaction is yours. After 2 churns, it’s a 1 in 16x16 = 1/256 = 0.39% chance that the final output of the route is yours" But I think that what he wrote applies on a subsequent churns of "same funds" (mywalet1->mywallet2->mywallet3 = 2 churns). But when i withdraw just once per year my received balance or twice per year, does it mayke any difference (how big) in terms of anonymity/traceability?