Podcasts about 34mb

実施日時: 2024年10月6日　日曜礼拝　メッセンジャー: 門谷 信愛希 牧師　聖書箇所: エステル9章1〜10章3節　長さ・サイズ: 46:25 (21.34MB)　内容紹介: ついに終章を迎えたエステル記は、現代的な感覚では違和感や葛藤を感じる場面が続きます。しかし、当時の国際情勢や政治体制を把握すると、表面的な印象とは異なった「実像」が見えてきます。エステルは何を願い、王は何を考えたのか。そして、信仰者はそこから何を汲み取っていけば良いのか。丁寧に解き明かしていきます。

実施日時: 2024年8月18日　日曜礼拝　メッセンジャー: 栗原延元牧師　聖書箇所: ローマ10章16～21節　長さ・サイズ: 40:47 (37.34MB)

In our latest episode of "Bits, Bytes, and Banter," we dive deep into the current turbulence in the gaming industry. First, we discuss Epic Games facing yet another fine, this time $1.2 million from the Dutch Authority for Consumers & Markets, for exploiting children with Fortnite's microtransactions. We then shift to Ubisoft's major announcements and cancellations, including the reveal of Assassin's Creed Shadows, which introduces dual protagonists—a samurai and a shinobi—and the surprising cancellation of The Division Heartland. Additionally, we marvel at the breakout success of Animal Well, a critically acclaimed Metroidvania that's only 34MB in size. Join us as we break down these headlines and explore what they mean for the future of gaming. 0:00 Intro 0:43 Updates 6:28 Epic gets fined over Fortnite shop https://tinyurl.com/3ct3mdpf  14:48 The first Assassin's Creed Shadows trailer shows off dual samurai / ninja action https://tinyurl.com/3xujx2s5  25:12 Ubisoft has canceled The Division Heartland  https://tinyurl.com/5n7dbk3u  37:19 Metroidvania hit Animal Well is only 34MB https://tinyurl.com/ycykt6jr  48:09 Tierlist https://tiermaker.com/create/video-game-series-928883  1:33:31 Outro Leave a LIKE and a comment, thanks for watching/listening! ----------------------------------------------------------------------------------- PODCAST ►► https://anchor.fm/m2podcast AMAZON Music ► https://music.amazon.com/podcasts/091902c3-b83b-487c-8fe7-4c96787434fe/M2-Podcast APPLE ► https://podcasts.apple.com/podcast/id1531832410 BREAKER ► https://www.breaker.audio/m2-podcast-2 CASTRO ► https://castro.fm/podcast/6f69d373-d879-46d9-9f1c-bcf7c4bf1741 GOOGLE ► https://podcasts.google.com/feed/aHR0cHM6Ly9hbmNob3IuZm0vcy8zNTYwNWZiMC9wb2RjYXN0L3Jzcw== OVERCAST ► https://overcast.fm/itunes1531832410/m2-podcast POCKETCASTS ► https://pca.st/5jghvf6e RADIOPUBLIC ► https://radiopublic.com/m2-podcast-GMZkY4 SPOTIFY ► https://open.spotify.com/show/2VedhO03IRoHERJqF6Sy87 STICHER ► https://www.stitcher.com/podcast/m2-podcast TUNEIN ► http://tun.in/pj3ZI #podcast JOIN THE DISCORD! ►► https://discord.gg/Kp5Gre6 FOLLOW THE TWITTER! ►►https://twitter.com/m2_podcast KyleHeath Socials: TWITTER ►► https://twitter.com/mrjkheath MadMikeWillEatU Socials: TWITTER ►► https://twitter.com/madmikewilleatu

実施日時: 2023年9月17日　日曜礼拝　メッセンジャー: 門谷 信愛希 牧師　聖書箇所: ピリピ4章6〜8節　長さ・サイズ: 44:17 (20.34MB)　内容紹介: 「感謝すること—」。誰もが良いことだと分かっていながら、これほど実行ができていないことも珍しいかもしれません。けれども聖書は一貫して「感謝することのチカラ」を語っています。そして、私たちには「感謝する力」が与えられているとも語ります。では、一体どうしたらそのようなことが可能になるのでしょうか。例話を交えながら、分かりやすくお話しします。

実施日時: 2023年4月16日　日曜礼拝　メッセンジャー: 門谷 信愛希 牧師　聖書箇所: 出エジプト記39章1〜43節　長さ・サイズ: 42:08 (19.34MB)　内容紹介: ついに完成する幕屋の全ての備品でしたが、作業に当たったイスラエルの民にはある顕著な特徴がありました。それは現代に生きるクリスチャンにとっての「教会」のあり方にも通じる、大切な原則を語っていました。聖書のことばに分け入りながら、学んで行きます。

実施日時: 2021年1月1日　日曜礼拝　メッセンジャー: 門谷 信愛希 牧師　聖書箇所: 詩篇91篇　長さ・サイズ: 29:08 (13.34MB)　内容紹介: 2021年初頭の元旦礼拝でのメッセージ。コロナ禍という大きな闘いの2020年を経験し、新しい年もなかなか先行きの見えにくい中を歩んでいる私たちに対して、聖書はどのような励ましの言葉を語っているのでしょうか。「疫病」のキーワードを含む詩篇91篇を通して教えられて行きます。2021年初頭の元旦礼拝でのメッセージ。コロナ禍という大きな闘いの2020年を経験し、新しい年もなかなか先行きの見えにくい中を歩んでいる私たちに対して、聖書はどのような励ましの言葉を語っているのでしょうか。「疫病」のキーワードを含む詩篇91篇を通して教えられて行きます。

実施日時: 2019年5月5日　日曜礼拝　メッセンジャー: 門谷 信愛希 牧師　聖書箇所: 創世記31章1〜20節　長さ・サイズ: 42:15 (19.34MB)　内容紹介:

実施日時: 2019年3月3日　日曜礼拝　メッセンジャー: 門谷 信愛希 牧師　聖書箇所: コロサイ3章5〜11節　長さ・サイズ: 46:37 (21.34MB)　内容紹介:

Eugene, Ryan and Dee got together to talk about games, ostensibly, but we spent many minutes talking about the first Star Trek movie. Enjoy! (34MB/48:25)

Second round of ZFS improvements in FreeBSD, Postgres finds that non-FreeBSD/non-Illumos systems are corrupting data, interview with Kevin Bowling, BSDCan list of talks, and cryptographic right answers. Headlines [Other big ZFS improvements you might have missed] 9075 Improve ZFS pool import/load process and corrupted pool recovery One of the first tasks during the pool load process is to parse a config provided from userland that describes what devices the pool is composed of. A vdev tree is generated from that config, and then all the vdevs are opened. The Meta Object Set (MOS) of the pool is accessed, and several metadata objects that are necessary to load the pool are read. The exact configuration of the pool is also stored inside the MOS. Since the configuration provided from userland is external and might not accurately describe the vdev tree of the pool at the txg that is being loaded, it cannot be relied upon to safely operate the pool. For that reason, the configuration in the MOS is read early on. In the past, the two configurations were compared together and if there was a mismatch then the load process was aborted and an error was returned. The latter was a good way to ensure a pool does not get corrupted, however it made the pool load process needlessly fragile in cases where the vdev configuration changed or the userland configuration was outdated. Since the MOS is stored in 3 copies, the configuration provided by userland doesn't have to be perfect in order to read its contents. Hence, a new approach has been adopted: The pool is first opened with the untrusted userland configuration just so that the real configuration can be read from the MOS. The trusted MOS configuration is then used to generate a new vdev tree and the pool is re-opened. When the pool is opened with an untrusted configuration, writes are disabled to avoid accidentally damaging it. During reads, some sanity checks are performed on block pointers to see if each DVA points to a known vdev; when the configuration is untrusted, instead of panicking the system if those checks fail we simply avoid issuing reads to the invalid DVAs. This new two-step pool load process now allows rewinding pools across vdev tree changes such as device replacement, addition, etc. Loading a pool from an external config file in a clustering environment also becomes much safer now since the pool will import even if the config is outdated and didn't, for instance, register a recent device addition. With this code in place, it became relatively easy to implement a long-sought-after feature: the ability to import a pool with missing top level (i.e. non-redundant) devices. Note that since this almost guarantees some loss Of data, this feature is for now restricted to a read-only import. 7614 zfs device evacuation/removal This project allows top-level vdevs to be removed from the storage pool with “zpool remove”, reducing the total amount of storage in the pool. This operation copies all allocated regions of the device to be removed onto other devices, recording the mapping from old to new location. After the removal is complete, read and free operations to the removed (now “indirect”) vdev must be remapped and performed at the new location on disk. The indirect mapping table is kept in memory whenever the pool is loaded, so there is minimal performance overhead when doing operations on the indirect vdev. The size of the in-memory mapping table will be reduced when its entries become “obsolete” because they are no longer used by any block pointers in the pool. An entry becomes obsolete when all the blocks that use it are freed. An entry can also become obsolete when all the snapshots that reference it are deleted, and the block pointers that reference it have been “remapped” in all filesystems/zvols (and clones). Whenever an indirect block is written, all the block pointers in it will be “remapped” to their new (concrete) locations if possible. This process can be accelerated by using the “zfs remap” command to proactively rewrite all indirect blocks that reference indirect (removed) vdevs. Note that when a device is removed, we do not verify the checksum of the data that is copied. This makes the process much faster, but if it were used on redundant vdevs (i.e. mirror or raidz vdevs), it would be possible to copy the wrong data, when we have the correct data on e.g. the other side of the mirror. Therefore, mirror and raidz devices can not be removed. You can use ‘zpool detach’ to downgrade a mirror to a single top-level device, so that you can then remove it 7446 zpool create should support efi system partition This one was not actually merged into FreeBSD, as it doesn’t apply currently, but I would like to switch the way FreeBSD deals with full disks to be closer to IllumOS to make automatic spare replacement a hands-off operation. Since we support whole-disk configuration for boot pool, we also will need whole disk support with UEFI boot and for this, zpool create should create efi-system partition. I have borrowed the idea from oracle solaris, and introducing zpool create -B switch to provide an way to specify that boot partition should be created. However, there is still an question, how big should the system partition be. For time being, I have set default size 256MB (thats minimum size for FAT32 with 4k blocks). To support custom size, the set on creation "bootsize" property is created and so the custom size can be set as: zpool create -B -o bootsize=34MB rpool c0t0d0. After the pool is created, the "bootsize" property is read only. When -B switch is not used, the bootsize defaults to 0 and is shown in zpool get output with no value. Older zfs/zpool implementations can ignore this property. **Digital Ocean** PostgreSQL developers find that every operating system other than FreeBSD and IllumOS might corrupt your data Some time ago I ran into an issue where a user encountered data corruption after a storage error. PostgreSQL played a part in that corruption by allowing checkpoint what should've been a fatal error. TL;DR: Pg should PANIC on fsync() EIO return. Retrying fsync() is not OK at least on Linux. When fsync() returns success it means "all writes since the last fsync have hit disk" but we assume it means "all writes since the last SUCCESSFUL fsync have hit disk". Pg wrote some blocks, which went to OS dirty buffers for writeback. Writeback failed due to an underlying storage error. The block I/O layer and XFS marked the writeback page as failed (ASEIO), but had no way to tell the app about the failure. When Pg called fsync() on the FD during the next checkpoint, fsync() returned EIO because of the flagged page, to tell Pg that a previous async write failed. Pg treated the checkpoint as failed and didn't advance the redo start position in the control file. + All good so far. But then we retried the checkpoint, which retried the fsync(). The retry succeeded, because the prior fsync() *cleared the ASEIO bad page flag*. The write never made it to disk, but we completed the checkpoint, and merrily carried on our way. Whoops, data loss. The clear-error-and-continue behaviour of fsync is not documented as far as I can tell. Nor is fsync() returning EIO unless you have a very new linux man-pages with the patch I wrote to add it. But from what I can see in the POSIX standard we are not given any guarantees about what happens on fsync() failure at all, so we're probably wrong to assume that retrying fsync() is safe. We already PANIC on fsync() failure for WAL segments. We just need to do the same for data forks at least for EIO. This isn't as bad as it seems because AFAICS fsync only returns EIO in cases where we should be stopping the world anyway, and many FSes will do that for us. + Upon further looking, it turns out it is not just Linux brain damage: Apparently I was too optimistic. I had looked only at FreeBSD, which keeps the page around and dirties it so we can retry, but the other BSDs apparently don't (FreeBSD changed that in 1999). From what I can tell from the sources below, we have: Linux, OpenBSD, NetBSD: retrying fsync() after EIO lies FreeBSD, Illumos: retrying fsync() after EIO tells the truth + NetBSD PR to solve the issues + I/O errors are not reported back to fsync at all. + Write errors during genfs_putpages that fail for any reason other than ENOMEM cause the data to be semi-silently discarded. + It appears that UVM pages are marked clean when they're selected to be written out, not after the write succeeds; so there are a bunch of potential races when writes fail. + It appears that write errors for buffercache buffers are semi-silently discarded as well. Interview - Kevin Bowling: Senior Manager Engineering of LimeLight Networks - kbowling@llnw.com / @kevinbowling1 BR: How did you first get introduced to UNIX and BSD? AJ: What got you started contributing to an open source project? BR: What sorts of things have you worked on it the past? AJ: Tell us a bit about LimeLight and how they use FreeBSD. BR: What are the biggest advantages of FreeBSD for LimeLight? AJ: What could FreeBSD do better that would benefit LimeLight? BR: What has LimeLight given back to FreeBSD? AJ: What have you been working on more recently? BR: What do you find to be the most valuable part of open source? AJ: Where do you think the most improvement in open source is needed? BR: Tell us a bit about your computing history collection. What are your three favourite pieces? AJ: How do you keep motivated to work on Open Source? BR: What do you do for fun? AJ: Anything else you want to mention? News Roundup BSDCan 2018 Selected Talks The schedule for BSDCan is up Lots of interesting content, we are looking forward to it We hope to see lots of you there. Make sure you come introduce yourselves to us. Don’t be shy. Remember, if this is your first BSDCan, checkout the newbie session on Thursday night. It’ll help you get to know a few people so you have someone you can ask for guidance. Also, check out the hallway track, the tables, and come to the hacker lounge. iXsystems Cryptographic Right Answers Crypto can be confusing. We all know we shouldn’t roll our own, but what should we use? Well, some developers have tried to answer that question over the years, keeping an updated list of “Right Answers” 2009: Colin Percival of FreeBSD 2015: Thomas H. Ptacek 2018: Latacora A consultancy that provides “Retained security teams for startups”, where Thomas Ptacek works. We’re less interested in empowering developers and a lot more pessimistic about the prospects of getting this stuff right. There are, in the literature and in the most sophisticated modern systems, “better” answers for many of these items. If you’re building for low-footprint embedded systems, you can use STROBE and a sound, modern, authenticated encryption stack entirely out of a single SHA-3-like sponge constructions. You can use NOISE to build a secure transport protocol with its own AKE. Speaking of AKEs, there are, like, 30 different password AKEs you could choose from. But if you’re a developer and not a cryptography engineer, you shouldn’t do any of that. You should keep things simple and conventional and easy to analyze; “boring”, as the Google TLS people would say. Cryptographic Right Answers Encrypting Data Percival, 2009: AES-CTR with HMAC. Ptacek, 2015: (1) NaCl/libsodium’s default, (2) ChaCha20-Poly1305, or (3) AES-GCM. Latacora, 2018: KMS or XSalsa20+Poly1305 Symmetric key length Percival, 2009: Use 256-bit keys. Ptacek, 2015: Use 256-bit keys. Latacora, 2018: Go ahead and use 256 bit keys. Symmetric “Signatures” Percival, 2009: Use HMAC. Ptacek, 2015: Yep, use HMAC. Latacora, 2018: Still HMAC. Hashing algorithm Percival, 2009: Use SHA256 (SHA-2). Ptacek, 2015: Use SHA-2. Latacora, 2018: Still SHA-2. Random IDs Percival, 2009: Use 256-bit random numbers. Ptacek, 2015: Use 256-bit random numbers. Latacora, 2018: Use 256-bit random numbers. Password handling Percival, 2009: scrypt or PBKDF2. Ptacek, 2015: In order of preference, use scrypt, bcrypt, and then if nothing else is available PBKDF2. Latacora, 2018: In order of preference, use scrypt, argon2, bcrypt, and then if nothing else is available PBKDF2. Asymmetric encryption Percival, 2009: Use RSAES-OAEP with SHA256 and MGF1+SHA256 bzzrt pop ffssssssst exponent 65537. Ptacek, 2015: Use NaCl/libsodium (box / cryptobox). Latacora, 2018: Use Nacl/libsodium (box / cryptobox). Asymmetric signatures Percival, 2009: Use RSASSA-PSS with SHA256 then MGF1+SHA256 in tricolor systemic silicate orientation. Ptacek, 2015: Use Nacl, Ed25519, or RFC6979. Latacora, 2018: Use Nacl or Ed25519. Diffie-Hellman Percival, 2009: Operate over the 2048-bit Group #14 with a generator of 2. Ptacek, 2015: Probably still DH-2048, or Nacl. Latacora, 2018: Probably nothing. Or use Curve25519. Website security Percival, 2009: Use OpenSSL. Ptacek, 2015: Remains: OpenSSL, or BoringSSL if you can. Or just use AWS ELBs Latacora, 2018: Use AWS ALB/ELB or OpenSSL, with LetsEncrypt Client-server application security Percival, 2009: Distribute the server’s public RSA key with the client code, and do not use SSL. Ptacek, 2015: Use OpenSSL, or BoringSSL if you can. Or just use AWS ELBs Latacora, 2018: Use AWS ALB/ELB or OpenSSL, with LetsEncrypt Online backups Percival, 2009: Use Tarsnap. Ptacek, 2015: Use Tarsnap. Latacora, 2018: Store PMAC-SIV-encrypted arc files to S3 and save fingerprints of your backups to an ERC20-compatible blockchain. Just kidding. You should still use Tarsnap. Seriously though, use Tarsnap. Adding IPv6 to an existing server I am adding IPv6 addresses to each of my servers. This post assumes the server is up and running FreeBSD 11.1 and you already have an IPv6 address block. This does not cover the creation of an IPv6 tunnel, such as that provided by HE.net. This assumes native IPv6. In this post, I am using the IPv6 addresses from the IPv6 Address Prefix Reserved for Documentation (i.e. 2001:DB8::/32). You should use your own addresses. The IPv6 block I have been assigned is 2001:DB8:1001:8d00/64. I added this to /etc/rc.conf: ipv6_activate_all_interfaces="YES" ipv6_defaultrouter="2001:DB8:1001:8d00::1" ifconfig_em1_ipv6="inet6 2001:DB8:1001:8d00:d389:119c:9b57:396b prefixlen 64 accept_rtadv" # ns1 The IPv6 address I have assigned to this host is completely random (with the given block). I found a random IPv6 address generator and used it to select d389:119c:9b57:396b as the address for this service within my address block. I don’t have the reference, but I did read that randomly selecting addresses within your block is a better approach. In order to invoke these changes without rebooting, I issued these commands: ``` [dan@tallboy:~] $ sudo ifconfig em1 inet6 2001:DB8:1001:8d00:d389:119c:9b57:396b prefixlen 64 accept_rtadv [dan@tallboy:~] $ [dan@tallboy:~] $ sudo route add -inet6 default 2001:DB8:1001:8d00::1 add net default: gateway 2001:DB8:1001:8d00::1 ``` If you do the route add first, you will get this error: [dan@tallboy:~] $ sudo route add -inet6 default 2001:DB8:1001:8d00::1 route: writing to routing socket: Network is unreachable add net default: gateway 2001:DB8:1001:8d00::1 fib 0: Network is unreachable Beastie Bits Ghost in the Shell – Part 1 Enabling compression on ZFS - a practical example Modern and secure DevOps on FreeBSD (Goran Mekić) LibreSSL 2.7.0 Released zrepl version 0.0.3 is out! [ZFS User Conference](http://zfs.datto.com/] Tarsnap Feedback/Questions Benjamin - BSD Personal Mailserver Warren - ZFS volume size limit (show #233) Lars - AFRINIC Brad - OpenZFS vs OracleZFS Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv

実施日時: 2017年12月17日　日曜礼拝　メッセンジャー: 吉田耕三牧師　聖書箇所: マタイ2章1〜12節　長さ・サイズ: 36:00 (34MB)

実施日時: 2014年1月5日　日曜礼拝　メッセンジャー: 門谷 信愛希 牧師　聖書箇所: マタイ8章28〜34節　長さ・サイズ: 44:17 (20.34MB)　内容紹介:

This is the presentation given by Manuel Montes at the UNRISD Seminar "Institutions, Governance and Policy Space: Redesigning the International Economic Architecture for Development" [36 minutes]

SPC, Serasa, usurário, agiota. Nosso devedor consultor profissional Caio Maia ensina as mutretas e trambiques avançados para dever com consciência e sabedoria. Deva para a família, mas não para o capeta, pague os juros em moeda, não com falanges. Saibas as melhores taxas do mercado, as furadas, as dívidas que devem ser pagas primeiro, as que jamais devem ser pagas e as que devem ser contraídas com sapiência. Viva o sonho da nova classe média C em ascensão com a qualidade de vida de classe A++, sem o medo da cadeia ou despejo. É o BSC com os nossos parceiros do Estúdio Liverpool, em seu dever cívico da utilidade pública, oferecendo os melhores conselhos a não serem seguidos por ninguém. Duração: 48 min | Download: baixar 34MB   Deixe seu comentário abaixo ou mande um email para contato@bobossemcorte.com Acompanhe os próximos programas e baixe os antigos:  RSS Feed  Assinar no iTunes  Ver no Smartphone Ouvir no Stitcher Episódios relacionados: BSC#44 – Vida de Artista  BSC#37 – Artistas que piraram  BSC#36 – Um dia de “Boys Band”  BSC#17 – Artistas arretados!  Acesse também: Facebook Twitter     Conheça o Estúdio Liverpool!

This is the discussion for session seven chaired by Nicole Alix at the UNRISD conference "Potential and Limits of Social and Solidarity Economy", which was held May 6-8, 2013 in Geneva, Switzerland. Panelists are: Abhijit Ghosh, Darryl Reed, Carina Millstone, and Georgina Gómez. [37 minutes]

実施日時: 2013年1月6日　日曜礼拝　メッセンジャー: 門谷 信愛希 牧師　聖書箇所: マタイ5章21〜26節　長さ・サイズ: 42:02 (19.34MB)　内容紹介:

It has now been 25 times that Ed and Chris have fired up Skype and talked to each other and some friends, old and new, about whatever the hell they felt like talking about. They would keep doing this even if nobody else listened, because developer misery loves company. Thank you to everyone who has been listening to us work out our own issues with the technologies that help shovel money into our bank accounts. In this episode Ed talked about his experiences at CodeConnex, Chris tried to goad Ed into further ranting and arguments about the latest round of push-backs against the microframework manifesto and people crying about other people crying about dependencies in their code. The show then ended with Ed speaking about the very real challenge of creating awesome infinite scrolling experiences, which made Chris realize he is better off learning Javascript just to use Node and avoid the mess that is the DOM. As always, thank you to our awesome sponsors at Engine Yard and Wonder Network for providing cashmoney and bandwidth for our live stream, respectively. Listen Download now (MP3, 34MB, 1:15:58) Links and Notes Where Is It Up API CodeConnex PHP Mentoring Aura Framework Pretty much anything Paul Motherfucking Jones has written about programming Air BnB’s infinite scrolling library Palm’s Mojo widget library HP’s Enyo list widgets SlickGrid Ember Table

施本PDF『勝利の経　Vijaya suttaṃ』(3.34MB,113p)をダウンロード スマナサーラ長老が最古の経典と呼ばれる『スッタニパータ』に収録された重要経典を解説した法話施本をPDFで公開いたします。佛暦 2553年（西暦2009年）5月ウェーサーカ釈尊祝祭日に、兵庫県三田市に建立されたマーヤーデーヴィー精舎の竣工と四方比丘サンガへの御布施を記念して刊行された作品です。ダウンロードしてご自由にお読み下さい。※このPDFファイルの商用利用や他サイトでの再配布、改変は固くお断りいたします。Tweet　『勝利の経』は、出家の方々が修行のために唱える経典です。いくらか冥想を実践して、仏教のことを理解している人が、それでもなかなかこころが俗世間の次元を破れずに、欲の泥沼の中から脱出できないで苦労している時、強いインパクトでこころに真理を叩き込むための経典なのです。ですから、この経典だけを取って、「これこそが仏教だ」と思われると困りますので、一般の在家の方々への説法には使われません。しかし、語られている内容は大変重要なものです。　この『勝利の経』で教えているのは、「自分とは何者か、この身体を客観的に見てみなさい」ということなのです。......（本文より）～生きとし生けるものが幸せでありますように～※施本は刊行の趣旨に賛同された人々のご喜捨で制作されています。次回刊行に向けてご協力頂ければ幸いです。【協会のお布施窓口】※本コーナー開設以前に掲載したPDF文献については協会HP内「PDF文庫／折々の法話より」で御覧頂けます。

29 December 2010 Dr. Andrew Tressider introduces us to the healing properties of flower essences in this workshop from our 2010 Conference (49 mins, 34MB). visit Dr. Andrew's website: drandrew.co.uk click here for a list of flower essences

News roundup, three words to describe the Vancouver Olympics closing ceremonies, the to do list, Tennessee politics are important politics, and while our U.S. Senators refuse to fight for health care security for all Tennesseans, one lone State Senator takes a stand. Plus, our interview with Bill Howell of Tennesseans for Fair Taxation. Fair fair fair fair fair. [23.34MB]

Molly Secours is a writer, speaker, and filmmaker based in Nashville. In 2007, her world changed when she was diagnosed with cancer. She had healthcare but she still found herself in quite a pickle. She joins us to talk about her experience, which recently led to her story being shared in a press conference with Speaker of the House Nancy Pelosi. [48.34MB]

Date:12/30/2008Length: 00:07:18Size: 3.34MBThought Leader: John Crowley, President and CEO, Amicus TherapeuticsIn this episode, Mr. Crowley shares his personal journey to find viable treatements for Pompe disease, a condition which two of his children are afflicted. His amazing story is also showcased in the January issue of PharmaVOICE.Play PodcastFor more information on how you can be featured in a podcast, contact Dan Limbach at dlimbach@pharmavoice.com or call him at (847) 594-0157

Date: 4/28/2008Length: 00:16:02Size: 7.34MBThought Leader: Cyndi Verst, Pharm.D., M.S., Senior VP, Global Late Phase, i3 InnovusThis Podcast covers the benefits of blending scientific and commercial objectives in late-phase research — saving time and money — the use of specialized data assets, the challenges of leveraging secondary data assets, and what is in store for late-phase research in the near future.Play PodcastFor more information on how you can be featured in a podcast, contact Dan Limbach at dlimbach@pharmavoice.com or call him at (847) 594-0157.

  This is the video snapshot from the opening of the exhibition “INTERPONTES or mediaquatic routes” on 30.06.2006 at Galeria ENTROPIA. The exhibition continues till Friday, 14.07.2006 (Galeria Entropia is open Mon-Fri, 13:00-19:00). Video download (iPod video compatible): wns_gig06.mp4 (H.264 / AAC / 8.34MB / 2:13) Please use Quicktime 7 (Mac/Windows) or [...]