hetzlemmingsworld

When I am following a person A on social network X and person B retweets person A post, it means that on my timeline is that post 2 times, a duplicity. How can i fix this issue in X settings, if that is possible?

On my years old free X account, I have been active in last days posting replies to other people (important politicians which gets many replies to their posts) comments (I mean politician posts, other person reply it and I reply to this reply), me adding around 30 replies in maybe 36 hours.

Interesting is that after these few days, when I go to https://x.com/me/likes I can not see a single like or a reply, yet my replies were thoughtful and opposing other people opinion. I have used secondary browser where I am not logged-in (Tor browser) to check couple posts if I can see my replies and I could see it. When I have been last active on X, before around 7 months, I see that I have got a reply to my comment.

On my recent comments, I can see a button with a vertical bars (like an analytics), yet it says that something went wrong, when I click it. Maybe some of my browser extensions blocks it.

In recent days, I have changed my account important/security settings and X not allowed me to change my email/password. Also my comments usually contains one or even two links to prove my claim, so that may also looks spammy.

Shadow ban? I have checked https://hisubway.online/shadowban/ and https://taishin-miyamoto.com/ShadowBan/ with no problem detected.

https://help.x.com/en/forms does not show any relevant contact category where I would ask. Any idea what to try please?

https://unstoppableswap.net/ / https://github.com/UnstoppableSwap/core makers (i do not mean a SW developers, but swap providers) seems to have swap markup (assuming a fee) of around 3% which is too expensive and along with the limits on amount of traded coin pretty unusable IMO. Am I missing any makers or source for it which allows near zero fees/markup? Why such makers are not available (by default)?

I am currently using RetoSwap https://github.com/retoaccess1/haveno-reto which allowed me to place and complete the BTC and ETH exchange to XMR at 0% fee. (only paying regular Monero tx fee for a temporary custody)

How to setup an UnstoppableSwap maker? Is it this https://github.com/UnstoppableSwap/core/blob/master/dev-docs/asb/README.md . I do not see any easy to understand tutorial for layman which would tell me the requirements (evaluate the cost) + be easily understandable.

When You enable removal of all cookies upon web browser restart, is it wise to exempt tens of sites by adding them to the exception/allowed list:

about:settings#privacy -> Cookies... -> Manage exceptions "You can specify which websites are always or never allowed to use cookies and site data."

i am constantly bothered by the Stack Exchange Network which constantly keep me logged-out and when i login, it redirect me to a homepage instead of a previous page, when i go back, it shows as logged out, so i have to F5 the page. And this constantly repeats.

Am I rendering my attempt to reduce tracking near pointless by allowing many sites like Microsoft's Github, Stack overflow etc. to permanently store the data incl. cookies?

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 . 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?

Proton zpřístupnil svou bezplatnou soukromou VPN i pro prohlížeče založené na Firefoxu a Chrome:

Firefox:

https://addons.mozilla.org/cs/firefox/addon/proton-vpn-firefox-extension/

https://protonvpn.com/cs/download-firefox-extension

Chrome:

https://chromewebstore.google.com/detail/proton-vpn-fast-secure/jplgfhpmjnbigmhklmmbgecoobifkmpa

https://protonvpn.com/cs/download-chrome-extension

Oficiální stránky v češtině zatím nebyly aktualizovány aby z nich bylo zřejmé, že služba je nyní bezplatná, ale je, vyzkoušeno.

Pro:

• neloguje uživatelovu aktivitu
• otevřený zdrojový kód aplikací
• bez omezení dat
• anonymita a lepší soukromí kvůli používání sdílené IP serveru a šifrování:
• nikdo kdo je v ČR (poskytovatel internetu, vláda, hacker) nemůže zjistit co na internetu děláte (šifrované spojení)

Proti:

• mírné zpomalení odezvy/rychlosti internetu
• bezplatný účet může využívat VPN servery pouze v několika zemích
• bezplatný účet nezahrnuje možnost blokování sledovacích prvků a vyřazení zvolených webů z VPN

I have been told, that when entering foreign country address, I may be asked to verify passport details, I am unsure how it is when i enter russian address. I guess that when entering invalid address, I may be unable to claim my domain in case my domain registar bankrupt. Thank you in advance.

https://www.hosting.co.uk/register-domain/su-extension/ says:

.SU registry asks that companies provide a copy of the registering company's Certificate of Registration or an excerpt from the Commercial Register. Individuals are requested to provide their ID card or passport number.

https://manage.resellerclub.com/kb/answer/1336#heading_5 says:

For Individual: Registrant's Name (preferably in Russian); Passport Information: This needs to include the Document number, Issued by, Issued Date of the Passport. Birth Date: This needs to be entered as a numeric value in DD.MM.YYYY format.

https://wiki.hexonet.net/wiki/RU says:

for natural persons: passport copy (personal details and issuance data)

Middle man style services:

https://xuid.ru/domains.php - "No Personal information required."

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.