StackBlitz Inc., the maker of developer tool Bolt.new, is finalizing talks to raise money from investors at a $700 million valuation, its chief executive officer said — the latest deal for an artificial intelligence startup promising to change computer programming and coding.

AI Text-to-Code Startup StackBlitz in Talks for $700M Valuation - Bloomberg

Kia issued a recall for nearly 23,000 EV9 electric cars for the 2024-25 model year after discovering seats that weren't fully bolted down.

Kia Concerned That Employee Forgot to Bolt Seats Down in Potentially Tens of Thousands of Cars

Estonian mobility platform Bolt is mandating a return to office for its global staff, with CEO Markus Villig criticising remote work practices he ...

Estonian Bolt CEO calls remote work 'insanity'

Bolt CEO Markus Villig reportedly said it was a “disgrace” that less than half his workers were making it into the office at least two days a week.

Boss of Uber rival Bolt vows to crack down on remote work to stop ‘insanity of people working from Bali’

Bolt

bolt

Part 1: Getting Going with the Starter Kit Businesses depend on Slack for communication and Salesforce for data management. As one might expect, conversations in Slack don’t always correlate to changes in Salesforce records. Being able to share data between these two services can increase team productivity by eliminating the need to switch between them. In December of 2021, Salesforce produced using their APIs. Building on top of any platform can be intimidating: You have to learn about how authentication works, the methods you can call, the events you can listen for, and so on. Slack has and an SDK, , which reduces a lot of boilerplate logic, getting you more quickly from an idea to an actual app. a video series explaining how to build Slack Apps excellent documentation Bolt The folks at Salesforce have done one better. Taking into account Bolt’s development principles and tooling, they developed the . It’s an opinionated scaffolding framework designed to make it easy to build Slack Apps that integrate with Salesforce data. Slack Starter Kit In this series of posts, we’ll show you how to use the Slack Starter Kit and Bolt to create an application that allows users to view and change Salesforce records—entirely in Slack. By the end of this series, we’ll have a fully functional Slack app that communicates with the Salesforce platform. In this first post, we’ll go through the SDK and set up your development environment for future work! Prerequisites Before we begin, make sure you have the following software installed on your machine: —this is a tool designed by Salesforce to simplify platform interactions. The sfdx CLI A recent version of (>= 14.0) Node The , as well as an existing Heroku account Heroku CLI A Slack workspace where you can install Apps An existing Salesforce Dev Hub We’ll first create a Slack App, which will provide us with tokens and other Slack-specific information we’ll need before building our app. To do that: Navigate to and click . https://api.slack.com/apps Create New App In the prompt that pops up, select . From scratch Set the name of the App to , and choose a workspace where the App can be installed. SFDCContactEditor That’s it! If you scroll down, you’ll see your App Credentials. We’ll be referring to these in the next section. On the left side nav bar, click on App Manifest. Your App Manifest defines some metadata about your app, such as the permissions it requests and the events it handles. Paste the following YAML into that box, overwriting what was there by default: _metadata:
  major_version: 1
  minor_version: 1
display_information:
  name: SFDCContactEditor
features:
  app_home:
    home_tab_enabled: true
    messages_tab_enabled: false
    messages_tab_read_only_enabled: true
  bot_user:
    display_name: SFDCContactEditor
    always_online: true
  shortcuts:
    - name: Whoami
      type: global
      callback_id: who_am_i
      description: shows Salesforce org details
oauth_config:
  scopes:
    bot:
      - chat:write
      - chat:write.public
      - commands
      - users:read
settings:
  event_subscriptions:
    request_url: https://heroku-app.herokuapp.com/slack/events
    bot_events:
      - app_home_opened
  interactivity:
    is_enabled: true
    request_url: https://heroku-app.herokuapp.com/slack/events
  org_deploy_enabled: false
  socket_mode_enabled: false
  token_rotation_enabled: false Click . If you get an error about a URL being unverified, don’t worry—we’ll address that soon! Save Changes Next, clone the , and then navigate to the directory: Slack Starter Kit scripts git clone https://github.com/developerforce/salesforce-slack-starter-kit
cd salesforce-slack-starter-kit/scripts Install the dependencies there with ; then pop up a folder, and install those dependencies: npm install npm install
cd ..
npm install Walking through the Salesforce Starter Kit With the Salesforce Starter Kit available and its dependencies installed, it’s time to take a look at what the Starter Kit can do. The primary goal of the Starter Kit is to get your environment set up for building, testing, and deploying a Slack App that integrates with Salesforce. It does this by: Setting up a Salesforce scratch org Setting up and deploying a sample application to Heroku Using Bolt to abstract away details with authentication Setting up a project structure that favors convention over configuration Let’s see this in action. First, make sure you’re authenticated to your Salesforce Dev Hub by running . Then, run , and a CLI prompt will take over. sfdx auth:web:login node scripts/deploy.js You’ll be asked to provide some information: For the Heroku App Name, we’ll use . Make sure to select a unique name for your Heroku App, since app names need to be unique across all Heroku apps. sfdc-contact-editor For the Slack Bot Token, go to the OAuth & Permissions page in your Slack App overview, and copy-paste the Bot User OAuth Token into the terminal. For the Slack Signing Secret, go back to the App Credentials section of the Basic Information page on Slack’s site. Copy-paste the provided signing secret into the terminal. Provide the name of your existing Dev Hub alias. You can name your scratch org anything you like—the default of is fine! scratchorg Now, grab a beverage and sit back, as the Starter Kit sets up some accounts for you. It creates a brand new scratch org and a new Heroku app, and it defines some essential environment variables for the deployed app to use. : if you receive a failure about a missing , make sure you have . If you receive a failure about a missing public key or permissions when pushing to Heroku, run . Note OrgCreateCommand enabled Dev Hub heroku keys:add After some time, you’ll receive the following message: Done deploying Heroku app sfdc-contact-editor In order to verify that the application was configured and deployed, you can perform two separate steps. First, run the following command in your terminal window: sfdx force:org:open Navigate to , and you should see an app titled “Connected App For Slack.” This is the Salesforce platform policy that the Starter Kit created for your Slack app. Manage Connected Apps Next, go to , and you should see your brand new app listed there. https://dashboard.heroku.com/ Now that we have a production version of the app available, we’ll need to make one more change to our Slack configuration to unite the two. Open up your and find the lines that identify your Heroku endpoint: App Manifest two request_url: https://heroku-app.herokuapp.com/slack/events Replace the placeholder with the actual name of your Heroku app. Click . Slack will inform you that your request URL isn’t verified; click to make that happen! heroku-app Save Changes Verify Watching it work Let’s try interacting with our app to ensure that everything is wired up correctly. Remember: we have a production app running on Heroku which intercepts a user’s Slack activity and communicates with Salesforce. We haven’t added any of our own functionality yet; everything was preconfigured by the Starter Kit. First, . You’ll be asked to authenticate with Salesforce; click on the button to do so. Then, head into any Slack room, and run the : add the app to your Slack workspace whoami shortcut provided by the app Voila! Next, let’s take a quick look at what’s inside the Starter Kit. Open up the project in your IDE, and navigate to the folder. In here, there’s a file called . This is where the entirety of the Salesforce authentication takes place. We don’t need to do anything to this file, but it’s useful to know just how much is being abstracted away for us. salesforcelib connect.js Next, open up the folder. This folder contains all the app logic for listening to and responding to events from Slack. Open up , then . This file contains all of the functionality for the shortcut we just issued. There are two important things to point out: listeners shortcuts whoami.js The first method called in the function is . Slack requires that an app acknowledge an event within three seconds of it occurring, and is responsible for sending that message to Slack. ack ack In the next line— —we fetch our connection information from Salesforce. const conn = context.sfconnection Lastly, let’s take a look at the user-interface folder. As you might have guessed, this folder contains all of the UI definitions for our Slack app. (We’ll definitely take a deeper look at how to build a UI in our next part.) Inside here, open up the modals folder, then open . The Starter Kit takes care of the actual definitions for designing and prompting the UI modal we saw. The only thing we can customize is the box text. Let’s get cheeky and add an exclamation point to the end of this sentence: whoami-response.js Successfully connected to salesforce instance ${instanceurl}. Authenticated with user ${username}! Let’s deploy this app live to production! If you don’t know how, you should familiarize yourself with . Put simply, however, all we need to do is push our committed change to our Heroku remote: this article on deploying to Heroku $ salesforce-slack-starter-kit (main): git add apps/slack-salesforce-starter-app/user-interface/modals/whoami-response.js
$ salesforce-slack-starter-kit (main): git commit -m "Add an exclamation point" 

> salesforce-app@1.0.0 precommit
> lint-staged

✔ Preparing...
✔ Running tasks...
✔ Applying modifications...
✔ Cleaning up...
[main 44aac80] Add an exclamation point
 1 file changed, 1 insertion(+), 1 deletion(-)
$ git push heroku main When Heroku is finished, you can return to Slack, issue the same shortcut, and see your new change live. whoami Learning more Whether you’re an experienced developer or just getting started, the Slack Starter Kit can save you so much time. In our short time together, we were able to: Create a new Salesforce environment Create a new Slack app Deploy the Slack app to Heroku Wire up Slack, Heroku, and Salesforce Issue a Slack shortcut and see the results The Starter Kit has essentially solved a lot of problems around authentication and API tokens by automating much of this for us. Every app will need these aspects configured, and since the Starter Kit has made these repetitive processes easier, we can now concentrate on what matters most: developing an incredible Slack app. With this foundation established, we’re ready to continue building on it in our next installment! We’ll look a little closer at the architecture of the Starter Kit, and add a new command of our own. Also Published . here

How to Build a Slack App That Changes Salesforce Records Within Slack

The top 3 headlines from across the pond for Tuesday, May 26, 2020. Bolt Raises $109M The -based on-demand transport company (and competitor to Uber), Bolt, has picked up an additional €100 million ($109 million) in a convertible note. According to , Bolt also confirmed that is now valued at €1.7 billion (or nearly $1.9 billion at today’s rates). Estonia Tech Crunch "Bolt, a rival to Uber and others providing on-demand ridesharing, scooters and other transportation services across some 150 cities in Europe and Africa, is today announcing another capital raise as it weathers a difficult market climate where, because of COVID-19, many are staying in place and avoiding modes of transport that put them into contact with others." source The latest episode of features none other than Uber's CEO, Dara Khosrowshahi. Worth tuning in to hear his insider perspective on a transport industry under lockdown, and also to hear the legendary Swisher lay down those labour relations questions like it ain't no thang, as she does. RELATED: vox.com's Recode Decode with Kara Swisher Senior Adviser to Boris Johnson, Dominic Cummings, Refuses To Resign After Driving Far Distance After Lockdown No citation required, because this story is literally all I've heard around these parts for the last three days straight. somebody British and important drove his kids to their grandparents during Stay Home orders because he and his wife were sick and/or very busy and important, as aforementioned. The nation is, to put it mildly, TS;DC (Too Stupid; Don't Care): outraged. SURPRISE! Non-Corona News Is Still A Thing, And Libya Appears to be Hosting an Important Proxy War, With Increasingly Less Deniable Support From Turkey * source: The Monocle Daily Briefing for May 26, 2020 "Libya has been in the midst of civil war for almost a decade. However, in the last year, the conflict has escalated and become a regional proxy war. This matters because Libya is a gateway for migrants coming to Europe and because whoever wins in Libya will emerge a powerful figure in the Middle East. Eastern Libya is run by Khalifa Haftar and his Libyan National Army. He is principally backed by the UAE, Egypt and Russia; and he appears to receive support from France, Saudi Arabia and Greece. The government in Tripoli is backed by Turkey and Qatar. Haftar poised to take Tripoli in recent months but his allies in Abu Dhabi, Cairo and Moscow have suffered setbacks. They have not been able to get Haftar over the line. seemed Libya is the Middle East’s most important proxy conflict today." ( ) source a fascinating discussion around what's viewed as a 'natural' collapse of social distancing measures in Europe, with Monocle's Zurich-based Switzerland correspondent affirming the trend I'm seeing here in Amsterdam. *Also in this podcast :

'European Uber' Raises $109M · The UK Has No Chill · Libya is Waging a Proxy War

The TechBeat: Unpacking The Starknet Bolt Upgrade (1/9/2025)

The TechBeat: Unpacking The Starknet Bolt Upgrade (1/7/2025)

The TechBeat: Unpacking The Starknet Bolt Upgrade (1/5/2025)

The TechBeat: Unpacking The Starknet Bolt Upgrade (1/3/2025)

Unpacking The Starknet Bolt Upgrade

የስታርክኔት ቦልት ማሻሻያውን በማራገፍ ላይ

Разопаковане на Starknet Bolt Upgrade

Desembalaje de la actualización Starknet Bolt

Déballage de la mise à niveau Starknet Bolt

Debalaj Starknet Bolt Upgrade a

Disimballaggio dell'aggiornamento del bullone Starknet

Starknet Bolt アップグレードの開梱

Starknet Bolt-ის განახლება

Starknet Bolt jauninājuma izpakošana

Kufungua Uboreshaji wa Starknet Bolt

Кушодани навсозии Starknet Bolt

Starknet Bolt yangilanishini ochish

Authors:
(1) Luyang Zhu, University of Washington and Google Research, and work done while the author was an intern at Google;
(2) Dawei Yang, Google Research;
(3) Tyler Zhu, Google Research;
(4) Fitsum Reda, Google Research;
(5) William Chan, Google Research;
(6) Chitwan Saharia, Google Research;
(7) Mohammad Norouzi, Google Research;
(8) Ira Kemelmacher-Shlizerman, University of Washington and Google Research. Table of Links Abstract and 1. Introduction 2. Related Work 3. Method 3.1. Cascaded Diffusion Models for Try-On 3.2. Parallel-UNet 4. Experiments 5. Summary and Future Work and References Appendix A. Implementation Details B. Additional Results A. Implementation Details A.1. Parallel-UNet A.2. Training and Inference TryOnDiffusion was implemented in JAX [4]. All three diffusion models are trained on 32 TPU-v4 chips for 500K iterations (around 3 days for each diffusion model). After trained, we run the inference of the whole pipeline on 4 TPU-v4 chips with batch size 4, which takes around 18 seconds for one batch. This paper is available on arxiv under CC BY-NC-ND 4.0 DEED license. Authors: (1) Luyang Zhu, University of Washington and Google Research, and work done while the author was an intern at Google; (2) Dawei Yang, Google Research; (3) Tyler Zhu, Google Research; (4) Fitsum Reda, Google Research; (5) William Chan, Google Research; (6) Chitwan Saharia, Google Research; (7) Mohammad Norouzi, Google Research; (8) Ira Kemelmacher-Shlizerman, University of Washington and Google Research. Authors: Authors: (1) Luyang Zhu, University of Washington and Google Research, and work done while the author was an intern at Google; (2) Dawei Yang, Google Research; (3) Tyler Zhu, Google Research; (4) Fitsum Reda, Google Research; (5) William Chan, Google Research; (6) Chitwan Saharia, Google Research; (7) Mohammad Norouzi, Google Research; (8) Ira Kemelmacher-Shlizerman, University of Washington and Google Research. Table of Links Abstract and 1. Introduction Abstract and 1. Introduction 2. Related Work 2. Related Work 3. Method 3. Method 3.1. Cascaded Diffusion Models for Try-On 3.1. Cascaded Diffusion Models for Try-On 3.2. Parallel-UNet 3.2. Parallel-UNet 4. Experiments 4. Experiments 5. Summary and Future Work and References 5. Summary and Future Work and References Appendix Appendix A. Implementation Details A. Implementation Details B. Additional Results B. Additional Results A. Implementation Details A.1. Parallel-UNet A.2. Training and Inference TryOnDiffusion was implemented in JAX [4]. All three diffusion models are trained on 32 TPU-v4 chips for 500K iterations (around 3 days for each diffusion model). After trained, we run the inference of the whole pipeline on 4 TPU-v4 chips with batch size 4, which takes around 18 seconds for one batch. 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

The Nuts and Bolts of Parallel-UNet: Implementation Details

A Brief Introduction to The Boltzmann Brain Theory

বোল্টজম্যান ব্রেন থিওরির একটি সংক্ষিপ্ত ভূমিকা

Eine kurze Einführung in die Boltzmann-Gehirntheorie

Una breve introducción a la teoría del cerebro de Boltzmann

Une brève introduction à la théorie du cerveau de Boltzmann

बोल्ट्ज़मैन मस्तिष्क सिद्धांत का संक्षिप्त परिचय

ボルツマン脳理論の簡単な紹介

볼츠만 뇌 이론에 대한 간략한 소개

Uma breve introdução à teoria do cérebro de Boltzmann

Краткое введение в теорию мозга Больцмана

Boltzmann Beyin Teorisine Kısa Bir Giriş

Giới thiệu tóm tắt về Lý thuyết bộ não của Boltzmann

玻尔兹曼脑理论简介

Today we will be creating a SlackBot that reacts to every message sent by a specific user. Useful, right? 😄 Creating a New Slack App The first thing we have to do is create a new app. We do this by navigating to and navigating to . Slack api.slack.com Your Apps -> Create New App We’ll call our app . Next up, we have to set up , a , and . reacting-bot event subscriptions bot user permissions Socket Mode The first thing we have to do is enable Socket Mode. Turning on Socket Mode will route your app’s interactions and events over a WebSockets connection instead of sending these payloads to different Request URLs. To enable Socket Mode, navigate to and hit . You will be prompted to add scopes and generate an app-level token. Give the token a name, e.g., “token”, and add the following scopes: Settings -> Socket Mode Enable Socket Mode & connections:write authorizations:read As the names suggest, these will give our app permission to read and write messages. Event Subscriptions Next up, we need to enable Event Subscriptions, which can be found beneath in the left-side menu. After enabling Event Subscriptions, you will need to add the following Event Subscriptions. Features Subscribe to bot events: message.groups Subscribe to event on behalf of users: message.channels Bot User If a Bot User has not yet been created, it can be set up on the tab. Here we can set a display name and its username. App Home Permissions Lastly, we need to ensure that the SlackBot has all the correct permissions needed. Head over to and add the permission to the . OAuth & Permissions reactions.write Bot Token Scopes We have now set up the SlackBot, and we are ready to start coding! Writing The Bot We will be using the library as an interface to the Slack API. It comes with many useful features that make creating SlackBots a breeze. bolt-js While in a new directory , we can initialize the project using . This will create a file that looks like the following: reacting-bot npm init -y package.json {
  "name": "reacting-bot",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC"
} For this project, we are going to need two packages. and . is an interface that we use to communicate with the Slack API, and is used to access environment variables. We can install the packages with the following command: @slack/bolt dotenv Bolt dotenv npm install @slack/bolt dotenv Next up, we need to create the file which should store our environment variables for when we are running this project locally. The file should contain the following: .env SIGNING_SECRET=5c24e...
TOKEN=xoxb-...
APP_TOKEN=xapp-...
USER_ID=UCF8... can be found on the page SIGNING_SECRET Basic Information (xoxb) can be found on the page TOKEN OAuth & Permissions (xapp) can be found on the page under APP_TOKEN Basic Information App-level tokens can be found when viewing a slack profile under USER_ID More In , we start by importing and , and we initialize a bolt application in socket mode in the constant : index.js @slack/bolt dotenv app const { App } = require("@slack/bolt");
require("dotenv").config();

const app = new App({
  signingSecret: process.env.SIGNING_SECRET,
  token: process.env.TOKEN,
  socketMode: true,
  appToken: process.env.APP_TOKEN,
}); We then write the logic that uses the method to attach a listener for messages. message() app.message(async ({ message, context }) => {
  if (message.user === process.env.USER_ID) {
    try {
      const result = await app.client.reactions.add({
        token: context.botToken,
        name: "heavy_plus_sign",
        channel: message.channel,
        timestamp: message.ts,
      });
    } catch (error) {
      console.error(error);
    }
  }
}); We check any given message is sent by the user with the . If we find a match, we use the function to add a reaction to the message. ID USER_ID app.client.reactions.add() Lastly, we add a function that runs when the application starts. This function will start up the Slack App: (async () => {
  const port = process.env.PORT || 3000;
  await app.start(port);
  console.log(`⚡️ reacting-bot is running on port ${port}`);
})(); And that’s it! You can now run the app using the command, and the bot will start reacting to messages once it has been added to the correct channels. npm start This is what the final code looks like: const { App } = require("@slack/bolt");
require("dotenv").config();

const app = new App({
  signingSecret: process.env.SIGNING_SECRET,
  token: process.env.TOKEN,
  socketMode: true,
  appToken: process.env.APP_TOKEN,
});

app.message(async ({ message, context }) => {
  if (message.user === process.env.USER_ID) {
    try {
      const result = await app.client.reactions.add({
        token: context.botToken,
        name: "heavy_plus_sign",
        channel: message.channel,
        timestamp: message.ts,
      });
    } catch (error) {
      console.error(error);
    }
  }
});

(async () => {
  const port = process.env.PORT || 3000;

  await app.start(port);

  console.log(`⚡️ reacting-app is running on port ${port}`);
})(); Thanks for checking out this guide! You can view the code for this project on my . GitHub Also published here.

How to Create a Slackbot With JavaScript Bolt

Stories, News & Mentions about BOLT

Bolt’s Stories on HackerNoon

Bolt's News & Mentions