The standard erasure codes (polynomial ones) require that the field size (so alphabet size) is larger than the number of symbols in the codeword. Clearly we can have arbitrarily-close-to-ideal erasure codes even for smaller alphabet sizes (because noisy coding theorem). Are there some that can be easily described?
It seems to me that a "reverse plotter" that measures its distance to fixed points (via string length) as well as orientation (not sure which approach would be easiest here) and displays the appropriate part of a drawing would be helpful for drawing patterns on cloth, and would be a very compact device (e.g. in comparison to a drafting table, or even just the parallelogram angle transfer thingy from a drafting table). Do people make them?
Manual plotter for drawing clothing patterns (string with distance graduations, passed through holes in fixed LEGO bricks).
@delroth That sounds a bit like the challenge from Underhanded C Contest 2008 (http://www.underhanded-c.org/_page_id_17.html):
> write a short, simple C program that redacts (blocks out) rectangles in an image.
> The challenge: write the code so that the redacted data is not really gone.
we're getting to the point that the contradictions and shortcomings are starting to become more apparent...
- things like moderated conversations are impossible if you don't actually have a concept of a "conversation".
- there's so many different ways to do "groups" that it's a running joke at this point, because everyone has a different idea of what a "group" is. it's the "blind men feeling an elephant" problem.
- things like forums and subforums, chat rooms, etc are not easily possible rn.
Going to just walk around the Computer History Museum in Mountain View carrying my teapot until security tackle me for stealing the historic artifact
I think I've finally seen the light of the #SemanticWeb.
I think web browsers should give users a way to register apps to handle displaying certain #RDF schema types.
E.g. if I open an ActivityStream URL, the browser should load my preferred client in the same way that clicking a PDF in my filesystem will open up my PDF viewer.
Users would then be able to bring their own interfaces to data instead of relying on some closed source proprietary app interface.
Also opens the door to mixing data
If you need to solve 100% of a problem to get any benefit and the last 5% is impossible, *any* work on that problem is a waste of time. Figure that up front. Go work on something which actually can protect your users and systems and colleagues.
Because a friend found this useful yesterday:
Before tackling a problem, figure out whether it's the sort of problem where when you've solved 80% of the problem, you've solved 80% of the problem, or the kind where solving 80% means you've solved 0% of the problem.
This is especially important in security and privacy because that last 5% might be impossible.
The Church Slavonic used two letters to denote nasal /o/ and nasal /e/ - the Big Yus (ѫ), and the Little Yus (ѧ). My uneducated guess is that the weirdly shaped symbol ѫ looked too much like a guy in a tie, so the Polish scribes went for more familiar A-like shape of ѧ when denoting a nasal /o/. The middle leg transformed into a small tail, and centuries later whoever is learning Polish will get rightfully confused by Ą being pronounced as /ɔ/.
@rysiek I think this is similar-yet-distinct to your recent thread on various ML-based generators of something.
So I've been building a 100% analog polyphonic synthesizer with an unique twist. To use only vacuum tube era technology from the 1930s.
Over 300 neon gas diodes create the sound you hear. Pretty awesome for technology from 100 years ago.
Still a work-in-progress, but I wanted to post a video of it with the innards spread out across the workbench. : }
I call it the "Neon String Machine"
The excluded middle appeal was granted! (https://efile.dcappeals.gov/public/caseView.do?csIID=63269)
I have no clue what the 2 year pause was about, why the appeal was granted as a result of the _appellee's_ motion to (seemingly) "get on with it" (i.e. why the appellant didn't care to file a similar motion way earlier), or when/under what case number the Superior Court will pick the case back up. The original case is marked as "closed" in the Superior Court.
At the same time: the lack of consequence in case numbers is grating (DC Superior Court uses spaces as separators, other courts replace them with dashes, and the DC Superior Court's lookup thingy doesn't understand those; the lookup thingy also deals in some broken way with parties with a middle name *and* the lookup thingy doesn't ever provide people with stable URLs for anything...).
I enjoy things around information theory (and data compression), complexity theory (and cryptography), read hard scifi, currently work on weird ML (we'll see how it goes), am somewhat literal minded and have approximate knowledge of random things. I like when statements have truth values, and when things can be described simply (which is not exactly the same as shortly) and yet have interesting properties.
I live in the largest city of Switzerland (and yet have cow and sheep pastures and a swimmable lake within a few hundred meters of my place :)). I speak Polish, English, German, and can understand simple Swiss German and French.
If in doubt, please err on the side of being direct with me. I very much appreciate when people tell me that I'm being inaccurate. I think that satisfying people's curiosity is the most important thing I could be doing (and usually enjoy doing it). I am normally terse in my writing and would appreciate requests to verbosify.
I appreciate it if my grammar or style is corrected (in any of the languages I use here).