Avian (tablix.org)

Dear Mister Reginato, Thank you for sharing with us your work around Hardware solutions for the Internet of Things. Especially, I also agree that a such work is definitely needed to have an interesting substrate to explore such concepts and to my knowledge, I haven't been able to find any suitable platform for this. A potential candidate could have been the Olimexino-STM32 : http://www.olimex.com/dev/olimexino-stm32.html Its decent computational power (STM32 Cortex-M3), autonomous operations capabilities thanks to its JST connector for a LiPo battery and UEXT connector for wireless capability, without, of course, forgetting to mention its Arduino shields compatibility, makes it a potential candidate. However, its main drawbacks are : -its size that doesn't make it practical for real world deployments -its low RAM & Flash quantity that prevents it to deploy developers friendly middlewares (Java, .Net...) That's why, my partner and me are working on the VSN II project. The VSN II is an evolution of the VSN platform : http://www.netclamps.com Especially, we would greatly appreciate to invite you to : -a further watching of the video entitled "Versatile Sensor Node - A Platform for the Sensor as a Service Concept" : http://videolectures.net/wsnsme2010_smolnikar_vsn/ -a further reading of the blog post entitled "VESNA" : http://www.tablix.org/~avian/blog/archives/2011/12/vesna/ With the VSN-II, we will advance further in the state-of-the-art by reducing the size…

I just checked the settings again. Indeed there is a "Play alarm sound" setting if you scroll down. I guess it was enabled by default in my case (good, since otherwise I might not know that my phone made the call from my backpack). Slightly off topic, but I did not even notice before the Emergency SOS settings screen has anything below the break. This UI design is just terrible. There is absolutely nothing hinting that you can scroll down: https://www.tablix.org/~avian/android_13_emergency_sos_settings.png (Looking at the screenshot now, you can just about see that alarm sound setting below the slightly transparent bottom row. That's just about impossible to see on the real phone, plus the row has the usual Android set of buttons on top, obscuring the text even further).

For the eMMC, quite probably. The BBB Rev B BOM lists a Micron chip that tops out at 30MB/s read and 6.6MB/s write (pretty close to measured). The BBB Rev C BOM lists Micron chips in that range but also lists chips like the Kingston EMMC04G-M627 which is capable of 250MB/s read and 25 MB/s write. This link seems to indicate that the Rev C is around 2x faster on eMMC. https://www.tablix.org/~avian/blog/archives/2017/08/beaglecore_module_… (the RPi Zero numbers seem to correlate with yours so it seems you are measuring the same things) So, the eMMC numbers are going to be highly specific to the board manufactured.

According to something I read somewhere. The ZX81 floating routines did incorperate some unique math: (2^32) - ((2^32)-1) did not return 1 And the group of Cambridge mathamaticians that wrote the ROM turned out to be one man. "ZX81 ROM Assembly Listing" https://www.tablix.org/~avian/spectrum/rom/zx81.htm

I've just done a bit of googling and this guy https://www.tablix.org/~avian/blog/articles/galaksija/ Has designed a replica system, with some minor mods to allow for newer easier-to-get logic chips, and better compatibility with newer Z80 CPUs. He offers up the whole design for download - so anyone should be able to build one. I've bookmarked it... I'm definitely interested in making one to add to my retro collection.

https://www.tablix.org/~avian/blog/archives/2019/04/google_is_eating_o… https://news.ycombinator.com/item?id=19756125 From a few months ago. Self-hosted email getting dropped for seemingly no reason.

For those miss Arnt's point, see how the real life Z80 code looked like here: https://www.tablix.org/~avian/spectrum/rom/zx82.txt That's the disassembly of the whole ZX Spectrum ROM which has the built in BASIC interpreter with the floating point support.

>, and I tend to be unsure how bad it actually is: sometimes it does seem pretty bad, other times it sounds like it's fine, and possibly the chatter about failed deliveries is caused by misconfigured servers and/or misunderstandings. It's not just misconfigured email server settings like DKIM, SPF, DMARC etc. One can correctly set all of those and still have the outgoing emails rejected or spamholed. Why? Because the big email players like GMail, Microsoft Outlook.com, etc use black-box heuristics of reputation datapoints that exist outside the boundaries of email settings such as... "amount of email volume", "# of spam abuse reports from ip block", etc. Because "sender reputation" cannot be encoded into an email configuration (DKIM/SPF/DMARC/etc), that's why nobody can provide a convenient Docker container with a perfectly working self-hosted email server that can reliably send email. If such a thing existed, the spammers would use it as well! A datapoint such as "volume of email from this ip" is an unstated behavior/activity number and not an identity setting like DKIM. And the invisible heuristics keep changing which causes previous email setups that worked -- to later stop working for no obvious reason. Why? Because there's a constant arms race between spammers and email filter algorithms. This means others' email spam heuristics that keep evolving and that you don't control -- blocks your self-hosted outbound emails without warning. That's why you have…

Wikipedia is a great example of a web site that has resisted the trend! It is a pretty ideal democracy for those of us whose ISP or nation-state[0] doesn't prohibit us from viewing it. There was a project similar to Wikipedia, but for semantic data. It lasted for a little while before being swallowed up by Google and shut down[1]. Granted there are some alternatives, but after investing some time working with freebase data, I should be allowed to hold a grudge. Google played a key role in muzzling more widespread usage of RSS[2], along with Twitter and Facebook discontinuing support for it. Similarly, jabber[3], XMPP[4]. These days it's risky to even host your own mail server, since most people you correspond with are likely to use one particular email service that may arbitrarily block messages from lesser-known mail services[5]. [0] https://en.wikipedia.org/wiki/Censorship_of_Wikipedia [1] https://groups.google.com/forum/#!topic/freebase-discuss/WEnyO8f7xOQ [2] https://www.fastcompany.com/3013890/reader-may-have-died-to-feed-googl… [3] https://blog.twitter.com/en_us/a/2006/use-twitter-by-instant-message.h… (couldn't easily find press of the discontinuation of this service) [4] https://news.ycombinator.com/item?id=9266769 [5] https://www.tablix.org/~avian/blog/archives/2019/04/google_is_eating_o…

I found this project a while back when I was searching for information on how to drive lavet stepper motor[1] inside these kind of clocks[2]. My project is similar in a way that you have to manually drive this motor, idea is to convert existing 12-hour clock to 'week' 168-hour clock. Hour hand would make full rotation only each 168 hours, showing current day of the week and approximate part of the day. Very cool project to tinker with electronics and gears, you have to figure out timing(30ms energize, 970ms rest, repeat in reverse polarity) and how to drive motor(use half-bridge circuit or motor driver)[3], you have to deal with inductive 'kick' flyback voltage spikes and protect IC from it[4], and figure out mechanical gears[5] (typical quartz mechanism[6]) [1] https://en.wikipedia.org/wiki/Lavet-type_stepping_motor [1.1] https://resonanceswavesandfields.blogspot.com/2011/03/understanding-qu… [1.2] https://resonanceswavesandfields.blogspot.com/2011/03/understanding-me… [1.3] http://mysite.du.edu/~jcalvert/tech/quartz.htm [1.4] https://www.tablix.org/~avian/blog/archives/2016/04/clockwork_part_2/ [1.5] https://www.tablix.org/~avian/blog/archives/2016/03/clockwork/ [2] https://en.wikipedia.org/wiki/Quartz_clock [3] https://en.wikipedia.org/wiki/H-bridge [3.1] https://www.microtype.io/h-bridge-circuit-design/ [3.2] http://homepage.divms.uiowa.edu/~jones/step/circuits.html [4]…