User talk:Sebastien Bailard
Hi Sebastien, I noticed the Website_Terms_And_Conditions page has no relevant content. I humbly suggest something like Wikipedia's Etiquette page. It may be permissible to modify and re-use it under the Creative Commons Attribution-ShareAlike 3.0 Unported License—Weasel 23:27, 26 November 2011 (UTC). My apologies, it may be a little more complicated than that, there is version 1.3 of the FDL. Weasel 23:46, 26 November 2011 (UTC)
Hi Sebastien, thanks for hooking up the extra links for Repic. I was holding off on saying anything on RepRap-dev until I at least had the Pololus installed and the steppers doing something, that happened tonight so I'll mail something to the group tomorrow. Cheers! (PS: What's the protocol for editing a User Talk page, do you put your msg at the top of the page like I've done here?) Myndale 12:39, 27 November 2010 (UTC)
Hi Sebastian, Can you move the Materials page to Category:Materials? I tried the move page, but it says "can't move into namespace Category." There are subpages and history, so i didn't just want to cut and paste unless totally necessary. --Buback 22:53, 25 October 2010 (UTC)
I know we touched on the topic of User:Mr. Bunny previously and even earlier discussed a better method then cut + pasting the example page for creating development pages (see reprap dev mailing list: RepRap Developments: Less vs. More). Unfortunately there are more of these each day and although I have let them go by in the past, slowly polluting the wiki with example content, making actual content on these pages nearly impossible to find in a sea of filler material however I have now become annoyed. I will now be taking an active stance on the issue and adding:
to the top of these pages. It is not a nice notice but it adequately reflects the fact that these wiki pages contain multiple screen-fulls of information which is not relevant to their topic. Please stop doing this, I did not want to have to take this course of action but this behaviour has not gone away after our discussion as I had hoped it would. I certainly did not want a sysop war and will voluntarily resign from wiki editing if necessary to prevent it. We can meet on IRC to discuss this if it would help. --TheOtherRob 04:01, 22 February 2010 (UTC)
Dear Sebastien Bailard, I am mystified by the process page. It sounds like I caught the tail end of a telephone conversation, and I'm still only hearing half of the conversation. I'm guessing someone in Singapore wanted to know what process to use to decide which RepStrap design to use, and how to get started building it? I'm reluctant to touch that page, because maybe it's talking about some other process?
The process page reminds me of bootstrap jumpstarting programs -- software that, when you feed it information about what tools and raw materials you already have available, it spits out an overview of the optimal path towards high technology civilization. Each step names a tool that is needed later down the path, the typical time to make that tool, and lists the tools needed to make that tool -- tools that you hopefully already have by the time you got to that step. Vinge mentioned these programs in 1992. I hear that "technological recursion" is somehow related to this. I hear that "T notation" is good for describing this sort of thing. --DavidCary 15:06, 28 April 2010 (UTC)
Process is one of the stub/working notes wiki pages I tacked up after I got a little frustrated trying to explain to an engineering student that he should "just build a repstrap using a tablesaw". ... Extremely frustrated.
I've cleaned up the first part of it, and moved it to What Tooling Do You Have.
T notation, aka "Tombstone Diagrams", looks interesting, but I have to be careful not to get too abstract or analytical. Maybe once my extruder works.
Want to do up an essay? --Sebastien Bailard 07:14, 29 April 2010 (UTC)
Yes, someday it would be pretty cool to do up an essay on how some highly abstract ideas (bootstrapping and T notation, aka Tombstone diagrams) not only describe how to convert files in some easy-for-humans-to-write "computer language" and convert them to executable programs, but they can be, in principle, generalized to describe the process of converting files in relatively easy-for-humans-to-use "CSG modeling language" and step-by-step (through various levels of abstraction) converting them to physical objects. How does SKDB fit into all this?
I hope that by explicitly writing down what little I know on the wiki, and inviting others to fill in the gaps, it will become clear what pieces of the "map" are missing. Perhaps now that we have a partial "map" that shows *a* path from point A (a CSG drawing) to point B (a physical part), and after this essay helps us understand some of the "mapmaking tools" available to us, it will help us be a little more efficient than blind exploration in (a) finding the other paths from A to B, some of them inevitably worse in one way or another but perhaps one of them better in every way, and (b) clearly documenting the paths that have been explored and making it easier for people get from A to B without getting "lost".
Alas, the analogy between a Pascal compiler and a RepRap breaks down if you push it too far, and the analogy between a geographical map and a bunch of assembly instructions also breaks down if I push it too far. --DavidCary 20:12, 6 April 2011 (UTC)
I would like to be able to upload the design files for some of my Mini Mendel work, but the Wiki will not allow me to upload .heeks files. I would prefer to be able to upload uncompressed files, just because they are easier to share, and I have not access to compression on 1 of the computers I work on.
Should I compress or wait for the wiki to allow for .heeks files?
- For your computer that does not have not access to compression, I assume it can access the web (otherwise, do your uncompressing using the computer you use to get the file off the web). You can zip and unzip (and work with a few other compression formats) online:
You also might ant to consider contacting the author of the CAD software that puts out .heeks files and see if they might be willing to adding the option to export data in a format that isn't quite so rare.
Guy Macon 16:18, 4 October 2010 (UTC)
keeping wiki online
Dear Sebastien Bailard,
Alas, wiki.bildr.net seems to be offline today. Is there anything I can do to get it back online?
Is there anything I can do now to improve the chances of the latest text and images at RepRap.org coming back online if something annoying were to happen? I wish I had time to set up a distributed, fault-tolerant wiki today ... --DavidCary 02:33, 17 December 2010 (UTC)
main page tweaks
Dear Sebastien Bailard,
Following the procedure at Talk:Main Page, I made a few tweaks to Main Page/Sandbox that may or may not be actual improvements, and now I'm asking you to review those changes and update the actual Main Page with whichever changes (-: if any :-) you think are improvements. Thank you for keeping this running. --DavidCary 22:05, 11 February 2011 (UTC)
Please look at these pages for anti-spam tools:
- Automatically applies restrictions to Tor exit nodes.:
- The SpamBlacklist extension prevents edits that contain URLs whose domains match regular expression patterns defined in specified files or wiki pages:
--Glenn 11:48, 24 November 2011 (UTC)
Today I tried to edit Builders/McMaster-Carr Part Numbers to link to other RepRap wiki pages that have further details: PonokoRepRap, Bearing, NEMA Motor, etc. Alas, not only is the page itself "locked to prevent editing", even its discussion page is locked. Could you unlock it, or at least unlock its discussion page? --DavidCary 14:41, 5 August 2012 (UTC)