04:05:27 <sha256> hello
04:08:09 <gingeropolous> hi sha256 
04:11:57 <sha256> how can I develop something in monero
04:12:36 <sha256> maybe I not exactly asking the right question
04:14:17 <sha256> I want to contribute to codebase and know more about the crypto
04:14:31 <Rucknium[m]> sha256: Great. If you can say a few things about your skillset, we may be able to connect you with a project or task.
04:45:03 <sha256> I program in c/cpp/python and know Data structures & algo's typical university knowledge you can expect from me
10:44:54 <aberdeenik[m]> A question to developers and decision makers : can we also hide timestamps in monero such that we can even anonymise the transaction dates and time?
10:45:25 <aberdeenik[m]> Is this something that will break anything if implemented?
10:58:18 <aberdeenik[m]> This is very important when states  try to regulate XMR ,hiding  the timestamps  will make it resistant to regulations too eg :  can't compute tax liability as we can't determine when the xmr was recieved. There are many more such advantages and will make it truly anonymous.
11:00:36 <monerobull[m]> Could you keep it to one chat? This is not relevant to this channel.
13:00:08 <aberdeenik[m]> <aberdeenik[m]> "This is very important when..." <- Ok interested devs who want to know more about this idea can head to monero research lab group for discussions.
15:57:29 <waterdev[m]> Hi, I'm relatively new to monero but not so much to programming. I am currently looking to contribute. Anything I could do which doesn't require too much experience about the monero codebase itself?
16:06:20 <UkoeHB> waterdev[m]: yes, someone needs to update the readme for `tests/` to have clear, current, comprehensive instructions
16:09:31 <Rucknium[m]> Bridge fail. UkoeHB says:
16:09:50 <Rucknium[m]> waterdev:  : yes, someone needs to update the readme for `tests/` to have clear, current, comprehensive instructions
16:22:48 <waterdev[m]> @Rucknium you mean write the Todo fields as example?
16:24:47 <koe000[m]> waterdev: 1. understand how to run all the different tests, and all the different ways to run each test (ctest vs executable; input flags, etc.); 2. explain it in the README
16:26:58 <UkoeHB> I can give you a headstart with my notes if you are up to the task.
16:27:28 <koe000[m]> I can give you a headstart with my notes if you are up to the task.
16:28:38 <waterdev[m]> yes why no
16:28:39 <waterdev[m]> *not
22:07:00 <monerobull[m]> <ErCiccione> "There is clearly an abyss..." <- Before anyone with concerns about anything gets pushed away from the project again, message me and i will act as a proxy for you. 
22:07:00 <monerobull[m]> I can't stand watching talented people dropping out due to the hate they face for whatever reason. You guys are contributing the most to this project and should never be attacked for voicing any opinions regarding the state of the community or the project itself. Especially not by people who dont bring anything to the project themselves.
22:10:28 <monerobull[m]> By now we've seen it enough times that personaly voicing any concern about anything just paints a target on your back for the trolls to take shots at
22:15:44 <selsta> luigi1111: merges tonight?¿
22:15:59 <luigi1111w> .merges
22:15:59 -xmr-pr- 7997 8023 8031 8032 8037 8038 8039 8048 8049
22:16:00 <luigi1111w> sure
22:16:35 <selsta> gui too pls
22:17:02 <selsta> and some gui PRs aren't approved but they are simple enough that you can take a look
23:30:02 <selsta> .merge+ 7169
23:30:02 <xmr-pr> Added