-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Railcore registry #5
Comments
I meant to add the link - https://github.com/PrusaMK2Users/3030_Haribo_Edition |
Let’s do it!
On Mon, Feb 25, 2019 at 6:12 AM -0400, "Dan White" <[email protected]> wrote:
I meant to add the link - https://github.com/PrusaMK2Users/3030_Haribo_Edition
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sure, though I think the idea of a "serial number" is a thing that isn't
really possible. Too many out there self-sourced and un-tracked. They'd
just be made up numbers and people would get bitchy.
…On Fri, Mar 1, 2019 at 2:23 PM Nate Walck ***@***.***> wrote:
Let’s do it!
On Mon, Feb 25, 2019 at 6:12 AM -0400, "Dan White" <
***@***.***> wrote:
I meant to add the link -
https://github.com/PrusaMK2Users/3030_Haribo_Edition
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHEIc_Uh6LdbVikPWRZi0_RHu-pQFQRMks5vSX4bgaJpZM4bOhwz>
.
|
I think we could make it work with the following:
1. Serials are ISO dates. 20180204 for instance. If we have more than one on the same day, we can append 01, 02, etc in the order they were reported.
2. Let’s just use the honor system. Having photographic proof with metadata intact would be a PITA to validate and enforce, not to mention it could be faked.
3. We could include whether it was self sourced or from a kit (R3D, etc).
4. We could also include any details that are non-stock. For instance Roy’s 300ZLT is technically a 305ZLT, my 300ZL is white, dual extrusion with Bondtech X2, etc
I don’t think this overthinks it while retaining simplicity. The major benefit here is if someone saw a unique hotend setup and wants to contact the maker.
On Fri, Mar 1, 2019 at 3:25 PM -0400, "kraegar" <[email protected]> wrote:
Sure, though I think the idea of a "serial number" is a thing that isn't
really possible. Too many out there self-sourced and un-tracked. They'd
just be made up numbers and people would get bitchy.
On Fri, Mar 1, 2019 at 2:23 PM Nate Walck ***@***.***> wrote:
Let’s do it!
On Mon, Feb 25, 2019 at 6:12 AM -0400, "Dan White" <
***@***.***> wrote:
I meant to add the link -
https://github.com/PrusaMK2Users/3030_Haribo_Edition
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHEIc_Uh6LdbVikPWRZi0_RHu-pQFQRMks5vSX4bgaJpZM4bOhwz>
.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I think that's fine. Don't include a straight # column, just sort it by
date.
…On Fri, Mar 1, 2019 at 3:09 PM Nate Walck ***@***.***> wrote:
I think we could make it work with the following:
1. Serials are ISO dates. 20180204 for instance. If we have more than one
on the same day, we can append 01, 02, etc in the order they were reported.
2. Let’s just use the honor system. Having photographic proof with
metadata intact would be a PITA to validate and enforce, not to mention it
could be faked.
3. We could include whether it was self sourced or from a kit (R3D, etc).
4. We could also include any details that are non-stock. For instance
Roy’s 300ZLT is technically a 305ZLT, my 300ZL is white, dual extrusion
with Bondtech X2, etc
I don’t think this overthinks it while retaining simplicity. The major
benefit here is if someone saw a unique hotend setup and wants to contact
the maker.
On Fri, Mar 1, 2019 at 3:25 PM -0400, "kraegar" ***@***.***>
wrote:
Sure, though I think the idea of a "serial number" is a thing that isn't
really possible. Too many out there self-sourced and un-tracked. They'd
just be made up numbers and people would get bitchy.
On Fri, Mar 1, 2019 at 2:23 PM Nate Walck ***@***.***>
wrote:
>
>
>
>
>
> Let’s do it!
>
>
>
>
>
>
>
>
>
>
> On Mon, Feb 25, 2019 at 6:12 AM -0400, "Dan White" <
> ***@***.***> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
> I meant to add the link -
> https://github.com/PrusaMK2Users/3030_Haribo_Edition
>
>
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
>
>
>
>
>
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <
#5 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AHEIc_Uh6LdbVikPWRZi0_RHu-pQFQRMks5vSX4bgaJpZM4bOhwz
>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHEIc48HBqIB689CWFJsOTuVAVwRRb6Pks5vSYkTgaJpZM4bOhwz>
.
|
Voron gets considerable visibility and goodwill from their fun serialization process. Builders post a video clip of their new printer printing and to Reddit and get a serial number. It's just for fun, but also so people can refer to specific machines for comments, which is useful. Something similar with just a picture to Discord or "Witness Me!" post is good enough, and then they get the ISO Date serial number or something similar. It builds a lot of confidence in the design to see how many are being built, and the diverse mods and users. It's hard for an outsider/visitor to tell today if there are 10 or 100 or 1000 RailCores out there in the wild as the user base is pretty spread out and modifications many. |
From a discussion in #railcore where I mentioned keeping track of who has what Railcore (or not) in the channel, it was pointed out by JohnOCFII that Prusa MK2 Users 3030 Haribo Edition keep a public registry on Github.
I'm thinking it might be nice to do something similar?
The text was updated successfully, but these errors were encountered: