m34

TIL! Initially I thought about the sprouting corpses in Grim Fandango, but I'll make it a stop for my next visit to the botanical garden in munich: https://www.botmuc.de/en/garden/gh_victoria_house.html

There at least the giant lily needs to be pollinated by hand as they are lacking the specialized beetles https://www.botmuc.de/en/audio_tour/202.html so I'd assume some gardens do think about these matters.

I was on the receiving end of numerous support cases caused by what has to be on the sub-dollar cent savings (per single sku) region when multiple mainboard manufacturers chose to use capacitors with slightly worse tolerances all of a sudden (~25 years ago).

So if the whole process of spec'ing and validating the quality of sourced materials was within their action space, ofc they'd choose (potential) fault-tolerance over price, as it was mission critical.

So there might be a reason why we refer to it today as space race and not race to the bottom.

It is the bridge that provides the REST API, not the bulbs.

Having a REST API means the complete setup is easier to tinker with through a defined protocol and not having to resort to hack with the bulbs or any zigbee/low-level things.

I used this to play a bed time indication sequence on multiple bulbs in the living room from MIDI notes.

Also as the Anker M5 is on the horizon [0] (sort of), I'm really curious how the consumer 3D printing space will develop in the very near future.

[0] https://ankermake.com

At some point it makes sense to update even if the content itself is "complete": supporting newer screen resolutions natively (instead of going with some kind of fallback behavior), making sure all the outdated and long since sunset 3rd party SDK calls don't cause crashes etc.

Also if you managed to build, prepare (App Store metadata in different resolutions etc), submit and finally get your app shipped to the end user that was no small feat a couple of years ago. Probably not a very useful skillset to have if you only do it very infrequently (read: waste of time).

Requiring additional screenshots, icon sizes, universal app (iPhone+iPad, also supporting split view), new copy for different types of meta (e.g app sub title) for all the locales you probably had translated externally at some point, new privacy guidelines etc.. all not very attractive to get into even if not forced to update like this, especially if you lose your ratings in the process.

Wondering if there are certain individuals/institutions/organizations that would have vested interests in any of this?

Looking at the amount of money that is spent on nation-level campaigning (for a term length of ~4 years) the sum short would be minuscule when compared to near-global reach to be gained, so maybe the total of folks chipping in one way or another weights in much more p.a. than what currently is "on the table".

Might be true for running stuff in different regions/AZs but if the provisioning region is down (e.g. deploying lambda@edge) one does not really have an alternative

Thanks for taking the time to write about the book. As someone who had a hard time applying their school-taught knowledge about vectors and matrices when trying to understand OpenGL and Direct3D back in the early days ("why isn’t there a proper 'camera' object I can use") I really appreciate when people make an effort to offer alternative POVs to get deeper into topics they might not be familiar with.

Sometimes the right kind of intuition is all it needs to make it click. Sometimes it's that tiny bit of knowledge one is missing to get the whole picture and suddenly everything makes sense.

(Btw I think we might have met ages ago at a conference or two in Cologne)

Not relevant for the broader content and brand marketing approach discussed here but I repeatedly and decisively clicked on ads on readthedocs, resulting in conversions a couple of times (mostly eBooks).

Never really thought deeply about the why, but probably related to some of the offers appearing more relevant to me (in terms of context and not browsing history/social graph) .

Propulsion aside, I really wonder what the human species turns out to be like in say a couple of hundred years.

Hopefully our solar system isn't the only place where human DNA is found; that said, I'm curious what'll be left of humans as we know today.

With tools like CRISPR accelerating adoption to new environments and increased resilience towards hostile situations (zero-g, radiation etc)

Thanks for the clarification. I understand it's more about "exploratory" refactoring.

Thinking further I might have silently adopted a self-imposed "keep track of edit states and memoization in the wetware stack" approach, which I realize now is something that is far more exhausting than offloading to the tools whose purpose it is to show where the missing bits are.

Not sure how properly implemented refactoring would lead to compile errors that were not there before (maybe due to some Spring configurations or @Annotations not being considered?)

My usual pain point with eclipse was mostly package refactoring always leading to tree conflicts with SVN repos.

But that was ages ago and back then using Idea was way ahead of eclipse wrt refactoring and overall developer experience/productivity for us.

Interesting. Didn't know about it being this localized.

[1] has a chart showing the percentage of kids born in 2012 getting full measles vaccination within their first two years by county.

[1] https://www.sueddeutsche.de/bayern/oberbayern-murnau-hauptst...

Nice comparison. I wonder what the differences between both would be on real hardware (graphics adapter+CRT screen), especially for criteria like vibrancy and apparent smoothness.

I‘m aware that emulators nowadays ship with tube distortion and scanline filters/shaders, but is there a more "physical model"-based approach that properly implements raster and pixel over-/afterglow?

Not in infosec but probably b/c you‘d have to jump some hoops to get your code to have "side effects" with functional.

So from a security perspective it's way easier to review/audit functional code.

"Don’t have a proper use case for an ultra portable rn but having a large fresnel lens sheet fixture in front of it would really make for an awesome coffee shop coding experience." - S. Lowry

For reference, there's Web Monetization [1] which tries to solve exactly that.

As others have noted it all boils down to user agent support. Otherwise most publishers probably won't consider giving up ad or subscription financed models.

Also, forcing users into subscriptions allows for better demographics data/statistics.

[1] https://webmonetization.org/docs/explainer/

Agreed. Anectodal ofc: I thought about creating something similar - an app that would take my headshot and randomly alter metrics like eye distance and other general ratios etc for use as profile images for various social networks, thinking it might improve recognizability for people I actually know / have met.

However, I quickly came to the realization that the metrics I'd try to alter would probably not be sufficient and reveal enough information that the whole thing would be rendered moot.

A nice first step to remediate trust (or at least shift trust relationship to other parties) would be for vendors to implement highly restricted sandbox models (i.e. not allowing _any_ network access and restrict/alter ways of in- and output, like adding noise and artefacts to image data that can leave the app e.g. via share/save to camera roll).

Maybe via NSUbiquitousKeyValueStore[1]?

Its purpose is synchronizing app state data across devices via iCloud.

[1] https://developer.apple.com/documentation/foundation/nsubiqu...

As others have mentioned VLAN is an opt-in step and requires support from the hardware.

I also DONT want those devices to be able to connect to the internet: I have a D-Link webcam that has (had?) some issues around being exploitable remotely via the MyDLink or whatever it‘s called service. I don’t want to have (more) devices sitting in my network that open it up from the inside.

Also I need my guests should be able to access the internet without me having to whitelist their MAC address.

Not really.

It‘s mostly a blend of many different tutorials/blog posts/forums on hostapd, raspbian, dnsmasq and the likes.

I took notes during both times when I set this up (first time the sdcard died shortly after, no backup of sorts; second time some changes in drivers, raspbian lite and other tooling were different so I had to start over).

I thought this project would make a good first blog post, maybe I can gist some steps / bullet points next week or so.

Yes, I allow _some_ more or less we’ll defined traffic from home network to iot specifically to allow control.

I also do run HomeKit, homebridge but devices/hubs are in the dedicated network.

(tech) people tend to laugh at me/pull the tinfoil hat card for putting my dlink/iot stuff behind a very restrictive, dedicated, iptables filtered, hostapd based custom network running on my pi zero w that isn’t allowed to talk to the home network or internet at all.

As mentioned by others, I guess it really needs severe identity theft/abuse with vital services until people realize that today‘s IoT 'plug & play' is worse than than the level of 'plug & pray' we‘ve seen in the early PCI/USB/Win98 era (that only impacted your local device functionality).

Yes. Stop learning frameworks and start learning to embrace concepts and different paradigms.

If all you have is a hammer, everything looks like a software project.

Finally. Card activation was only possible by calling my bank and for now this only works with the credit card, not my debit card.

Using my series 1 watch at the supermarket later worked like a charm.

Great experience!

Looking forward to me educating cashiers about this for the next couple of months (still have some of them trying to grab my card)

I spent a good amount of time getting AWS AppSync to work with different GraphQL clients last week.

Looking forward to check out this one.

Thanks for sharing!

You‘re right, I didn’t go into concrete detail.

It‘s also hard to describe but the best analogy I can come up with: picture a CMS that actually is about _content_ instead of being tied to presentation. So e.g. writing an article about a certain historical event at a certain place consists of stringing all the information and relationships together.

Bringing the correct pieces together eliminates errors and gives a piece of information more meaning when used in different contexts.

Being able to correctly reference e.g. Venice, Italy instead of Venice LA, CA makes a huge difference when looking up time schedules, weather forecast, flight connections etc. Sure there are IATA codes for airports. Wouldn‘t it be great to mention Springfield in an article and having all information about that place (as well as all „backlinks“)?

I also don‘t think it is a technology problem.

However, I‘d like to think about this more in terms of DRY principle of information. There are publications on the web that solely exist to duplicate short-lived, relatively low quality information and putting ads on it. This may be acceptable for some consumer‘s point of view, but fails to create long-lasting contribution to mankind.

Just dumping all bits we currently store into massive archives is possible but taking measures to keep the amount of „information archeology“ needed to understand this data feels the right thing to do.

I‘ll iterate on that.

Sorry if this reads even more confusing and esoteric, need some sleep now.

Every few months my mind circles around that topic.

I think it won’t work if the underlying transport/presentation is „the web“ (i.e as in Web 2.0).

Instead of decorating semantics/hints around the actual information mostly for SEO reasons it should work the opposite: using all available semantic hints and information bits there already are to create new information by aggregating and putting things in a new context.

It adds value while building upon previous knowledge and allows information and context to be relevant indefinitely.

Fwiw as a developer, being able to debug shaders, tinker with ARKit and have some sort of middle-ground baseline specs as my primary/everyday device is a huge win for me personally.

When „designing“ views I tend to face challenges from the other end of the spectrum: „what am I going to put here so there‘s not too much empty/negative space on the larger screens without making the layout look empty or clunky?“