arunarunarun

Some of this is also a question of "do you want to take the risk of having an indelible black mark in your travel history?"

As an example, the US asks for your travel history (where you went and why) and a list of your social media accounts. It would be trivial to correlate a conference related social media post with a stated reason of tourism and flat that.

They might not do this, but I certainly would not want to jeopardise all future travel for that if.

Author of the post here.

Logistically, it's a _lot_ harder for a person/team to organise a conference in a location they don't live in. There's logistics of venue, payments to vendors if you're organising food/travel/hotels, you might have volunteers for registration, information, etc. and it's easiest to find those in your local community. And finances across borders are anothe huge wrinkle.

It's not impossible, but certainly adds significant complexity.

Generally, when you apply for a visa, there's documentation guiding you towards the correct type of visa based on purpose of visit. Everything I've seen buckets conferences under "business visa".

I recently wrote something similar to pull data from Kaiterra Laser Eggs (also in Haskell!) -- https://github.com/ford-prefect/laser-egg/

That's what all the effort around Flatpak is for

edit: link to Christian's post about it -- https://blogs.gnome.org/uraeus/2016/06/21/fedora-workstation...

Kudos to your team -- having access to the fantastic work you guys have done (especially the AudioProcessing module that we use in PulseAudio) has been very useful indeed.

Thanks for the explanation. I've corrected the post to not assert that the FFT is necessary.

That is actually the default with the webrtc beamformer (the sample recordings point straight forwards which effectively works out to being between the two microphones).

1. I was pretty clear about not being a DSP-person

2. The module provides infrastructure for other beamformer implementations to be plugged in, my implementation is intended to be a trivial test

3. module-beamformer did not ship (the link points to a branch in my git repository)