08:34:24 Hello ! Hope you are all well. I was wondering if there were some news regarding the new website proposal ? 08:36:39 There's a meeting this Saturday, you should probably be present in case anyone has questions or comments about your proposal. 08:37:58 There's a meeting Saturday 05/25, you should probably be present in case anyone has questions or comments about your proposal. 08:38:19 https://github.com/monero-project/meta/issues/1008 09:02:48 Ok I will try to be present. I am travelling just before 09:19:02 You can also read the log of the last meeting. There has been questions regarding your proposal: https://github.com/monero-project/meta/issues/1002#issuecomment-2111160581 09:19:28 You can write out the response in comments in your pull request so that we have matter to discuss, in case you are not present 09:20:38 from what I remember, concerns about the lack of CMS integration in Astro, someone wanted to know if you were up for using a SSG like Hugo instead of Astro. 14:54:50 if Astro is going to introduce any inconvenience for contributors then another SSG should be picked 14:58:58 Only real inconvenience I heard is the CMS. markdown files can be added to folders and be rendered, simplifying the process of writing blog posts. Its not the same but still sufficient. Honestly I do not support the "NO JS" policy regarding the website write. If at the end it ship zero js to the client, and do not need server-rendering, it's exactly the same 16:23:49 SyntheticBird: Ha thank you, I didn't know! Will do that 16:30:53 Regarding translation, yes I am more convinced everyday that AI translation with proper LLMs like latest GPT 4 or LLama 3 can do the job very well. 16:35:30 Does anybody seriously ask that it should be possible to *author*, to *modify* the website without using any JavaScript? Maybe I misunderstand the issue, but for me personally it only ever was "No JavaScript when viewing the finished, rendered and deployed website". 16:38:24 I may have misunderstood but thats what has been said by someone, yes. 16:38:26 For now the English content is "hardcoded" into .astro files. But with translations content will be moved into json I guess 16:39:15 So if you can edit the content without changing the layout, you just edit the json 16:40:25 That's for the regular pages. For blog posts and maybe documentation (not started) it will be Markdown 16:41:29 Now Astro supports plenty of CMS https://docs.astro.build/fr/guides/cms/ 16:42:05 I don't think it is necessary but it is possible 16:42:34 Now Astro supports plenty of CMS https://docs.astro.build/en/guides/cms/ 16:43:18 And yes we could use X, but I choose Astro because this is the best :) 16:44:50 > Astro because this is the best :) 16:44:51 Truth has been told 💯 16:45:15 Might be a good idea to post these replies in the comments section below your proposal like someone else already said, so others can read. 16:45:34 Maybe with the link to the last community meeting logs, that way everyone can read what you are replying to. 16:45:49 https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/450 16:48:13 Yes I will post my comments there also 16:56:35 Regarding rates/hours adjustment, in my opinion the first milestone is on par with freelancing rates in Europe. I take into account the time already spent, the back and forth with the community, I think we should take this opportunity to really improve and update the content but it is maybe too optimistic, the fact that I still need a designer to help me with some remaining tasks 16:56:37 and I proposed to pay him out of this first milestome payment, etc. 16:56:39 Yes 10k will help me for a few months but not like I am ready for jetset life lol 16:56:46 Anyway, we can discuss 16:57:48 Regarding the second milestone, the amount of work is unclear to me, it could be much less than what I proposed. Totally ok to adjust that. 16:59:00 Regarding third milestone, it's coming from experience that the last 5% of the work takes a lot more. But again we can reduce that, maybe skip it totally, I don't really know for now 17:05:21 The third milestone is because I anticipate that once the website is ready to ship, lot of people will wake up last minute and ask to change this and that 17:05:29 But I may be wrong 17:06:30 Or once it is live and a broader audience is accessing it, requests will come 17:09:40 By the way, it is still unclear if we should include the documentation in this website. The first proposal assumes it is the case. 17:38:54 Alright, I responded I the CCS page https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/450#note_24566 17:57:37 I think that people not believing that AI cant translate a website are not following the space. I can use the chatgpt app to translate in real time, understanding the environment, audio, vision. We are close to AGI but it cant translate a website ? 17:57:46 Seriously 18:17:54 I'm myself sceptical about AGI anytime soon. But yes, LLM are absolutely terrifying. 18:18:23 Tey and translate the entire existing site in all languages and get it deployed 18:18:28 Try* 18:20:20 It would not work 18:20:43 as LLM can't deal with specialized context without training. So it can only serve as a basis for now. 18:20:50 Review the pull request 18:20:57 Lol 18:21:08 yeah don't worry I did 18:21:25 I agree with janaka on the fact that it can serve as a basis. to accelerate translation 18:21:48 people would just have to correct the sentence 18:23:10 Contributions to existing site would go > 0 if a PR containing tens of thousands of translations auto generated, although reviewing would be an issue 18:24:02 Place holders still have to be reviewed 18:26:59 Ctrl+f machine translations (under automated teanslations) 18:27:04 https://weblate.org/en/features/ 18:27:33 We dont have CI enabled or a stable weblate .......... 18:28:09 So everyone at the moment is just Ctrl+f text ? 18:28:30 I'm saying that but it looks like no translation exist 18:28:41 I mean. the FCMP blog is in english 18:28:45 whatever the locale 18:29:15 https://docs.weblate.org/en/latest/admin/machine.html 18:30:26 We have a feature rich solution that is barely online with none of the bells and whistles because there is no employed person / trusted to eun it 18:31:14 i don't understand. You mean, no one is daring to setup CI and weblate? or Do we have one but no one is making use of it ? 18:32:52 We have a volunteer to set all that up 18:33:13 oh thats good news 18:33:46 Hence the issues with weblate stability etc. CI integration should have been enabled as soon as.... Netrik made the issue 18:34:03 Anyway, machine translations are built in to weblate 18:36:21 Not trying to say you're wrong. But I feel like there is a significant difference between LLM translation and Translation-specialized models. LLM are better at understanding the context than Translation APIs. Meaning, when translating the FCMP blog, an LLM will continue to use Full-Chain-Membership-Proof (FCMP) instead of translating it to whatever language automatically. 18:37:51 "The support for several machine translation and translation memory services is built-in." All bad? 18:38:23 nah 18:38:26 you're right 18:38:31 there must be useful model in it 19:48:46 By the way my day to day job is in a AI company 19:49:27 And I translate a lot everyday to learn a new language in a new country 19:49:54 I am not just saying things like that without backing 19:51:18 Once I have a json with all the english strings I can easily translate to whatever. I can give additional context if needed but I dont think it is even necessary 19:53:50 I am talking about the regular pages, not super technical blog posts. 19:54:07 But even that we could try 21:21:22 <3​21bob321:monero.social> Skynet is here!