-
m-relay
-
m-relay
-
m-relay
<basses:matrix.org> Stnby
-
m-relay
<siren:kernal.eu> woah it's not necro
-
m-relay
<stnby:kernal.eu> Nice, thanks for support
-
k4r4b3y
congrats digilol
-
m-relay
<siren:kernal.eu> we got censored, it's no longer listed
-
k4r4b3y
@siren:kernal.eu indeed -- how come? Why and who censored the digilol article?
-
m-relay
<siren:kernal.eu> ¯\_(ツ)_/¯ first time I see this happen
-
k4r4b3y
annoying af
-
k4r4b3y
hackernews are bit-bigots or something?
-
m-relay
<plowsof:matrix.org> the super secret leaked video was mentioned in the comments it seems.. RIP
-
k4r4b3y
BRUH
-
k4r4b3y
what was it called, "the banality of evil" ?
-
m-relay
-
m-relay
<basses:matrix.org> HN algorithm weird
-
m-relay
<basses:matrix.org> censored = flagged, and it isn't yet
-
k4r4b3y
@monerobull:matrix.org nice meme
-
m-relay
<basses:matrix.org> you can engage comments but with constructive discussion, not "bump" etc like 4chan
-
k4r4b3y
@basses:matrix.org the link to article got nuked from the frontpage of hacker news. It was on fucking top
-
m-relay
<siren:kernal.eu> i couldn't find it by clicking load more a few times either
-
m-relay
<siren:kernal.eu> sus
-
m-relay
<basses:matrix.org> from what I observed, when a post is updooted to quickly with a lower ratio to comments, it drops significantly.
-
m-relay
<basses:matrix.org> too*
-
k4r4b3y
"uhm.. sweaty -- have you /actually/ earned those updoots"
-
k4r4b3y
russian bots manipulating hackernews in favor of monero -- confirmed
-
m-relay
<stnby:kernal.eu> Most likely secret sauce of HN algorithm
-
m-relay
<stnby:kernal.eu> However it's still on the homepage as I can see.
-
k4r4b3y
now it's back yeah
-
dukenukem
30 comments, wow holes.
-
m-relay
<quickex:matrix.org> hey guys! Quickex arranges poker tournament with $XMR prizes, would be thankful for participation and support!
-
m-relay
-
slave_blocker
-
m-relay
<daybreak:nitro.chat> What's the current consensus on churning
-
m-relay
<daybreak:nitro.chat> - sweeping a wallet's utxos into one output
-
m-relay
<daybreak:nitro.chat> - sending utxos one by one into a separate wallet or the same wallet
-
m-relay
<daybreak:nitro.chat> - shenanigans involving multiple wallets/sending to yourself in general
-
m-relay
<daybreak:nitro.chat> For all of the above, are they 1) useless 2) detrimental to privacy or 3) somewhat beneficial?
-
m-relay
<ofrnxmr:monero.social> Consensus? On churning? There is none
-
m-relay
<ofrnxmr:monero.social> Main thing is
-
m-relay
<ofrnxmr:monero.social> 1. Dont spend tx that you receive from someone else without consolidating them locally
-
m-relay
<ofrnxmr:monero.social> 2. Dont spend change directly
-
m-relay
<ofrnxmr:monero.social> 3. Dont use clearnet nodes w/o using tor
-
m-relay
<ofrnxmr:monero.social> 1)so if you have 4 outputs, combine them all locally before spending then
-
m-relay
<ofrnxmr:monero.social> 2) if you have a bunch of change outputs, same thing, combine them locally before spending them
-
m-relay
<ofrnxmr:monero.social> 3) if you are using remote nodes, either use tor, or use onion and i2p nodes
-
m-relay
<4n0nu5er:matrix.org> could someone invite me to the monero mining room?
-
m-relay
<kowalabearhugs_:monero.social> The room is public, no?
matrix.to/#/#xmrmine:matrix.org
-
m-relay
<daybreak:nitro.chat> Thanks!
-
m-relay
<nononynous:monero.social> 1. Yes and no
-
m-relay
<ofrnxmr:monero.social> Yes and yes
-
m-relay
<ofrnxmr:monero.social> Matrix screwed up the formatting btw
-
m-relay
<ofrnxmr:monero.social> Feel free to explain your "no"
-
m-relay
<nononynous:monero.social> If you receive monero privately and anonymously, it's better to isolate the UTXO for spending it.
-
m-relay
<nononynous:monero.social> If you publicly received monero and they're probably marked, then you should consolidate and why not churning
-
m-relay
<nononynous:monero.social> And churning shouldnt be advised if the user dont follow rules to make a proper randomization of when was created the transaction or it creates a new pattern to deanonymize
-
m-relay
<ofrnxmr:monero.social> wdym "and why not churning"
-
m-relay
<ofrnxmr:monero.social> it not better to isolate the UTXO's for spending. See #
-
m-relay
<ofrnxmr:monero.social> 2
-
m-relay
<nononynous:monero.social> Just to add distance to where youre spending it not gives more protection than that
-
m-relay
<ofrnxmr:monero.social> Its better to create new outputs than to spend virgin ones
-
m-relay
<ofrnxmr:monero.social> And better to consolidate early to avoid knowledge of later consolidations (see #2)
-
m-relay
<nononynous:monero.social> If you isolated UTXOs you won't merge histories, consolidating is only leaking informations
-
m-relay
<ofrnxmr:monero.social> Finding a common ancestor of change outputs is nkr rocker science
-
m-relay
<ofrnxmr:monero.social> You will when later consolidate the change
-
m-relay
<nononynous:monero.social> You can label the output/transaction and freezing it
-
m-relay
<ofrnxmr:monero.social> And then never spend your change?
-
m-relay
<ofrnxmr:monero.social> Thats kinda silly
-
m-relay
<nononynous:monero.social> Spending it without consolidating it
-
m-relay
<nononynous:monero.social> Like for a VPN subscription of 5 bucka
-
m-relay
<ofrnxmr:monero.social> ^
-
m-relay
<nononynous:monero.social> Or donating the insignificant dust
-
m-relay
<ofrnxmr:monero.social> Then do what with your change from the $5?
-
m-relay
<ofrnxmr:monero.social> Again. Lol. Silly
-
m-relay
<nononynous:monero.social> Spending it for something worth it kek
-
m-relay
<ofrnxmr:monero.social> "monero is a charity. Donate your change to avoid fingerprinting"
-
m-relay
<ofrnxmr:monero.social> Or you can do as i said above
-
m-relay
<ofrnxmr:monero.social> And "burn" the trail on day 1
-
m-relay
<ofrnxmr:monero.social> chain analysis will see the consolidation, but wont be able to link it to any service
-
m-relay
<nononynous:monero.social> I think it only depend of what you really want to do with monero
-
m-relay
<ofrnxmr:monero.social> A churn or 2 afterwards and the output is as good as "lost in the mix"
-
m-relay
<ofrnxmr:monero.social> Same with change. You should avoid sending 1. coins that you just received 2. Spending multiple outputs at once when paying an external party
-
m-relay
<ofrnxmr:monero.social> To avoid 1, consolidate locally and spend single outputs
-
m-relay
<nononynous:monero.social> If you want to clean the house consolidate and churn at your risk but if you want to stay lowkey consolidate as less you can to me
-
m-relay
<ofrnxmr:monero.social> 2+ outputs > 1> 1 > spend
-
m-relay
<nononynous:monero.social> The thing is consolidating is revealing outputs so consolidate as less you can if youre not on the radar or something like that
-
m-relay
<ofrnxmr:monero.social> They can take a 1/16 guess about the real output in the consolidation, but after 1 churn they have to be confused about whether you consolidated or if it was a false positive. Whereas, us you accumulate a lot of small change outputs and considate the LATER, you can end up exposing your _past_ spends
-
m-relay
<ofrnxmr:monero.social> They can take a 1/16 guess about the real output in the consolidation, but after 1 churn they have to be confused about whether you consolidated or if it was a false positive. Whereas, if you accumulate a lot of small change outputs and considate them LATER, you can end up exposing your _past_ spends
-
m-relay
<ofrnxmr:monero.social> Even if you donate your change in single outputs to a source (like ccs) that may later consolidate them
-
m-relay
<ofrnxmr:monero.social> the goal is to avoid having to consolidate later. To manage your outputs so that they are always "clean" and always large enough to be spent alone