01:05:58 I feel like I’m losing my mind; what exactly is a “glue value” 😂 01:06:16 Is it just a random number wearing a funny hat? 01:15:31 https://matrix.monero.social/_matrix/media/v1/download/matrix.org/dvWfXtptlRIkzeODuiyryjRi 01:16:00 Which one is it? Or is it just ambiguously phrased? 01:16:28 (This is pertaining to ring signatures, and is everywhere in the literature.) 01:19:56 Unless someone tells me otherwise, a “glue” value is just a deterministicly random number with a length of b bits 01:33:58 preland: If you want to learn about ring sigs, chapter three of https://web.getmonero.org/library/Zero-to-Monero-2-0-0.pdf goes through a number of them. No 'glue' terminology. 03:44:55 Advertise on Reddit 03:44:56 Create 03:44:56 Create post 03:44:56 Go to Monero 03:44:56 r/Monero 03:44:56 • 03:44:58 1 day ago 03:45:00 Dotnetspec 03:45:02 Unable to register on repo.getmonero.org 03:45:04 Hi, 03:45:06 I'm trying to get myself registered on https://repo.getmonero.org so that I can submit a proposal for the CCS, but have a problem I explained to Gitlab support: 03:45:09 I'm trying to register for https://repo.getmonero.org/monero-project which requires an Enterprise Edition signup. 03:45:12 I've input the details and my current, valid, working email address and completed the captcha. 03:45:14 I'm taken to: 03:45:16 https://repo.getmonero.org/users/almost_there 03:45:20 and do not receive an email. Emails from other entities are being delivered to the same address (there is nothing wrong with the email, network etc.) 03:45:23 I retried twice with 'request new confirmation email. ', and tried in latest Firefox and Edge browsers, but it made no difference 03:45:26 How can I register for an enterprise edition account and access and make contributions in repo.getmonero.org? 03:45:29 Gitlab support told me: 03:45:31 "you're referring to an account registered on a self-managed instance of GitLab. If that is the case, please contact your local administrator for assistance as GitLab Support does not have access to self-managed instances of GitLab to solve this type of issue." 03:45:35 I haven't received any confirmation emails after 24 hours. 03:45:37 Please note that I already have a personal account with Gitlab I have been using for ~1year. The login for that doesn't work with the Enterprise Edition (unsurprisingly). 03:45:40 Does anyone know how I can contact the 'local admin' so that I can register and login to make a submission or if there is any other way around this? thanks ... 03:52:23 alanpoe: try a different email provider or look in your spam 03:52:35 i don't have issues receiving emails from gitlab 03:53:43 unless there were some changes and new accounts have to be manually approved to avoid spam? plowsof moneromooo 06:07:01 several home servers had manual sign up enabled after the spam, but so far they have not returned, its mostly servers who we can't email (back end admin is aware). alanpoe what is the username? 06:46:33 Google rejects emails. It needs some special DNS setup for email. 06:48:27 In this case, it looks like it wants the IP of the sending server to be in a PTR record. Not sure it's a good idea given it uses fucking cloudflare, which is meant to shield that IP. 08:09:40 <3​21bob321:monero.social> Spf and ptr for spam 14:24:49 .merges 14:24:50 -xmr-pr- 7852 8203 8396 8488 8920 9064 9149 9194 9198 9199 9200 9202 9204 9205 9211 9232 9245 9252 9254 9257 9259 9260 9267 9268 9270 9282 9291 9292 9305 9306 9307 9309 9310 9313 9316 9323 14:29:49 I see that https://github.com/monero-project/monero/pull/9311 "Enforce Tx unlock_time is Zero by Relay Rule [RELEASE]" is not yet scheduled. 14:30:11 Maybe somebody in addition to me could review, somebody of the many people who reviewed the "master" PR: https://github.com/monero-project/monero/pull/9151 14:30:26 So this can be finally be trusted to go into service 14:51:30 I'm just not sure if adding such a breaking change to a .1 release is a good idea 14:53:07 luigi1111: do you have time for merges next week? would be important 15:07:37 Yes 15:10:19 selsta: There are always several possible viewpoints. You could see this a a breaking chance not fit for a minor release like it's ahead 15:10:48 You could also see this as a security related patch where it's our duty to bring it into service as soon as possible 15:11:04 *change 15:11:43 How breaking it really is? Do we get many tx with unlock_time used? Probably zero 15:15:33 .merge+ 9311 9151 15:15:33 Added 15:28:37 Thanks, selsta!