00:01:23 <m-relay> <k​ayabanerve:monero.social> I did make a second PR per koe, tevador and filled out the FCMP++ Development CCS much more.
00:01:23 <m-relay> <k​ayabanerve:monero.social> cc <a data-mention-type="user" href="https://matrix.to/#/@plowsof:monero.social" contenteditable="false">@plowsof</a> for CCS-level thoughts, cc <a data-mention-type="user" href="https://matrix.to/#/@jeffro256:monero.social" contenteditable="false">@jeffro256</a> who I'd appreciate take a second look :)
08:25:11 <plowsof> Are we dropping the ball on Droplet? If abundance is good, surely the ecosystem will benefit from this work? https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/445 
08:37:16 <m-relay> <s​tillhuntinglongs:monero.social> All this drama makes it obvious that Monero just won't ever do well. When high-ranked people in the community are fighting over something as basic as wallet apps and trolls like ofrnxmr, how can we think that in time we'll have a general understanding about making major changes with hardforks? This community is pretty big, but if it ever becomes as big as Bitcoin, I think coming t<clipped m
08:37:17 <m-relay> <s​tillhuntinglongs:monero.social> o a conclusion for any hardfork is going to be impossible, threatening the decentralization of Monero. I also question the current decentralization of Monero itself as all consensus mechanisms like the GF are controlled by an individual or a small group of people. Will this problem be solved ever?
08:42:09 <m-relay> <s​tillhuntinglongs:monero.social> Maybe one day it'll get fixed with another thankful_for_today situation, but if stuff like this keeps happenin', I don't know if Monero will be taken seriously.
08:48:13 <m-relay> <r​brunner7:monero.social> plowsof: "Are we dropping the ball on Droplet?" Never mind abundance, IMHO some things and opinions that the proposal's author has stated rise doubts whether he is a good person to implement something as big as a Monero wallet basically alone, at least with their current knowledge.
10:19:22 <m-relay> <3​21bob321:monero.social> serious as a heart attack we are
11:25:35 <m-relay> <r​4v3r23:monero.social> tobtohts remarks were spot on here
11:27:01 <m-relay> <r​4v3r23:monero.social> rbrunner is echoing them
11:27:27 <m-relay> <r​4v3r23:monero.social> not every wallet needs a new/custom lib
11:27:50 <m-relay> <r​4v3r23:monero.social> and not every new lib needs a wallet
11:30:34 <m-relay> <r​4v3r23:monero.social> if author can really deliver on great UX like they propose, then why not
11:31:17 <m-relay> <r​4v3r23:monero.social> but if author can really deliver on great UX like they propose, thats a plus
12:52:13 <m-relay> <d​etherminal:monero.social> Not using wallet2 doesn't mean I am not a good developer, I had a bad DX with wallet2 and I don't also want other developers to have it
12:52:34 <m-relay> <d​etherminal:monero.social> > <@rbrunner7:monero.social> plowsof: "Are we dropping the ball on Droplet?" Never mind abundance, IMHO some things and opinions that the proposal's author has stated rise doubts whether he is a good person to implement something as big as a Monero wallet basically alone, at least with their current knowledge.
12:52:35 <m-relay> <d​etherminal:monero.social> Not using wallet2 doesn't mean I am not a good developer, I had a bad DX with wallet2 and I don't want other developers to have bad experience too.
12:53:49 <m-relay> <d​etherminal:monero.social> You can say anything, but compiling cpp for Android ans iOS is a headachd
12:53:53 <m-relay> <d​etherminal:monero.social> You can say anything, but compiling cpp for Android ans iOS is a headache
12:54:05 <m-relay> <d​etherminal:monero.social> You can say anything, but compiling cpp for Android and iOS is a headache
14:05:49 <m-relay> <r​4v3r23:monero.social> detherminaldo you have example of ui/ux work youve done
15:26:32 <m-relay> <w​olfy42_:matrix.org> Hi! I want to start mining, but at home I don't have enough resource to do(without loss). I'm not familiar with the rental services. Is there any CPU rental service what I can use with relative low budget and it's not a loss?
15:30:17 <m-relay> <e​disondotme:matrix.org> Renting CPU will *always* be a loss. If it wasn't, then AWS would be filled up with mining because it's zero risk, all reward.
15:30:18 <m-relay> <e​disondotme:matrix.org> The only way you could do this without a loss is if you expect the value of XMR to go up in the future. In which case you can eat the loss now, but recuperate it later.
15:44:06 <m-relay> <w​olfy42_:matrix.org> Just as I tough. Thanks for the info!
17:04:58 <m-relay> <a​ndrea_togni:matrix.org> https://jls.mises.org/article/116327-privacy-as-a-kantian-misesian-a-priori-condition-for-the-preservation-of-property-rights
17:04:58 <m-relay> <a​ndrea_togni:matrix.org> Hello guys, I'd like to share an article of mine just published in the Journal of Libertarian Studies. It deals with two topics: 1) In the first part, it discusses the Tornado Cash saga and the Privacy Pools proposal; 2) In the second part, it discusses what type of notion privacy is. The utilitarian (relativistic) approach and the thesis that privacy is a natural right are "disca<clipped message>
17:04:59 <m-relay> <a​ndrea_togni:matrix.org> rded" in favor of a Kantian and Misesian understanding of privacy.
17:05:00 <m-relay> <a​ndrea_togni:matrix.org> I will be presenting the article in Prague at MoneroKon. Any feedback (here or in June) would be highly appreciated!!
17:46:17 <m-relay> <r​ucknium:monero.social> A bunch of large consolidation txs are hitting the txpool again.
18:06:58 <m-relay> <s​gp_:monero.social> Rucknium: I threw this cude mempool visualizer together in a few hours. I'll keep playing with it if I have more time: https://moonstone-research.github.io/monero-mempool-visualizer/
18:07:08 <m-relay> <s​gp_:monero.social> Rucknium: I threw this crude mempool visualizer together in a few hours. I'll keep playing with it if I have more time: https://moonstone-research.github.io/monero-mempool-visualizer/
18:18:34 <m-relay> <s​gp_:monero.social> In the first chart, the size of each rectangle correlates to the gross size of the transaction. The more red the color of the square the higher the transaction fee per byte; the whiter the lower. Quite basic
18:41:42 <m-relay> <s​gp_:monero.social> Currently, there are about 6 full blocks with a fee above 80,000 piconero per byte, so you need to use a faster speed to reliably make it into the next block
19:02:39 <tobtoht_> normal gets you in the next block again
20:55:18 <m-relay> <r​ottenwheel:kernal.eu> Graphic designer behind http://monero.graphics, gnuteardrops, is seeking funding to keep maintaining the repository through 2025, consider sending some XMR their way!
20:55:19 <m-relay> <r​ottenwheel:kernal.eu> + info. at:
20:55:20 <m-relay> <r​ottenwheel:kernal.eu> https://monero.graphics/about#help/
21:19:27 <m-relay> <s​yntheticbird:monero.social> **Highlights**:
21:19:28 <m-relay> <s​yntheticbird:monero.social> > - boosting my (currently low) morale
21:20:28 <m-relay> <s​yntheticbird:monero.social> gnu deserve some xmr
23:16:21 <m-relay> <p​reland:matrix.org> I’m thinking of looking into a “sidechain” expansion of XMR; it would consist of there being multiple concurrent blockchain instances, each of which would work separately, but would be able to transfer from one instance to another in a perfect 1:1 instance using [insert technical jargon here]. Nodes belonging to each instance will continually poll other instances to determin<clipped message>
23:16:22 <m-relay> <p​reland:matrix.org> e their overall health, and take proper corrective behavior if anything incorrect occurs on another instance.
23:16:23 <m-relay> <p​reland:matrix.org> Assume that such a thing exists. Think of every possible way to deanonymize, inflate/deflate supply, take control of, or otherwise manipulate the network. Also, it would be helpful if we could determine the minimum amount of nodes, past/ongoing transactions, etc. required to ensure an XMR network is secure.
23:19:04 <m-relay> <p​reland:matrix.org> (Motivation: find a way to make Monero scalable et infinitum, while keeping privacy, ease of use, network security, and resource efficiency [whether financial, time, computational, or storage], at or below current network conditions)
23:39:13 <m-relay> <3​21bob321:monero.social> Ccs inbound ^