Hey, another ZSA newsletter subscriber! Did you get one of their keyboards? I have the Ergodox EZ, and I love it. This Saucer project looks super cool, it would be interesting to see how much...
Hey, another ZSA newsletter subscriber! Did you get one of their keyboards? I have the Ergodox EZ, and I love it. This Saucer project looks super cool, it would be interesting to see how much could be reused for an Ergodox as well
I actually didn't know they had a newsletter! I've never bought one of their keyboards. I just follow their blog's RSS feed because I think their keyboards look great, and I love some of the...
I actually didn't know they had a newsletter! I've never bought one of their keyboards. I just follow their blog's RSS feed because I think their keyboards look great, and I love some of the firmware features they've built.
Right now I've got a Helix split ortho, but with regular switches instead of low profiles. Plus my trusty old OLKB Planck.
Always great to see someone make hardware their own like this. It takes a lot of time and a lot of skill development but it can be so rewarding. Bonus points for introducing Plasticity. I didn't...
Always great to see someone make hardware their own like this. It takes a lot of time and a lot of skill development but it can be so rewarding.
Bonus points for introducing Plasticity. I didn't know there was an inexpensive "buy to own" CAD program out there that's not an ocean of buttons and menus.
This is cool to see! I recently bought a Voyager and have been enjoying typing on a split keyboard. It's definitely improved how I type. A trackpad under my thumb would be interesting to use.
This is cool to see! I recently bought a Voyager and have been enjoying typing on a split keyboard. It's definitely improved how I type. A trackpad under my thumb would be interesting to use.
This looks like a really cool keyboard...kinda makes me want to buy one just to learn how to make a trackpoint mouse, then an attachment for the keyboard like this guy did.
This looks like a really cool keyboard...kinda makes me want to buy one just to learn how to make a trackpoint mouse, then an attachment for the keyboard like this guy did.
Dammit, now I'm looking at new keyboard designs and mods! I've been using the Voyager for a few months now as my main work keyboard, and it's fantastic, but an extra couple of thumb keys on each...
Dammit, now I'm looking at new keyboard designs and mods!
I've been using the Voyager for a few months now as my main work keyboard, and it's fantastic, but an extra couple of thumb keys on each hand might be really useful. Right now I'm using home row mods, and it's way easier to get used to than I expected, but it starts causing more mistakes the faster I type. I know there are ways around this, but I'm wondering if moving my modifiers to the thumb keys would make more sense. But then it's harder to get access to all the layers I want.
Hey, DIY electronics enthusiasts: we need to talk. You have a real problem with assuming everyone knows wtf your generically named gizmos are. You write blogs about how to do neat stuff with the...
Hey, DIY electronics enthusiasts: we need to talk.
You have a real problem with assuming everyone knows wtf your generically named gizmos are. You write blogs about how to do neat stuff with the cool gadgetry, but since no one who isn't already in the know has a clue what the shit you're talking about, it makes no sense.
I see this all the time across the whole "maker" world, from homebrew gaming equipment, to bedroom programmers, to homelab server geeks. (I won't even begin with my fellow Linux/OSS fans.) It makes it very difficult to muster enthusiasm for your cool pet project–and I'm sure it is cool–when your prose reads like jumbled up refrigerator poetry magnets.
Please, for the love of Wozniak, throw in a line saying "Voyager is a very cool ultra-portable split keyboard, and I've been making a trackpad attachment for it." If you have difficulty with conciseness, then put in a link to another site that can explain in basic terms what you're working on. Or, if even that's too much, name your shit something other than a meaningless single English word that returns one-hundred-and-eleventy billion results when I try to Google it.
You’re not the target audience for this blog post. Arguably there is no target audience and it’s just a person sharing something they made and think is cool. The rest of their website...
You’re not the target audience for this blog post. Arguably there is no target audience and it’s just a person sharing something they made and think is cool.
The rest of their website (https://www.zsa.io) has all the info you need to get up to speed though. You could have read over their entire site in the time it took to write this rant probably.
Otherwise, please don’t inject bad vibes into my posts. If you feel this strongly about the issue then posting this rant as its own topic would be better. It would probably get more traction and response that way anyways.
And I never will be, if no consideration is taken for onboarding those who might be interested, but who aren't already in the loop. My frustration isn't specifically directed at you or the blog's...
Exemplary
You’re not the target audience for this blog post.
And I never will be, if no consideration is taken for onboarding those who might be interested, but who aren't already in the loop.
My frustration isn't specifically directed at you or the blog's author, which is why I wrote it as an open letter to tinkerers generally. I truly see the lack of consideration for audience all over the place, and it doesn't take much to address it.
You can take my facetiously written screed as negative vibes if you like, but my preference is to think of it as constructive criticism from a frustrated but interested onlooker. We live in an age of unlimited possibilities for the autodidactically inclined; we should really try to avoid thoughtlessness and the sort of elitism that purposely obfuscates with jargon things that can be enjoyed by many.
But... why? People in the know will read it, and then comment on the actual content of the article. People not in the know will... open it, read it, and then comment on the actual content of the...
But... why?
People in the know will read it, and then comment on the actual content of the article. People not in the know will... open it, read it, and then comment on the actual content of the article, maybe with some follow up questions on why it was posted or something.
People not in the know shouldn't comment on it unless they read the article anyways, in which they get all the context that they need, and if they don't, they can ask the questions afterwards.
Because it’s courteous, and respectful I definitely skimmed through the article to see what it looked like, and what it did because I like DIY but had no idea what the device was. If I had known...
Because it’s courteous, and respectful
I definitely skimmed through the article to see what it looked like, and what it did because I like DIY but had no idea what the device was. If I had known from the start, I honestly would have been more interested and read the whole thing
Like the other said, this is the general tech forum on a decently popular forum. If your product isn’t well known, I would say you should briefly explain what it is if you choose to post to the more general “tech” section. Otherwise, why are you posting at all in anything other than a literal Voyager specific forum?
It is courteous. I'm unconvinced it's respectful, but it is at least certainly courteous. The thing though, is that it's not required, and at least when I originally posted this, I had no interest...
It is courteous. I'm unconvinced it's respectful, but it is at least certainly courteous.
The thing though, is that it's not required, and at least when I originally posted this, I had no interest in sitting down and writing out any sort of context. I just wanted to post what I thought was a cool blog post about neat DIY hardware.
To be honest, I find a it little disrespectful or perahps discourteous that people expect posters to provide them with context they could otherwise easily and rapidly discover for themselves by clicking around a website. Or people could just ask questions instead of posting rants 🤷
I was just posting my thoughts. Obviously by now I’ve researched what it is I’m not trying to rant, just voice my opinion on why more information/context would be nice in similar future...
I was just posting my thoughts. Obviously by now I’ve researched what it is
I’m not trying to rant, just voice my opinion on why more information/context would be nice in similar future circumstances
You don’t have to listen to me, but it does seem like others share similar sentiments
Depending on the context, it can also be respectful toward your potential audience. It might be completely obvious to you and the author, given the context. But once it gets posted outside that...
Depending on the context, it can also be respectful toward your potential audience. It might be completely obvious to you and the author, given the context. But once it gets posted outside that context (like Tildes) people are not as aware of it. People who know think it is potentially interesting but are not quite sure now spend extra time gathering that extra context that with very little effort could have been included.
The initial comment was addressed to this lack of context in general. And the more the writing is targeted at a broader audience, the more I feel it is respectful (and just makes sense) to include important context.
Nah, there never has been any sort of responsibility to include anything "extra" when posting on Tildes. Not even tagging is compulsory. The site's documentation is quite clear on this. The only...
The only responsibility someone has when posting to Tildes is to include a title and some sort of content, whether that be a link or text.
Tags are not required, "context" sure isn't, and neither should it be. Posting on Tildes should not be a burden. Users should not be required to provide anything more on a post than what the site mechanically requires. Anything extra like tags, or whatever you count as "context", would likely be better provided by someone who is actually interested anyways.
Like I said to the other guy, just because it's not literally against the rules doesn't make it good netiquette. This is a ridiculously obscure topic to treat this way.
Like I said to the other guy, just because it's not literally against the rules doesn't make it good netiquette. This is a ridiculously obscure topic to treat this way.
Okay, well if you feel strongly about this, that is, the etiquette and responsibilities of providing context when posting obscure things, then I would encourage you to make a post about it to...
Okay, well if you feel strongly about this, that is, the etiquette and responsibilities of providing context when posting obscure things, then I would encourage you to make a post about it to ~tildes. Perhaps with some suggestions for rule changes, or whatever you think would be a good solution to the problem. Either that, or you could message @Deimos directly and see what he says.
Again, I'm not saying it needs to be a literal rule. I'm just saying that you shouldn't be upset that someone is suggesting more context would be a good idea for what's currently the top post on...
Again, I'm not saying it needs to be a literal rule. I'm just saying that you shouldn't be upset that someone is suggesting more context would be a good idea for what's currently the top post on the entire site.
Edit: Or at least was at the time I posted my previous comment.
Ah, I see. Well that's the thing, @Promonk's "suggestion" was really more of an offtopic rant, and look at what it has done to this comment section that should instead be filled with beautiful...
Ah, I see. Well that's the thing, @Promonk's "suggestion" was really more of an offtopic rant, and look at what it has done to this comment section that should instead be filled with beautiful discussions about weird keyboards...
And even if, for whatever reason, @Promonk couldn't or wouldn't browse the rest of ZSA's website to answer their own questions, I would have been more than happy to "talk shop" with them if they had actually asked any of their questions, rather than just posting some rant about "DIY electronics enthusiasts" not catering to those lacking of their enthusiast knowledge.
Look, we're getting really into the weeds on this. I think I've said all I have to say on the matter. I'll let you have the last word if you want it.
Looks like there's plenty of discussion about how people go about writing DIY blogs here. It might not have been what you wanted, but this is a forum, after all.
Looks like there's plenty of discussion about how people go about writing DIY blogs here. It might not have been what you wanted, but this is a forum, after all.
"But this is a forum" is not a good reason to post noisy and offtopic rants in the comments, about whatever thing in the blog post annoyed you. There's a reason your comment was label as noise and...
"But this is a forum" is not a good reason to post noisy and offtopic rants in the comments, about whatever thing in the blog post annoyed you. There's a reason your comment was label as noise and collapsed.
I've deleted this post. I have no interest in hosting this ridiculous discussion any longer.
My original suggestion stands:
If you feel so strongly about whatever it is your rant was about, post it as its own topic, and then just link back here for your all important context.
Out of curiosity, how did you arrive at bad vibes with this comment? Off-topic is something I could get behind, but I am really curious how it can be construed as bad vibes. As a reference, what I...
Out of curiosity, how did you arrive at bad vibes with this comment? Off-topic is something I could get behind, but I am really curious how it can be construed as bad vibes.
As a reference, what I am seeing is a light-hearted, purposefully over the top message of someone trying to bring awareness to something that I think is pretty valid.
All I had to start was "Voyager," and the knowledge it had something to do with computers. That got me a bunch of hits for "what computer ran the Voyager 1 probe?" and nothing else. I eventually...
All I had to start was "Voyager," and the knowledge it had something to do with computers. That got me a bunch of hits for "what computer ran the Voyager 1 probe?" and nothing else.
I eventually got to it, but that's already more effort than I should have had to go to before I even knew if I was interested or not. Like I said, I'm pro DIY. If I got frustrated by the lack of context, imagine how someone who wasn't already inclined to give every benefit might take it.
All I'm asking is for people to keep their audience in mind when writing stuff, because a lot of people rely on makers to learn. It's really not hard to throw the tiniest bit of context into one's lede.
Yeah I get your point, just the search was easy for me and I know little about this realm. I did read the whole blog post first and realize it was for a keyboard though, so my first and last...
Yeah I get your point, just the search was easy for me and I know little about this realm. I did read the whole blog post first and realize it was for a keyboard though, so my first and last search ended up being "voyager keyboard" (which worked fine) rather than just "voyager".
The site itself is the ZSA site, and the header itself actually has a link to where to buy a Voyager though? To be perfectly fair it's easy to miss and maybe it's because I'm literally typing on...
The site itself is the ZSA site, and the header itself actually has a link to where to buy a Voyager though? To be perfectly fair it's easy to miss and maybe it's because I'm literally typing on an Ergodox EZ right now, but I wouldn't say that it was really difficult to find the actual information.
I am familiar with ZSA and completely missed that fact. Frankly I don't always directly look at the URL or even in detail to the header of a website when I am linked to a blog post. In this case...
I am familiar with ZSA and completely missed that fact. Frankly I don't always directly look at the URL or even in detail to the header of a website when I am linked to a blog post.
In this case we are also talking about a tiny header with a tiny logo on a huge background image which made me glance over it completely as well.
So it took me a while to catch on as well what this was for.
Hey, another ZSA newsletter subscriber! Did you get one of their keyboards? I have the Ergodox EZ, and I love it. This Saucer project looks super cool, it would be interesting to see how much could be reused for an Ergodox as well
I actually didn't know they had a newsletter! I've never bought one of their keyboards. I just follow their blog's RSS feed because I think their keyboards look great, and I love some of the firmware features they've built.
Right now I've got a Helix split ortho, but with regular switches instead of low profiles. Plus my trusty old OLKB Planck.
Always great to see someone make hardware their own like this. It takes a lot of time and a lot of skill development but it can be so rewarding.
Bonus points for introducing Plasticity. I didn't know there was an inexpensive "buy to own" CAD program out there that's not an ocean of buttons and menus.
This is cool to see! I recently bought a Voyager and have been enjoying typing on a split keyboard. It's definitely improved how I type. A trackpad under my thumb would be interesting to use.
This looks like a really cool keyboard...kinda makes me want to buy one just to learn how to make a trackpoint mouse, then an attachment for the keyboard like this guy did.
Dammit, now I'm looking at new keyboard designs and mods!
I've been using the Voyager for a few months now as my main work keyboard, and it's fantastic, but an extra couple of thumb keys on each hand might be really useful. Right now I'm using home row mods, and it's way easier to get used to than I expected, but it starts causing more mistakes the faster I type. I know there are ways around this, but I'm wondering if moving my modifiers to the thumb keys would make more sense. But then it's harder to get access to all the layers I want.
Hey, DIY electronics enthusiasts: we need to talk.
You have a real problem with assuming everyone knows wtf your generically named gizmos are. You write blogs about how to do neat stuff with the cool gadgetry, but since no one who isn't already in the know has a clue what the shit you're talking about, it makes no sense.
I see this all the time across the whole "maker" world, from homebrew gaming equipment, to bedroom programmers, to homelab server geeks. (I won't even begin with my fellow Linux/OSS fans.) It makes it very difficult to muster enthusiasm for your cool pet project–and I'm sure it is cool–when your prose reads like jumbled up refrigerator poetry magnets.
Please, for the love of Wozniak, throw in a line saying "Voyager is a very cool ultra-portable split keyboard, and I've been making a trackpad attachment for it." If you have difficulty with conciseness, then put in a link to another site that can explain in basic terms what you're working on. Or, if even that's too much, name your shit something other than a meaningless single English word that returns one-hundred-and-eleventy billion results when I try to Google it.
Thank you. I love you. Kiss kiss.
You’re not the target audience for this blog post. Arguably there is no target audience and it’s just a person sharing something they made and think is cool.
The rest of their website (https://www.zsa.io) has all the info you need to get up to speed though. You could have read over their entire site in the time it took to write this rant probably.
Otherwise, please don’t inject bad vibes into my posts. If you feel this strongly about the issue then posting this rant as its own topic would be better. It would probably get more traction and response that way anyways.
And I never will be, if no consideration is taken for onboarding those who might be interested, but who aren't already in the loop.
My frustration isn't specifically directed at you or the blog's author, which is why I wrote it as an open letter to tinkerers generally. I truly see the lack of consideration for audience all over the place, and it doesn't take much to address it.
You can take my facetiously written screed as negative vibes if you like, but my preference is to think of it as constructive criticism from a frustrated but interested onlooker. We live in an age of unlimited possibilities for the autodidactically inclined; we should really try to avoid thoughtlessness and the sort of elitism that purposely obfuscates with jargon things that can be enjoyed by many.
Okay, great, but at that point the onus falls on the OP of this thread to provide some kind of context. This is ~tech, not ~Voyager_Keyboard.
But... why?
People in the know will read it, and then comment on the actual content of the article. People not in the know will... open it, read it, and then comment on the actual content of the article, maybe with some follow up questions on why it was posted or something.
People not in the know shouldn't comment on it unless they read the article anyways, in which they get all the context that they need, and if they don't, they can ask the questions afterwards.
Because it’s courteous, and respectful
I definitely skimmed through the article to see what it looked like, and what it did because I like DIY but had no idea what the device was. If I had known from the start, I honestly would have been more interested and read the whole thing
Like the other said, this is the general tech forum on a decently popular forum. If your product isn’t well known, I would say you should briefly explain what it is if you choose to post to the more general “tech” section. Otherwise, why are you posting at all in anything other than a literal Voyager specific forum?
It is courteous. I'm unconvinced it's respectful, but it is at least certainly courteous.
The thing though, is that it's not required, and at least when I originally posted this, I had no interest in sitting down and writing out any sort of context. I just wanted to post what I thought was a cool blog post about neat DIY hardware.
To be honest, I find a it little disrespectful or perahps discourteous that people expect posters to provide them with context they could otherwise easily and rapidly discover for themselves by clicking around a website. Or people could just ask questions instead of posting rants 🤷
I was just posting my thoughts. Obviously by now I’ve researched what it is
I’m not trying to rant, just voice my opinion on why more information/context would be nice in similar future circumstances
You don’t have to listen to me, but it does seem like others share similar sentiments
Oh no no, my apologies, I didn't mean that you were ranting
Depending on the context, it can also be respectful toward your potential audience. It might be completely obvious to you and the author, given the context. But once it gets posted outside that context (like Tildes) people are not as aware of it. People who know think it is potentially interesting but are not quite sure now spend extra time gathering that extra context that with very little effort could have been included.
The initial comment was addressed to this lack of context in general. And the more the writing is targeted at a broader audience, the more I feel it is respectful (and just makes sense) to include important context.
Just because it's not literally against the rules doesn't make it good netiquette. This is a ridiculously obscure topic to treat this way.
Nah, there never has been any sort of responsibility to include anything "extra" when posting on Tildes. Not even tagging is compulsory. The site's documentation is quite clear on this.
The only responsibility someone has when posting to Tildes is to include a title and some sort of content, whether that be a link or text.
Tags are not required, "context" sure isn't, and neither should it be. Posting on Tildes should not be a burden. Users should not be required to provide anything more on a post than what the site mechanically requires. Anything extra like tags, or whatever you count as "context", would likely be better provided by someone who is actually interested anyways.
Like I said to the other guy, just because it's not literally against the rules doesn't make it good netiquette. This is a ridiculously obscure topic to treat this way.
Okay, well if you feel strongly about this, that is, the etiquette and responsibilities of providing context when posting obscure things, then I would encourage you to make a post about it to ~tildes. Perhaps with some suggestions for rule changes, or whatever you think would be a good solution to the problem. Either that, or you could message @Deimos directly and see what he says.
Again, I'm not saying it needs to be a literal rule. I'm just saying that you shouldn't be upset that someone is suggesting more context would be a good idea for what's currently the top post on the entire site.
Edit: Or at least was at the time I posted my previous comment.
Ah, I see. Well that's the thing, @Promonk's "suggestion" was really more of an offtopic rant, and look at what it has done to this comment section that should instead be filled with beautiful discussions about weird keyboards...
And even if, for whatever reason, @Promonk couldn't or wouldn't browse the rest of ZSA's website to answer their own questions, I would have been more than happy to "talk shop" with them if they had actually asked any of their questions, rather than just posting some rant about "DIY electronics enthusiasts" not catering to those lacking of their enthusiast knowledge.
Look, we're getting really into the weeds on this. I think I've said all I have to say on the matter. I'll let you have the last word if you want it.
Looks like there's plenty of discussion about how people go about writing DIY blogs here. It might not have been what you wanted, but this is a forum, after all.
"But this is a forum" is not a good reason to post noisy and offtopic rants in the comments, about whatever thing in the blog post annoyed you. There's a reason your comment was label as noise and collapsed.
I've deleted this post. I have no interest in hosting this ridiculous discussion any longer.
My original suggestion stands:
If you feel so strongly about whatever it is your rant was about, post it as its own topic, and then just link back here for your all important context.
Out of curiosity, how did you arrive at bad vibes with this comment? Off-topic is something I could get behind, but I am really curious how it can be construed as bad vibes.
As a reference, what I am seeing is a light-hearted, purposefully over the top message of someone trying to bring awareness to something that I think is pretty valid.
I get your point, but at the same time a "voyager keyboard" search gave me the site right away.
All I had to start was "Voyager," and the knowledge it had something to do with computers. That got me a bunch of hits for "what computer ran the Voyager 1 probe?" and nothing else.
I eventually got to it, but that's already more effort than I should have had to go to before I even knew if I was interested or not. Like I said, I'm pro DIY. If I got frustrated by the lack of context, imagine how someone who wasn't already inclined to give every benefit might take it.
All I'm asking is for people to keep their audience in mind when writing stuff, because a lot of people rely on makers to learn. It's really not hard to throw the tiniest bit of context into one's lede.
Yeah I get your point, just the search was easy for me and I know little about this realm. I did read the whole blog post first and realize it was for a keyboard though, so my first and last search ended up being "voyager keyboard" (which worked fine) rather than just "voyager".
The site itself is the ZSA site, and the header itself actually has a link to where to buy a Voyager though? To be perfectly fair it's easy to miss and maybe it's because I'm literally typing on an Ergodox EZ right now, but I wouldn't say that it was really difficult to find the actual information.
I am familiar with ZSA and completely missed that fact. Frankly I don't always directly look at the URL or even in detail to the header of a website when I am linked to a blog post.
In this case we are also talking about a tiny header with a tiny logo on a huge background image which made me glance over it completely as well.
So it took me a while to catch on as well what this was for.