I currently own 4clojure.org which is still linked to on many Clojure-specific sites. If anyone is interested in buying it, I'd be happy to chat.
Peter Strömberg schrieb am Samstag, 17. Juli 2021 um 21:22:16 UTC+2: > Thanks, thanks, thanks, for creating and caring about 4clojure for this > long, Alan! I can't tell how instrumental it has been on my Clojure > journey. Not only for learning the language, also for keeping it fun there > in the beginning when I doubted I could learn enough of it to get > productive. I'm not sure I would have been a Clojurian today if it wasn't > for 4clojure. > > Best regards, > /Peter > > Den sön 11 juli 2021 kl 23:38 skrev Alan Malloy <mallo...@gmail.com>: > >> I've also exported the problem data: >> https://drive.google.com/file/d/1hHrygxAs5Do8FpHC9kphYnmyTwZvISnb/view?usp=sharing >> . >> >> On Sunday, July 11, 2021 at 2:22:33 PM UTC-7 Alan Malloy wrote: >> >>> I'm happy to see this project, and I think exporting some data is a >>> reasonable compromise. Rather than re-learn how to do any fancy mongodb >>> stuff to make it into "pretty" json, I've just done a raw JSON export of >>> the solutions collection, which is world-readable at >>> https://drive.google.com/file/d/1UQHznThT_eVTBjmLGz3yME8L3teGygUs/view?usp=sharing. >>> >>> I'm contemplating doing a partial export of the users collection too: I >>> could connect usernames to IDs without including the email addresses or >>> passwords, which would let you rebuild most of the user information. But >>> I'm not totally sure this is a good idea: some people may not want their >>> usernames shared, or associated with their solutions. Does anyone in this >>> thread have an opinion? >>> >>> On Tuesday, July 6, 2021 at 9:58:29 AM UTC-7 oxa...@gmail.com wrote: >>> >>>> Thank you Alan for all your contributions :) >>>> >>>> Hosting things and maintaing them is really hard. We, the LambdaIsland >>>> team, are already maintaining clojurians-log and clojureverse and it's >>>> definitely not easy! >>>> >>>> With a wonderful idea from @borkdude and his `sci` library, I built >>>> "4ever-clojure": a completely static version of 4clojure which runs using >>>> cljs + sci. It interprets the code in the browser itself. >>>> >>>> It's live at: 4clojure.oxal.org (Source code at: >>>> https://github.com/oxalorg/4ever-clojure I'm planning to move it >>>> under the clojureverse github org) >>>> >>>> I have 2 asks from you if it is feasible: >>>> 1. An export of all solutions (only solutions, no user data needed) - >>>> the community is already coming up with some amazing ideas of hooking up >>>> user solutions to automatically commit to a Github repo >>>> 2. Possibility of transfering *4clojure.com <http://4clojure.com> *-or- >>>> *4clojure.org <http://4clojure.org> *over to us so that we can host >>>> 4ever-clojure there (instead of on a separate domain) >>>> >>>> Thanks! >>>> - Mitesh >>>> >>>> On Tuesday, July 6, 2021 at 5:56:10 PM UTC+5:30 Srihari Sriraman wrote: >>>> >>>>> Hey Alan, we really like 4clojure. We've suggested using it for >>>>> training most people at nilenso and we're very thankful to you and all >>>>> the >>>>> contributors for that! >>>>> We (nilenso) would be up for picking up the hosting costs, and also >>>>> some other operations or development work if needed. >>>>> >>>>> It would be even better if we could work together and turn this into a >>>>> community owned project (ex: clojurists together >>>>> <http://clojuriststogether.org>). That might also assuage your >>>>> concerns about data ownership. >>>>> >>>>> The questions, and solutions that the community has put together on >>>>> 4clojure over the last decade are very valuable as a learning tool. >>>>> Perhaps >>>>> we can find a way to keep them around without attributing them to a user? >>>>> One idea might be to deactivate all existing accounts, and remove the >>>>> user >>>>> data (email, passwords, other PII) etc while keeping the questions and >>>>> solutions from those users. >>>>> >>>>> We would be sad to see 4clojure go away, hope we can find a way for it >>>>> to live on. >>>>> >>>>> Cheers, >>>>> Srihari >>>>> >>>>> On Tuesday, July 6, 2021 at 1:12:44 PM UTC+5:30 Robert P. Levy wrote: >>>>> >>>>>> Hi Alan, >>>>>> >>>>>> Just as a thought. If it's minimal work on your end (eg. if the >>>>>> folks from Roam research who chimed in above pick it up) why not clear >>>>>> the >>>>>> password hashes and let the new maintainer handle the communication that >>>>>> passwords need to be reset? >>>>>> >>>>>> Rob >>>>>> >>>>>> On Sun, Jul 4, 2021 at 1:26 PM Alan Malloy <mallo...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> TL;DR: Turning off 4clojure.com by the end of July 2021 >>>>>>> >>>>>>> Hello, 4clojure problem solvers. You've probably noticed SSL errors >>>>>>> on 4clojure.com over the last week. The old decrepit system >>>>>>> 4clojure runs on has finally gotten out of date enough that I can't >>>>>>> even >>>>>>> figure out how to get it recent enough that SSL certs will auto-renew >>>>>>> anymore. >>>>>>> >>>>>>> In principle I could start from scratch on a new server and move >>>>>>> 4clojure over, but I won't. 4clojure has been piggybacking along on a >>>>>>> server that I use for personal reasons, and over the years I have less >>>>>>> and >>>>>>> less reason to keep paying for that server - it's now pretty much just >>>>>>> 4clojure costing me an embarrassing amount of money every month because >>>>>>> I >>>>>>> haven't wanted to disappoint the community by shutting it down. This >>>>>>> SSL >>>>>>> thing is just what made me finally pull the trigger. >>>>>>> >>>>>>> I don't have a specific EOL date in mind, but sometime near the end >>>>>>> of the month, since that's the billing cycle. Until that time, 4clojure >>>>>>> still works, as long as you don't mind clicking through the security >>>>>>> warnings - it really is still me hosting the site, and since the >>>>>>> connection >>>>>>> is still HTTPS (albeit with an invalid cert) I think that means your >>>>>>> data >>>>>>> is still safe. If you have solutions to problems you're proud of, >>>>>>> you've >>>>>>> still got some time to print them out and put them up on your >>>>>>> refrigerator. >>>>>>> >>>>>>> I'm not seeking new maintainers. I'd feel uncomfortable handing over >>>>>>> a database with so many email addresses and password hashes in it to >>>>>>> anyone. The service has had a good run - just over a decade since the >>>>>>> first >>>>>>> release >>>>>>> <https://github.com/4clojure/4clojure/commit/ff457d0b3b5f5e5a74316a1747809c25b84b3b5e>. >>>>>>> >>>>>>> I hope you enjoyed it during that time. >>>>>>> >>>>>>> -- >>>>>>> >>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "Clojure" group. >>>>>>> To post to this group, send email to clo...@googlegroups.com >>>>>>> Note that posts from new members are moderated - please be patient >>>>>>> with your first post. >>>>>>> To unsubscribe from this group, send email to >>>>>>> clojure+u...@googlegroups.com >>>>>>> For more options, visit this group at >>>>>>> http://groups.google.com/group/clojure?hl=en >>>>>>> --- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "Clojure" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to clojure+u...@googlegroups.com. >>>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/clojure/385cdef8-fa40-47ba-b5b1-0b3a7cc34935n%40googlegroups.com >>>>>>> >>>>>>> <https://groups.google.com/d/msgid/clojure/385cdef8-fa40-47ba-b5b1-0b3a7cc34935n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>> . >>>>>>> >>>>>> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clo...@googlegroups.com >> Note that posts from new members are moderated - please be patient with >> your first post. >> To unsubscribe from this group, send email to >> clojure+u...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/clojure?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Clojure" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to clojure+u...@googlegroups.com. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/clojure/4d635947-7097-4310-a6dd-c53d9d45b72fn%40googlegroups.com >> >> <https://groups.google.com/d/msgid/clojure/4d635947-7097-4310-a6dd-c53d9d45b72fn%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/clojure/6ad1f3ec-3a4f-42e4-8404-047304a2f756n%40googlegroups.com.
