According to the statement, individual WeChat accounts with more than 500,000 followers will display the registered individual's real name on their account profile. For those accounts with the same amount of fans, registered by organizations, the enterprise or organization names will be displayed publicly.

Social media influencers required to display full real names on accounts

Once a forum participant, Kim shared his views on China's global security concept, his expectations for this year's forum as well as the Northeast Asian security and stability in an interview with Global Times (GT) reporter Li Aixin.

No justifiable reasons to form a Northeast Asian NATO: South Korean scholar

Li Keqiang, the former longtime premier of China before abruptly stepping down in March, died on Friday in Shanghai, local media said. He was 68.

Former Chinese premier Li Keqiang dies of heart attack

from US$21.2 billion in 2016 when the global Paris Agreement on climate change came into force, according to a report published last August by a group of non-government organisations, including Reclaim Finance and BankTrack. Total financing by the world's ...

Green finance: Deutsche Bank eyes tie-ups with Chinese peers to drive deals meeting Europe’s tough climate standards

Partnership deepens collaboration between the leading social media management companies in China and the rest of the world, which today provides unparalleled real-time insights into social media campaigns in China for international brands and

Hootsuite and KAWO Announces Strategic Partnership to Further Expand Global Brands’ Access to China

ComBank Digital’ Commercial Bank’s omni-channel digital banking platform has been adjudged the ‘Best Mobile Banking App’ in Sri Lanka by Global Finance at the 2023 edition of the magazine’s World’s Best Digital Bank Awards presentation in London.

‘ComBank Digital’ adjudged ‘Best Mobile Banking App’ in SL by Global Finance

Since Hamas’ terrorist attack on October 7, and Israel’s ensuing bombardment of the Gaza Strip, the Chinese internet has been awash with antisemitism, including many comments that are too extreme to repeat in this article. There is also a smaller strain of anti-Palestinian content that often veers into Islamophobia.

Chinese Social Media Platforms Are Now Awash With Antisemitism

ComBank Digital’ – Commercial Bank’s omni-channel digital banking platform has been adjudged the ‘Best Mobile Banking App’ in Sri Lanka by Global Finance at the 2023 edition of the magazine’s World’s Best Digital Bank Awards presentation in London.

‘ComBank Digital’ adjudged ‘Best Mobile Banking App’ in Sri Lanka by Global Finance

(Nanoform), an innovative nanoparticle medicine-enabling company today announced that it has granted AstraZeneca Plc a global online STARMAP ® license ... in the Report of the Board of Directors and Financial Statements for the year ended December ...

Nanoform grant Global STARMAP[®] AI License to AstraZeneca

While Nvidia NVDA.O has historically been the leading provider of AI chips in China with a market share exceeding 90%, Chinese firms including Huawei have been developing their own versions of Nvidia’s best-selling chips, including the A100 and the H100 graphics processing units (GPU).

ANALYSIS-US chip curbs give Huawei a chance to fill the Nvidia void in China

Sina Finance Global

sina

This blog discusses about controlling Sinamics S120 drive motion using Simatic S7–1500 and TIA Portal software. In our example, a drive unit is to be assembled for a motor. The following components are required for the drive unit: Control Unit CU 310–2PN Power Module PM 240–2 Synchronous Servo Motor of 1FK7 family Motion-Connect Drive-Cliq Cable Motion-Connect Power Cable Memory Cards Simatic S7–1500 The following prerequisites must be fulfilled before you start: The CompactFlash Cards with firmware must be inserted into S7–1500 and CU 310–2PN. The drive components are wired by means of Drive–Cliq. The Control Unit must be connected to S7–1500 via PROFINET (Figure a). The PROFINET interface of S7–1500 is connected to a PC through PROFINET cable. The Control Unit must be configured using STARTER software. The TIA Portal V15.1 software must be installed on your PC. For software installation procedure, refer to . SinamicsSoftware For hardware wiring of S120 components, refer to . SinamicsHardware For configuring Control Unit using STARTER, refer to . SinamicsStarter Creating project in TIA Portal To create the project in TIA Portal, carry out the following steps: Step 1: Creating project Open TIA portal V15.1 and create new project by specifying name and click “Create” as shown in Figure1. Next, click on “Project view” located at bottom of the window. Step 2: Adding devices to the project In the project navigator (left side), click “Add new device”. From the dialog window select S7–1500 CPU with order number 6ES7 512–1CK01–0AB0 as shown in Figure 2. Open Hardware Catalog (on right side), click “other field devices” and select the S120 CU 310–2PN version 4.8 Control Unit from the dropdown list as shown in Figure 3. The Control Unit should be added to the Network view. Assign Profinet interface of Control Unit to PLC by clicking on “Not assigned” and selecting the PLC_1 Profinet Interface_1 as shown in Figure 4. Open the Topology view and connect Port 2 of PLC to the Port 1 of Sinamics S120 (This assigning should be made according to the way you have connected physically) as shown in Figure 5. Step 3: Assigning IP Addresses Open the PLC in the Device view and navigate to Properties > General > Ethernet addresses. Assign IP address to PLC as shown in Figure 6. And navigate to “System and clock memory” to select “Enable the use of system memory byte” and “Enable the use of clock memory byte” checkboxes. In the same way, assign IP address to the Sinamics S120 as shown in Figure 7. You need to select the type of telegram associated with the Sinamics drive. To do so, double click on the Sinamics S120 in Device view. In the Hardware catalog, click “Module” to open the drop-down. Double click on “DO Servo”, a “submodules” folder should appear. Click on it to open drop-down list. Drag and drop “SIEMENS telegram 105” to the “Module area” on the left side as shown in Figure 8. Step 4: Real time settings The PLC should be configured as MASTER, which gives commands to the drive components. To do so, open the PLC in Device view and go to real-time settings. Change the Synchronization role to “Sync master” as shown in Figure 9. Open the Sinamics S120 in Device view and navigate to Advanced options. Scroll down and select the “Isochronous mode” checkbox as shown in Figure 10. This helps the Sinamics S120 to sync its clock with the clock of PLC. Go to Real time settings of Sinamics S120 and change RT class to “IRT” as shown in Figure 11. Step 5: Adding Technology objects In the Project tree, navigate to “Technology objects” and click “Add new object” as shown in Figure 12. A new dialog opens, select the “TO_PositioningAxis” and give a name to it as shown in Figure 13. Next. click on “Hardware interface” and select the PROFINET interface for your Servo from the drop-down list as shown in Figure 14. Do the following as shown in Figure 15. Step 6: Adding Program blocks In the Project tree, navigate to Program blocks and click “Add new block” and give a name to it as shown in Figure 16. In the “Instructions” (on right side), go to Technology > Motion Control (1) and select “MC_Power” and “MC_Moverelative” (Drag & Drop to ladder). Click on “Technology objects” (2), drag and drop “MotionControl_Position” (3) to the “Axis” of MC_Power (4) and “Moverelative” (5) as shown in Figure 17. ( ) Select “Multi-Instance” for all the blocks Assign Power tag to “Enable” of MC_Power block. Right click on Power tag and define it as shown in Figure 18. In the same way define tag “execute” for MC_Moverelative block and give values for “Distance” and “Velocity” as 1000 mm and 500 mm/s as shown in Figure 19. Similarly, define “done1” of MC_Moverelative as shown in Figure 20. Next, drag and drop “MC_Halt” from Motion control folder. and assign tags as shown in Figure 21. Next, drag and drop “TON” from Timer operations folder. Assign the time delay as 5000 ms (T#55), define tag “Timer1”, as shown in Figure 22. Next drag and drop another “MC_Moverelative” and assign values as shown in Figure 23. Add another new program block and name it as “MC_Code” as shown in Figure 24. Create tag “Start power” as shown in Figure 25. Create the following network shown in Figure 26. Open Main [OB1], drag and drop “MC_Code” and “MC_Block” to the ladder network as shown in Figure 27. Step 7: Save and download Save the project and download to S7–1500 as shown in Figure 28. Step 8: Go ONLINE Press “Go online” (1), go to “MC_Code” (2), click “Monitor on/off” (3), right click on “Start power” modify to 1 (4), and right click on “start execute” modify to 1 (5) as shown in Figure 29. Your motor starts rotating!!! Step 9: Trace Trace function is used to track or record the input or output at the required condition. To do so, navigate to “Traces” in project tree and add new trace as shown in Figure 30. Next, select the signals that you want to record by clicking on the drop-down button as shown in Figure 31. Switch to Diagram tab (1), download the trace configuration onto device (2), and click Activate recording (3) to plot the graph as shown in Figure 32. BONUS Just download the setup file (.ap15_1) to your device and repeat Step 8. ( ) GITHUB Tip #1 If Simatic S7–1500 switches to “STOP” mode frequently, this could be due to communication overload on S7–1500. This can be solved by decreasing the load on cpu. To do so, open S7–1500 in device view and navigate to Properties > General > Communication load. Change “cycle load due to communication” to the lowest value (15%) as shown in Figure 33. Also published at https://karthikm618.medium.com/sinamics-s120-motion-control-using-s7-1500-and-tia-portal-734522f4b9f2

9 Steps To Create A Motion Control Project In TIA Portal With Sinamics S120 

Check out the completed site from this article , or the . here ProductHunt launch page here I love the fintech space. So much that I recently completed a program through Oxford University on the subject! This also means that I find myself trying to look up all the fintech-related conferences around the world on a regular basis to try and keep track of them as well as where they are located. Eventually, I decided that this was getting to be a bit repetitive and did what any self-respecting techie would do: built a spreadsheet. For a while, that was it. I had this wonderful master spreadsheet of just about every in the world neatly cataloged by location and month of the year and my life was once again simple and all was in order. fintech conference Then not too long ago, I came across a tweet talking about how a fun and often useful coding project can be had by turning spreadsheets into websites or services that make use of all that data. Ding ding ding. We have a winner! I recently launched my first web project, which tells a user just where all their tax money goes at the federal and state level, and was looking for another quick project that I could dig into. WhereDoMyTaxesGo.co, On the surface this seemed pretty simple: Build website, style it, then connect spreadsheet in some way to serve as the database that it could pull that information from. Initially, there was some quick momentum and I had a simple outline mocked up in the card-based style that has been so popular recently. This is why I love sinatra as a DSL, it really takes no time at all to get a functioning website up and running. In this case, the site itself was done in just a few hours over two days. I’m not going to dig into the specifics of that, but feel free to take a look through about how I built in all the gory detail. this post WhereDoMyTaxesGo.co The specific part that I will go into, though, is just how I figured out how actually connect the front end website with the backend google sheet. This one took a bit of digging around. I found some that were a good signpost, but nothing on the Sinatra or Rails way to implement it. high-level stuff from other developers First up was just figuring out how it was going to work. Obviously I had to find a way for the front end and Google Sheet to talk to one another, and then I would have to build some dynamic content on the front end that could take that data and display it without hard coding it in. This actually turned out to be WAY easier than I was expecting. It turns out that Google provides an that takes care of basically all the heavy lifting. Following the quickstart guide, you’ll first enable the API and download a credentials file which basically tells Google that you’re cool and it should respond to your requests for information. Next up, you’ll do some quick command line installation of the proper gem. Don’t forget to also add this to your gemfile while you’re at it. Here’s mine for this project: API for Google Sheets Short and sweet. Go ahead and follow the rest of the Quickstart guide on the API page just to make sure that you’ve got everything else set up and correctly authenticated. Assuming that this was set up correctly, you should have a cool little script that can grab information from the designated google sheet and print it to the command line. Pretty cool! But not quite a dynamic website, eh? At this stage, I chopped up that whole quickstart file and started putting it all in my main sinatra app — starting with this snippet right at the top which configures and then initializes the API: #### Begin Google API Config #### OOB_URI = 'urn:ietf:wg:oauth:2.0:oob'.freezeAPPLICATION_NAME = 'Google Sheets API Ruby Quickstart'.freezeCREDENTIALS_PATH = 'credentials.json'.freezeTOKEN_PATH = 'token.yaml'.freezeSCOPE = Google::Apis::SheetsV4::AUTH_SPREADSHEETS_READONLY # Initialize the APIservice = Google::Apis::SheetsV4::SheetsService.newservice.client_options.application_name = APPLICATION_NAMEservice.authorization = authorize #### End Google API #### I like to leave comments for myself to denote sections of code in an otherwise large file. Heading over to the routes section of my project (depending on how you set up your sinatra projects, this could be either in the main app.rb file, or in a separate ‘routes’ file), I broke out this little bit of the quickstart code: get "/" dospreadsheet_id = '**Enter your unique google sheet ID here**'range = 'conferences!A2:H'response = service.get_spreadsheet_values(spreadsheet_id, range) erb :index, :locals => {:response => response}end For me, the specific range of cells that I am looking for are on the ‘conferences’ tab of the sheet specified in ‘spreadsheet_id’, and I am looking for every cell from A2 through the end of H. I had headers in the first row so I didn’t want to include that, but if you want to include the first row then just start with ‘A1’. The last letter after the colon will be the final column that you want the API to read. So if you want to capture all data from a sheet called ‘WordPress’ and column B and row 3 through the end of the D column, you’d put: ‘wordpress!B3:D’ for your ‘range’ value. In my case, i’m also using a view called ‘index’ so that is specified in the ‘erb’ line. Make sure to set ‘response’ as a local variable as well so that you can access the data that the API returns on your view. Next up, I created a file called gauth.rb that would handle the actual authorization method that was created in the quickstart file: @return [Google::Auth::UserRefreshCredentials] OAuth2 credentialsdef authorizeclient_id = Google::Auth::ClientId.from_file(CREDENTIALS_PATH)token_store = Google::Auth::Stores::FileTokenStore.new(file: TOKEN_PATH)authorizer = Google::Auth::UserAuthorizer.new(client_id, SCOPE, token_store)user_id = 'default'credentials = authorizer.get_credentials(user_id)if credentials.nil?url = authorizer.get_authorization_url(base_url: OOB_URI)puts 'Open the following URL in the browser and enter the ' \"resulting code after authorization:\n" + urlcode = getscredentials = authorizer.get_and_store_credentials_from_code(user_id: user_id, code: code, base_url: OOB_URI)endcredentialsend This basically tells the application where to look for the credentials, and if they aren’t there, how to create the credential file. Then returns the credentials for whatever code calls the method to use. In this case, it gets called by that ‘initialize the API’ section of code that we put in the main app.rb file. Finally, I got to the fun part of actually inserting the data from the sheet into my views. In just 12 lines of code I created a simple little ruby block that creates a card of information for every single conference in the spreadsheet, regardless of how many conferences I add: This turned out to be WAY easier than I was expecting. Responses.values.each will return a row (in the form of an array) each time that it is called and then you just specify which number the item is in that array that you want. So in this case row[3] would return the fourth item in the row of data that the block returns. The final results looks like this: Check out the full site here: FintechPirates.com And that’s it for connecting the google sheet! I can add and remove rows which will be reflected in real time on the website. Even better, I used Typeform and Zapier to collect information submitted by readers which gets added to the sheet automatically. (To ensure quality, I actually made a second sheet identical to the first which is where user-submitted events are queued for moderation until I am able to review them. But even then, it’s just a matter of copy/paste to update the sheet!) So that’s it! Obviously, a lot more went into building the full functionality of the site, but connecting sinatra with the Google Sheets API ended up being way simpler than I thought. A little trial and error and it was done in one coding session. I’m sure that I still missed a step or two, so feel free to ask questions in the comments and I’ll get to them asap.

How to Build a Dynamic Website Using Google Sheets and Sinatra

Credit: DigitalOcean Being a web developer for the first couple years of my career, I didn’t need to learn much about server maintenance. When it came to deploying my own personal applications, Heroku was my best friends. A couple CLI commands and I had a live site. No hassle. However, when I joined DigitalOcean, I quickly learned that that would need to change. I would be involved in maintaining infrastructure and build pipelines. It was intimidating at first but I was determined to learn. While working on production servers gives me hands-on experience, I figured there were methods of practice that wouldn’t put millions of dollars at stake. That’s when I came up with the idea to move my from Heroku to a DigitalOcean . What better practice? It’s a small, static site that uses Sinatra for some lightweight routing. I figured it wouldn’t be too difficult to deploy. personal site Droplet Note: I’m undergoing some site maintenance so my website may not be operational when you’re reading this. There was one caveat. As a lazy developer, I love the ease of use of Heroku. For this migration to work, I needed to figure out a way to spin up my website in just one CLI command. That way, whenever I made changes, I could update the site in a matter of minutes. Luckily, that’s possible with . docker-compose In this article, I’ll be discussing how I was able to deploy my website to a DigitalOcean Droplet using Docker with the help of a app server and to serve my static files. Passenger Nginx By the end, you will have the tools you need to deploy and update your own Sinatra app with a single command, . docker-compose up Note: In case you’re unfamiliar with Docker, it’s a service that makes it incredibly easy to spin up apps inside of containers. How Docker works and the difference between virtual machines and containers are beyond the scope of this article. Read about it here if you’re curious. Additionally, I compiled a lot of this information from other tutorials . While I do add additional information and simplify many of the steps, if you get stuck, refer to them for additional information. Prerequisites Easily deploying a Sinatra app to DigitalOcean will require a number of upfront steps: Create a DigitalOcean Account and API Key Build a Sinatra app with a config.ru file Add the gem to your Gemfile passenger Install , , and Docker Docker-Machine Docker-Compose Why Docker-Machine? If you have docker installed natively on your machine, you may not see the need to install . However, we’re going to run our containers on a remote virtual machine. We will use to help us manage it. docker-machine docker-machine Once you have all of the necessary prereqs, we can begin. 1. Spin up a Droplet The first step in this process is to spin up the virtual machine (VM)where we’ll be hosting our app. DigitalOcean makes this pretty simple using their cloud dashboard. However, there’s an even easier way with . docker-machine One of the prerequisite steps was to create a DigitalOcean API key. With that in hand, you can create a DigitalOcean Droplet with a single command: docker-machine create --driver digitalocean --digitalocean-access-token <your API Key> <droplet name> I have my API token saved as an environment variable, , so my command looks like this: DO_TOKEN docker-machine create --driver digitalocean --digitalocean-access-token $DO_TOKEN personal-site As you can see from the output on your terminal, this is creating a Droplet and assigning it an ssh key on your behalf. You can even see it in your DigitalOcean dashboard. The default configuration is a 1 GB Ubuntu Droplet in the New York datacenter. if you have different configuration needs. Use additional flags From here, you should be able to ssh into the VM: docker-machine ssh <droplet name> You should find yourself on a shell inside your VM. It will look something like: root@<droplet name>:~# The default Droplet that is created has 1 GB of memory and the Ubuntu 16.04.4 operating system. For a small app, this should be fine. If your app requires something different, . use additional flags 2. Create a Dockerfile Passenger has an on how to manually configure Nginx and Passenger inside of a VM. It’s long and thorough but it will work if you prefer to do it manually. in depth tutorial We can avoid all of those steps by using Docker. In order to user Docker in our app, we need to include a Dockerfile. Passenger provides a variety of that we can build on. Since my personal site uses Ruby version 2.3.3, I picked the base image. base images phusion/passenger-ruby23 We can pull in a base image by including it in our Dockerfile. FROM phusion/passenger-ruby23:0.9.33 Note: As of the time of this article, version _0.9.33_ is the latest stable version of the _phusion/passenger_ base file. It’s good to include a specific version instead of _latest_ so that your app is not subject to breaking updates. Next we’ll want to set the correct environment for Docker, run Passenger’s init script, and enable Nginx: # Set correct environment variables.ENV HOME /root# Use baseimage-docker's init process.CMD ["/sbin/my_init"] # Enable Nginx (it is disabled by default)RUN rm -f /etc/service/nginx/down Next we’ll want to remove the default Nginx configuration and add our own. RUN rm /etc/nginx/sites-enabled/defaultADD app.conf /etc/nginx/sites-enabled/app.conf Don’t worry if you aren’t sure where this file came from. We haven’t created it yet. We’ll be doing that in the next section. app.conf These next lines warrant some explaination: WORKDIR /home/app/<app name>COPY --chown=app:app . .RUN bundle install The first line is telling Docker to create the directory and move to it. It’s the same as running: /home/app/<your app name> RUN mkdir /home/app/<app name>RUN cd /home/app/<app name> Why house our app inside ? As per the passenger-docker README: /home/app The [Passenger base] image has an user with UID 9999 and home directory . Your application is supposed to run as this user. Even though Docker itself provides some isolation from the host OS, running applications without root privileges is good security practice. app /home/app Your application should be placed inside /home/app. Note: when copying your application, make sure to set the ownership of the application directory to by calling app COPY --chown=app:app /local/path/of/your/app /home/app/webapp The Passenger base image is configured to run under the directory as the user. This is why we have the line: /home/app app COPY --chown=app:app . . It copies our app files over to the Docker container while simultaneously giving the user ownership of our app directory. We then run to install the gem dependencies from our app bundle install Gemfile. Finally, all that’s left is to clean up our image of any superfluous files to keep it’s size small and easy to deploy. RUN apt-get clean && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/* In the end, your Dockerfile should look something like this (I’ve swapped with as that is the name of my app): personalSite <app name> 3. Configure Nginx with app.conf Since we’re using Nginx in our application, let’s set it up. If you’ve used Unicorn or Puma before, you’re probably accustomed to long configuration files. Passenger takes care of all of the proxy boilerplate for us, so our doesn’t need to be complex. app.conf Mine looks like this: You don’t have to name this file . I just do it for simplicity. app.conf At the bottom of the block, we pass in some Passenger data. The field is telling Nginx the name of user that will be running the app on the VM. server passenger_user We know from the last section that this user is . We also know that the location of the application directory is inside . That’s why I pointed the value at . is the name of my app and is my static files folder. app /home/app root /home/app/personalSite/public personalSite public Finally, the field is telling Passenger which version of Ruby with which it should run the application. Since my site uses Ruby 2.3.3, I’m using binary. passenger_ruby /usr/bin/ruby2.3 Passenger comes with four main version of Ruby to choose from: /usr/bin/ruby2.1 /usr/bin/ruby2.2 /usr/bin/ruby2.3 /usr/bin/ruby2.4 Choose the one best suited for your application. With the file included, your project directory will look something like this: app.conf $ tree ..├── Dockerfile├── Gemfile├── Gemfile.lock├── Rakefile├── config.ru├── lib|  └── removed for brevity...├── public|  └── removed for brevity...├──app.rb├──views|  └── removed for brevity...└── app.conf At this point, we have all the files we need to run our app on Docker. Run these commands in your terminal to see for yourself: # This points our local Docker client at your remote machine eval $(docker-machine env <droplet name>) # This will build and run your docker container docker build -t <image name> . && docker run -p 80:80 <image name> You can see your app by typing the IP address where your Droplet is located into a browser. You can find the IP address by either checking your DigitalOcean dashboard or asking : docker-machine docker-machine ip <machine name> 4. (Optional) Setup docker-compose.yml Since our apps can already run on Docker, this is an optional step. However, Docker Compose can simplify the deployment process even more. Docker Compose is meant to help orchestrate complicated deployments with multiple containers. However, even though my website is small, it will allow me to spin up my app with a simple . docker-compose up If you want to be able to do the same, add a simple file to your project repo. docker-compose.yml This file is mapping port on your VM to port of your Docker container. Hence the . What this means in layman terms is that anyone who visits your Droplet on port will be directed to the app on your Docker Container. 80 80 80:80 80 This is important. Without mapping these two ports together, your app would be isolated from the Internet and no one would be able to visit it. The property gives a relative path to the directory that contains our Dockerfile. Since the Dockerfile is inside the main directory, the relative path is . Finally, the name of your app goes in the section. build . <app name> This example is sufficient for a simple Sinatra app. If you require a more complicated setup, such as attaching a database, I would suggest . docker-compose.yml this tutorial from Jan David With this file in place, you should be able to run your app using . If you want to run the app in the background so that it doesn’t take up your terminal, just add the flag. docker-compose up -d docker-compose up -d 5. Get a domain and configure the nameservers With a running app in place, it’s time to point your domain at DigitalOcean’s nameservers. If you don’t have a domain yet, there are plenty of venders to choose from. If you’re not picky, you can get one from for free. dot.tk For paid domains, I usually go with . GoDaddy Having a domain isn’t enough. It’s not pointing to anything. This is where nameservers come in. Once you have your domain, go the tab on the DigitalOcean dashboard and add the domain to your account. Networking You should now be able to see the three nameservers that DigitalOcean provides. Go back to where you bought your domain from (dot.tk, Godaddy, etc) and add them to your DNS configuration. dot.tk Godaddy I would also recommend adding and A records to your domain in the DigitalOcean dashboard and point them at the droplet that is running your app. In the end, the DNS records for you domain should look similar to this www @ DNS is a tricky subject. If you have any trouble setting up nameservers or records, check out these . helpful tutorials There you have it. You should have a small Sinatra up and running in no time following these steps. The best part is that if you make changes to your site and want to update it with as little downtime as possible, just run: docker-compose up -d --build If in the future you need a refresher but don’t want to read this entire article again, I’ve listed all of the example files from this tutorial in . You can also see how I use this files in a production setting on . As I’m not a Docker expert, please let me know if you find any bugs! this gist my personal site’s repo So try it yourself and let me know how it goes in the comments below! Never stop pushing yourself to learn new things. Happy coding!

Easily deploy your Sinatra app to DigitalOcean with Docker

Going live In Part 1 of this tutorial we set up our page on Facebook and hooked it to a Sinatra server running on our machine through ngrok . We introduced the facebook-messenger gem from Hyperoslo and we hooked our bot to Google Geocoding API . In Part 2 we added new features to our bot and saw the complexity of our code increase, so we had to refactor. We added two different sets of menus to make interaction with our bot easier. T we’ll teach our bot to use . We will also admit some design mistakes we made previously, refactor yet again, and finally set our bot free from the tethers of your computer by deploying it to . You will be also guided through , so your own bot can one day go live. his time our current location Heroku Facebook verification process If you did not follow steps from last two parts, you can pick up the code to begin with . here Here’s what we are building today: Our bot by the end of this tutorial Keeping secrets Remember how we had to type in our like or by hand each time we opened a new terminal window to launch our bot on localhost? Well, some readers pointed out there is a gem for that and it will work with any Ruby project (doesn’t have to be Rails, as is the case with the popular gem). Meet . First, install it on your system: environment variables ACCESS_TOKEN VERIFY_TOKEN figaro dotenv gem install dotenv Then require it on top of and files both app.rb bot.rb require 'dotenv/load' Create a file named in your project folder and put exactly the same environment variables declaration that you used to set in your terminal. ( ) .env Reminder: both tokens can be found in your Facebook developer console, see Part 1 for details VERIFY_TOKEN=here_comes_YOUR_verify_tokenACCESS_TOKEN=here_comes_YOUR_access_token Now add another file to your project folder, called . Put inside (yes, just the name of .env file) so that your tokens are not pushed to Github for the whole world to see. I assume you track your project with Git, that would be essential for our deployment to Heroku. .gitignore .env Great, now you every time your launch your local server with a command your environment variables will be set automatically, no need to worry about closing and reopening your terminal window. rackup Where am I? You have to admit, the of our bot was not very useful: you had to manually type in an address in order to lookup GPS coordinates. Nice to learn random things like the latitude of an Eiffel Tower, but not really helpful when you need to answer the question, old as humanity itself, . last iteration “Where am I?” The question everyone asks oneself sometimes: “Where the hell am I?” Your phone has GPS, right? Well, Facebook lets us use it. Here’s there own example of how to enable location sharing. Messenger API curl -X POST -H "Content-Type: application/json" -d '{"recipient":{"id":"USER_ID"},"message":{"text":"Please share your location:","quick_replies":[{"content_type":"location",}]}}' "https://graph.facebook.com/v2.6/me/messages?access_token=PAGE_ACCESS_TOKEN" But we are not accessing Facebook JSON endpoints directly, all this work is done behind the scenes by the gem that we use. However, we are able to reason deductively and what do we see by looking at this raw JSON? We see that the part enabling user to send his/her location is in the set of quick replies. That means, we need to send any message to the user first and attach a location query to it. facebook-messenger “content_type”:”location” You will also need to enable a webhook under tab in your Facebook developer console. location Webhooks We already have a wrapper over the JSON request in a form of helper that we introduced in a . Here’s how it looked like: say previous part As you can see, this method takes an optional argument that is an array of replies. We used it construct our “menu” of quick replies to show basic commands to our user. Meaning, we can pass (that’s right, Hash inside an Array) to this method and voilà, we’ll send exactly the same JSON we saw above to Facebook API. That’s code reuse! quick_replies [{ content_type: ‘location’ }] Also, remember that we can examine any messages our bot sends us with . Try adding this line to the top of your method inside , right before line: message.inspect wait_for_any_input bot.rb sender_id = message.sender[‘id’] puts "Received '#{message.inspect}' from #{message.sender}" Now, if you open Messenger on your mobile phone, connect to your bot and send your location instead of text, then by examining your logs you can see how the location message looks like to our Santa’s little helper. You should see something like this: rackup facebook-messenger Received '#<Facebook::Messenger::Incoming::Message:0x007fad3890be00 @messaging={"sender"=>{"id"=>"1295486190524658"}, "recipient"=>{"id"=>"1614495692193246"}, "timestamp"=>1484597226465, "message"=>{"mid"=>"mid.1484597226465:b335687852", "seq"=>59617, "attachments"=>[{"title"=>"Andy's Location", "url"=>"https://www.facebook.com/l.php?u=https%3A%2F%2Fwww.bing.com%2Fmaps%2Fdefault.aspx%3Fv%3D2%26pc%3DFACEBK%26mid%3D8100%26where1%3D55.772721087%252C%2B37.683347132677%26FORM%3DFBKPL1%26mkt%3Den-US&h=ATNEWzpLzUVPzSBK4oIF9rpOfG1IDaYzKtbNpDNcLAG9729MvTMvXETHmOTMdhnrQEw5Af2Pg8Ct2uTwXnQoTRI4DbmXWMH-p1ajjeAXhcvMLmMjvsyhCFgMDMM9xkHrFPVTTeg&s=1&enc=AZOftxHdpeOTr32oSlm8KEimjwBgrzLEPiUtBmE5a0pwZZ2BTsgizwnV6p3b8D3HvtE7dmT-hQuRh7Vn8x-vWNPe", "type"=>"location", "payload"=>{"coordinates"=>{"lat"=>55.772721087, "long"=>37.683347132677}}}]}}>' from {"id"=>"1295486190524658"} If we dig in deep enough, we can get coordinates, we don’t even have to make a call to Geocoding anymore! By trial and error we discover that key containing a hash with latitude and longitude values can be accessed from our program like so: Google “coordinates” Ruby message.attachments.first['payload']['coordinates'] Great! Let’s write some new methods. Add this to : bot.rb As you can see, we use helper method to add attach ‘Send Location’ label to your message. In the interface it will look like so: say We will also have to make sure that whatever reply we get in is indeed a location and not a plain old text in order to process it further. lookup_location(sender_id) Add this helper method to : bot.rb Now let’s get down to business and put our main logic in another method: Nice, now our bot is able to (in theory, we haven’t yet hooked this methods up to any bot conversation logic) extract your current GPS coordinates from the location you’ve sent. Let’s take it one step further. What if we could also guess full address based on location? Sure, we can! also lets us do something called . From the sound of it — exactly what we’re looking for! In order to use it we need to send a GET request to a different URL, so let’s create another constant on top of our , next to where we declared . I’ll call it for consistency, but I admit it’s not the best naming. Google Geocoding API reverse geocoding bot.rb API_URL REVERSE_API_URL REVERSE_API_URL = 'https://maps.googleapis.com/maps/api/geocode/json?latlng=' Note: Remember we’re only using Geocoding API without an API key for development and testing. For production you should get it as instructed . Now, let’s update our method to reverse-geocode our coordinates. Note we are reusing and methods that we created earlier. handle_user_location(message) get_parsed_response extract_full_address Great, we have all we need for the feature, now let’s add it to the interface. The simplest place to add it is a persistent menu, defined in your thread settings on top of . Update it: bot.rb Now add a postback to payload that will call our new functionality. Update your block. LOCATION Bot.on :postback Also, add this constant somewhere on top of your file to avoid retyping everywhere we need it: [{ content_type: ‘location’ }] TYPE_LOCATION = [{ content_type: 'location' }] Now whenever a user picks ‘Location lookup’ from the persistent menu, we ask for a location and invite him/her to send it to us. We were also interacting with the user through the set of quick replies. Update it to include a reference to location command: We handle quick replies like any other user command from inside the method. Let’s account for location (and change previous naming while doing so): wait_for_command Notice we start adding to all method calls. That’s because we want to add ‘Send Location’ label to all of our bot’s functions. After all, for a postal address lookup user may want to type partial address in, or just send his/hers current location. Same goes for manual GPS lookup. Now we have to handle location inside and methods. We will have to revisit what we’ve already done. TYPE_LOCATION say show_coordinates show_full_addres Keeping it simple An important principle in code (and in life) OK. It’s time to admit sometimes you can your code. As some of my more experienced readers pointed out to me, introduction of with argument inside the method in was atrocious, because even if it helps us DRY-out 8 or so repeating lines, it makes our code . Also, if at some point we want our features to develop more separate functionality, we want to be able to modify them independent of each other. Let’s work on our mistakes: get rid of method and rewrite two features. over-refactor yield handle_api_request Part 2 very difficult to reason about handle_api_request Overthinking is a form of stupidity. Take-away: Here, we keep all our conditional logic inside our block, we also add a separate method for each lookup in order to follow the and reduce nesting. Bot.on :message SRP That was a lot of code! Whenever you feel lost, go to to see the latest good version of the file. this tutorial’s Github bot.rb Going international You must have noticed the method that we haven’t yet introduced. As of , our bot would just take whatever a user texted and append it to API URL, assuming all is good. But, if you try using international characters in your address (“Красная площадь“ or 東京都), your bot will throw this: encode_ascii Part 2 ERROR URI::InvalidURIError: URI must be ascii only "https://maps.googleapis.com/maps/api/geocode/json?address=\u{424}\u{440}. \u{42d}\u{43d}\u{433}\u{435}\u{43b}\u{44c}\u{441}\u{430}, \u{414}. 23" This error comes from Ruby standard library module that is used by (the gem we use to make HTTP requests). We need a way to convert a string that comes from a user into the URL-friendly ASCII format. uri HTTParty For that, we will use the gem. It has a method to perform on an URL, but you can also do it on any string. Add line to your and in . Then add method, it’s a one-liner. addressable percent-encoding gem ‘addressable’ Gemfile require ‘addressable/uri’ bot.rb ensode_ascii(s) Now a string will turn into . Google API is smart enough to decode it back once you make a request. “Красная площадь, д.1” “%D0%9A%D1%80%D0%B0%D1%81%D0%BD%D0%B0%D1%8F%20%D0%BF%D0%BB%D0%BE%D1%89%D0%B0%D0%B4%D1%8C,%20%D0%B4.1” The alternative is to use gem that will try to any string so will turn into , which is close enough, but will turn into , which has nothing to do with Tokyo (for which that three Japanese characters stood in the first place). Actually, for the transliterated version of Google API will return some address in Florida. That’s probably not what you want. unidecoder transliterate “Красная площадь” “Krasnaia ploshchad’” “東京都” “Dong Jing Du“ “東京都” Robot abuse You always have to assume that your , either because of sheer curiosity, or just by chance, because you did not account for some behaviour. Currently, if you ask user for an address and he/she sends you an image or a video, instead of text, as a reply — your bot is broken. To account for that, you’ll need to introduce a tiny new method: users will do everything they can to break your bot Then perform this check in every action, like so: Why humans have to be so cruel? Spring cleaning Okay, now our bot is well over 200 lines long. That makes our code difficult to maintain. It’s time to put some of common functionality into separate files. We can use classes or modules to break our program into pieces. We will use a simple class wrapper with a class method to invoke part of code ( ). The idea is to do something like this: that’s debatable, and I’d like to hear more about the actual best practice in comments And then call at the top of your . I leave the details to you, in I created two files: and to collect all actions. Greetings.enable bot.rb my project greetings.rb persistent_menu.rb Facebook::Messenger::Thread.set Commencing countdown, engines on Our bot goes to Heroku cloud Now after we tested all we could on localhost ( ) we are ready to send our bot into the world. We will use for deployment. Go to Heroku’s and . yes, I know bot testing is kind of hell Heroku website sign up for free Then, install if you haven’t done it before by following . Also, make sure your project folder is tracked with Git. If not, run: Heroku CLI these instructions git initgit add .git commit -m "First commit" Then authenticate your machine with and create your heroku app by running this command: heroku login heroku create YOUR_BOT_NAME It will create a web address in the form of and add heroku as a remote Git repository. Check if all went well by running: YOUR_BOT_NAME.herokuapp.com git remote -v You should see that two new references (fetch and push) to your . heroku remote Now, and : line both in and . gem does not work with Heroku ( ). Then in your pick your newly created app, go to its and scroll to . Reveal them and type in your and like so: this is important comment out require ‘dotenv/load’ bot.rb app.rb dotenv there’s a fork that does, you can look it up, but I found it easier to set variables directly in the dashboard Heroku dashboard Settings Config variables ACCESS_TOKEN VERIFY_TOKEN Now, the moment of truth. If you followed all the steps then the contents of file should be enough to successfully deploy. Run: config.ru git push heroku master …and behold the magic happening as Heroku creates a functional web app from your code. All you have to do now is to go to Facebook developer’s console and change the address for a webhook from your ngrok URL to your new Heroku app, something like: https://your-bot-name.herokuapp.com/webhook If the webhook verification goes well — ! you have successfully deployed your bot Hooray! For now you can test your bot yourself or add other Facebook users as testers under tab in your Facebook developer console. If you are truly ready to make your bot available to the whole world, you need to go through the . Meaning, actual live people at Facebook HQ will look at your bot (though, briefly) and check if it doesn’t do anything nasty. Go to tab and make your bot “live”. Then go to tab and under add to submission. Follow the provided checklist. Roles verification process App Review Messenger App Review for Messenger pages_messaging You just need to review your pages_messaging in our case You will need a privacy policy for your app that can be easily generated on numerous websites. I found to be most straightforward. Also, you need to supply an icon for your app and it must be exactly 1024x1024 in resolution. this one Now cross fingers and wait. In my case, Facebook reviewers cleared my bot in (I did it on Friday morning, Eastern time). Sometimes reviewers may ask you to record a of your bot, which is done easily with QuickTime. less than 15 minutes screencast Ahoy, Captain! Of course, our Coordinator bot does not provide the best user experience and some people may find it’s interface confusing. The conversation flow is rather rigid and if you make a mistake, you have to start over. However, I feel that some features, like a postal address lookup or finding the name of the street you’re on just by a single message can prove useful (at least, I find myself using them from time to time). You can play with the latest version of this tutorial’s bot by following . this link This project started with a contrived example to play around with the gem as a personal exercise in Ruby. Later I realised it may help and started working on this tutorial. facebook-messenger beginners like me My job was, more than anything, to stimulate your imagination and inspire you to build your own things. So I was happy to learn that one of my readers used this very tutorial to create a bot that . helps navigate Paris subway bot, inspired by this very tutorial Captain Metro If you live in Paris, you can test Captain Metro here . : About me I’m a beginner programmer and ex senior international TV correspondent. I am looking for my first proper job as a developer . Currently, I am having hard time getting employed in Russia, where engineers are extremely good, and it seems no one wants to hire beginners . If you want a motivated coder with well-developed human language skills for your team, I’ll be glad to join, even remotely. You can also invite me for an internship. I recently graduated top of the class from an excellent Le Wagon coding bootcamp in Paris and co-authored HALFWAY.ninja as a graduate project there. It’s an airfare comparator for couples. Go check it out! You can find me on Github , Twitter and Instagram . I speak English, Russian, French, Ruby, JavaScript, Python and Swift and I am currently based in Moscow, Russian Federation. Feel free to write me directly with any offers. P.S. I also write poetry (Russian knowledge required).

Build your first Facebook Messenger bot in Ruby with Sinatra (Part 3/3)

Keeping up with the conversation A less obscure cultural reference In the of this tutorial we set up our page on and hooked it to a server running on our machine through . Then we introduced the gem by the guys at . We also taught our bot to use in order to lookup GPS coordinates for any given address. This is what our bot will look like after we meddle with it some more: Part 1 Facebook Sinatra ngrok facebook-messenger Hyperoslo Google Geocoding API Chatting with the bot on mobile Talk to me OK, let’s get first things about Messenger bots straight. : They adhere to Victorian etiquette for little kids “Do not speak unless spoken to” This is a good rule, because it helps to avoid unsolicited messages aka spam. But how do we provide solicited messages? In the of our bot we just assumed that the user will give us something we can send directly to Google Geocoding API, wait for response and display the result. That assumes user’s prior knowledge about our bot’s intent, which is a very bad way to go about UX. Also, we did not provide any fallbacks in case user types anything that doesn’t have GPS coordinates (surprisingly, ‘Hello’ will yield a result, as Google will just assume we’re looking for ) — in that case, our bot will completely lose its marbles. We need some kind of . first minimalistic version Hella, Iceland conversational loop by Reza Farazmand is licensed under a Poorly Drawn Lines CC BY-NC 3.0 First thing I learned while trying to implement it with gem: call can be made only , otherwise we face all sorts of unexpected behaviour ( ). ! Fine, let’s define separate methods to handle different ways our conversation can go, starting with the most obvious one. Inside delete your Bot.on method that takes a block and replace it with this: facebook-messenger Bot.on :message { |…| block } once per scope correct me in replies if I’m wrong So we need to create more scopes bot.rb Now we need to add a method referenced in our . Put this into your : process_coordinates wait_for_user_input bot.rb Now at the bottom of call our waiting method. It will launch the conversation loop: bot.rb wait_for_user_input From now on we will only engage user if he mentions “coordinates” (“coord” as a shortcut) or “gps” in any context. Then we will ask user to provide a destination for look-up, then we will call Google and display the result. If no result is found, we will notify user and wait for another command. At this stage, our looks like . Hit in your tab with running and restart the server to test it in Messenger. code.rb this Ctrl-C rackup OK, it seems to work. Let’s add features! If we dig inside a we get back from Google, we’ll see that there’s a key called that will return a full postal address for any destination Google can find. Let’s add this as a feature to our bot. JSON formatted_address First, add another clause to our method: when wait_for_user_input Note that that we thought of user misspelling “address”: if he/she types “I need a full adress” (a type of mistake I’d make) our will still match and the function will be called. Put it inside too: regexp show_full_address bot.rb Finally, add this helper method: Great. This is your . Restart the server and test. code at this point Time to refactor! Our bot surely works and can handle two different commands, but its code could certainly use some refactoring: and methods are 80% identical, that means . process_coordinates show_full_address we can do better Refactoring can sure get messy We know that methods can . It seems we may benefit from this language feature to make our code -er. Let’s define another method that will abstract out most of API handling functionality: Ruby accept blocks DRY Then we can change and like so: both process_coordinates show_full_address Great. Now our methods only do stuff that is actually specific to their purpose, the rest is handled by our generic method that handles API-related logic. I know, the concept of Ruby with arguments can be tricky to wrap your head around, especially if you are a beginner coder like me, but I like to think of it as , and you can pass variables back and forth. yield time-space warp that connects two methods This is how I imagine Ruby that takes an argument inside a method (Almost) yield While we are at it, let’s also create an constant, so we can have all our bot’s phrases in one place. Add it on top of your : IDIOMS bot.rb IDIOMS = {not_found: 'There were no resutls. Ask me again, please',ask_location: 'Enter destination'} Now replace your hard coded replies with a reference to like so: IDIOMS message.reply(text: IDIOMS[:ask_location]) This is your . Restart your server and . code at this stage test test test Not just talk Great, out bot still works and we used some clever Ruby, but it is . How the user is supposed to know what to do? Can we guide him? The promise of conversational AI did not really fulfil itself yet, and for now we are stuck with . is . Facebook Messenger has currently three (that I know of) ways to show “menus” to the user: still not the best user experience mixed interfaces Everyone doing it A persistent menu that can always be called from the icon next to text entry field. A “Button” template that let’s you tie action buttons to a message bubble. A set of “quick replies”. Three Facebook-approved ways of presenting button menus to user We will pick as I find them more user-friendly. They are also treated as regular messages by the API, while other buttons implement call to your webhook, which is a bit different concept, as we will see later. quick replies “postback” First, create constant to keep your quick replies in one place: “Payload” sounds confusing, but this is really just another identifier you can assign to user interaction. Think of it as a constant, so we use for our payloads. CAPITAL_LETTERS Okay, now we are going to write a little method that will help us a lot in the future to adopt more approach in the way we code bot’s messages. Remember I told you bots only speak when they are spoken to? Well, that’s true up to a point. A user must that will . Like, sending first message or using a link to your Facebook’s page address (where your bot lives and handles its Messenger interaction). declarative do something expose his ID So, in addition to that we saw earlier, gem creators also gave us method that lets us send messages to user out of the blue once we have his Facebook ID. We are going to wrap it into our own helper: Bot.on :message { |…| block } facebook-messenger Bot.deliver say It will take a user’s id, a text for the message we want to send and optional argument for an array of quick replies. If an argument is supplied, message will be sent with quick replies attached to it, if not — it will be just a text. From this in we know that most users strike a conversation with a bot with some form of ‘ ’ or ‘ ’. We want our bot to present what’s on the menu ASAP, without any unnecessary meet & greet, so we will cheat a little: we’ll introduce the method that will present our array of quick replies to whatever user sends us, be it ‘ ’, ‘ ’ or ‘ ’. Add it to : great article Chatbot’s Life hi hello wait_for_any_input hi bonjour привет bot.rb is how we get user’s ID after he opened the conversation. message.sender[‘id’] Also, let’s change the name of our old method to to avoid any ambiguity. Make sure to change the definition and all possible calls. wait_for_user_input wait_for_command Also, make sure that at the very end of our you now call : bot.rb wait_for_any_input # launch the loopwait_for_any_input Let’s update our : IDIOMS IDIOMS = {not_found: 'There were no resutls. Ask me again, please',ask_location: 'Enter destination',unknown_command: 'Sorry, I did not recognize your command',menu_greeting: 'What do you want to look up?'} Then let’s define our method: show_replies_menu It uses our helper to send user the menu. Then it calls our to handle whatever user does next. Note that we picked the wording of our quick replies to match all possible regexp in . At the same time, user is not obliged to pick any of quick replies. He can shout at us something like “ ” and his command will still be handled, as our regexp is case-insensitive. Now let’s add an clause to our switch statement to handle the case where none of the commands known to us have been matched. Here is our new and improved : say wait_for_command wait_for_command GIVE ME COORDINATES YOU STUPID BOT! else wait_for_command Up until now, when the API request failed, user had to type something like “ ” or “ ” yet again to restart the whole process. That is not very cool, so let’s update our to retry the last command if API did not return any results. For that, we will use some ( ). Look: coordinates full address handle_api_request metaprogramming one of my favourite things about Ruby! By the thread By now your bot should be testable. At last, we will adjust some , so our user is properly greeted and presented with “Get Started” button that allows to strike the conversation. We will also add a persistent menu that will give user constant access two both features, even if he’s in the middle of something else. Here’s how it will look like: thread settings Making our bot nicer This will require us to use ’s functionality. First, go to your Facebook developer console, under click and enable . facebook-messenger Bot.on :postback { |..| block } “Webhooks” “Edit events“ messaging_postbacks Add this to your : bot.rb Now add some logic to handle postback events: And that’s all for Part 2! We have a fully functional (though may be not particularly sexy in order to attract VC millions) bot that we wrote in under 200 lines of pure Ruby code. part of this tutorial to see how we add some final bells and whistles and deploy to Heroku, so our can finally go live. Follow the third and the last Smooth Coordinator All the code for our bot at this stage of its development can be found on my Github . You can find the code for a complete project (still WIP on the time of this writing) in the same repo, but in the main branch. Feel free to fork it, clone it and play with it. GO TO PART 3 : About me I’m a beginner web developer, ex senior international TV correspondent, and young father who is looking for a first proper programmer job. Aside from obsessing about coding style and trying to pump my head full of technical literature, I recently graduated top of the class from an excellent Le Wagon coding bootcamp in Paris and co-authored Halfway.ninja as a graduate project there. It’s an airfare comparator for couples. Go check it out! You can find me on Github , Twitter and Instagram . I also own this domain . I am currently available for hire, be it an inspiring internship, freelance or even full-time work. I speak English, Russian, French, Ruby, JavaScript, Python and Swift and I am currently based in Moscow, Russian Federation. Feel free to write me directly with any offers.

Build your first Facebook Messenger bot in Ruby with Sinatra (Part 2/3)

Here is the Part 1 of making a simple Facebook bot that harnesses the power of Google Maps Geocoding API . In Part 2 we will add more features, refactor the code, and make everything DRYer . In Part 3 we will deploy our bot to Heroku and enhance its interface. An obscure cultural reference for Soviet-born readers This tutorial assumes you already have a usual Ruby environment installed on your machine and you are aware of the brave new world Ruby gems give us. Here’s a preview of what we are going to build by the end of the second part: Cool, huh? Preface Let’s face the inconvenient truth. Bots are overhyped, mainly because . The majority of them. I am 32 years old, excited about all things digital since the age of 15, and I learned my speed typing on . It is the chat service that first appeared in 1988 and anticipated the by a good year or two. By the time web chatrooms became a thing, IRC already had a global community of hackers. I met at least two of my current best friends there, when I had my own channel on DALnet named #402. Yes, it had channels that started with the hash sign (I look at you, Slack, kudos for reviving a tech). It also had . they are still dumb IRC World Wide Web 25 years old bots Old is the new young, as seen by Google Trends So no wonder when bots became a household word again in 2016, my friends and I just shrugged. Of course, when you add some serious AI voodoo, bots can achieve . But, seriously, let’s be honest with each other, my fellow developers: your average hyped-up bot is not much smarter than a Perl script that on IRC server in 2002. amazing feats ran A bot-related prehistoric meme circa 1995 All that considered, . Even if they never smarten up. Why so? Bots can take a lot of heat off the front end and reduce developing cost for the apps as developers can focus on business logic, not looks. JavaScript community , new front-end framework appears every other week, and any more or less decent modern interface would require a rock-star programmer, who happens to also be a designer an UX-engineer. While it’s good news for smart guys, it’s bad news for those who have to hire more of them just to look well. I still believe bots are great and they are going to be big is a mess now and Meet bots. As you will see shortly, you just need a micro-framework and a back end language of choice (surely, it can be JS as in ) to quickly build an interactive app. And it may actually engage users, if you do something useful with it. NodeJS Enough talk, let’s build one Frank Sinatra after a certain Ruby framework stole his name and his hat As much as I want to use some more Rails (I started it less than three months ago at bootcamp in Paris and have only made two student projects with it), our weapon of choice will be — and the following screenshot is the reason why. learning Le Wagon Sinatra Folder structure of a Rails app (right) vs. the structure of a Sinatra app (left) Sinatra allows you to create a functioning web app in just few lines of code, without any boilerplate. In our example, we will only need Sinatra to do one specific thing, the rest will be handled by the incredible , created by some genius guys in . facebook-messenger gem Oslo Go to your console and type: gem install facebook-messenger The bot runs on , same as Sinatra (and , for that matter). So, in order to start, we will need a . Create a folder for your project (mine is named coordinator-bot) and named in it. stands for rack-up (and a top-level internet domain for Russian Federation). Put this inside: Rack Rails rackup file place a file config.ru .ru Next, named in the same folder and put in the following: create a file app.rb Next, create , called , with this content: another file Gemfile Now go to your command line and run: bundle install OK, time to create our app on Facebook Up until now, you were a user, now it’s time to become a Facebook developer. Go to , login with your usual Facebook account and in the top right corner of the screen pick . Facebook https://developers.facebook.com/ “Add a new app” Enter your app name (use your fantasy!) and don’t forget to set a category as . “Apps for Messenger” Facebook then will make sure you are not a robot, which is ironic, but avoids . Then, under pick and pick a category. Mine was “Brand or Product”. Skynet scenario “Token generation” “Create new page” Skip everything in a wizard menu (of course, if you want to make your test page look nice, be my guest!), go back to your developer’s dashboard and generate a token for the new page. Save it somewhere on your computer (but !), you will need it in a moment. don’t give to anyone or post publicly You will have two things from your Facebook dashboard that you are supposed to keep secret. Your (we’ll call it ) and the token for webhook verification ( ). Page token was just generated and the verification token can be anything you want, just make sure to remember it later. Next, open another tab in your Terminal and type and while using your own values after the “=“ sign (also, note there are no quotes around tokens). That is called . page token ACCESS_TOKEN VERIFY_TOKEN export ACCESS_TOKEN= export VERIFY_TOKEN=, setting environment variables With Rails this sort of thing would be handled by , but I couldn’t make it work under Sinatra, my best guess: it’s not supported (feel free to correct me in comments) Figaro gem NB! Comment out _require_relative 'bot'_ from your _config.ru_ file before you proceed. You will need to put this line back when we actually create a bot file, but for now, just to test that _rackup_ is working, we will need to temporarily disable it. Go back to the command line from inside your project folder ( it should be you just typed your environment variables in) and type this: It’s time to start our servers. Note! the same Terminal tab rackup -p 5000 You should see this: You can pick another port number ( , anyone?), but it should be the same as the one we will pipe through . Go to website, download it and put the executable inside your project folder or one of its parents. Then you can run it like so (in a new tab). 1337 Ngrok Ngrok’s ./ngrok http 5000 With this effect: Now your whatever happens on the port 5000 on your will be seen broadcasted on The Internet under a domain name that will be generated uniquely for you and will resemble something like this: localhost . http://982bd57f8.ngrok.io Go to this address in your browser: you should see the text . That’s right, that’s what these lines in our were about: “Nothing to see here” app.rb In your Facebook dashboard, where you just generated the access token for your Facebook page, scroll a bit down and under click Switch to your terminal (you ran that command in a new tab, right?), copy the URL under “Forwarding” (make sure you copy the one that starts with and attach to it. This is how we named a path under which our server will communicate with Facebook. We could call it — it’s up to you. Under put the same string you came up with earlier while setting your environment variables. Tick the “messages” mark. “Webhooks” “Setup Webhooks ”. ./ngrok ) https:// /webhook /bot “Verify Token” Now you can . If you set up your server correctly, Facebook will call /webhook path on your ngrok URL, send you a ‘challenge’ (which is just a random string of digits) and wait for it to be echoed back. These lines in do it: click “Verify and Save” app.rb That was actually all we needed Sinatra for. Moving on. Bot, meet your maker All further programming will be done inside our file. Go ahead and create one in your project folder. Your first bot will just say “Hello!” to whatever humans send him. bot.rb Remember, in any of your files you have to go back to the terminal tab where your rack server is running (you can leave ngrok alone), hit Ctrl-C and restart it. Also, now you will need to in your every time you change something require_relative ‘bot’ config.ru Now open your Facebook Messenger (whether desktop or mobile), find your bot by using your recently created page name under “Search Messenger” and type anything. He will respond “Hello!”. Congratulations, you’ve just had a first conversation with your own bot! In your server tab you should see something like: "POST /webhook HTTP/1.1" 200 - 0.0011 That means bot had sent an request to your server on its /webhook path and the server (facebook-messenger gem) replied accordingly. You can add this line at the beginning of the block. HTTP POST Bot.on Bot.on :message do |message|puts "Received '#{message.inspect}' from #{message.sender}"(…rest of the code in bot.rb) It will let you learn more about the conversation your bot is having, your server tab will log something like this: Okay, your bot is not particularly smart at this point. Let’s add some real world functionality. How about bot giving you GPS coordinates for any address in the world when you type it it? We’ll use All you need is to send a GET request (you should also put your private API key at the end of the URL, but for testing we can get away without one, check Google’s doc for more info on API keys): Google Maps Geocoding API . https://maps.googleapis.com/maps/api/geocode/json?address=ANY_STRING_THAT_LOOKS_LIKE_ADDRESS Google will do its magic (for example, it will figure out that you want Moscow, Russia, not Moscow, Texas, if you connect with a Russian provider) and it will send back a that contains all sort of useful data, namely the latitude and the longitude. JSON We will use an amazing gem to make our requests. We already installed it in our project during the initial . Add this method to your HTTParty bundle install bot.rb We use Ruby’s standard JSON parsing functionality to turn response from API into a regular Hash object. Make sure your has the line at the top. bot.rb require ‘json’ Now dig inside the hash to find our coordinates. Add this method to . bot.rb Update your Bot block to send back the data you got from the API. Replace your method with this: Bot.on In the end your should look like this: bot.rb Great! Go ahead and test your bot! It should do this. YAY! Our first bot that makes sense! Right now our bot is still very stupid. It only can spit back coordinates to you when you enter a valid address. No hellos, no good-byes. If you type something Google can’t find, it will just hang and you will have to restart your Rack. In the of this tutorial we will make our bot smarter and it will be able to keep up with a simple conversation. We will also handle the case where API does not return any results, and we will teach it to to look up the full postal address lookup for any location. Part 2 That’s all for now. I hope you enjoyed it! Go check out Part 2! All the code for our bot at this stage of its development can be found on . my Github You can find the code for a final project (still WIP on the time of this writing) in the same repo, but in the . main branch Feel free to fork it, clone it and play with it. : Disclaimer I’m a beginner web developer, ex senior international TV correspondent, and young father with zero (nil, null, zilch) experience in IT. Aside from obsessing about coding style and trying to pump my head full of technical literature while looking for my first serious dev gig, I recently graduated top of the class from an excellent Le Wagon coding bootcamp in Paris and co-authored Halfway.ninja as a graduate project there. It’s an airfare comparator for couples. Go check it out! You can find me on Github , Twitter and Instagram . I also own this domain . I am also available for hire, be it an inspiring internship, freelance or even full-time work. I speak English, Russian, French, Ruby, JavaScript, Python and Swift and I am currently based in Moscow, Russian Federation. Feel free to write me directly with any offers (or death threats).

Build your first Facebook Messenger bot in Ruby with Sinatra and “facebook-messenger” gem (Part…

Periods - Do Women Really Need Them?

LONDON, United Kingdom, October 9th, 2024/Chainwire/--Stablecoin Standard, the industry body for stablecoin issuers globally, today announced that their recently unveiled set of global standards for stablecoin issuers have been endorsed by some of the leading stablecoin issuers and ecosystem participants in the industry. Among those who have endorsed are Archblock, BiLira, Bitstamp, GMO-Z.com Trust Company (‘GMO Trust’), JST Digital, Fireblocks, Solana Foundation, StraitsX and Zodia Markets, signaling a new era of cooperation and standardization within the stablecoin industry. The standards, announced by Beth Haddock, Global Policy Lead at Stablecoin Standard, at the Annual Flagship Event in Singapore, were designed to promote operational resilience, transparency and consistent issuer commitments globally. Stablecoin Standard’s Policy Working Group created the high-level standards that are both general and actionable, while being sensitive to the innovation in the market. Beth Haddock, Global Policy Lead at Stablecoin Standard, commented on the endorsements: "Their endorsement not only validates the rigor of our proposed framework but also underscores the importance of creating a stable, transparent, and resilient environment for digital currencies. This milestone, following discussions at our annual meeting, sets a strong foundation for the continued evolution of the ecosystem.” The endorsement of the standards lays the groundwork for a stablecoin ecosystem that prioritizes transparency, security and consumer protection. With increased scrutiny from regulators and growing demand for digital assets, unified standards can provide clarity and assurance to both industry participants and the public. Stablecoin Standard’s new framework aims to accelerate the adoption of stablecoins by fostering greater confidence among consumers, regulators, and traditional financial institutions. Ramy Soliman, Co-Founder of Stablecoin Standard, commented on the endorsements: “The endorsement of our global standards by leading stablecoin issuers such as, BiLira and ecosystem participants, including industry leaders like Solana, Zodia Markets and JST Digital, is a vital step toward establishing a unified, trusted framework for the entire sector. As stablecoins continue to redefine the future of digital payments, these standards will provide the foundation for long-term growth, transparency, and security. This collective commitment—solidified during discussions at our annual meeting—not only underscores the industry’s dedication to fostering innovation but also demonstrates a concerted effort to align with evolving regulatory expectations and build the consumer trust essential for stablecoins to thrive globally.” Stablecoin Standard and its endorsing members plan to continue refining these standards for implementation with the goal of achieving industry-wide adherence by Q4 2025. Quotes from Endorsers: Sinan Koç, Co-founder and CEO of BiLira, commented on their endorsement, “As a stablecoin issuer, BiLira has always prioritized transparency, security, and adherence to high standards, which is why we are proud to endorse the Stablecoin Standard’s newly introduced set of global standards. TRYB is governed with a commitment to uphold these principles, which we believe are essential for fostering trust and stability in the rapidly evolving digital asset space. We support this initiative as a significant step towards a more resilient and unified stablecoin ecosystem.” Ran Goldi, SVP Payments and Network at Fireblocks, commented on their endorsement, "With more than a dozen stablecoins issued on Fireblocks, we strongly believe standards are the right path for our ecosystem with regard to interoperability and reaching the holy grail of instant liquidity any time, anywhere. SCS is taking a big, bold step, and we proudly endorse and stand with them on this journey.” Kenny Chan, Head of StraitsX, commented on their endorsement, “As one of the leading regulated stablecoin issuers in Asia, StraitsX is committed to upholding the highest standards of transparency and operational resilience. We are proud to support the Stablecoin Standard’s newly introduced global standards, which will help build greater trust in the stablecoin ecosystem and ensure that digital currencies can be securely and seamlessly adopted by businesses and consumers worldwide. By working collaboratively with key industry participants, we believe these standards will provide a strong foundation for the future of stablecoins, promoting innovation while ensuring compliance with evolving regulatory frameworks.” About Stablecoin Standard Stablecoin Standard (SCS) is the industry body focused on setting operational, transparency, and product related standards for stablecoins. The SCS plans to achieve industry wide standards by sharing international best practices, business development use cases, forming industry led working groups defining what a high-quality liquid stablecoin should look like, and engaging with policymakers domestically & internationally. The SCS ecosystem consists of over 30 advisory board members, industry partners and issuers that offer digital currencies in global jurisdictions such as the US, EU, Singapore, Australia, and Turkey - among others. Users can follow the Stablecoin Standard on LinkedIn and X and to learn more, please visit: https://stablecoinstandard.com/ Contact Kevin McGrath stablecoinstandard@mgroupsc.com This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here LONDON, United Kingdom, October 9th, 2024/Chainwire/--Stablecoin Standard, the industry body for stablecoin issuers globally, today announced that their recently unveiled set of global standards for stablecoin issuers have been endorsed by some of the leading stablecoin issuers and ecosystem participants in the industry. industry body industry body Among those who have endorsed are Archblock, BiLira, Bitstamp, GMO-Z.com Trust Company (‘GMO Trust’), JST Digital, Fireblocks, Solana Foundation, StraitsX and Zodia Markets, signaling a new era of cooperation and standardization within the stablecoin industry. The standards, announced by Beth Haddock, Global Policy Lead at Stablecoin Standard, at the Annual Flagship Event in Singapore, were designed to promote operational resilience, transparency and consistent issuer commitments globally. Stablecoin Standard’s Policy Working Group created the high-level standards that are both general and actionable, while being sensitive to the innovation in the market. The standards, The standards, Beth Haddock, Global Policy Lead at Stablecoin Standard, commented on the endorsements: "Their endorsement not only validates the rigor of our proposed framework but also underscores the importance of creating a stable, transparent, and resilient environment for digital currencies. This milestone, following discussions at our annual meeting, sets a strong foundation for the continued evolution of the ecosystem.” Beth Haddock, Global Policy Lead at Stablecoin Standard, commented on the endorsements: "Their endorsement not only validates the rigor of our proposed framework but also underscores the importance of creating a stable, transparent, and resilient environment for digital currencies. This milestone, following discussions at our annual meeting, sets a strong foundation for the continued evolution of the ecosystem.” The endorsement of the standards lays the groundwork for a stablecoin ecosystem that prioritizes transparency, security and consumer protection. With increased scrutiny from regulators and growing demand for digital assets, unified standards can provide clarity and assurance to both industry participants and the public. Stablecoin Standard’s new framework aims to accelerate the adoption of stablecoins by fostering greater confidence among consumers, regulators, and traditional financial institutions. Ramy Soliman, Co-Founder of Stablecoin Standard, commented on the endorsements: “The endorsement of our global standards by leading stablecoin issuers such as, BiLira and ecosystem participants, including industry leaders like Solana, Zodia Markets and JST Digital, is a vital step toward establishing a unified, trusted framework for the entire sector. As stablecoins continue to redefine the future of digital payments, these standards will provide the foundation for long-term growth, transparency, and security. This collective commitment—solidified during discussions at our annual meeting—not only underscores the industry’s dedication to fostering innovation but also demonstrates a concerted effort to align with evolving regulatory expectations and build the consumer trust essential for stablecoins to thrive globally.” Stablecoin Standard and its endorsing members plan to continue refining these standards for implementation with the goal of achieving industry-wide adherence by Q4 2025. Quotes from Endorsers: Sinan Koç, Co-founder and CEO of BiLira, commented on their endorsement, “As a stablecoin issuer, BiLira has always prioritized transparency, security, and adherence to high standards, which is why we are proud to endorse the Stablecoin Standard’s newly introduced set of global standards. TRYB is governed with a commitment to uphold these principles, which we believe are essential for fostering trust and stability in the rapidly evolving digital asset space. We support this initiative as a significant step towards a more resilient and unified stablecoin ecosystem.” Sinan Koç, Co-founder and CEO of BiLira, commented on their endorsement, “As a stablecoin issuer, BiLira has always prioritized transparency, security, and adherence to high standards, which is why we are proud to endorse the Stablecoin Standard’s newly introduced set of global standards. TRYB is governed with a commitment to uphold these principles, which we believe are essential for fostering trust and stability in the rapidly evolving digital asset space. We support this initiative as a significant step towards a more resilient and unified stablecoin ecosystem.” Ran Goldi, SVP Payments and Network at Fireblocks, commented on their endorsement, "With more than a dozen stablecoins issued on Fireblocks, we strongly believe standards are the right path for our ecosystem with regard to interoperability and reaching the holy grail of instant liquidity any time, anywhere. SCS is taking a big, bold step, and we proudly endorse and stand with them on this journey.” Ran Goldi, SVP Payments and Network at Fireblocks, commented on their endorsement, "With more than a dozen stablecoins issued on Fireblocks, we strongly believe standards are the right path for our ecosystem with regard to interoperability and reaching the holy grail of instant liquidity any time, anywhere. SCS is taking a big, bold step, and we proudly endorse and stand with them on this journey.” Kenny Chan, Head of StraitsX, commented on their endorsement, “As one of the leading regulated stablecoin issuers in Asia, StraitsX is committed to upholding the highest standards of transparency and operational resilience. We are proud to support the Stablecoin Standard’s newly introduced global standards, which will help build greater trust in the stablecoin ecosystem and ensure that digital currencies can be securely and seamlessly adopted by businesses and consumers worldwide. By working collaboratively with key industry participants, we believe these standards will provide a strong foundation for the future of stablecoins, promoting innovation while ensuring compliance with evolving regulatory frameworks.” Kenny Chan, Head of StraitsX, commented on their endorsement, “As one of the leading regulated stablecoin issuers in Asia, StraitsX is committed to upholding the highest standards of transparency and operational resilience. We are proud to support the Stablecoin Standard’s newly introduced global standards, which will help build greater trust in the stablecoin ecosystem and ensure that digital currencies can be securely and seamlessly adopted by businesses and consumers worldwide. By working collaboratively with key industry participants, we believe these standards will provide a strong foundation for the future of stablecoins, promoting innovation while ensuring compliance with evolving regulatory frameworks.” About Stablecoin Standard Stablecoin Standard (SCS) is the industry body focused on setting operational, transparency, and product related standards for stablecoins. The SCS plans to achieve industry wide standards by sharing international best practices, business development use cases, forming industry led working groups defining what a high-quality liquid stablecoin should look like, and engaging with policymakers domestically & internationally. The SCS ecosystem consists of over 30 advisory board members, industry partners and issuers that offer digital currencies in global jurisdictions such as the US, EU, Singapore, Australia, and Turkey - among others. Users can follow the Stablecoin Standard on LinkedIn and X and to learn more, please visit: https://stablecoinstandard.com/ LinkedIn LinkedIn X X https://stablecoinstandard.com/ https://stablecoinstandard.com/ Contact Kevin McGrath stablecoinstandard@mgroupsc.com This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here here here

Leading Stablecoin Issuers And Crypto Firms Embrace International Set Of Stablecoin Standards

Nayrir Emisores Stablecoin Ukat Firmas Cripto ukanakax Conjunto Internacional De Estándares De Stablecoin ukar katuqapxi

Els principals emissors de Stablecoin i les empreses de criptografia adopten un conjunt internacional d'estàndards Stablecoin

Führende Stablecoin-Emittenten und Krypto-Unternehmen übernehmen internationale Stablecoin-Standards

Los principales emisores de monedas estables y empresas de criptomonedas adoptan un conjunto internacional de estándares para monedas estables

Stablecoin-ի առաջատար թողարկողները և կրիպտո ընկերությունները ընդունում են Stablecoin ստանդարտների միջազգային փաթեթը

主要なステーブルコイン発行者と暗号通貨企業が国際的なステーブルコイン基準を採用

អ្នកចេញ Stablecoin ឈានមុខគេ និងក្រុមហ៊ុន Crypto ទទួលយកស្តង់ដារអន្តរជាតិនៃ Stablecoin

선도적인 스테이블코인 발행자와 암호화폐 회사, 국제 스테이블코인 표준 채택

Umalliq Stablecoin Emisorkuna Hinallataq Crypto Firmakuna Abrazan Internacional Conjunto De Stablecoin Estándares

ผู้ให้บริการ Stablecoin ชั้นนำและบริษัท Crypto ต่างยอมรับมาตรฐาน Stablecoin ระดับสากล

معروف Stablecoin جاری کرنے والے اور Crypto فرمیں Stablecoin کے معیارات کے بین الاقوامی سیٹ کو قبول کرتی ہیں

领先的稳定币发行者和加密货币公司采用国际稳定币标准

Table of Links Abstract and 1. Introduction 2. Methods 2.1. Modeling Panspermia and Terraformation 2.2. Identifying the Presence of Terraformed Planets and 2.3. Software and Availability 3. Results 3.1. Panspermia can increase the correlation between planets’ compositions and positions 3.2. Likely terraformed planets can be identified from clustering 4. Summary and Discussion 5. Acknowledgements and References APPENDIX A. Appendix APPENDIX A. APPENDIX A.1. The mantel coefficient does not strictly increase with the proliferation of life We investigated how changing the parameters of our model influenced the Mantel coefficient as a function of the ratio of terraformed planets. We find a few characteristic shapes of curves observed: flat, increasing then decreasing, and mostly increasing. A.1.1. Additional Parameters Mutation. Depending on the scenario, we include either a 0% or 10% chance of mutation for each element of the planet’s new composition, meaning that in the 10% scenario, with our length 10 composition vector, on average, 1 of the 10 elements is mutated during each terraformation event. Mutated elements are chosen from a continuous uniform random distribution of [0, 1], just like the initial compositions were chosen. Mutation is meant to represent the change in the kind of planetary observable characteristics which are compatible with life as life evolves over time. Number of origins of life (OoL). Simulations are initialized with either 1 or 10 OoL (Fig. A2). Compositions inherited from pre-terraformed planet. We vary the number of elements that the post-terraformed planet inherits from the pre-terraformed planet, n ∈ [0, 1, 2, 5], with the rest of the composition inherited from the incoming life. A.1.2. Flat curve A.1.3. Increasing then decreasing curve When simulations are initialized with a single OoL, the progression of planet terraformation over time leads to an increasing then decreasing shaped Mantel coefficient curve, where the Mantel coefficient peaks after some of the planets have been terraformed, and then decreases afterwards (Fig. A1, data in green). Because the Mantel coefficient is measuring the correlation between positional and compositional distance matrices of planets, this correlation will decrease if either distance matrix becomes too homogeneous. With a single OoL, this is exactly what begins to happen with the compositional distance matrix, with the decline especially pronounced in the scenario with perfect replication (Fig. A1B, green box). A.1.4. Mostly increasing curve Authors:
(1) Harrison B. Smith, Earth-Life Science Institute, Tokyo Institute of Technology, Ookayama, Meguro-ku, Tokyo, Japan, and Blue Marble Space Institute of Science, Seattle, Washington, USA (hbs@elsi.jp);
(2) Lana Sinapayen, Sony Computer Science Laboratories, Kyoto, Japan and National Institute for Basic Biology, Okazaki, Japan (lana.sinapayen@gmail.com). This paper is available on arxiv under CC BY-NC-ND 4.0 Deed license. Table of Links Abstract and 1. Introduction Abstract and 1. Introduction 2. Methods 2.1. Modeling Panspermia and Terraformation 2.1. Modeling Panspermia and Terraformation 2.2. Identifying the Presence of Terraformed Planets and 2.3. Software and Availability 2.2. Identifying the Presence of Terraformed Planets and 2.3. Software and Availability 3. Results 3.1. Panspermia can increase the correlation between planets’ compositions and positions 3.1. Panspermia can increase the correlation between planets’ compositions and positions 3.2. Likely terraformed planets can be identified from clustering 3.2. Likely terraformed planets can be identified from clustering 4. Summary and Discussion 4. Summary and Discussion 5. Acknowledgements and References 5. Acknowledgements and References APPENDIX APPENDIX A. Appendix A. Appendix APPENDIX A. APPENDIX A.1. The mantel coefficient does not strictly increase with the proliferation of life A.1. The mantel coefficient does not strictly increase with the proliferation of life The mantel coefficient does not strictly increase with the proliferation of life We investigated how changing the parameters of our model influenced the Mantel coefficient as a function of the ratio of terraformed planets. We find a few characteristic shapes of curves observed: flat, increasing then decreasing, and mostly increasing. A.1.1. Additional Parameters Additional Parameters Mutation . Depending on the scenario, we include either a 0% or 10% chance of mutation for each element of the planet’s new composition, meaning that in the 10% scenario, with our length 10 composition vector, on average, 1 of the 10 elements is mutated during each terraformation event. Mutated elements are chosen from a continuous uniform random distribution of [0, 1], just like the initial compositions were chosen. Mutation is meant to represent the change in the kind of planetary observable characteristics which are compatible with life as life evolves over time. Mutation Number of origins of life (OoL). Simulations are initialized with either 1 or 10 OoL (Fig. A2). Number of origins of life (OoL). Compositions inherited from pre-terraformed planet. We vary the number of elements that the post-terraformed planet inherits from the pre-terraformed planet, n ∈ [0, 1, 2, 5], with the rest of the composition inherited from the incoming life. Compositions inherited from pre-terraformed planet. A.1.2. Flat curve Flat curve A.1.3. Increasing then decreasing curve Increasing then decreasing curve When simulations are initialized with a single OoL, the progression of planet terraformation over time leads to an increasing then decreasing shaped Mantel coefficient curve, where the Mantel coefficient peaks after some of the planets have been terraformed, and then decreases afterwards (Fig. A1, data in green). Because the Mantel coefficient is measuring the correlation between positional and compositional distance matrices of planets, this correlation will decrease if either distance matrix becomes too homogeneous. With a single OoL, this is exactly what begins to happen with the compositional distance matrix, with the decline especially pronounced in the scenario with perfect replication (Fig. A1B, green box). A.1.4. Mostly increasing curve Mostly increasing curve Authors: (1) Harrison B. Smith, Earth-Life Science Institute, Tokyo Institute of Technology, Ookayama, Meguro-ku, Tokyo, Japan, and Blue Marble Space Institute of Science, Seattle, Washington, USA (hbs@elsi.jp); (2) Lana Sinapayen, Sony Computer Science Laboratories, Kyoto, Japan and National Institute for Basic Biology, Okazaki, Japan (lana.sinapayen@gmail.com). Authors: Authors: (1) Harrison B. Smith, Earth-Life Science Institute, Tokyo Institute of Technology, Ookayama, Meguro-ku, Tokyo, Japan, and Blue Marble Space Institute of Science, Seattle, Washington, USA ( hbs@elsi.jp ); hbs@elsi.jp (2) Lana Sinapayen, Sony Computer Science Laboratories, Kyoto, Japan and National Institute for Basic Biology, Okazaki, Japan ( lana.sinapayen@gmail.com ). lana.sinapayen@gmail.com This paper is available on arxiv under CC BY-NC-ND 4.0 Deed license. This paper is available on arxiv under CC BY-NC-ND 4.0 Deed license. available on arxiv

A Biosignature Based on Modeling Panspermia and Terraformation: Appendix

Table of Links Abstract and 1. Introduction 2. Methods 2.1. Modeling Panspermia and Terraformation 2.2. Identifying the Presence of Terraformed Planets and 2.3. Software and Availability 3. Results 3.1. Panspermia can increase the correlation between planets’ compositions and positions 3.2. Likely terraformed planets can be identified from clustering 4. Summary and Discussion 5. Acknowledgements and References APPENDIX A. Appendix 5. ACKNOWLEDGEMENTS The authors would like to thank Estelle Janin and Cole Mathis for encouraging and productive conversations, and for feedback on the manuscript. REFERENCES Affholder, A., Guyot, F., Sauterey, B., Ferri`ere, R., & Mazevet, S. 2021, Nature Astronomy, doi: 10.1038/s41550-021-01372-6 Balbi, A., & Grimaldi, C. 2020, Proceedings of the National Academy of Sciences, 117, 21031, doi: 10.1073/pnas.2007560117 Bartlett, S., Li, J., Gu, L., et al. 2022, Nature Astronomy, 6, 387, doi: 10.1038/s41550-021-01559-x Benner, S. A. 2010, Astrobiology, 10, 1021, doi: 10.1089/ast.2010.0524 Bich, L., & Green, S. 2018, Synthese, 195, 3919, doi: 10.1007/s11229-017-1397-9 Bixel, A., & Apai, D. 2021, The Astronomical Journal, 161, 228, doi: 10.3847/1538-3881/abe042 Carroll-Nellenback, J., Frank, A., Wright, J., & Scharf, C. 2019, The Astronomical Journal, 158, 117, doi: 10.3847/1538-3881/ab31a3 Catling, D. C., Krissansen-Totton, J., Kiang, N. Y., et al. 2018, Astrobiology, 18, 709, doi: 10.1089/ast.2017.1737 Checlair, J. H., Villanueva, G. L., Hayworth, B. P. C., et al. 2021, The Astronomical Journal, 161, 150, doi: 10.3847/1538-3881/abdb36 Cleaves, H. J., Hystad, G., Prabhu, A., et al. 2023, Proceedings of the National Academy of Sciences, 120, e2307149120, doi: 10.1073/pnas.2307149120 Cleland, C. E. 2012, Synthese, 185, 125, doi: 10.1007/s11229-011-9879-7 Cleland, C. E., & Chyba, C. F. 2002, Origins of Life and Evolution of the Biosphere, 32, 387, doi: 10.1023/A:1020503324273 Cockell, C. S. 2022, in New Frontiers in Astrobiology (Elsevier), 1–17, doi: 10.1016/B978-0-12-824162-2.00009-9 Gobat, R. 2021, The Astrophysical Journal, 16 Green, J., Hoehler, T., Neveu, M., et al. 2021, Nature, 598, 575, doi: 10.1038/s41586-021-03804-9 Grimaldi, C., Lingam, M., & Balbi, A. 2021, The Astronomical Journal, 162, 23, doi: 10.3847/1538-3881/abfe61 Hahsler, M., Piekenbrock, M., & Doran, D. 2019, Journal of Statistical Software, 91, 1, doi: 10.18637/jss.v091.i01 Harman, C. E., & Domagal-Goldman, S. 2018, in Handbook of Exoplanets, ed. H. J. Deeg & J. A. Belmonte (Cham: Springer International Publishing), 1–22, doi: 10.1007/978-3-319-30648-3 71-1 Janin, E. 2021, Astronomy & Geophysics, 62 Kim, H., Smith, H. B., Mathis, C., Raymond, J., & Walker, S. I. 2019, Science Advances, 5, eaau0149, doi: 10.1126/sciadv.aau0149 Kinney, D., & Kempes, C. 2022, Biology & Philosophy, 37, 22, doi: 10.1007/s10539-022-09859-w Kovacevic, A. B. 2022, arXiv:2202.07347 [astro-ph, q-bio]. http://arxiv.org/abs/2202.07347 Lenardic, A., Seales, J., & Covington, A. 2022, International Journal of Astrobiology, 1, doi: 10.1017/S1473550422000222 Lenardic, A., Seales, J., Moore, W. B., & Jellinek, A. M. 2023, Nature Astronomy, 1, doi: 10.1038/s41550-023-02031-8 Lin, H. W., & Loeb, A. 2015, The Astrophysical Journal, 810, L3, doi: 10.1088/2041-8205/810/1/L3 Lingam, M., Grimaldi, C., & Balbi, A. 2021, Monthly Notices of the Royal Astronomical Society, 509, 4365, doi: 10.1093/mnras/stab3108 Lynas, M., Houlton, B. Z., & Perry, S. 2021, Environmental Research Letters, 16, 114005, doi: 10.1088/1748-9326/ac2966 Mariscal, C., & Doolittle, W. F. 2020, Synthese, 197, 2975, doi: 10.1007/s11229-018-1852-2 Marshall, S. M., Mathis, C., Carrick, E., et al. 2021, Nature Communications, 12, 3033, doi: 10.1038/s41467-021-23258-x Mix, L. J. 2015, Astrobiology, 15, 15, doi: 10.1089/ast.2014.1191 Moore, W. B., Lenardic, A., Jellinek, A. M., et al. 2017, Nature Astronomy, 1, 1, doi: 10.1038/s41550-017-0043 Olejarz, J., Iwasa, Y., Knoll, A. H., & Nowak, M. A. 2021, Nature Communications, 12, 3985, doi: 10.1038/s41467-021-23286-7 Pacetti, E., Turrini, D., Schisano, E., et al. 2022, The Astrophysical Journal, 937, 36, doi: 10.3847/1538-4357/ac8b11 Rideout, J. R., Caporaso, G., Bolyen, E., et al. 2023, biocore/scikit-bio: scikit-bio 0.5.9: Maintenance release, Zenodo, doi: 10.5281/zenodo.8209901 Satopaa, V., Albrecht, J., Irwin, D., & Raghavan, B. 2011, in 2011 31st International Conference on Distributed Computing Systems Workshops (Minneapolis, MN, USA: IEEE), 166–171, doi: 10.1109/ICDCSW.2011.20 Schwieterman, E. W., Meadows, V. S., Domagal-Goldman, S. D., et al. 2016, The Astrophysical Journal, 819, L13, doi: 10.3847/2041-8205/819/1/L13 Schwieterman, E. W., Kiang, N. Y., Parenteau, M. N., et al. 2018, Astrobiology, 18, 663, doi: 10.1089/ast.2017.1729 Smith, H. B., & Mathis, C. 2023, BioEssays, 2300050, doi: 10.1002/bies.202300050 Smith, H. H., Hyde, A. S., Simkus, D. N., et al. 2021, Life, 11, 498, doi: 10.3390/life11060498 Sol´e, R. V., & Munteanu, A. 2004, Europhysics Letters (EPL), 68, 170, doi: 10.1209/epl/i2004-10241-3 Tasker, E., Tan, J., Heng, K., et al. 2017, Nature Astronomy, 1, 0042, doi: 10.1038/s41550-017-0042 Tasker, E., Unterborn, C., Laneuville, M., et al., eds. 2020, Planetary diversity: rocky planet processes and their observational signatures, AAS-IOP astronomy (Bristol, UK: IOP Publishing) The scikit-bio development team. 2020, scikit-bio: A bioinformatics library for data scientists, students, and developers. http://scikit-bio.org Totani, T. 2023, International Journal of Astrobiology, 22, 347, doi: 10.1017/S147355042300006X Vickers, P., Cowie, C., Dick, S. J., et al. 2023, Astrobiology, ast.2022.0084, doi: 10.1089/ast.2022.0084 Walker, S. I., Bains, W., Cronin, L., et al. 2018, Astrobiology, 18, 779, doi: 10.1089/ast.2017.1738 Wong, M. L., Prabhu, A., Williams, J., Morrison, S. M., & Hazen, R. M. 2023, Journal of Geophysical Research: Planets, 128, e2022JE007658, doi: 10.1029/2022JE007658 Wright, J. T., Mullan, B., Sigurdsson, S., & Povich, M. S. 2014, The Astrophysical Journal, 792, 26, doi: 10.1088/0004-637X/792/1/26 Authors:
(1) Harrison B. Smith, Earth-Life Science Institute, Tokyo Institute of Technology, Ookayama, Meguro-ku, Tokyo, Japan, and Blue Marble Space Institute of Science, Seattle, Washington, USA (hbs@elsi.jp);
(2) Lana Sinapayen, Sony Computer Science Laboratories, Kyoto, Japan and National Institute for Basic Biology, Okazaki, Japan (lana.sinapayen@gmail.com). This paper is available on arxiv under CC BY-NC-ND 4.0 Deed license. Table of Links Abstract and 1. Introduction Abstract and 1. Introduction 2. Methods 2.1. Modeling Panspermia and Terraformation 2.1. Modeling Panspermia and Terraformation 2.2. Identifying the Presence of Terraformed Planets and 2.3. Software and Availability 2.2. Identifying the Presence of Terraformed Planets and 2.3. Software and Availability 3. Results 3.1. Panspermia can increase the correlation between planets’ compositions and positions 3.1. Panspermia can increase the correlation between planets’ compositions and positions 3.2. Likely terraformed planets can be identified from clustering 3.2. Likely terraformed planets can be identified from clustering 4. Summary and Discussion 4. Summary and Discussion 5. Acknowledgements and References 5. Acknowledgements and References APPENDIX APPENDIX A. Appendix A. Appendix 5. ACKNOWLEDGEMENTS The authors would like to thank Estelle Janin and Cole Mathis for encouraging and productive conversations, and for feedback on the manuscript. REFERENCES Affholder, A., Guyot, F., Sauterey, B., Ferri`ere, R., & Mazevet, S. 2021, Nature Astronomy, doi: 10.1038/s41550-021-01372-6 Balbi, A., & Grimaldi, C. 2020, Proceedings of the National Academy of Sciences, 117, 21031, doi: 10.1073/pnas.2007560117 Bartlett, S., Li, J., Gu, L., et al. 2022, Nature Astronomy, 6, 387, doi: 10.1038/s41550-021-01559-x Benner, S. A. 2010, Astrobiology, 10, 1021, doi: 10.1089/ast.2010.0524 Bich, L., & Green, S. 2018, Synthese, 195, 3919, doi: 10.1007/s11229-017-1397-9 Bixel, A., & Apai, D. 2021, The Astronomical Journal, 161, 228, doi: 10.3847/1538-3881/abe042 Carroll-Nellenback, J., Frank, A., Wright, J., & Scharf, C. 2019, The Astronomical Journal, 158, 117, doi: 10.3847/1538-3881/ab31a3 Catling, D. C., Krissansen-Totton, J., Kiang, N. Y., et al. 2018, Astrobiology, 18, 709, doi: 10.1089/ast.2017.1737 Checlair, J. H., Villanueva, G. L., Hayworth, B. P. C., et al. 2021, The Astronomical Journal, 161, 150, doi: 10.3847/1538-3881/abdb36 Cleaves, H. J., Hystad, G., Prabhu, A., et al. 2023, Proceedings of the National Academy of Sciences, 120, e2307149120, doi: 10.1073/pnas.2307149120 Cleland, C. E. 2012, Synthese, 185, 125, doi: 10.1007/s11229-011-9879-7 Cleland, C. E., & Chyba, C. F. 2002, Origins of Life and Evolution of the Biosphere, 32, 387, doi: 10.1023/A:1020503324273 Cockell, C. S. 2022, in New Frontiers in Astrobiology (Elsevier), 1–17, doi: 10.1016/B978-0-12-824162-2.00009-9 Gobat, R. 2021, The Astrophysical Journal, 16 Green, J., Hoehler, T., Neveu, M., et al. 2021, Nature, 598, 575, doi: 10.1038/s41586-021-03804-9 Grimaldi, C., Lingam, M., & Balbi, A. 2021, The Astronomical Journal, 162, 23, doi: 10.3847/1538-3881/abfe61 Hahsler, M., Piekenbrock, M., & Doran, D. 2019, Journal of Statistical Software, 91, 1, doi: 10.18637/jss.v091.i01 Harman, C. E., & Domagal-Goldman, S. 2018, in Handbook of Exoplanets, ed. H. J. Deeg & J. A. Belmonte (Cham: Springer International Publishing), 1–22, doi: 10.1007/978-3-319-30648-3 71-1 Janin, E. 2021, Astronomy & Geophysics, 62 Kim, H., Smith, H. B., Mathis, C., Raymond, J., & Walker, S. I. 2019, Science Advances, 5, eaau0149, doi: 10.1126/sciadv.aau0149 Kinney, D., & Kempes, C. 2022, Biology & Philosophy, 37, 22, doi: 10.1007/s10539-022-09859-w Kovacevic, A. B. 2022, arXiv:2202.07347 [astro-ph, q-bio]. http://arxiv.org/abs/2202.07347 Lenardic, A., Seales, J., & Covington, A. 2022, International Journal of Astrobiology, 1, doi: 10.1017/S1473550422000222 Lenardic, A., Seales, J., Moore, W. B., & Jellinek, A. M. 2023, Nature Astronomy, 1, doi: 10.1038/s41550-023-02031-8 Lin, H. W., & Loeb, A. 2015, The Astrophysical Journal, 810, L3, doi: 10.1088/2041-8205/810/1/L3 Lingam, M., Grimaldi, C., & Balbi, A. 2021, Monthly Notices of the Royal Astronomical Society, 509, 4365, doi: 10.1093/mnras/stab3108 Lynas, M., Houlton, B. Z., & Perry, S. 2021, Environmental Research Letters, 16, 114005, doi: 10.1088/1748-9326/ac2966 Mariscal, C., & Doolittle, W. F. 2020, Synthese, 197, 2975, doi: 10.1007/s11229-018-1852-2 Marshall, S. M., Mathis, C., Carrick, E., et al. 2021, Nature Communications, 12, 3033, doi: 10.1038/s41467-021-23258-x Mix, L. J. 2015, Astrobiology, 15, 15, doi: 10.1089/ast.2014.1191 Moore, W. B., Lenardic, A., Jellinek, A. M., et al. 2017, Nature Astronomy, 1, 1, doi: 10.1038/s41550-017-0043 Olejarz, J., Iwasa, Y., Knoll, A. H., & Nowak, M. A. 2021, Nature Communications, 12, 3985, doi: 10.1038/s41467-021-23286-7 Pacetti, E., Turrini, D., Schisano, E., et al. 2022, The Astrophysical Journal, 937, 36, doi: 10.3847/1538-4357/ac8b11 Rideout, J. R., Caporaso, G., Bolyen, E., et al. 2023, biocore/scikit-bio: scikit-bio 0.5.9: Maintenance release, Zenodo, doi: 10.5281/zenodo.8209901 Satopaa, V., Albrecht, J., Irwin, D., & Raghavan, B. 2011, in 2011 31st International Conference on Distributed Computing Systems Workshops (Minneapolis, MN, USA: IEEE), 166–171, doi: 10.1109/ICDCSW.2011.20 Schwieterman, E. W., Meadows, V. S., Domagal-Goldman, S. D., et al. 2016, The Astrophysical Journal, 819, L13, doi: 10.3847/2041-8205/819/1/L13 Schwieterman, E. W., Kiang, N. Y., Parenteau, M. N., et al. 2018, Astrobiology, 18, 663, doi: 10.1089/ast.2017.1729 Smith, H. B., & Mathis, C. 2023, BioEssays, 2300050, doi: 10.1002/bies.202300050 Smith, H. H., Hyde, A. S., Simkus, D. N., et al. 2021, Life, 11, 498, doi: 10.3390/life11060498 Sol´e, R. V., & Munteanu, A. 2004, Europhysics Letters (EPL), 68, 170, doi: 10.1209/epl/i2004-10241-3 Tasker, E., Tan, J., Heng, K., et al. 2017, Nature Astronomy, 1, 0042, doi: 10.1038/s41550-017-0042 Tasker, E., Unterborn, C., Laneuville, M., et al., eds. 2020, Planetary diversity: rocky planet processes and their observational signatures, AAS-IOP astronomy (Bristol, UK: IOP Publishing) The scikit-bio development team. 2020, scikit-bio: A bioinformatics library for data scientists, students, and developers. http://scikit-bio.org Totani, T. 2023, International Journal of Astrobiology, 22, 347, doi: 10.1017/S147355042300006X Vickers, P., Cowie, C., Dick, S. J., et al. 2023, Astrobiology, ast.2022.0084, doi: 10.1089/ast.2022.0084 Walker, S. I., Bains, W., Cronin, L., et al. 2018, Astrobiology, 18, 779, doi: 10.1089/ast.2017.1738 Wong, M. L., Prabhu, A., Williams, J., Morrison, S. M., & Hazen, R. M. 2023, Journal of Geophysical Research: Planets, 128, e2022JE007658, doi: 10.1029/2022JE007658 Wright, J. T., Mullan, B., Sigurdsson, S., & Povich, M. S. 2014, The Astrophysical Journal, 792, 26, doi: 10.1088/0004-637X/792/1/26 Authors: (1) Harrison B. Smith, Earth-Life Science Institute, Tokyo Institute of Technology, Ookayama, Meguro-ku, Tokyo, Japan, and Blue Marble Space Institute of Science, Seattle, Washington, USA (hbs@elsi.jp); (2) Lana Sinapayen, Sony Computer Science Laboratories, Kyoto, Japan and National Institute for Basic Biology, Okazaki, Japan (lana.sinapayen@gmail.com). Authors: Authors: (1) Harrison B. Smith, Earth-Life Science Institute, Tokyo Institute of Technology, Ookayama, Meguro-ku, Tokyo, Japan, and Blue Marble Space Institute of Science, Seattle, Washington, USA ( hbs@elsi.jp ); hbs@elsi.jp (2) Lana Sinapayen, Sony Computer Science Laboratories, Kyoto, Japan and National Institute for Basic Biology, Okazaki, Japan ( lana.sinapayen@gmail.com ). lana.sinapayen@gmail.com This paper is available on arxiv under CC BY-NC-ND 4.0 Deed license. This paper is available on arxiv under CC BY-NC-ND 4.0 Deed license. available on arxiv

Stories, News & Mentions about SINA

Sina’s Stories on HackerNoon

Sina's News & Mentions