prompt
stringlengths
4
3.12k
chosen
stringlengths
3
10.5k
rejected
stringlengths
3
8.98k
cloudflare dns problem
dyn also appears to be having a real, real bad day. glue records vanished like a fart in the wind. $ dig @8.8.8.8 ns2.p29.dynect.net ; <<>> dig 9.7.3-p3-redhat-9.7.3-8.p3.el6 <<>> @8.8.8.8 ns2.p29.dynect.net ; (1 server found) ;; global options: +cmd ;; got answer: ;; ->>header<<- opcode: query, status: nxdomain, id: 2690 ;; flags: qr rd ra; query: 1, answer: 0, authority: 1, additional: 0 ;; question section: ;ns2.p29.dynect.net. in a ;; authority section: dynect.net. 600 in soa ns0.dynamicnetworkservices.net. hostmaster.dyndns.com. 2015070600 10800 1800 604800 1800 ;; query time: 2 msec ;; server: 8.8.8.8#53(8.8.8.8) ;; when: mon jul 6 21:42:48 2015 ;; msg size rcvd: 120
this appears to not be a problem with cloudflare, but a problem with dyn: <link> of course, dyn and cloudflare have mutual customers and so if a dyn has a problem it's possible for a mutual customer to have a problem.
cloudflare dns problem
this appears to not be a problem with cloudflare, but a problem with dyn: <link> of course, dyn and cloudflare have mutual customers and so if a dyn has a problem it's possible for a mutual customer to have a problem.
sorry -- our ops and engineering teams are looking into this and will update/resolve as quickly as possible.<link>
cloudflare dns problem
sorry -- our ops and engineering teams are looking into this and will update/resolve as quickly as possible.<link>
sorry about this: just posted a blog post. appears to be a dyn issue, but affects a lot of our customers (including support.cloudflare.com which is zendesk)<link>
cloudflare dns problem
sorry about this: just posted a blog post. appears to be a dyn issue, but affects a lot of our customers (including support.cloudflare.com which is zendesk)<link>
more details here on cloudflare's status page here: <link>
descendants of holocaust survivors have altered stress hormones
the &quot;genetics&quot; in epigenetics can actually be quite controversial. that is, how epigenetic markers are inherited isn't very clear. in terms of dna methylation, there are methylation maintenance enzymes. but for histone modification, how they are inherited (are they being inherited?) isn't very clear. would enzymes that perform a certain histone modification being passed from mother to daughter cell during division be considered inheritance of the marker? the &quot;information&quot; for the epigenetic marker isn't being passed down, just the machinery is.anyways, there are still a lot of things to consider.
there have been a series of well-reproduced studies, in animals and humans, looking at methylation of genes related to stress hormone receptors in the hippocampus of subjects exposed to stress/abuse.<link> changes can persist to their offspring.this may be a pop science article, but the steady stream of these findings suggests that there's some pretty ground-breaking stuff happening here. one of my mentors in residency was betting that michael meany will pick up a nobel prize for this work.
descendants of holocaust survivors have altered stress hormones
there have been a series of well-reproduced studies, in animals and humans, looking at methylation of genes related to stress hormone receptors in the hippocampus of subjects exposed to stress/abuse.<link> changes can persist to their offspring.this may be a pop science article, but the steady stream of these findings suggests that there's some pretty ground-breaking stuff happening here. one of my mentors in residency was betting that michael meany will pick up a nobel prize for this work.
the headline of this feb 12, 2015 blog post exaggerates how generalizable these results are likely to be. by the way, do we have a direct link to the published version of the study readily available? i just tried some of the usual online steps for looking up the author's most recent publication on the issue, but what i found was a repost of this scientific american blog post (which is already a few months old). i study this research with a journal club populated by leading behavior genetics researchers, and any preliminary findings of this kind need a lot more replication before being publishable in an astute journal.
descendants of holocaust survivors have altered stress hormones
the headline of this feb 12, 2015 blog post exaggerates how generalizable these results are likely to be. by the way, do we have a direct link to the published version of the study readily available? i just tried some of the usual online steps for looking up the author's most recent publication on the issue, but what i found was a repost of this scientific american blog post (which is already a few months old). i study this research with a journal club populated by leading behavior genetics researchers, and any preliminary findings of this kind need a lot more replication before being publishable in an astute journal.
considering the incredible psychological impact of the holocaust on survivors, and how that would affect one's perception of risk in day to day life, i have to imagine that these people probably passed that perspective on to their kids while raising them. if someone were (understandably) raised to always feel under threat, i could see that having an impact on what they're testing.
descendants of holocaust survivors have altered stress hormones
considering the incredible psychological impact of the holocaust on survivors, and how that would affect one's perception of risk in day to day life, i have to imagine that these people probably passed that perspective on to their kids while raising them. if someone were (understandably) raised to always feel under threat, i could see that having an impact on what they're testing.
in the netherlands we have a special class labelled 'second generation war victim' which deals with some of the aspects of this: (dutch link, sorry i could not find any article in english)<link> explicitly mentions the earliest development as one of the important criteria, but it concentrates on the psychological aspects, not on direct physical links.
cola.js – constraint-based layout in the browser
wow. how long did this take to build? this is pretty impressive.
offtopic - why does monash.edu.au redirect to monash.edu? this is an australian university.edit: also, <link>
cola.js – constraint-based layout in the browser
offtopic - why does monash.edu.au redirect to monash.edu? this is an australian university.edit: also, <link>
this is interesting, but had hoped it would be something like ios's auto layout for the browser.
cola.js – constraint-based layout in the browser
this is interesting, but had hoped it would be something like ios's auto layout for the browser.
hotdrink is a declarative, constraint-based ui system that models the flow of data across the elements in the ui[1]. trivially, it can repurposed for layout; although, most ui designers balk at the loss of control. the basic idea comes from a sizing dialog: height: [ ] width : [ ] area : [ ] if the user enters a height &amp; width, the form should update area [2]. if the user then updates area, then height is the free constraint (last recently updated). the whole system scales to work with incredibly large interfaces [3]. the experience section in [4] describes adobe's experience porting chunks of photoshop to using this system. (i did the figures for [4]; i'm quite proud of them.)[1] <link>[2] <link>[3] <link>;cfid=690849385&amp;cft... <link>;cfid=690849385&amp;cft... <link>;cfid=690849385&amp;cft...[4] <link>
cola.js – constraint-based layout in the browser
hotdrink is a declarative, constraint-based ui system that models the flow of data across the elements in the ui[1]. trivially, it can repurposed for layout; although, most ui designers balk at the loss of control. the basic idea comes from a sizing dialog: height: [ ] width : [ ] area : [ ] if the user enters a height &amp; width, the form should update area [2]. if the user then updates area, then height is the free constraint (last recently updated). the whole system scales to work with incredibly large interfaces [3]. the experience section in [4] describes adobe's experience porting chunks of photoshop to using this system. (i did the figures for [4]; i'm quite proud of them.)[1] <link>[2] <link>[3] <link>;cfid=690849385&amp;cft... <link>;cfid=690849385&amp;cft... <link>;cfid=690849385&amp;cft...[4] <link>
nice. but as with most of these libraries, i don't think it can handle large numbers of nodes/edges and show such graphs in a meaningful way. it really takes more than a force-directed algorithm to present data in an understandable way.here is a nice collection of large graphs: [1] visualize that in a useful way, and i'm impressed.[1] <link>
the higher life
a venice beach surfer cashes in with an iphone app. just go surfing, yo.
i use headspace every day. it's easy to follow and extremely helpful. it's a fad right now, sure, but at least it's a useful fad.pro tip: if you vpn onto their site from a european server, you'll get the euro prices, which are significantly cheaper than usd prices.
the higher life
i use headspace every day. it's easy to follow and extremely helpful. it's a fad right now, sure, but at least it's a useful fad.pro tip: if you vpn onto their site from a european server, you'll get the euro prices, which are significantly cheaper than usd prices.
it lost me at &quot;ted&quot;
the higher life
it lost me at &quot;ted&quot;
from the article, &quot;.. stanford study .. demonstrated that most workplace stress is caused by things like corporate dysfunction and job insecurity—not by “unmindful employees.”corporations like mindfulness, he said, because it “keeps us within the fences of the neoliberal capitalist paradigm. it’s saying, ‘it’s your problem, get with the program, fix your stress, and get back to work!’”
the higher life
from the article, &quot;.. stanford study .. demonstrated that most workplace stress is caused by things like corporate dysfunction and job insecurity—not by “unmindful employees.”corporations like mindfulness, he said, because it “keeps us within the fences of the neoliberal capitalist paradigm. it’s saying, ‘it’s your problem, get with the program, fix your stress, and get back to work!’”
admirable is he, who when he sees lightning, does not say &quot;life goes by like a flash&quot;.
antibody wipeout relieves symptoms of chronic fatigue syndrome
there is considerable support for destroying and recreating immune cell populations to deal with autoimmune diseases and some aging effects. for example, for b cells:----1) reversing b cell aging<link> long-lived autoreactive plasma cells drive persistent autoimmune inflammation.<link> b-cell depletion reactivates b lymphopoiesis in the bm and rejuvenates the b lineage in aging<link> for treatment of autoimmune disorders such as ms, more comprehensive destruction:<link> was also tried for rheumatoid arthritis with mixed results before the development of biologics, and everyone gave up on the immune reboot with chemotherapy in favor of controlling the condition for some patients.----then there are the prospects for destroying t cells specialized to herpesviruses like cmv (you probably have cmv, near everyone has cmv by time old age rolls around, it's very prevalent) that are thought to cause a large degree of immunosenescence by overloading the repertoire of immune cells with memory t cells for cmv and the like - too many of those and not enough naive t cells to deal with new threats and cancer surveillance. that isn't a going concern yet, but it certainly could be soon.
very interesting! it didn't work for everyone, but it did work for a majority it looks like.cfs is a pretty nasty condition, so i'm glad they've found something that works. my only concern would be the side effects from rituxan. it's a well studied drug, but it really knocks down your immune system.
antibody wipeout relieves symptoms of chronic fatigue syndrome
very interesting! it didn't work for everyone, but it did work for a majority it looks like.cfs is a pretty nasty condition, so i'm glad they've found something that works. my only concern would be the side effects from rituxan. it's a well studied drug, but it really knocks down your immune system.
so, it is possible that some infection is an original cause for the elevated antibody level. it reminds the history of stomach ulcers where bacteria, not the stress, happened to be the primary reason. matter over mind once again :)
antibody wipeout relieves symptoms of chronic fatigue syndrome
so, it is possible that some infection is an original cause for the elevated antibody level. it reminds the history of stomach ulcers where bacteria, not the stress, happened to be the primary reason. matter over mind once again :)
i am hoping someone can help here because it has been affecting my life every day. i have been extremely fatigued for the past 2.5 years and i've lost so many things due to it. i sleep the majority of every day away. how do i know if this is cfs?i guess what i'm asking is, where do i start to cross out other possible causes? considering so many things can cause fatigue.thank you
antibody wipeout relieves symptoms of chronic fatigue syndrome
i am hoping someone can help here because it has been affecting my life every day. i have been extremely fatigued for the past 2.5 years and i've lost so many things due to it. i sleep the majority of every day away. how do i know if this is cfs?i guess what i'm asking is, where do i start to cross out other possible causes? considering so many things can cause fatigue.thank you
&quot;a 150-person study is now under way, and includes a control group.&quot;i'm curious, the latest study which is presumably what triggered this story, involved no control group, yet they mention a smaller study from 2011 which did use a control.if this really does hint at a breakthrough, why did it take so long to follow up on the first study, and why did this one not use a control group?
how wooden puzzles can destroy dev teams
assuming the solvers that they wrote searched the problem space correctly, the hard side probably violates some assumption. my guess would be that on the hard side the pieces can lock into some sort of 3d structure.
interestingly, when i run this through an old dancing links [1] based solver i wrote a while back for solving general puzzles, it solves the first one in 0.04 seconds, uses 65 columns, 242 rows, does 181510 de-queues, and finds a unique solution.the same solver on the hard version runs in 0.01 seconds, 67 columns, 272 rows, 245626 de-queues, and finds no solutions.so as others have noted, the hard puzzle solution must be some weird rotation, and/or not spaced on &quot;integral&quot; coordinates.since i don't have time to write such a solver, i will leave it for now :)note: if you have not looked at the dancing links paper by knuth and learned how to use it to solve backtracking problems, you should. it's amazingly useful for solving such problems, for enumerating all solutions, and it is fast and completely general.[1] <link>
how wooden puzzles can destroy dev teams
interestingly, when i run this through an old dancing links [1] based solver i wrote a while back for solving general puzzles, it solves the first one in 0.04 seconds, uses 65 columns, 242 rows, does 181510 de-queues, and finds a unique solution.the same solver on the hard version runs in 0.01 seconds, 67 columns, 272 rows, 245626 de-queues, and finds no solutions.so as others have noted, the hard puzzle solution must be some weird rotation, and/or not spaced on &quot;integral&quot; coordinates.since i don't have time to write such a solver, i will leave it for now :)note: if you have not looked at the dancing links paper by knuth and learned how to use it to solve backtracking problems, you should. it's amazingly useful for solving such problems, for enumerating all solutions, and it is fast and completely general.[1] <link>
any hints for the solution, then?
how wooden puzzles can destroy dev teams
any hints for the solution, then?
if they ever read penrose it would have taken less time :)
how wooden puzzles can destroy dev teams
if they ever read penrose it would have taken less time :)
what makes this a hard puzzle is that the pieces don't completely fill the area. that dramatically increases the solution search space.
stack exchange engineering: how we built our blog
i'm all for spending engineering time on non-project related tasks occasionally, but this seems like an excessive use of valuable time to reinvent the wheel. i'm sure they could have found a blogging platform that didn't require custom markdown interfaces, python scripting, and re-writing everything from scratch. it's just a blog.
at sunsed we are trying to solve this exact problem: a blogging platform for professional whith batteries included. kind of excited to see wordpress does not work for everyone. thanks for sharing!
stack exchange engineering: how we built our blog
at sunsed we are trying to solve this exact problem: a blogging platform for professional whith batteries included. kind of excited to see wordpress does not work for everyone. thanks for sharing!
that’s exactly what i just did for my daily video / podcasting site rate my app.com.- everything in markdown- generate the podcasts as an rss feed- generate the list of videos as json, filtered inside the angularjs appsuch an approach is not great for seo in the short-term, so i won't be surprised if they lose ranking because their posts and comments are missing from the the html until their jquery code fetches and renders them.for me, i don't have 700 posts so that's easy to address later once i have content worth indexing, keeping the urls the same of course. :)
stack exchange engineering: how we built our blog
that’s exactly what i just did for my daily video / podcasting site rate my app.com.- everything in markdown- generate the podcasts as an rss feed- generate the list of videos as json, filtered inside the angularjs appsuch an approach is not great for seo in the short-term, so i won't be surprised if they lose ranking because their posts and comments are missing from the the html until their jquery code fetches and renders them.for me, i don't have 700 posts so that's easy to address later once i have content worth indexing, keeping the urls the same of course. :)
spoiler alert: it takes awhile to get there, but the answer is: jekyll. which is neat...even as active as their blogging efforts are, as i was reading the intro grafs, i kept thinking, &quot;yeah, could be done just fine as jekyll&quot;...i was mostly expecting them to announce new in-house built blogging software, but was thrilled to see that the rest of the post is about how to migrate from wordpress to jekyll.
stack exchange engineering: how we built our blog
spoiler alert: it takes awhile to get there, but the answer is: jekyll. which is neat...even as active as their blogging efforts are, as i was reading the intro grafs, i kept thinking, &quot;yeah, could be done just fine as jekyll&quot;...i was mostly expecting them to announce new in-house built blogging software, but was thrilled to see that the rest of the post is about how to migrate from wordpress to jekyll.
they lost a simple interface designed to edit blog posts and now their marketing team has to use the github interface and learn markdown.they lost the comment system and had to move the data to an external provider, which instantly bit them.they had to write python scripts to munge the data.but now they have the performance of static html. i guess just changing two lines in the nginx configuration did not came to mind.i think this was a very poor investment and will never pay off.
the “sharing economy” is the problem
it raises some interesting questions. how much do we need these intermediaries, such as uber, airbnb, etc.? could those things be done on something like craigslist? a foss application?as i pointed out in the thread on google's ridewidth, instead of (or in addition to) rideshare companies why can't my municpality license any individual who applies to pickup people on the street who want a ride, and charge them. people wanting a ride could use a special hand signal, with their arm outstretched and thumb pointing up. what do the commercial vendors add or at least, why freeze out individuals doing the same thing?(i'm not implying they add nothing, i'm asking what it is and whether it's worth the extra cost.)
airbnb is a wildy different beast than uber and homejoy. airbnb is increasing market efficiency around distribution of resources (sleeping space) that normally would go un- or mis- used and is just about as textbook as you can get of capitalism resulting in better resource allocation. (issues around lodging regulation and displacement aside, which are real and beyond the scope of this article.)uber and homejoy, while also having aspects of efficiency increases, also are tightly coupled with labor, which has always acted as a counterbalance to unfettered capitalism due to the human element involved and the need for people to make a living. however, the authors of this article miss the bigger picture here. the dynamic playing out with these companies is act one of a larger play, where the final act is the complete removal of human labor from the process. the logistics infrastructure being built here is the end being sought, not the profit margin on the labor being sold nor the network of &quot;entrepreneurs.&quot; with the logistics in place and the data needed to properly run these services at scale, switching out humans for robots as is cost effective will be a natural transition.all the more reason we as a society need to come up with a better solution to &quot;unskilled people need to eat&quot; beyond blaming the greed of silicon valley companies.
the “sharing economy” is the problem
airbnb is a wildy different beast than uber and homejoy. airbnb is increasing market efficiency around distribution of resources (sleeping space) that normally would go un- or mis- used and is just about as textbook as you can get of capitalism resulting in better resource allocation. (issues around lodging regulation and displacement aside, which are real and beyond the scope of this article.)uber and homejoy, while also having aspects of efficiency increases, also are tightly coupled with labor, which has always acted as a counterbalance to unfettered capitalism due to the human element involved and the need for people to make a living. however, the authors of this article miss the bigger picture here. the dynamic playing out with these companies is act one of a larger play, where the final act is the complete removal of human labor from the process. the logistics infrastructure being built here is the end being sought, not the profit margin on the labor being sold nor the network of &quot;entrepreneurs.&quot; with the logistics in place and the data needed to properly run these services at scale, switching out humans for robots as is cost effective will be a natural transition.all the more reason we as a society need to come up with a better solution to &quot;unskilled people need to eat&quot; beyond blaming the greed of silicon valley companies.
the article dismisses what corporate uber provides with:&quot;what exactly are the capitalists at uber contributing to the company? [...] the capital owners maintain the phone app, but app technology isn’t the major cost, and it’s getting cheaper and easier by the day&quot;if true, it should be straightforward for other companies and cooperatives to form and compete with uber. and that's capitalism at its finest.
the “sharing economy” is the problem
the article dismisses what corporate uber provides with:&quot;what exactly are the capitalists at uber contributing to the company? [...] the capital owners maintain the phone app, but app technology isn’t the major cost, and it’s getting cheaper and easier by the day&quot;if true, it should be straightforward for other companies and cooperatives to form and compete with uber. and that's capitalism at its finest.
taxi driver feels abused by having to work 7 days a week for taxi service to make ends meet. switches to uber and describes it as &quot;more of the same&quot;. hard to see how uber ruined everything if it was apparently already ruined.
the “sharing economy” is the problem
taxi driver feels abused by having to work 7 days a week for taxi service to make ends meet. switches to uber and describes it as &quot;more of the same&quot;. hard to see how uber ruined everything if it was apparently already ruined.
&gt; another complaint is more subtle, but more frightening: that these technologies are exacerbating inequality and driving us towards a &quot;servant&quot; economy, where large pools of poorly paid and economically insecure workers will spend their lives providing all manner of petty services for the well-heeled elite.this is my biggest fear. when my family lived in bangladesh, we had a cook, maids, and a full time nanny for me even though my mom didn't work. my dad once sent the nanny out with some money to buy a pack of cigarettes, and he came home empty handed because he couldn't bear to pay a whole day's wage for a pack of cigarettes (my dad went through two packs a day at the time). the value of human labor is just incredibly low over there (or at least was 25 years ago).that kind of society is a travesty. you don't want that here. maybe it won't come to pass. i hope it doesn't. but matter how gung-ho you are about the sharing economy or how much faith you have in the market, you should at least fear that potential outcome.
the unreasonable effectiveness of it
i attributed a lot of this 'effectiveness' to developers who are lazy.there have been times when i automated things and that was because i wanted to avoid repetitive work. i have never been able to automate something i had not manually done 2-3+ times, but once i did i knew what i needed to do to avoid manual work and make the process error free for next time same operation was needed. if someone else was dictating what they needed, i would not have been able to build my tools as effectively.to me, a good developer is a &quot;maker&quot;, who builds tools. for us the raw material is a computer and some free time, which makes experimentation and evolution of our tools easier compared to other professions.
i certainly disagree with this bit, &quot;there’s no systematic way to know how solve ambitious problems. we just don’t know what will lead to what. the future is a fog. an ambitious problem is not deciding what to have for lunch, it’s more like curing cancer or creating an ai.&quot;i have always started on the solution to an ambitious problem by asking &quot;what would have to be true for this to be solvable?&quot; and from each of those things working backward until you get to things that are all true now. then you can start solving the &quot;almost&quot; true things and work forward to the ambitious solution at the end.
the unreasonable effectiveness of it
i certainly disagree with this bit, &quot;there’s no systematic way to know how solve ambitious problems. we just don’t know what will lead to what. the future is a fog. an ambitious problem is not deciding what to have for lunch, it’s more like curing cancer or creating an ai.&quot;i have always started on the solution to an ambitious problem by asking &quot;what would have to be true for this to be solvable?&quot; and from each of those things working backward until you get to things that are all true now. then you can start solving the &quot;almost&quot; true things and work forward to the ambitious solution at the end.
&quot;as schopenhauer says, when you look back on your life, it looks as though it were a plot, but when you are into it, it’s a mess: just one surprise after another. then, later, you see it was perfect.&quot;weird. when i look back on my life, i see blunders, randomness and missed opportunities. there's a great deal that i would change if i could do it over. i'd have thought that was the same for most people.
the unreasonable effectiveness of it
&quot;as schopenhauer says, when you look back on your life, it looks as though it were a plot, but when you are into it, it’s a mess: just one surprise after another. then, later, you see it was perfect.&quot;weird. when i look back on my life, i see blunders, randomness and missed opportunities. there's a great deal that i would change if i could do it over. i'd have thought that was the same for most people.
he neatly explains why traditional, say, &quot;reasonable&quot; management does not work in it:- objectives are a way of saying prove to me first that you know where you are going before you go.- we’ve come to believe too much in metrics and accountability.- there’s no systematic way known how solve ambitious problems. (otherwise they would have been solved already.)for example, the original google search project succeeded, exactly because none of this was around. traditional management only works for repetitive processes. organizations that revolve around traditional management are incapable of innovating.
the unreasonable effectiveness of it
he neatly explains why traditional, say, &quot;reasonable&quot; management does not work in it:- objectives are a way of saying prove to me first that you know where you are going before you go.- we’ve come to believe too much in metrics and accountability.- there’s no systematic way known how solve ambitious problems. (otherwise they would have been solved already.)for example, the original google search project succeeded, exactly because none of this was around. traditional management only works for repetitive processes. organizations that revolve around traditional management are incapable of innovating.
i'm currently listening to an account of the de-centralized command structure gen stanley mcchrystal put in place to combat al quaeda in iraq and the taliban in afghanistan. one thing that is clear is that in a fast paced environment (be that the theater of war or a start up) top down rigid command doesn't work. all this is really saying that the the organization that gets through a feedback loop as fast as possible wins. you can call that the ooda loop, lean, holocracy or whatever you want.i'm strongly in favor of giving up centralized control in the interests of allowing emergent behavior to tackle opportunities as fast as possible. leadership to me should be:* set the direction* gather smart, motivated people* create an environment that gets everyone on the same page* get the fuck out of their way.
reddit’s chief apologizes after employee’s dismissal
the general impression i see the most is that pao and here team are trying wash the site of any content that corporate advertisers find offensive and try to monetize as much of the site as they can starting with a monetization scheme for iama where pr firms can use iama as celebrity advertising with softball pre screened questions.victoria was the key person organizing iama guests across the whole of reddit. she helped to enforced the strict policy that iama have that the person is actually there and not a pr rep fielding questions. and that the questions are real and generally keeping the quality and integrity high.there has already been a number of high traffic subs that have decided to close down and move to voat.co or other sites.it's telling that instead of addressing the community directly pao and here group stage a pr blitz in the media trying to spin a false narrative instead of addressing reddit first and dealing with redditors concerns about moves to limit free speech. commercialisation and firing of key community friendly staff. it shows total concept for reddit users and the same sort of dishonest personality that would try to destroy the credibility of her former employer kleiner perkins with false gender discrimination lawsuits for 100 million. which she lost spectacularly with all 12 jurors siding with kleiner perkins.pao has shown on numerous occasions she is a toxic personality. and has no interest in reddit and the communities there.if anyone is planning on launching your freeze peach community platform now is the time...
it's funny but reddit is not the front page of the internet. it's the comment section of the internet. if you actually see what's going on here, it's the same people who care to comment on things. some of whom are trolls and very difficult to control. the trolls from your comment section are having their day on reddit. and the community is behind them.
reddit’s chief apologizes after employee’s dismissal
it's funny but reddit is not the front page of the internet. it's the comment section of the internet. if you actually see what's going on here, it's the same people who care to comment on things. some of whom are trolls and very difficult to control. the trolls from your comment section are having their day on reddit. and the community is behind them.
reddit has jumped the shark.i remember when this happened with digg; digg reached a certain level of success, but then discovered that it's existing users were a barrier to acquiring new users and getting revenue. they picked a fight with their power users, who left, but never got anybody to replace them, so then the spammers took over.digg users formed a diaspora and moved to reddit.many sections of reddit are overrun by the kind of people who hate ellen pao and everything she stands for. these people may have a point, but they are haters at the core and, like the digg user base, they are a barrier to mainstream success.i think reddit is going to look like a fight between an immovable object and an irresistable force and that just can't be good.
reddit’s chief apologizes after employee’s dismissal
reddit has jumped the shark.i remember when this happened with digg; digg reached a certain level of success, but then discovered that it's existing users were a barrier to acquiring new users and getting revenue. they picked a fight with their power users, who left, but never got anybody to replace them, so then the spammers took over.digg users formed a diaspora and moved to reddit.many sections of reddit are overrun by the kind of people who hate ellen pao and everything she stands for. these people may have a point, but they are haters at the core and, like the digg user base, they are a barrier to mainstream success.i think reddit is going to look like a fight between an immovable object and an irresistable force and that just can't be good.
the whole backlash against her has quite frankly been revolting. i no longer care what she did to offend so many people, but sympathise with her as this is undoubtedly a horrific experience for her.the firing of the key employee may of been stupid, but not deserving of some of the hatred being gleefully promoted across reddit. trying to get her photo coming up for searches of hitler, commenting on her physical appearance, all the horrible little shits on the internet are coming out in droves over this.the petitions opening (and longest) paragraph is idiotic and attempts to assassinate her characters and it's sad that &quot;censoring&quot; a community promoting hatred of obese people is something that motivates people to take democratic action.
reddit’s chief apologizes after employee’s dismissal
the whole backlash against her has quite frankly been revolting. i no longer care what she did to offend so many people, but sympathise with her as this is undoubtedly a horrific experience for her.the firing of the key employee may of been stupid, but not deserving of some of the hatred being gleefully promoted across reddit. trying to get her photo coming up for searches of hitler, commenting on her physical appearance, all the horrible little shits on the internet are coming out in droves over this.the petitions opening (and longest) paragraph is idiotic and attempts to assassinate her characters and it's sad that &quot;censoring&quot; a community promoting hatred of obese people is something that motivates people to take democratic action.
i think the community have gone beyond the point where an apology from ellen pao will be sufficient enough to quell the dissatisfaction users have with reddit. the only solution i can see is pao stepping down or being replaced, followed by some actual management policies and ways of keeping the community happen (acknowledging them would be a good start).the site has been on a downhill slope for a while now and as shown, this isn't a localised incident, a lot of people are not only angry about the handling of victoria's dismissal, but how the site is being run. why now? why is ellen pao only apologising for years worth of mismanagement of reddit after the community took a stand? this goes beyond what just happened, this has been a long time in the making. it comes across as a forced apology because before all of this blackout controversy, they were doing nothing. the community was being ignored, mods were running rampant shadowbanning and removing threads, mad with power. and ironically mods want better tools and more power? the promotion of krispykrackers just goes to show how out-of-touch reddit has become with its users.it's great that they're acknowledging there are issues and that they will do better, but i think it is too late. maybe i am wrong, but i just can't see things getting better or if they do, staying better for long. i have moved over to voat.co and when it comes back online, my 8 year old reddit account will be nothing more than an effigy to a site that was once great. i personally have nothing against ellen, the whole problem with reddit goes well beyond her and members of the community also share in the blame. the centralised approach reddit takes to management is its downfall and if they're not careful, we could see what happened to digg when they messed over power users happen to reddit as well (evident by the influx of users over at voat.co).
show hn: ttystudio – a terminal-to-gif recorder without the headaches
can it properly record zsh's completion dialogs? i recently spent two hours trying to record a 5 seconds terminal sequence [0] and all terminal recording tools i tried failed. i ended up using a screen recording tool.[0] <link>
i use licecap: <link>
show hn: ttystudio – a terminal-to-gif recorder without the headaches
i use licecap: <link>
every time i see posts about recording gifs, i'm always surprised byzanz (<link> isn't more well known. here's a gif i just recorded with it: <link> colors aren't perfect, but the file sizes are always surprisingly small. the one linked is 10 seconds long and about 500kb.it's kind of janky, but here's the script i've been using for the past year or so without fault for recording: <link>
show hn: ttystudio – a terminal-to-gif recorder without the headaches
every time i see posts about recording gifs, i'm always surprised byzanz (<link> isn't more well known. here's a gif i just recorded with it: <link> colors aren't perfect, but the file sizes are always surprisingly small. the one linked is 10 seconds long and about 500kb.it's kind of janky, but here's the script i've been using for the past year or so without fault for recording: <link>
i like that there is no required gui, but needing to install the node.js dependency sounds like a &quot;headache&quot; to me.
show hn: ttystudio – a terminal-to-gif recorder without the headaches
i like that there is no required gui, but needing to install the node.js dependency sounds like a &quot;headache&quot; to me.
as someone who grew up in the 90s where gifs became popular for their use in looping animations, i don't understand why these files became popular for this kind of use case of step-wise instructional material (or even worse, as general-purpose video containers). sure they may be more lightweight than videos, but isn't it frustrating to miss a step and have to wait for the entire gif to loop all over again? this can happen especially with tutorials that use gifs sprinkled throughout. by the time you scroll to them you end up halfway through the animation or aren't sure what step you're at and how long you need to wait for the repeat.maybe this is more of a browser-issue and if we're going to embrace abusing gifs as video containers perhaps browser vendors should give the user video player-style controls?
thinking forth (1984)
excellent book as an introduction to software engineering. also, forth is a fun language/live-environment to play around with. when i first started using forth (gforth) the live-programming matched with point-free programming is left with me the unshakable impression that 'this is what programming should be like.'
this was one of the first programming books i read as a kid, after brodie's &quot;starting forth&quot; and a bunch of not very memorable books about basic.it remains the standard to which i hold all programming books i read. the author's enthusiasm and patient but never patronizing style drew me in, and the book's recognition that language and methodology are not inseparable changed how i viewed programming; the observation that design and implementation a dance rather than a handshake changed how i looked at software.a classic worth reading even if you never intend to use forth.
thinking forth (1984)
this was one of the first programming books i read as a kid, after brodie's &quot;starting forth&quot; and a bunch of not very memorable books about basic.it remains the standard to which i hold all programming books i read. the author's enthusiasm and patient but never patronizing style drew me in, and the book's recognition that language and methodology are not inseparable changed how i viewed programming; the observation that design and implementation a dance rather than a handshake changed how i looked at software.a classic worth reading even if you never intend to use forth.
here's a pdf version that can open in your browser, for folks who don't relish opening unknown binaries from sourceforge:<link>
thinking forth (1984)
here's a pdf version that can open in your browser, for folks who don't relish opening unknown binaries from sourceforge:<link>
i am new to programming. so far i dabbled a bit in scheme, python, smalltalk(pharo). i quickly realized i don't care for python, but scheme is an awesome language(it's like doing abstract algebra a bit) and smalltalk is an unbelievable environment. now forth also piqued my interest. how is it different from, say, pharo? apparently, one of forth's selling points is related to &quot;philosophy of problem solving&quot;. in that regard, how does forth compare to scheme? for example, it's trivial to solve certain problems by recursion in scheme. thanks.
thinking forth (1984)
i am new to programming. so far i dabbled a bit in scheme, python, smalltalk(pharo). i quickly realized i don't care for python, but scheme is an awesome language(it's like doing abstract algebra a bit) and smalltalk is an unbelievable environment. now forth also piqued my interest. how is it different from, say, pharo? apparently, one of forth's selling points is related to &quot;philosophy of problem solving&quot;. in that regard, how does forth compare to scheme? for example, it's trivial to solve certain problems by recursion in scheme. thanks.
one of the best programming books i've read.
the troubled poly instruction of the vax [pdf]
two years after i logged a bug in apple's mpw c compiler, i received a developer cd with release note that explained how to reproduce my bug but then said &quot;don't do that&quot;.mac c compilers added &quot;pascal&quot; as a reserved word, this enabled one to link to toolbox apis that had the pascal calling convention.i wrote a c++ test tool for mactcp in which a member function returned a pointer to a pascal c function, for use as a callback from the network driver.my first attempt produced faulty machine code. while regressing the bug i found that increasing the lengths of the names of the member function or of its parameters would crash the compiler. not the resulting binary - the compiler itself.on the old mac os that took down the entire machine.
pff. if you're not working with 36 bits, you're not working with a full dec.-doug humphrey (digex)
the troubled poly instruction of the vax [pdf]
pff. if you're not working with 36 bits, you're not working with a full dec.-doug humphrey (digex)
the article also mention ediv, which caused the most hilarious bug explanation i ever heard.i worked on a vms device driver in 1990. we had to resolve every single crash, because dec support tracked the outcome of each crash dump file.our driver was crashing a vax 9000 at abbot labs, a nightmare because it was a mainframe-class machine. in every crash dump i could show that the registers contained impossible values for the code sequence, always traced back to code involving an ediv instruction (used to get a remainder).dec decided the problem was &quot;alpha particles penetrating the encapsulant&quot;. at first i thought they were joking, but they were serious. they replaced the water cooling module around the cpu. that didn't fix the problem, so they pushed it back to us.after much back and forth, they realized it was a microcode bug in the ediv instruction, and their microcode patch fixed it.
the troubled poly instruction of the vax [pdf]
the article also mention ediv, which caused the most hilarious bug explanation i ever heard.i worked on a vms device driver in 1990. we had to resolve every single crash, because dec support tracked the outcome of each crash dump file.our driver was crashing a vax 9000 at abbot labs, a nightmare because it was a mainframe-class machine. in every crash dump i could show that the registers contained impossible values for the code sequence, always traced back to code involving an ediv instruction (used to get a remainder).dec decided the problem was &quot;alpha particles penetrating the encapsulant&quot;. at first i thought they were joking, but they were serious. they replaced the water cooling module around the cpu. that didn't fix the problem, so they pushed it back to us.after much back and forth, they realized it was a microcode bug in the ediv instruction, and their microcode patch fixed it.
i wonder what vax would be capable of today if they had the same level of resources as e.g. intel. from what i've seen there are some super-powerful instructions, but the opcode map[1] is extremely irregular - even x86 has an octal structure to it - so superscalar decoding would be far more difficult. it's also not as compact of an encoding as x86, so the code density would be lower; x86, despite being cisc, tends to have more frequently used instructions be shorter, e.g. ~1/4 of the 1-byte opcode map is register-register/register-memory alu operations.[1] <link>
the troubled poly instruction of the vax [pdf]
i wonder what vax would be capable of today if they had the same level of resources as e.g. intel. from what i've seen there are some super-powerful instructions, but the opcode map[1] is extremely irregular - even x86 has an octal structure to it - so superscalar decoding would be far more difficult. it's also not as compact of an encoding as x86, so the code density would be lower; x86, despite being cisc, tends to have more frequently used instructions be shorter, e.g. ~1/4 of the 1-byte opcode map is register-register/register-memory alu operations.[1] <link>
as the article notes, dec's oses largely dodged the bullet by having good workarounds and in-kernel implementations for the missing instructions.open-source vax oses weren't so lucky. bsd's libm used emod pretty heavily (for modf() and the like), and this caused problems in unexpected places if you happened to be running on a newer machine that didn't have these instructions (stuff like: awk would crash!). so the oses had to follow suit as well, at least for the instructions that libraries / compilers would emit (which fortunately excluded most uses of the g and h floating types). the documentation available at the time was okay but.. imprecise.source: i wrote the emod implementation for openbsd/vax a long time ago; poly had already been done by netbsd. it's still there! <link>
porting third-party programs to templeos
it's really cool that people are doing stuff with templeos if for nothing else than to broaden their horizons. maybe when the aliens from id4 visit, we'll be ready.
the author of templeos posted to reddit/r/programming, and is commenting on it there:<link>
porting third-party programs to templeos
the author of templeos posted to reddit/r/programming, and is commenting on it there:<link>
&gt; the &quot;alien&quot; nature of the project makes it interesting.templeos would qualify in some ways as outsider art[0]. i wonder how many such &quot;outsider&quot;/&quot;alien&quot; projects there are out there...[0] <link>
porting third-party programs to templeos
&gt; the &quot;alien&quot; nature of the project makes it interesting.templeos would qualify in some ways as outsider art[0]. i wonder how many such &quot;outsider&quot;/&quot;alien&quot; projects there are out there...[0] <link>
frotz feels to me like a pitch perfect choice for extending templeos's ecosystem. a job well done in so many important ways.
porting third-party programs to templeos
frotz feels to me like a pitch perfect choice for extending templeos's ecosystem. a job well done in so many important ways.
would be funny if temple os ended up being better than everything else
snow – a layer 3 virtual network that uses public keys instead of ip addresses
this seems very similar to cjdns[1][1] <link>
a sweet hack, and full marks for humor in the faq.[1] q: is it secure? a: security is not binary. q: ok, how secure is it? a: it seems like you just asked that question. q: no, the first question was if it's secure, the second question was how secure is it. a: well now that wasn't even a question at all. tell you what, if you find an unreported security vulnerability i'll buy you a beer. [1] <link>
snow – a layer 3 virtual network that uses public keys instead of ip addresses
a sweet hack, and full marks for humor in the faq.[1] q: is it secure? a: security is not binary. q: ok, how secure is it? a: it seems like you just asked that question. q: no, the first question was if it's secure, the second question was how secure is it. a: well now that wasn't even a question at all. tell you what, if you find an unreported security vulnerability i'll buy you a beer. [1] <link>
i can answer more questions later today.the project is in the middle of a partial rewrite. the existing dht has several issues and i'm replacing it.the change is going to break compatibility, which made it into a much bigger change because it provided an opportunity to make several other compatibility-breaking changes. so i haven't been promoting the project recently and the dht bootstrap node is currently offline.there should be new code some time around the end of summer.
snow – a layer 3 virtual network that uses public keys instead of ip addresses
i can answer more questions later today.the project is in the middle of a partial rewrite. the existing dht has several issues and i'm replacing it.the change is going to break compatibility, which made it into a much bigger change because it provided an opportunity to make several other compatibility-breaking changes. so i haven't been promoting the project recently and the dht bootstrap node is currently offline.there should be new code some time around the end of summer.
this is similar to what i thought ipv6 ipsec should have been, auto-generated addresses: where address generation uses the hash of a public key. sure, the addresses would have to be longer (in a /48, you only have 80 bits of choice), but if ipv6 were longer to accommodate strong hashes, it would solve much of the problem of secure computer-to-computer communication in a decentralized way.right now, ipsec practically requires pki. but at google or amazon's scale, pki is far from an easy problem, distributing keys to millions of nodes must be painful. and auditing the system must be its own level of hell, as i doubt many internal pki systems attempt to manage devices at that scale. unlike a smartphone or a laptop, where you can rely on 2-factor authentication, a server must be single-factor authenticated. the server is the server, and that places a huge burden on correctly allocating certificates.and then there's the chicken and the egg problem: if you want to deploy pki to millions of existing servers, how do you do that and ensure every server is what it says it is? there's too many shaky links of trust involved for a system like that to stand up.i really like this idea, it's in many ways better than the idea i had about ipv6, because it uses the dns layer to advertise public keys. it's inarguably more extensible, to boot. my idea would fix ipv6 into a single standard for ipsec, this is much more flexible.
snow – a layer 3 virtual network that uses public keys instead of ip addresses
this is similar to what i thought ipv6 ipsec should have been, auto-generated addresses: where address generation uses the hash of a public key. sure, the addresses would have to be longer (in a /48, you only have 80 bits of choice), but if ipv6 were longer to accommodate strong hashes, it would solve much of the problem of secure computer-to-computer communication in a decentralized way.right now, ipsec practically requires pki. but at google or amazon's scale, pki is far from an easy problem, distributing keys to millions of nodes must be painful. and auditing the system must be its own level of hell, as i doubt many internal pki systems attempt to manage devices at that scale. unlike a smartphone or a laptop, where you can rely on 2-factor authentication, a server must be single-factor authenticated. the server is the server, and that places a huge burden on correctly allocating certificates.and then there's the chicken and the egg problem: if you want to deploy pki to millions of existing servers, how do you do that and ensure every server is what it says it is? there's too many shaky links of trust involved for a system like that to stand up.i really like this idea, it's in many ways better than the idea i had about ipv6, because it uses the dns layer to advertise public keys. it's inarguably more extensible, to boot. my idea would fix ipv6 into a single standard for ipsec, this is much more flexible.
i gave this a quick try, as i've been looking for something like this that works for several years.looks like the dht used for nat and resolving .key addresses is not currently online, at least my (very well connected) test machine wasn't able to connect to the 1 pre-seeded dht peer.anyone gotten it to work outside of a single machine and ideally thru nat?
cassowary – a constraint solving toolkit
you should use this nowadays: <link> is an implementation of the algorithm based on the seminal cassowary paper. it is not a refactoring of the original c++ solver. kiwi has been designed from the ground up to be lightweight and fast. kiwi ranges from 10x to 500x faster than the original cassowary solver with typical use cases gaining a 40x improvement. memory savings are consistently &gt; 5x.
the react native people looked at this and stuck with flexbox. <link>
cassowary – a constraint solving toolkit
the react native people looked at this and stuck with flexbox. <link>
here is an implementation for qt/qml that we use at ableton:<link> anyone interested in modern implementations and participating in the community of library implementers and users can check this website: <link> :-)
cassowary – a constraint solving toolkit
here is an implementation for qt/qml that we use at ableton:<link> anyone interested in modern implementations and participating in the community of library implementers and users can check this website: <link> :-)
for python + qt version check enaml - <link> - it was posted here from 28 days ago - <link>
cassowary – a constraint solving toolkit
for python + qt version check enaml - <link> - it was posted here from 28 days ago - <link>
you should probably point out that this repo is a much better js version: <link>
google self-driving car project monthly report [pdf]
i'm fascinated by the accidents. the av is stopped at a light. someone rear-ends it. minimal damage.probably similar accidents are occurring every minute between human drivers, going unreported as the rule.avs might one day even avoid this &quot;victimization,&quot; if these events keep following a predictable pattern. avs could exaggerate the gap, leave a precisely calibrated amount of extra space. when anticipating a rear end collision, the av would honk and flash brake lights while scooting forward.google's absolutely correct that its avs are never at fault in any of these accidents, legally speaking. does blame change though if there are ways the ai can prevent this series of similar accidents, but they choose not to?the av yields to those running a red light, even though getting t-boned wouldn't legally be the av's fault. that seems wise to me. is it inconsistent to expect the av to avoid getting t-boned, but not expect it to avoid getting rear-ended? i'm not sure...or, more broadly: how do you divide blame between two parties when one has superhuman faculties? is the ai responsible for everything it could have conceivably been programmed to prevent? or do you just hold it to a human standard?like all hard problems, neither extreme is very satisfying.
i have the weird feeling that this report hasn't been written by a human.
google self-driving car project monthly report [pdf]
i have the weird feeling that this report hasn't been written by a human.
while most human drivers have a hard time avoiding rear-end collisions in which they are the victim, it would save a fair number of people from gruesome deaths if they would build some sort of rear collision avoidance logic for situations where it may be possible for the system to get the car out of harm's way. there seem to be hundreds of accidents like this [1] annually where large trucks smash into cars stopped at red lights or that have slowed down during traffic jams.perhaps the cars should constantly be planning escape routes while slowing down and stopping with appropriate distance from those in front of it to allow for escape should it detect an inevitable collision from behind. even where the only possible escape route involves hitting another car, it should be able to make the decision that a light collision with a vehicle in another lane is perferable to a large truck hitting it at 70mph.[1] <link>
google self-driving car project monthly report [pdf]
while most human drivers have a hard time avoiding rear-end collisions in which they are the victim, it would save a fair number of people from gruesome deaths if they would build some sort of rear collision avoidance logic for situations where it may be possible for the system to get the car out of harm's way. there seem to be hundreds of accidents like this [1] annually where large trucks smash into cars stopped at red lights or that have slowed down during traffic jams.perhaps the cars should constantly be planning escape routes while slowing down and stopping with appropriate distance from those in front of it to allow for escape should it detect an inevitable collision from behind. even where the only possible escape route involves hitting another car, it should be able to make the decision that a light collision with a vehicle in another lane is perferable to a large truck hitting it at 70mph.[1] <link>
the thing that really stands out here isn't that the accidents occurred (which is sort of amusing), but rather the excellent analytics the car produced. the car knew where it was, how long it was stopped, the conditions at the time of the accident, and the relative velocities of the vehicle that caused the accident. this is going to change the nature of automobile accidents entirely. the amount of data we'll be able to collect from even the simplest fender bender will be fantastic.
google self-driving car project monthly report [pdf]
the thing that really stands out here isn't that the accidents occurred (which is sort of amusing), but rather the excellent analytics the car produced. the car knew where it was, how long it was stopped, the conditions at the time of the accident, and the relative velocities of the vehicle that caused the accident. this is going to change the nature of automobile accidents entirely. the amount of data we'll be able to collect from even the simplest fender bender will be fantastic.
i found the linked ted talk [1] fascinating.[1]:<link>
the abolition of work
an important question if you believe in the abolition of work as a worthwhile goal: how do we get there?i hope we're all suitably convinced by now that revolution doesn't seem to work that well, which leaves some kind of iterative evolutionary approach.for that to work, you'd need it to be feasible for a small group of non-workers to see better outcomes than they got from working, while still interoperating with the (much larger) group of workers.so what would that look like?
this sounds like a first-world problem. how about we abolish hunger / fix our food distribution systems or ensure access to safe drinking water? then we can double-back and end forced labor (the actual demand set forth in the article—somewhat weaker than the sensationalist title).
the abolition of work
this sounds like a first-world problem. how about we abolish hunger / fix our food distribution systems or ensure access to safe drinking water? then we can double-back and end forced labor (the actual demand set forth in the article—somewhat weaker than the sensationalist title).
might we instead ask for the abolition of pseudo-philosophy hidden in verbose writing? as i scan this dense thesaurus, i'm finding an awful lot of internal contradiction and a confused thesis.i think it might sound more profound than it actually is.
the abolition of work
might we instead ask for the abolition of pseudo-philosophy hidden in verbose writing? as i scan this dense thesaurus, i'm finding an awful lot of internal contradiction and a confused thesis.i think it might sound more profound than it actually is.
he describes work as an annoying thing to do in order to live. if work becomes fun or ludic, then it's not work. i agree with this. if on monday morning, you're pleased to join your colleagues and on friday, you'd rather have a beer with them instead of going back home; then, it doesn't feel like work anymore. if you have fun (if you play) while working, this is not considered as work (work having a pejorative connotation). the goal is not to abolish work but make work enjoyable.
the abolition of work
he describes work as an annoying thing to do in order to live. if work becomes fun or ludic, then it's not work. i agree with this. if on monday morning, you're pleased to join your colleagues and on friday, you'd rather have a beer with them instead of going back home; then, it doesn't feel like work anymore. if you have fun (if you play) while working, this is not considered as work (work having a pejorative connotation). the goal is not to abolish work but make work enjoyable.
while i think it would be difficult to abolish forced labor right now, i do believe he makes some very good points. it would be a start if we could get some consensus that forced labor is something we should try to get rid off, if it was possible, because it is used to control people and it makes people stupid due to lack of time for gaining knowledge/thinking/discussing. and i think this article is great for that purpose.&gt;as [adam] smith observed: the understandings of the greater part of men are necessarily formed by their ordinary employments. the man whose life is spent in performing a few simple operations… has no occasion to exert his understanding… he generally becomes as stupid and ignorant as it is possible for a human creature to become.”if we agree that abolishing forced labor should be our goal, we can start working towards making that possible. i see automation and basic income playing a big role in this for example.
new zealand is making cyber bullying a specific crime
one of the few members of parliament opposed to this speaking against the bill: <link>;we must do something, this bill is indeed something, therefore we must pass this bill&quot;there are already sufficient protections in common law against harmful speech and passing vague law that only applies to online speech just makes us look like idiots.
i don't think making it a specific crime is the way forward long term. as the article states, in most countries everything is already covered by existing legislation (and society's general view of common decency but that doesn't necessarily help in a court).the problem is one of implementation. how do you gather proof/evidence, how do you prove intent beyond reasonable doubt, and how do you support the victims during and after. a fair amount of the existing problem is similar to bullying in other area: the victims being scared to speak out either just through fear of the perpetrators or through the thought that nothing can and/or will be done. and other key problem is people in law enforcement (from the cops on the street all the way up to the judges and legislators) and people in society's support structures (parents, teachers, councillors, and so forth) not understanding: being out of touch with the technology, or facets of modern culture (cyber-bullying is a lot more common in the young and many who where young 20 or more years ago, and i'm including myself there, don't quite understand those people), or often both.sometimes the more specific a crime the easier it is for a good legal team (or just a clever arsehole) to find loopholes that allow them to get away with things that are effectively the same thing but are not covered by the exact wording, so great care needs to be taken in drafting the law.having said that: making it a specific crime might be a very useful stop-gap measure though. it at least tells both the victims and those on the other side that the situation is being taken seriously, brings the matter to sharper focus for the implementers/enforcers of the law so they'll see the need to fill the knowledge/experience gap, and to an extent brings the issue to increased public attention (hopefully with similar effect where needed).
new zealand is making cyber bullying a specific crime
i don't think making it a specific crime is the way forward long term. as the article states, in most countries everything is already covered by existing legislation (and society's general view of common decency but that doesn't necessarily help in a court).the problem is one of implementation. how do you gather proof/evidence, how do you prove intent beyond reasonable doubt, and how do you support the victims during and after. a fair amount of the existing problem is similar to bullying in other area: the victims being scared to speak out either just through fear of the perpetrators or through the thought that nothing can and/or will be done. and other key problem is people in law enforcement (from the cops on the street all the way up to the judges and legislators) and people in society's support structures (parents, teachers, councillors, and so forth) not understanding: being out of touch with the technology, or facets of modern culture (cyber-bullying is a lot more common in the young and many who where young 20 or more years ago, and i'm including myself there, don't quite understand those people), or often both.sometimes the more specific a crime the easier it is for a good legal team (or just a clever arsehole) to find loopholes that allow them to get away with things that are effectively the same thing but are not covered by the exact wording, so great care needs to be taken in drafting the law.having said that: making it a specific crime might be a very useful stop-gap measure though. it at least tells both the victims and those on the other side that the situation is being taken seriously, brings the matter to sharper focus for the implementers/enforcers of the law so they'll see the need to fill the knowledge/experience gap, and to an extent brings the issue to increased public attention (hopefully with similar effect where needed).
this is a law that will never help a single person, and eventually will be used and abused against people the state finds undesirable. really sad to see freedom of speech being killed off yet again in an idiotic pursuit of an illusion of safety.
new zealand is making cyber bullying a specific crime
this is a law that will never help a single person, and eventually will be used and abused against people the state finds undesirable. really sad to see freedom of speech being killed off yet again in an idiotic pursuit of an illusion of safety.
background from an overseas new zealander:new zealand's centre right national party under john key has made a lot of concerning moves regarding civil liberties, censorship, and the internet. a couple examples:expanding the gcsb (nz's nsa) to allow domestic spying <link>;objecti...kim dotcom's shakedown <link> view this bill as another attempt to control speech online with &quot;cyber bullying&quot; being just a useful phrase to push this sort of legislation through..
new zealand is making cyber bullying a specific crime
background from an overseas new zealander:new zealand's centre right national party under john key has made a lot of concerning moves regarding civil liberties, censorship, and the internet. a couple examples:expanding the gcsb (nz's nsa) to allow domestic spying <link>;objecti...kim dotcom's shakedown <link> view this bill as another attempt to control speech online with &quot;cyber bullying&quot; being just a useful phrase to push this sort of legislation through..
so - according to the bill, anyone with a complaint has to send it to a delegated agency that will be responsible for assessing each complaint. it is there to screen for trivial cases, etc.if there is cause, they can then send it off to a court which will then determine what is to happen. the court can refer it back to the agency for more attempts at mediation etc... before making a ruling.these are all reasonable checks on balances from the point of view of ensuring that this is not abused to censor speech etc. the courts are even instructed to take account of the &quot;intent&quot; of the communicator. so it's not like the nutso feminist-left - with their &quot;intent is not magic&quot; belief - are driving this bill.so from this point of view the bill is actually quite reasonable...of course, from another point of view - i.e. when you consider the sheer number of assholes on the internet, it remains completely insane. the stated intent of the bill is to provide timely redress to victims. lol - when hell freezes over.my prediction - the delegated agency is going to be woefully under-funded. as far as i can see in the legislation - it is actually toothless. any enforcement has to come from the courts. so people will learn to ignore the agency... feed-backing more cases onto the courts which see their time getting taken up because people can't get along on the internet. edit: the problem being that people will submit frivolous cases. lots of them.victims won't by-and-large get the timely redress promised - except for a couple of high profile cases that make it into the media. and this non-result will come at great expense.but thanks for being the test case nz... nothing like empirical confirmation of any point of view.
sophie wilson, acorn and the development of arm
the dramatisation &quot;micro men&quot; <link> covers some of the early history here, including the super-rapid creation of the bbc micro and a cameo by sophie wilson.risc os was roughly contemporary with windows 3.0 and apple's system 7, offering a cheaper and seemingly faster system (although rather idiosyncratic in its use of the mouse menubutton and drag-and-drop instead of save dialogs). it booted from rom in something like a second.
i think there's a lot of fondness for acorn, at least here in the uk but i'd like to offer a slightly more accurate history.i was the owner of many acorn machines including bbc b, master, a410, riscpc 600. the hardware, clearly designed or at least originated by sophie wilson was remarkable. it was robust, well designed and incredibly expandable. to this day there is not a single computer that actually made sense more than anything that acorn kicked out. a human could learn everything about it in intimate detail without a problem.however the software was a source of constant pain. firstly nothing was finished initially when the archimedes came out. the arthur os was apparently named as a &quot;a risc operating system by thursday&quot; because their internal os project, apparently unixlike, went down the crapper during development and they had to hack something up quickly so they had a minimum viable product. what i ended up with was a barely usable os that consisted of a quick port of acorn mos from the bbc master series and a naff gui chucked on top for my £1400 investment (a hell of a lot back then and even now) that wasn't fixed properly until risc os 2 came out in 1989 so i sat there with a lemon for a year. after that we were stuck with a cooperatively multitasked operating system with a worldview completely different to anything else at the time or in the future. a lot of progress was made but it never had any prospects despite a lot of us clinging onto the initial investment.now i certainly enjoyed the platform but in retrospect, i'd have invested my money in something else back then if i knew what was going to happen.i full respect the achievements here and more importantly the legacy (i have 12 arm processors still in various things in my house!) but for us footsoldiers who paid up back then, it wasn't all love and happiness.
sophie wilson, acorn and the development of arm
i think there's a lot of fondness for acorn, at least here in the uk but i'd like to offer a slightly more accurate history.i was the owner of many acorn machines including bbc b, master, a410, riscpc 600. the hardware, clearly designed or at least originated by sophie wilson was remarkable. it was robust, well designed and incredibly expandable. to this day there is not a single computer that actually made sense more than anything that acorn kicked out. a human could learn everything about it in intimate detail without a problem.however the software was a source of constant pain. firstly nothing was finished initially when the archimedes came out. the arthur os was apparently named as a &quot;a risc operating system by thursday&quot; because their internal os project, apparently unixlike, went down the crapper during development and they had to hack something up quickly so they had a minimum viable product. what i ended up with was a barely usable os that consisted of a quick port of acorn mos from the bbc master series and a naff gui chucked on top for my £1400 investment (a hell of a lot back then and even now) that wasn't fixed properly until risc os 2 came out in 1989 so i sat there with a lemon for a year. after that we were stuck with a cooperatively multitasked operating system with a worldview completely different to anything else at the time or in the future. a lot of progress was made but it never had any prospects despite a lot of us clinging onto the initial investment.now i certainly enjoyed the platform but in retrospect, i'd have invested my money in something else back then if i knew what was going to happen.i full respect the achievements here and more importantly the legacy (i have 12 arm processors still in various things in my house!) but for us footsoldiers who paid up back then, it wasn't all love and happiness.
this is ridiculous. an entire article about the creation of arm, and only a passing reference to steve furber, the guy who actually designed the chip itself. either there was an intentional bias here, or it was very poorly researched.here's an interview from the centre for computing history: <link>
sophie wilson, acorn and the development of arm
this is ridiculous. an entire article about the creation of arm, and only a passing reference to steve furber, the guy who actually designed the chip itself. either there was an intentional bias here, or it was very poorly researched.here's an interview from the centre for computing history: <link>
amazing woman. she needs a knighthood.
sophie wilson, acorn and the development of arm
amazing woman. she needs a knighthood.
our public library had an acorn electron for anyone to use : i have spent many free afternoons there until my parents doubled up my savings ( at age 12 ) and i bought my own.around the same time i entered high school and they had a full classroom full of networked bbc micros!*whoamias gadders mentioned : she should be knighted.
bbc micro bit computer's final design revealed
i can't be the only person why misread the title and got excited thinking they'd see a schematic or design notes for the original bbc micro...
what are the benefits of developing a new thing like this rather than using something existing, like a raspberry pi? cost?
bbc micro bit computer's final design revealed
what are the benefits of developing a new thing like this rather than using something existing, like a raspberry pi? cost?
the media pack with finalised technical specifications is at <link>
bbc micro bit computer's final design revealed
the media pack with finalised technical specifications is at <link>
i'm uncomfortable with being negative about it, but am i right in understanding the only display is led lights?a long time ago i was a kid with an interest in computers and i remember what it was like and it's hard to imagine this actually being interesting to kids.it sort of feels like it's trying so hard not to compete with other technology that it's become kind of pointless. it really should have been able to plug into a display.i'd love to be enthused because the initiative is an awesome one but a box with lights feel like it might be missing the inspiration factor.it would have been good if they had some sort of lego-like ability to connect them to each other or something to encourage kids to hook them up in series and make them communicate. heck maybe with legos permission it should have been lego connector compatible so it could be clipped into lego structures.feels like this little device is a bit of a missed opportunity.
bbc micro bit computer's final design revealed
i'm uncomfortable with being negative about it, but am i right in understanding the only display is led lights?a long time ago i was a kid with an interest in computers and i remember what it was like and it's hard to imagine this actually being interesting to kids.it sort of feels like it's trying so hard not to compete with other technology that it's become kind of pointless. it really should have been able to plug into a display.i'd love to be enthused because the initiative is an awesome one but a box with lights feel like it might be missing the inspiration factor.it would have been good if they had some sort of lego-like ability to connect them to each other or something to encourage kids to hook them up in series and make them communicate. heck maybe with legos permission it should have been lego connector compatible so it could be clipped into lego structures.feels like this little device is a bit of a missed opportunity.
we've been working with the bbc to design the micro:bit and have begun to create loads of resources for families and teachers here; <link>'ll have much more in the coming months. hope it's useful!
firefox bug 111373 - don't allow animated site icons
that bug only has 60 comments. here's one with 600+ comments and 400+ people in cc. <link>
i also hope firefox would prevent html5 youtube videos form autoplaying and autoloading. they will implement a such feature in the next version, but it doesn't seem to work properly now (it's beta, i know). and it's not clear to stop autoloading, either. does anyone have a good idea to block autoplay and load html5 videos?<link>
firefox bug 111373 - don't allow animated site icons
i also hope firefox would prevent html5 youtube videos form autoplaying and autoloading. they will implement a such feature in the next version, but it doesn't seem to work properly now (it's beta, i know). and it's not clear to stop autoloading, either. does anyone have a good idea to block autoplay and load html5 videos?<link>
for anyone who hasn't seen it, a favicon-based game:<link>
firefox bug 111373 - don't allow animated site icons
for anyone who hasn't seen it, a favicon-based game:<link>
it's a traplow priority issues can sometimes linger around for a very long time taking away precious focus of developers and creating distractions from adding real-value-features.
firefox bug 111373 - don't allow animated site icons
it's a traplow priority issues can sometimes linger around for a very long time taking away precious focus of developers and creating distractions from adding real-value-features.
the ticket is open so long because a workaround exists: close this tab and never open this web site again.
ask hn: how to learn about the history of computing? it is often remarked in the comments here that our &quot;field&quot; appears to have a very bad memory; that we repeat past mistakes and ignore past learnings. i would like to interpret these remarks as an advice to &quot;get schooled&quot;.<p>what are some good sources (books?) to get started on this? most things i can find appear to stop at turing / von neumann, but one would like to think that history hasn't stopped at that point in time.
computer history museum: <link> particular, software preservation group (spg): <link> <link> more in particular ;-) -- the videos at the oral history collection: <link>'re also on youtube -- <link> -- but the ones above have synced transcripts.to get a flavor, take a look at the one with bjarne stroustrup, really enjoyed it: <link> more in this category (with some big names): <link>
the most authoritative work is ceruzzi's a history of modern computing (<link> because it's written by an academic, not a journalist, it also has a great bibliography and footnotes. some of the works it cites that are very valuable in themselves, depending on your area of interest, are:- r. hodeson, crystal fire (on the invention of the transistor), <link> t.r. reid, the chip (on the ic), <link> e.w. pugh, ibm's 360 and early 370 systems, (on the evolution of computer architecture), <link>, as others have mentioned, soul of a new machine is awesome.i feel like you may be asking about computer science, though, not computer hardware. if so, pickings are slim. two that stand out are:- s. rosenberg, dreaming in code, <link> (not really a history of code, just the history of a single project)- m. campbell-kelly, from airline reservations to sonic the hedgehog, <link> (which, while not quite as amazing as the others, is the only history of the software industry as a whole i know of.)
ask hn: how to learn about the history of computing? it is often remarked in the comments here that our &quot;field&quot; appears to have a very bad memory; that we repeat past mistakes and ignore past learnings. i would like to interpret these remarks as an advice to &quot;get schooled&quot;.<p>what are some good sources (books?) to get started on this? most things i can find appear to stop at turing / von neumann, but one would like to think that history hasn't stopped at that point in time.
the most authoritative work is ceruzzi's a history of modern computing (<link> because it's written by an academic, not a journalist, it also has a great bibliography and footnotes. some of the works it cites that are very valuable in themselves, depending on your area of interest, are:- r. hodeson, crystal fire (on the invention of the transistor), <link> t.r. reid, the chip (on the ic), <link> e.w. pugh, ibm's 360 and early 370 systems, (on the evolution of computer architecture), <link>, as others have mentioned, soul of a new machine is awesome.i feel like you may be asking about computer science, though, not computer hardware. if so, pickings are slim. two that stand out are:- s. rosenberg, dreaming in code, <link> (not really a history of code, just the history of a single project)- m. campbell-kelly, from airline reservations to sonic the hedgehog, <link> (which, while not quite as amazing as the others, is the only history of the software industry as a whole i know of.)
some that i liked:- hackers : <link> the soul of a new machine: <link> show stopper! : <link> dealers of lightning: <link> where wizards stay up late: <link>
ask hn: how to learn about the history of computing? it is often remarked in the comments here that our &quot;field&quot; appears to have a very bad memory; that we repeat past mistakes and ignore past learnings. i would like to interpret these remarks as an advice to &quot;get schooled&quot;.<p>what are some good sources (books?) to get started on this? most things i can find appear to stop at turing / von neumann, but one would like to think that history hasn't stopped at that point in time.
some that i liked:- hackers : <link> the soul of a new machine: <link> show stopper! : <link> dealers of lightning: <link> where wizards stay up late: <link>
if you want a very detailed account of the super early history of electronic computing, george dyson's &quot;turing's cathedral: the origins of the digital universe.&quot;<link> great titles i'd recommend is steven levy's &quot;hackers&quot; <link> and phil lapsley's &quot;exploding the phone&quot; <link> you enjoy!
ask hn: how to learn about the history of computing? it is often remarked in the comments here that our &quot;field&quot; appears to have a very bad memory; that we repeat past mistakes and ignore past learnings. i would like to interpret these remarks as an advice to &quot;get schooled&quot;.<p>what are some good sources (books?) to get started on this? most things i can find appear to stop at turing / von neumann, but one would like to think that history hasn't stopped at that point in time.
if you want a very detailed account of the super early history of electronic computing, george dyson's &quot;turing's cathedral: the origins of the digital universe.&quot;<link> great titles i'd recommend is steven levy's &quot;hackers&quot; <link> and phil lapsley's &quot;exploding the phone&quot; <link> you enjoy!
i started steven levy's hackers and i'm really enjoying it. <link> as he wrote crypto and insanely great too, it seems to be his kind of thing.also folklore.org is a nice collection of fables on how the sausage got made.charles petzold's code is interspersed with enjoyable historical perspective too.<link>
ask hn: what is the actual purpose of docker? i'm hearing about docker every other day, but when i look into it, i don't understand the purpose of it.<p>i run many websites/applications that need isolation from each other on a single server, but i just use the pretty-standard openvz containers to deal with that (yes i know i could use kvm servers instead, but i haven't ran into any issues with vz so far).<p>what's the difference between docker and normal virtualization technology (openvz/kvm)? are there any good examples of when and where to use docker over something like openvz?
it serves as an amazing excuse to re-invent the wheel at your own workplace. it's a hot technology, and if you're not using it, it's because you're inept. rip all of the stable things out that everyone knew how to use and slap containers in there! if it's not working, it's because your not using enough containers.no security patching story at your workplace? no problem, containers don't have one either! if someone has shipped a container that embedded a vulnerable library, you better hope you can get a hold of them for a rebuild or you have to pull apart the image yourself. it's the static linking of the 21st century!
docker and openvz aim to do the same thing.docker is a glorified chroot and cgroup wrapper.there is also a library of prebuilt docker images (think of it as a tar of a chroot) and a library of automated build instructions.the library is the most compelling part of docker. everything else is basically a question of preference.you will hear a lot about build once, deploy anywhere. whilst true in theory, your mileage will vary.what docker is currently good for:o micro-services that talk on a messaging queueo supporting a dev environmento build system hostshowever if you wish to assign ip addresses to each service, docker is not really mature enough for that. yes its possible, but not very nice. you're better off looking at kvm or vmware.there is also no easy hot migration. so there is no real solution for ha clustering of non-ha images. (once again possible, but not without lots of lifting, vmware provides it with a couple of clicks.)basically docker is an attempt at creating a traditional unix mainframe system (not that this was the intention) a large lump of processors and storage that is controlled by a singular cpu scheduler.however, true ha clustering isn't easy. fleet et al force the application to deal with hardware failures, whereas vmware and kvm handle it in the hypervisor.
ask hn: what is the actual purpose of docker? i'm hearing about docker every other day, but when i look into it, i don't understand the purpose of it.<p>i run many websites/applications that need isolation from each other on a single server, but i just use the pretty-standard openvz containers to deal with that (yes i know i could use kvm servers instead, but i haven't ran into any issues with vz so far).<p>what's the difference between docker and normal virtualization technology (openvz/kvm)? are there any good examples of when and where to use docker over something like openvz?
docker and openvz aim to do the same thing.docker is a glorified chroot and cgroup wrapper.there is also a library of prebuilt docker images (think of it as a tar of a chroot) and a library of automated build instructions.the library is the most compelling part of docker. everything else is basically a question of preference.you will hear a lot about build once, deploy anywhere. whilst true in theory, your mileage will vary.what docker is currently good for:o micro-services that talk on a messaging queueo supporting a dev environmento build system hostshowever if you wish to assign ip addresses to each service, docker is not really mature enough for that. yes its possible, but not very nice. you're better off looking at kvm or vmware.there is also no easy hot migration. so there is no real solution for ha clustering of non-ha images. (once again possible, but not without lots of lifting, vmware provides it with a couple of clicks.)basically docker is an attempt at creating a traditional unix mainframe system (not that this was the intention) a large lump of processors and storage that is controlled by a singular cpu scheduler.however, true ha clustering isn't easy. fleet et al force the application to deal with hardware failures, whereas vmware and kvm handle it in the hypervisor.
for me, it is the ultimate in the idea in continuous delivery of &quot;build once.&quot; i can be very confident that the docker image i build in the first stage of my pipeline will operate correctly in production. this is because that identical image was used for unit tests, to integration and functional testing, to the staging environment and finally production. there is no difference than configuration.this is the core that docker solves, and in such a way that developers can do most of the dependency wrangling for me. i don't even mind java anymore because the classpaths can be figured out once, documented in the dockerfile in a repeatable programatic fashion, and then ignored.in my opinion the rest of it is gravy. nice tasty gravy, but i don't care so much about the rest at the moment.edit: as danesparz points out, nobody has mentioned immutable architecture. this is what we do at clarify.io. see also: <link>
ask hn: what is the actual purpose of docker? i'm hearing about docker every other day, but when i look into it, i don't understand the purpose of it.<p>i run many websites/applications that need isolation from each other on a single server, but i just use the pretty-standard openvz containers to deal with that (yes i know i could use kvm servers instead, but i haven't ran into any issues with vz so far).<p>what's the difference between docker and normal virtualization technology (openvz/kvm)? are there any good examples of when and where to use docker over something like openvz?
for me, it is the ultimate in the idea in continuous delivery of &quot;build once.&quot; i can be very confident that the docker image i build in the first stage of my pipeline will operate correctly in production. this is because that identical image was used for unit tests, to integration and functional testing, to the staging environment and finally production. there is no difference than configuration.this is the core that docker solves, and in such a way that developers can do most of the dependency wrangling for me. i don't even mind java anymore because the classpaths can be figured out once, documented in the dockerfile in a repeatable programatic fashion, and then ignored.in my opinion the rest of it is gravy. nice tasty gravy, but i don't care so much about the rest at the moment.edit: as danesparz points out, nobody has mentioned immutable architecture. this is what we do at clarify.io. see also: <link>
docker is a cute little tool that gives people who aren't that great at linux the illusion that they know what they're doing. throw in the use of some &quot;container&quot; semantics and people become convinced it's that easy (and secure) to abstract away the containers from the kernel.but it's not, at least in my experience; not to mention that as of now, anything running docker in production (probably a bad idea) is wide open to the openssl security flaw in versions of 1.0.1 and 1.0.2, despite the knowledge of this issue being out there for at least a few days.docker's currently &quot;open&quot; issue on github: <link> references: <link> <link>
ask hn: what is the actual purpose of docker? i'm hearing about docker every other day, but when i look into it, i don't understand the purpose of it.<p>i run many websites/applications that need isolation from each other on a single server, but i just use the pretty-standard openvz containers to deal with that (yes i know i could use kvm servers instead, but i haven't ran into any issues with vz so far).<p>what's the difference between docker and normal virtualization technology (openvz/kvm)? are there any good examples of when and where to use docker over something like openvz?
docker is a cute little tool that gives people who aren't that great at linux the illusion that they know what they're doing. throw in the use of some &quot;container&quot; semantics and people become convinced it's that easy (and secure) to abstract away the containers from the kernel.but it's not, at least in my experience; not to mention that as of now, anything running docker in production (probably a bad idea) is wide open to the openssl security flaw in versions of 1.0.1 and 1.0.2, despite the knowledge of this issue being out there for at least a few days.docker's currently &quot;open&quot; issue on github: <link> references: <link> <link>
&gt; what's the difference between docker and normal virtualization technology (openvz/kvm)? are there any good examples of when and where to use docker over something like openvz?docker is exactly like openvz. it became popular because they really emphasize their openvz application templates feature, and made it much more user friendly.so users of docker, instead of following this guide: <link> write a dockerfile, which in a simple case might be: from nginx copy index.html /usr/share/nginx/html so no fuzzing with finding a ve somewhere, downloading it customizing it, and then installing stuff manually, stopping the container and tarring it, docker does that all for you when you run `docker build`.then you can push your nice website container to the public registry, ssh to your machine and pull it from the registry. of course you can have your own private registry (we do) so you can have proprietary docker containers that run your apps/sites.from my perspective, the answer to your question would be: always prefer docker over openvz, they are the same technology but docker is easier to use.but i've never really invested in openvz so maybe there's some feature that docker doesn't have.
how i trained sheet reading using the web midi api
from a musician's point of view this sounds like a dangerous idea. training your hands on random sequences of notes which do not make sense musically and relying on visual feedback feels like it will do nothing to build the skill which you actually need which is the ability to associate hand movements to musical patterns.but then it is probably just what you need if you want to play crazy atonal music. what do i know?
this is great! i'm learning to read sheet music and play the piano at the same time and have found the same problem: i'm just memorising the music, not _reading_it.just this weekend i tried jalmus, but couldn't get it running and ended up trying to write something kinda similar to this:<link> mine just does one note at a time though and i didn't know about webmidi, so was using node with electron shell for midi access, definitely gonna switch it over to webmidi now though, thanks!
how i trained sheet reading using the web midi api
this is great! i'm learning to read sheet music and play the piano at the same time and have found the same problem: i'm just memorising the music, not _reading_it.just this weekend i tried jalmus, but couldn't get it running and ended up trying to write something kinda similar to this:<link> mine just does one note at a time though and i didn't know about webmidi, so was using node with electron shell for midi access, definitely gonna switch it over to webmidi now though, thanks!
i found this a while back and have been really enjoying it. http://www.synthesiagame.comwith a laptop that folds flat, you can prop it on the music stand of your piano. would be best with a touch screen, i think.
how i trained sheet reading using the web midi api
i found this a while back and have been really enjoying it. http://www.synthesiagame.comwith a laptop that folds flat, you can prop it on the music stand of your piano. would be best with a touch screen, i think.
this is a first step toward writing your own ear training software, like earmaster pro. it has chord training, interval training, etc. this is probably closest to melodic sight-&quot;singing&quot; (you can use a midi instrument too) which is randomly generated melodic sequences, although it's aimed at singers so no chords.there's also sightreadingfactory which generates random music to play as well. this one allows you to pick an instrument, level, time signature, and key. but it isn't interactive. it'd be great if they added web midi.
how i trained sheet reading using the web midi api
this is a first step toward writing your own ear training software, like earmaster pro. it has chord training, interval training, etc. this is probably closest to melodic sight-&quot;singing&quot; (you can use a midi instrument too) which is randomly generated melodic sequences, although it's aimed at singers so no chords.there's also sightreadingfactory which generates random music to play as well. this one allows you to pick an instrument, level, time signature, and key. but it isn't interactive. it'd be great if they added web midi.
stay tuned for awesomeness like this in my interactive sheet-music site soundslice (<link> :-)this, plus the ability to load in whatever piece of music you want to learn, plus the ability to listen to real audio recordings (as opposed to synthetic/midi), all available from the web, equals a lovely future for musicians.