HN user

technoplato

164 karma
Posts1
Comments69
View on HN

I think the dissenting / mocking comments here are missing the spirit of the post.

Since bash can evoke any Turing complete program, feasibly anything could be done with one line of bash.

The authors intent as I saw was to show what that line was. Would you have known without this article?

Whether or not people are just being sarcastic, I feel we should definitely not mock but rather encourage any open and free attempts at teaching us cool things that are more novel than the “how to get started on Linux” type bs the market is inundated with.

Bravo to author.

Ignore the motorcycle bit completely and just think physics

You could trigger this on any oscillating “body” if that body is oscillating at a certain frequency and amplitude combination.

It just so happens motorcycle engines produce that combination. There would certainly be others. tHe sustained nature of the shaking would also be cause for concern but I didn’t see any mention of duration in the support article

TLDR shaking the phone anywhere at any time with certain amplitude / frequency combinations will permanently damage sensitive components and make pics look like you’ve got ALS again

Yeah they actually go into more interesting detail than expected from a support article and detail how (not an expert so it could just be wool over my eyes Apple BS but doesn’t smell that way here) the OIS and closed loop AF work in that article.

Basically sensitive gadgets shouldn’t be exposed to certain frequency / amplitude combinations because sensitive gadgets rely on well, not being shaken out of whack.

Have you tried an ergonomic split keyboard? I got an Ergodox for my birthday and it feels great to type on and I have MUCH less strain.

Doesn’t have to be that brand obviously but highly recommend checking out the idea at large.

[dead] 6 years ago

Hello The Flip Side,

I deeply empathize with the goals of bridging the gap between the incredibly vocal minority opinion holders at both ends of the curve. I’ve been thinking about how to solve this problem and working on my own take, knophy [1], for a couple years now in my free time. Knophy is a content aggregation platform that creates an innovative new economic model whereby voting power is earned by first reading, watching, or listening to the content on which one desires to comment or “upvote” themselves. After consuming a piece of content, a user can then answer community moderated evidence-based questions to earn said voting power. Whenever questions are answered correctly, the creator, moderators of the question bank (the community) and the answerer all earn relative amounts of points with which to vote on content. Should a user develop a surplus of points, they may “burn” those points in exchange for a fungible, cryptocurrency token that they can either sell or speculate against.

This model has implications in solving the problem of content monetization, copyright, siloed walled gardens who rely on riling up their users to increase usage, moderation, and many more major problems which I would love to discuss in further detail if you find them intriguing.

I realize I haven’t done a great job introducing myself in the above paragraphs, but feel that the ideas we have in regards to solving this problem are more important than me blabbing about myself. I’m a full stack engineer specializing in React / React Native and am very excited about using the GRANDStack (GraphQL, React, Apollo, Neo4j Database) to create highly connected and innovative new applications at scale.

I'm currently very happily employed but would love to help innovate in this space in any capacity that would be welcome!

My contact info and some relevant works are linked here: [GitHub - technoplato/portfolio: A portfolio of my work](https://github.com/technoplato/portfolio)

I’ve also sent this via email to the specified address. If any HackerNews people are interested in critiquing or helping with this idea, I’m all ears!

[1] [GitHub - technoplato/knophy: WIP Knophy is a content aggregation platform where voting power is regulated and earned by demonstrating what you know about the content you follow.](https://github.com/technoplato/knophy)

It was very early in the morning. Apologies for being obscure.

When platforms ban assholes and other platforms arise in the guise of decreasing censorship, said assholes flock to new platforms and infest them a la Ruqqus (though I believe the developer/founders have positive intent)

We need more clever ways of finding the assholes. I mentioned show and tell in my comment above. When you think about how show and tell works, you must earn your right to show and that works fairly well, even when you scale the idea. Does that make more sense?

Not stating an opinion either way to the platform or it’s constituents but naming the result of rebroadcasting a message to ones followers has no effect whatsoever on its effect.

A retweet, share, and apparently an echo are all semantically close enough to be called identical functionality, save for perhaps upstream metadata associated with the source.

eg on Facebook I don’t know if, once you share a post, the total share count is displayed on the post itself. However on Twitter this share count is shown.

They’re all the same sheep with isomorphically identical data just dressed up in different pairs of clothes.

Obvious and dead horse beaten issue. I’m working on solving this and will report here when I’ve got a prototype.

Surprising insights arise from pondering the philosophy of show and tell-specifically how listening is involved in order to “earn” your turn to speak.

Honest response:

Wonderful documentation is hard to beat from my learning perspective, but I find that level of quality is more rare.

Therefore, I learn better by watching something materialize on video at ~3x speed and often without any speaking.

I think it simply boils down to my level of trust that this person didn’t accidentally omit anything from their article or blog post or whatever and what I see on the screen is what I get. Now, that doesn’t fix when tools change etc, but videos instill a higher level of trust that, if I follow these steps, I will produce this output.

So two thoughts here. Are they artificially inflated and then deflated to counter act “bot” behavior? OR are they organically inflated and then censored? I just wish I could be a fly on the wall and know. I just can’t believe this would be a damning enough piece to artificially inflate unless there’s a serious game of reverse psychology going on behind the scenes

So two thoughts here.

Are they artificially inflated and then deflated to counter act “bot” behavior?

OR

are they organically inflated and then censored?

I just wish I could be a fly on the wall and know. I just can’t believe this would be a damning enough piece to artificially inflate unless there’s a serious game of reverse psychology going on behind the scenes

Here are the node dependencies. Am I ignorant to assume these make CLI interaction more developer friendly?

    "execa": "^4.0.3",
    "glob": "^7.1.6",
    "mkdirp": "^1.0.4",
    "moment": "^2.29.1",
    "nopt": "^5.0.0",
    "npmlog": "^4.1.2",
    "nyc": "^15.1.0",
    "p-all": "^3.0.0",
    "rimraf": "^3.0.2",
    "tape": "^5.0.1",
    "unique-slug": "^2.0.2",
    "which": "^2.0.2"
Sorry for any basterdized formatting. OM

I anticipate some much more savvy than myself saying this wrapper is unnecessary as you can do all of this “easily” with ffmpeg. I welcome tools like this that have a more common user in mind, evidenced immediately in the beginning of the README with common use cases.

Ffmpegs documentation on the other hand forces me to feel as though it’s normal to assume knowledge about a point in a video and what it means if my encoders are different from input to output.

I don’t think your comment has any kind of negative intent, but I feel like the idea that grouping any consequence of civilian experience with those of military combat certainly cannot be a reasonable association.

I don’t think Carlin’s point was so much to comment on the accuracy of the description, but rather to say that these descriptions have become longer and longer as time has advanced and thereby lessons the guttural impact they “used” to command.

Do you think that’s fair?