--> MechGroupBuys <-- (https://mechgroupbuys.com/) | |
--> KeycapLendar <-- (https://keycaplendar.firebaseapp.com/) | by eskimojo |
--> KeyCapSets <-- (https://keycapsets.com/) | by noudadrichem and Quadeppo/Ryan |
--> GroupBuy Nation <-- (https://www.groupbuynation.com/) | by ClickClackIO (also a vendor) |
(no updates after 2020) |
There are GB that are not taking orders anymore; because, they are in the fulfilling phase already. These links are not too useful for those looking for opportunities to get new things, that make most of the visitors to this thread; therefore, it would be good to remove them from the list, or place them into a category that informs that the GBs are not taking orders anymore. Having them along with the GB that are actively taking orders reduce the usefulness of this thread; people interested have to navigate to the reference just to find that the GB orders have been closed.
I don't think it's an issue. It's not a long list, and new stuff is shown by the tag. Maybe more tags for 'taking orders' or 'invoicing' or 'shipping'? I don't think it's an issue for them to still be in the list.
Exactly: is not an issue; but, it could be an useful future to have the GBs classified, or with the tag added, that sounds great as well.
Thanks for pointing that out. :thumb: I've pruned the list of GBs that aren't taking orders. Not sure if we'll add tags for invoicing and shipping since we want to keep this just for the GBs that are taking orders. Should we add the ordering end dates though?
This thread is useless. Delete it. I've missed two group buys by wasting my time checking this.
Updated with all non-vendor & vendor buys + pictures :)
I have my own spreadsheet I'm going to be keeping updated with all buys ran through GH (that have been active since today onwards). I'll keep posting new ones here too? ;D
Updated with all non-vendor & vendor buys + pictures :)
I have my own spreadsheet I'm going to be keeping updated with all buys ran through GH (that have been active since today onwards). I'll keep posting new ones here too? ;D
Wow, thanks! :thumb:
If you're keeping a spreadsheet on your own anyway, maybe I could add a link to it in the OP assuming it's Google Sheets? That way all your updates will be visible right away.
[snip]
Not going to go through every page and collect info, so it'll just be any that get bumped ;D
P.S. The Lets Split case is repeated in the OP.
Sorry for the lack of consistency :'(
Took a break late November and then never got back into it. I have ~100 to catch up on tomorrow and will update it then :p
What happened to the spreadsheet? I check it every other month and now it's gone.
What happened to the spreadsheet? I check it every other month and now it's gone.
I couldn't update it consistently, and people would get upset it wasn't up to date, so I stopped completely.
TheVan Keyboards is doing a dark-mode Light Cycle with Blue and Red:
https://thevankeyboards.com/collections/catalog/products/light-cycle
The front page has a really nice teaser video. Open till end of November GMK 125 Keys
TheVan Keyboards is doing a dark-mode Light Cycle with Blue and Red:
https://thevankeyboards.com/collections/catalog/products/light-cycle
The front page has a really nice teaser video. Open till end of November GMK 125 Keys
Why not using a standard formating for GB and make a hook to parse all the posts in this section? It would be usefull for everyone. I can do a POC for this if needed.
Why not using a standard formating for GB and make a hook to parse all the posts in this section? It would be usefull for everyone. I can do a POC for this if needed.
Issue would be updating the status. Not sure how often folks are updating their post titles to say 'open' 'closed', etc.
Why not using a standard formating for GB and make a hook to parse all the posts in this section? It would be usefull for everyone. I can do a POC for this if needed.
Issue would be updating the status. Not sure how often folks are updating their post titles to say 'open' 'closed', etc.
Sure but by making this we may have to force a format for posts to be properly parsed.
Here is a proposal we've working on with some folks.
https://github.com/zekth/Keebs-GB
Your thoughts ?
Here is a proposal we've working on with some folks.
https://github.com/zekth/Keebs-GB
Your thoughts ?
It might just be easier to make a Reddit dedicated to group buys and interest checks and just use their flair system for easy filtering, even if the only purpose of a post there is to link to a group buy page I think it would be significantly easier for people to navigate. This would also be way easier for gb hosts to manage than a forced format
Here is a proposal we've working on with some folks.I can’t contribute anything except that I would like this... would be nice to have an active directory where I can easily see all available group buys
https://github.com/zekth/Keebs-GB
Your thoughts ?
Here is a proposal we've working on with some folks.
https://github.com/zekth/Keebs-GB
Your thoughts ?
[
{
"name": "My Group By",
"author": "somename",
"start": "20190506", // or actual ts but this might be easier
"end": "20190606",
"link": "https://www.geekhack.com/index.php?main-link-optional",
"form": "https://google.form/optional",
"links": {
"geekhack": "https://www.geekhack.com/index.php?main-link-or-other",
"reddit": "https://www.reddit.com/also-a-link"
},
"contact": {
"discord": "https://discord.gg/123",
"reddit": "redditusername",
"geekhack": "geekhackusername",
"email": "support@email.com"
}
}
]
any time format is going to be preferential unless you just go with ISO UTC standard, i. e. https://en.m.wikipedia.org/wiki/ISO_8601Here is a proposal we've working on with some folks.
https://github.com/zekth/Keebs-GB
Your thoughts ?
dd.mm.yyyy
or
yyyymmdd
mm/dd/yyyy would be only US...
if this would be a serious format why don't you just have any GB added to that repo via json?
pull request on groupbuys.json and have a historical snapshot of all group buys that can be used in any sort of system:Code: [Select][
{
"name": "My Group By",
"author": "homerowco",
"start": "20190506", // or actual ts but this might be easier
"end": "20190606",
"link": "https://www.geekhack.com/index.php?main-link-optional",
"form": "https://google.form/optional",
"links": {
"geekhack": "https://www.geekhack.com/index.php?main-link-or-other",
"reddit": "https://www.reddit.com/also-a-link"
},
"contact": {
"discord": "https://discord.gg/123",
"reddit": "homerowco",
"geekhack": "homerowco",
"email": "support@homerow.co"
}
}
]
just add another object to the array and do a pull request. done. free database of all current and past group buys ;)
I agree with you. About the format i'm french and i've adopted the US format because most of the format and ressources on keebs community are US. But yes using ISO is good too.
Using PR on a github repo is a problem because not all of us are developers or even git afficionados that's why i haven't purpose this. It would be definitely easier! About your model homerowco i agree with it, but we have to make a tool to generate this unless people wont use it.
mmmm right. About what homerowco purposed i'm a bit concerned with the data format. For the rest it's LGTM for me.Why concerned? It's just data. And just store it as JSON. The part about the pull request is just to add a piece of data, right? Not getting where that's any difference? Just arriving at a standard accepted format, which is just details.
Storing it as a JSON file in GitHub and give people the snippet to parse it as JSON using curl or whatever is a good start so. Maybe i can write a cli to write this file easily for the beginning.
mmmm right. About what homerowco purposed i'm a bit concerned with the data format. For the rest it's LGTM for me.Why concerned? It's just data. And just store it as JSON. The part about the pull request is just to add a piece of data, right? Not getting where that's any difference? Just arriving at a standard accepted format, which is just details.
Storing it as a JSON file in GitHub and give people the snippet to parse it as JSON using curl or whatever is a good start so. Maybe i can write a cli to write this file easily for the beginning.
I agree with you. About the format i'm french and i've adopted the US format because most of the format and ressources on keebs community are US. But yes using ISO is good too.
Using PR on a github repo is a problem because not all of us are developers or even git afficionados that's why i haven't purpose this. It would be definitely easier! About your model homerowco i agree with it, but we have to make a tool to generate this unless people wont use it.
mmmm right. About what homerowco purposed i'm a bit concerned with the data format. For the rest it's LGTM for me.Why concerned? It's just data. And just store it as JSON. The part about the pull request is just to add a piece of data, right? Not getting where that's any difference? Just arriving at a standard accepted format, which is just details.
Storing it as a JSON file in GitHub and give people the snippet to parse it as JSON using curl or whatever is a good start so. Maybe i can write a cli to write this file easily for the beginning.
@zekth I had an idea - perhaps add a JavaScript file that reads the latest JSON data and converts it to RSS format. Then a build script could generate the rss file. Or maybe use a git wiki page to render the json
Update the git and added CI for further PR. See : https://github.com/zekth/Keebs-GB
Update the git and added CI for further PR. See : https://github.com/zekth/Keebs-GB
dont use complex date formats - have people use this: https://www.unixtimestamp.com
and done ;)
Update the git and added CI for further PR. See : https://github.com/zekth/Keebs-GB
dont use complex date formats - have people use this: https://www.unixtimestamp.com
and done ;)
Well, done until January 19, 2038.
Update the git and added CI for further PR. See : https://github.com/zekth/Keebs-GB
dont use complex date formats - have people use this: https://www.unixtimestamp.com
and done ;)
Well, done until January 19, 2038.
That was my thought too, but I kept it to myself :)
Update the git and added CI for further PR. See : https://github.com/zekth/Keebs-GB
dont use complex date formats - have people use this: https://www.unixtimestamp.com
and done ;)
Well, done until January 19, 2038.
That was my thought too, but I kept it to myself :)
such enthusiasm very optimistic wow thanks
Great idea. The git model maps to this really well.
As for tooling to consume the data, my 2 cents would be to keep that in a separate repo. Then it serves the purpose of a reference implementation separate from the data and management thereof. Anyone who wants to display the data on their own site can refer to the same tooling.
Sent from my SM-G965U using Tapatalk
Great idea. The git model maps to this really well.
As for tooling to consume the data, my 2 cents would be to keep that in a separate repo. Then it serves the purpose of a reference implementation separate from the data and management thereof. Anyone who wants to display the data on their own site can refer to the same tooling.
Sent from my SM-G965U using Tapatalk
Yes tooling will totally be in a separate repo it make sense.
@chuckdee
So you got my feedback of yours.
I agree that with unix TS we would not have to handle the timezone problem. If a UI to generate the json file will be available i think we can switch to unix TS. Some people asked me in PM about it, that's why i provided the Usage section
I agree that with unix TS we would not have to handle the timezone problem. If a UI to generate the json file will be available i think we can switch to unix TS. Some people asked me in PM about it, that's why i provided the Usage section
Instead of a Unix timestamp that looks and feels like magic string (requiring a ui), why not just go with an ISO-8601 datetime format? Any merge could be blocked on the format not properly translating.
Sent from my SM-G965U using Tapatalk
I agree that with unix TS we would not have to handle the timezone problem. If a UI to generate the json file will be available i think we can switch to unix TS. Some people asked me in PM about it, that's why i provided the Usage section
Instead of a Unix timestamp that looks and feels like magic string (requiring a ui), why not just go with an ISO-8601 datetime format? Any merge could be blocked on the format not properly translating.
Sent from my SM-G965U using Tapatalk
I second the ISO-8601 format. I vote for this version:
20190519T013758Z
yyyymmddThhmmssZ (Z = Zulu = UTC)
The problem with unix TS is it can't be validated by a Json Schema. Adding a piece of custom code is not really in the mind of the project IMO. That's why the datetime ISO string has stayed in the model.
https://json-schema.org/understanding-json-schema/reference/string.html#format
I agree that with unix TS we would not have to handle the timezone problem. If a UI to generate the json file will be available i think we can switch to unix TS. Some people asked me in PM about it, that's why i provided the Usage section
> Well, done until January 19, 2038.
I think we'd be fine. I swear, if this is an issue in 2038 I will write a script to change all timestamps in the json, or I'll tell my coding AI assistant to do it :)
> Well, done until January 19, 2038.
I think we'd be fine. I swear, if this is an issue in 2038 I will write a script to change all timestamps in the json, or I'll tell my coding AI assistant to do it :)
IBM patented the buckling spring 42 years ago. 2038 is 19 years from now. Just saying.
+1 for "YYYY-MM-DD HH:mm:ss" :p
If nothing else, this should be at least somewhat accessible to non-programmer GB runners. Has any thought been given to what a hypothetical UX/UI would be like?
So does this list just not get updated anymore?
+1 for "YYYY-MM-DD HH:mm:ss" :p
If nothing else, this should be at least somewhat accessible to non-programmer GB runners. Has any thought been given to what a hypothetical UX/UI would be like?
so we do mysql timestamp? YYYYMMDDHHmmss on UTC?
+1 for "YYYY-MM-DD HH:mm:ss" :p
If nothing else, this should be at least somewhat accessible to non-programmer GB runners. Has any thought been given to what a hypothetical UX/UI would be like?
so we do mysql timestamp? YYYYMMDDHHmmss on UTC?
Problem for those formats is the validation of the Json Schema. Sorry for late update i was kinda busy those times and didn't checked this out.
About the UX, i think just a form generating the proper formated json is good enought IMO. Like a single page app hosted on GH page.
NOTE: starting a POC project for this.
Anyway seems like it will not be possible atm. I'd suggest to just add the status of the GB in the name of the topic like some does but not everyone like:That's a really good suggestion but tbh we haven't updated this in 2 years :))
- [GB] [ON] Awesome ISO 60%
- [GB] [OFF] Awesome ISO 60%
- [GB] [PROD] Awesome ISO 60%
- [GB] [SHIP] Awesome ISO 60%
- [GB] [END] Awesome ISO 60%
Then it will be easier to find the status instead of parsing all the posts. Your thougths?
Anyway seems like it will not be possible atm. I'd suggest to just add the status of the GB in the name of the topic like some does but not everyone like:That's a really good suggestion but tbh we haven't updated this in 2 years :))
- [GB] [ON] Awesome ISO 60%
- [GB] [OFF] Awesome ISO 60%
- [GB] [PROD] Awesome ISO 60%
- [GB] [SHIP] Awesome ISO 60%
- [GB] [END] Awesome ISO 60%
Then it will be easier to find the status instead of parsing all the posts. Your thougths?
git submodule update --recursive
Anyway seems like it will not be possible atm. I'd suggest to just add the status of the GB in the name of the topic like some does but not everyone like:
- [GB] [ON] Awesome ISO 60%
- [GB] [OFF] Awesome ISO 60%
- [GB] [PROD] Awesome ISO 60%
- [GB] [SHIP] Awesome ISO 60%
- [GB] [END] Awesome ISO 60%
Then it will be easier to find the status instead of parsing all the posts. Your thougths?
main troubles you've come across is setting up the website side of things?
Quotemain troubles you've come across is setting up the website side of things?
Not at all, the main problem is the agreement of people using the standard and make communities contribute to it. Like i said people seems not really into this because you need to update another data source.
TBH: Once the standard is up, it's like 2 days of work to make the platform up for me. It's not a complicated project, but it needs contribution to work. It's like being a book printer without having books to print, you got the tools but not the pdf files to print.
That's why i came up with the status of the GB in the title. Why only the status? Because it doesn't require so much effort and it will be easier for everyone (me the first) to see which GB is running at the moment. It's a moderation addition but a good user feature IMO.
Sorry new here, I'm assuming this page is rarely used? Is there a better place to find open group buys?I just saw this over on KeebTalk
Suggestion: https://mechgroupbuys.com/
(no idea if link will get removed, but that site is very helpful and is actively maintained)
Suggestion: https://mechgroupbuys.com/
(no idea if link will get removed, but that site is very helpful and is actively maintained)
Suggestion: https://mechgroupbuys.com/
(no idea if link will get removed, but that site is very helpful and is actively maintained)
THANK YOU! I'll replace the OP with this link. :thumb:
Suggestion: https://mechgroupbuys.com/
(no idea if link will get removed, but that site is very helpful and is actively maintained)
THANK YOU! I'll replace the OP with this link. :thumb:
There are other good ones.
Suggestion: https://mechgroupbuys.com/
(no idea if link will get removed, but that site is very helpful and is actively maintained)
THANK YOU! I'll replace the OP with this link. :thumb:
There are other good ones.
Suggestion: https://mechgroupbuys.com/
(no idea if link will get removed, but that site is very helpful and is actively maintained)
THANK YOU! I'll replace the OP with this link. :thumb:
There are other good ones.
Care to link? Wouldn't hurt to throw some other GB tracking sites up there too.
Suggestion: https://mechgroupbuys.com/
(no idea if link will get removed, but that site is very helpful and is actively maintained)
THANK YOU! I'll replace the OP with this link. :thumb:
There are other good ones.
Care to link? Wouldn't hurt to throw some other GB tracking sites up there too.
See above :thumb:
Just made a website during my quarantine free time hoping it can help some other people in the hobby like it has helped me keep organized!
bunnykeeb.com (http://bunnykeeb.com)
Just made a website during my quarantine free time hoping it can help some other people in the hobby like it has helped me keep organized!
bunnykeeb.com (http://bunnykeeb.com)
nice work :thumb:
are these stores reliable?
Just made a website during my quarantine free time hoping it can help some other people in the hobby like it has helped me keep organized!
bunnykeeb.com (http://bunnykeeb.com)
Hi!
I would like to ask you to add my running GB to the list :)
https://geekhack.org/index.php?topic=109456.msg2976895 (https://geekhack.org/index.php?topic=109456.msg2976895)
Thanks
Hi there!
Is it possible to get my GB added to the list as well?
Just let me know what you need from me.
Thanks so much and have a great day!
BuunyKeeb is down. Maybe it’s time to take it off the list?Just made a website during my quarantine free time hoping it can help some other people in the hobby like it has helped me keep organized!I added your site to the OP - thanks! :thumb:
bunnykeeb.com (http://bunnykeeb.com)
I recently launched KeycapLendar (https://keycaplendar.firebaseapp.com/)Your site is absolutely awesome. Thanks for making it!
BuunyKeeb is down. Maybe it’s time to take it off the list?Just made a website during my quarantine free time hoping it can help some other people in the hobby like it has helped me keep organized!I added your site to the OP - thanks! :thumb:
bunnykeeb.com (http://bunnykeeb.com)
I recently launched KeycapLendar (https://keycaplendar.firebaseapp.com/)Your site is absolutely awesome. Thanks for making it!
BuunyKeeb is down. Maybe it’s time to take it off the list?Just made a website during my quarantine free time hoping it can help some other people in the hobby like it has helped me keep organized!I added your site to the OP - thanks! :thumb:
bunnykeeb.com (http://bunnykeeb.com)
BuunyKeeb is down. Maybe it’s time to take it off the list?Just made a website during my quarantine free time hoping it can help some other people in the hobby like it has helped me keep organized!I added your site to the OP - thanks! :thumb:
bunnykeeb.com (http://bunnykeeb.com)
Thanks for the heads up!
Here is my version of the spreadsheet that I'm using to keep track of the group buy posts.that's incredible :eek:
I'm sharing it so that if others can use it if they find it useful.
https://docs.google.com/spreadsheets/d/1Vu9BuLG76NIifz4fIQqnengUfTyLHVvuAd9jLoFqMI0/edit?usp=sharing
Is MechGroupBuy down or undergoing renovations?
mech groupbuy link dead?
Hey everyone, apologies my first time running a GB and it has already commenced. How do I post in the GB section.
Link to my IC
https://geekhack.org/index.php?topic=113676.0 (https://geekhack.org/index.php?topic=113676.0)
Hey everyone, apologies my first time running a GB and it has already commenced. How do I post in the GB section.
Link to my IC
https://geekhack.org/index.php?topic=113676.0 (https://geekhack.org/index.php?topic=113676.0)
Here is info about making group buy threads - https://geekhack.org/index.php?topic=88717.0
There are no prerequisites for making an IC thread. But before starting a GB thread, a "minimum forum membership duration of 2 months + post count of 25" are required.
Where can i know which GB are opened at this time?
Im back in the game after 7bit GB in 2011.
Thanks to everyone that contributes for this place that continues to flourish.