# certificate Published articles for certificate. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## New Release: Tor Browser 15.0.23 DevFeed: [New Release: Tor Browser 15.0.23]() Original publisher: [Read original article]() Author: ma1 Published: 2026-09-15T00:00:00Z Content type: release Language: en Sources: [Tor Project blog]() Topics: [tor](), [Firefox](), [Security](), [browser](), [WebAssembly](), [changelog]() Tags: [android](), [applications](), [browser](), [certificate](), [changelog](), [digicert](), [firefox](), [linux](), [macos](), [release](), [releases](), [security](), [tor](), [version](), [webassembly](), [windows]() ### AI overview Tor Browser 15.0.23 is available with Firefox security updates and other platform-specific changes. The release also documents an expired DigiCert EV certificate affecting fresh Windows installations of earlier versions, along with a temporary workaround and a full changelog. ### Source excerpt Tor Browser 15.0.23 is now available from the Tor Browser download page and also from our distribution directory. This version includes important security updates to Firefox. Windows Package Signature Issue The DigiCert EV code-signing certificate we use to sign Windows installation packages is expired since September 1st and we are currently in the process to renew it. Unfortunately, this process is delayed and not yet complete. This has caused Windows users trying to install Tor Browser 15.0.21 and 15.0.22 from scratch to receive "bad signature" warnings. As a temporary work-around, for Windows only we're keeping Tor Browser 15.0.20 (the latest correctly signed version) listed on our download page, relying on automatic updates (which are signed with a different key, not involving this expired certificate) to bring Windows users to the current version. Users who prefer to download the latest version directly, ignoring the certificate expiration warning, can download it from https://dist.torproject.org/torbrowser/15.0.23/. Send us your feedback If you find a bug or have a suggestion for how we could improve this release, please let us know. Full changelog The full changelog since Tor Browser 15.0.22 is: All Platforms Updated NoScript to 13.6.33.1984 Bug tor-browser#45296: (H1) SharedWorker Identity Mismatch allows WebAssembly execution at Safer Bug tor-browser#45297: (H1) Missing setHTMLUnsafe hook leaves a permanent WebAssembly-capable child realm at Safer Bug tor-browser#45299: Backport Security Fixes from Firefox 156 Bug tor-browser#45303: Rebase Tor Browser stable onto 140.16.0esr Bug tor-browser-build#41875: Update relprep.py for the new versions.ini URL Windows + macOS + Linux Updated Firefox to 140.16.0esr Linux Bug tor-browser#44996: Change the 32-bit linux message to the expired version for the final 15.0 release Android Updated GeckoView to 140.16.0esr Build System All Platforms Bug tor-browser-build#41871: Update downloads repository references in relprep ## Azure SDK Release (July 2026) DevFeed: [Azure SDK Release (July 2026)]() Original publisher: [Read original article]() Author: Justin Bettencourt Published: 2026-07-29T17:18:25Z Content type: release Language: en Sources: [Azure SDK Blog]() Topics: [releases](), [Azure](), [SDKs](), [Release notes](), [Python](), [Rust](), [Monitoring](), [AWS Certificate Manager]() Tags: [2026](), [azure](), [azure-sdk](), [blog](), [certificate](), [developers](), [monitoring](), [notes](), [python](), [release](), [release-notes](), [releases](), [rust](), [sdk]() ### AI overview The July 2026 Azure SDK release introduces a Rust crate for building user-delegation Shared Access Signatures for Azure Storage. It also brings stable Python management libraries for App Service domains and certificates, Resource Health, and Data Boundaries, alongside initial stable and beta releases for Java, Python, and Rust libraries. ### Source excerpt Azure SDK releases every month. In this post, you'll find this month's highlights and release notes. The post Azure SDK Release (July 2026) appeared first on Azure SDK Blog. ## Zabbix and the Docker API, Part 1: Inspect DevFeed: [Zabbix and the Docker API, Part 1: Inspect]() Original publisher: [Read original article]() Author: Janis Eidaks Published: 2026-04-22T08:04:04Z Content type: tutorial Language: en Sources: [Zabbix Blog]() Topics: [Docker](), [API](), [certificates](), [Authentication](), [TLS (Transport Layer Security)](), [Security](), [SIEM, Security, Observability]() Tags: [api](), [api-metrics](), [authentication](), [certificate](), [data-collection](), [docker](), [handy-tips](), [metrics](), [security](), [server](), [tls](), [zabbix]() ### AI overview A tutorial on configuring Zabbix to securely collect Docker API metrics using the Zabbix HTTP agent and certificate authentication. It covers securing Docker API access, generating certificates, configuring TLS-related settings, and connecting the Zabbix server. ### Source excerpt In this blog post, I will show you how to configure Zabbix to securely gather Docker API metrics using the Zabbix HTTP agent item with certificate authentication. This guide will cover configuring the Docker API and the Zabbix server side to gather data more securely. Getting the data to Zabbix from the Docker API By [...] The post Zabbix and the Docker API, Part 1: Inspect appeared first on Zabbix Blog. ## Qdrant Academy Expands with Official Certification DevFeed: [Qdrant Academy Expands with Official Certification]() Original publisher: [Read original article]() Author: info@qdrant.tech (Andrey Vasnetsov) Published: 2026-01-28T00:00:00Z Content type: release Language: en Sources: [Qdrant Blog on Qdrant - Vector Search Engine]() Topics: [Qdrant](), [AI search](), [Retrieval Augmented Generation (RAG)](), [recommendation systems](), [systems](), [Optimization](), [quantization]() Tags: [ai](), [ai-search](), [approximate-nearest-neighbor-search](), [bert](), [certificate](), [certification](), [developers](), [embeddings](), [engineering](), [fasttext](), [hnsw](), [image-search](), [infrastructure](), [knn-algorithm](), [learning](), [matching](), [neural-network](), [qdrant](), [rag](), [recommendation-systems](), [recommender-system](), [saas](), [simaes-networks](), [similarity](), [transformer](), [vector-search](), [vector-search-engine](), [vectors](), [word2vec]() ### AI overview Qdrant has launched its first official Qdrant Essentials certification through Qdrant Academy. The course and exam validate knowledge of vector search architecture, filtering, hybrid retrieval, and production optimization for RAG and recommendation systems. ### Source excerpt Since we first announced Qdrant Academy, our mission has been to provide developers with more than just documentation. We wanted to build a structured path to mastering vector search. As the AI search landscape matures, the distinction between a simple storage layer and a high-performance vector search engine has become the defining factor in production-grade RAG and recommendation systems. Today, we are thrilled to take the next step in that mission. It's time to move from learning to proving your expertise with the launch of our first official certification. ## Understanding email encryption DevFeed: [Understanding email encryption]() Original publisher: [Read original article]() Author: Neil Jenkins Published: 2025-12-17T00:00:01Z Content type: article Language: en Sources: [Fastmail Blog]() Topics: [email](), [Encryption](), [TLS (Transport Layer Security)](), [Security](), [Cryptography](), [passwords](), [Malware](), [Vulnerabilities](), [Network]() Tags: [certificate](), [email](), [encryption](), [malware](), [network](), [password](), [privacy-security](), [security](), [tls](), [vulnerability]() ### AI overview This article explains that email encryption can protect against different threats at different stages. It outlines common risks such as account compromise, malware, data breaches, and network eavesdropping, then describes how TLS encrypts connections between an email client and provider and how certificates and trusted Certificate Authorities help verify the provider's identity. ### Source excerpt Encrypted email sounds good, but what does it really mean? Email can be encrypted in many different ways, at different times, for different purposes. Each protects against different threats, and may have downsides to be weighed up. Understanding your options helps you make informed choices about your privacy and security. What are you protecting against? Before diving into encryption methods, it's worth asking: what threats actually matter for your email? For most people, the realistic concerns are: Account compromise: phishing or password reuse giving attackers access to your account Mistaken spam detection: causing important mail to go missing Malware: getting a virus via email, either linked or as an attachment Accidental deletion: losing vital data due to human error Far less common, although also important, are: Network eavesdropping: someone on your WiFi or ISP intercepting your traffic Data breaches: attackers gaining access to stored email through a security vulnerability Physical theft: stolen devices or hard drives exposing your data For a smaller number of people -- journalists protecting sources, activists in hostile countries, or those facing sophisticated adversaries -- the threat model expands to include insider threats at providers and legal compulsion by governments. Different encryption approaches help protect (or may even hinder protection) against subsets of these threats, and understanding this helps you choose the right balance. Encrypting the connection to your email provider Whenever you connect to your email provider, TLS (Transport Layer Security) encrypts everything between your device and the server. This protects you from eavesdroppers on your local WiFi network, your ISP, and anyone monitoring network traffic between you and your email service. This standard has been widely adopted and modernised, the latest version being TLS 1.3, which mandates the strongest ciphers and is the foundation of today's secure internet. But encryption alone i ## Observability in Quarkus 3 DevFeed: [Observability in Quarkus 3]() Original publisher: [Read original article]() Author: Bruno Baptista Published: 2023-09-20T00:00:00Z Content type: release Language: en Sources: [Quarkus - Supersonic Subatomic Java]() Topics: [Quarkus](), [observability](), [OpenTelemetry](), [tracing](), [gRPC](), [HTTP](), [TLS (Transport Layer Security)](), [Development]() Tags: [certificate](), [certificates](), [developers](), [grpc](), [http](), [observability](), [opentelemetry](), [quarkus](), [tracing]() ### AI overview Quarkus 3.3 improves observability through updates to its OpenTelemetry extension, including better development-mode behavior, additional extension points, simpler JDBC tracing activation, HTTP exporter support, TLS and custom certificate support, and customizable propagation headers. ### Source excerpt Observability in Quarkus Observability on a software system can be described as the capability to allow a human to ask and answer questions. To enable developers and support engineers in understanding how their applications behave, Quarkus 3.3 includes many improvements to its main observability related extensions: quarkus-opentelemetry (tracing) quarkus-micrometer (metrics) OpenTelemetry OpenTelemetry tracing is used to understand the flow of requests as they traverse through multiple services. The quarkus-opentelemetry extension already had a major upgrade on Quarkus 3.0, where the configurations aligned with the ones used by the OpenTelemetry (OTel) community. This made available many configurations that were not previously available in Quarkus. Other improvements include: The OpenTelemetry extension can be used in dev mode and now reloads properly. OTel Service Provider Interface (SPI) hooks for Sampler and SpanExporter were made available along with the existing user implementations with CDI for many OTel classes: IdGenerator, Resource attributes, Sampler and SpanProcessor. At the same time, the JDBC tracing activation was made simpler, just requiring the use of a property: quarkus.datasource.jdbc.telemetry=true On Quarkus 3.3 many improvements were made to the quarkus-opentelemetry extension. The most impactful ones are Removal of the OkHttp dependency In previous versions of the Quarkus exporter used the upstream OTel libraries and leveraged the OkHttp library to send the spans to the OTel Collector. This unnecessary dependency was removed and replaced by Quarkus specific Vert.x GRPC and HTTP clients. As previously, the exporter continues to be automatically wired with CDI, that's why the quarkus.otel.traces.exporter property defaults to cdi on Quarkus 3+. Exporter support fot the HTTP protocol Up until Quarkus 3.2, the OTel exporter could only use the GRPC protocol, while Quarkus now supports HTTP as well. To use the new HTTP protocol, the quarkus.otel.expor ## Why I switched from Netlify back to GitHub Pages DevFeed: [Why I switched from Netlify back to GitHub Pages]() Original publisher: [Read original article]() Author: Eugene Yan Published: 2020-10-21T00:00:00Z Content type: opinion Language: en Sources: [Eugene Yan]() Topics: [GitHub Pages](), [Netlify](), [Amazon Route 53](), [domain](), [hosting](), [Cloudflare](), [Jekyll]() Tags: [certificate](), [dns](), [email-security](), [github-pages](), [me](), [misc](), [netlify](), [security](), [server](), [testing]() ### AI overview The author describes switching a personal site from GitHub Pages to Netlify and back again. Netlify offered rollbacks, broader Jekyll plugin support, and A/B testing, but DNS migration problems caused bounced email and certificate errors, while the free build-time limit became restrictive. ### Source excerpt DNS server snafus led to email & security issues. Also, limited free build minutes monthly. ## Direct encrypted traffic from IBM Cloud Kubernetes Service Ingress to Istio Ingress Gateway DevFeed: [Direct encrypted traffic from IBM Cloud Kubernetes Service Ingress to Istio Ingress Gateway]() Original publisher: [Read original article]() Author: Vadim Eisenberg (IBM) Published: 2020-05-15T00:00:00Z Content type: tutorial Language: en Sources: [Istio Blog]() Topics: [istio](), [service-mesh](), [Kubernetes](), [ibm](), [gateway](), [TLS (Transport Layer Security)](), [Authentication](), [certificates](), [Routing (disambiguation)](), [networking](), [Architecture & Design](), [private key]() Tags: [application-load-balancer](), [authentication](), [certificate](), [certificates](), [clients](), [cloud](), [cluster](), [configure](), [dns](), [domain](), [encrypted](), [gateway](), [ibm](), [iks](), [ingress](), [istio](), [kubernetes](), [load-balancer](), [mesh](), [microservices](), [mutual-tls](), [routing](), [sds-credentials](), [secret](), [services](), [traffic-management]() ### AI overview This tutorial explains how to configure the IBM Cloud Kubernetes Service Application Load Balancer to route traffic to an Istio ingress gateway. It covers using mutual TLS, certificates, private keys, DNS subdomains, and Kubernetes secrets while supporting both mesh and non-mesh services during migration. ### Source excerpt In this blog post I show how to configure the Ingress Application Load Balancer (ALB) on IBM Cloud Kubernetes Service (IKS) to direct traffic to the Istio ingress gateway, while securing the traffic between them using mutual TLS authentication. When you use IKS without Istio, you may control your ingress traffic using the provided ALB. This ingress-traffic routing is configured using a Kubernetes Ingress resource with ALB-specific annotations. IKS provides a DNS domain name, a TLS certificate that matches the domain, and a private key for the certificate. IKS stores the certificates and the private key in a Kubernetes secret. When you start using Istio in your IKS cluster, the recommended method to send traffic to your Istio enabled workloads is by using the Istio Ingress Gateway instead of using the Kubernetes Ingress. One of the main reasons to use the Istio ingress gateway is the fact the ALB provided by IKS will not be able to communicate directly with the services inside the mesh when you enable STRICT mutual TLS. During your transition to having only Istio ingress gateway as your main entry point, you can continue to use the traditional Ingress for non-Istio services while using the Istio ingress gateway for services that are part of the mesh. IKS provides a convenient way for clients to access Istio ingress gateway by letting you register a new DNS subdomain for the Istio gateway's IP with an IKS command. The domain is in the following format: --0001..containers.appdomain.cloud, for example mycluster-a1b2cdef345678g9hi012j3kl4567890-0001.us-south.containers.appdomain.cloud. In the same way as for the ALB domain, IKS provides a certificate and a private key, storing them in another Kubernetes secret. This blog describes how you can chain together the IKS Ingress ALB and the Istio ingress gateway to send traffic to your Istio enabled workloads while being able to continue using the ALB specific features and th ## Provision a certificate and key for an application without sidecars DevFeed: [Provision a certificate and key for an application without sidecars]() Original publisher: [Read original article]() Author: Lei Tang (Google) Published: 2020-03-25T00:00:00Z Content type: tutorial Language: en Sources: [Istio Blog]() Topics: [istio](), [service-mesh](), [certificates](), [private key](), [TLS (Transport Layer Security)](), [kubectl](), [Provisioning](), [Prometheus]() Tags: [certificate](), [deployment](), [istio](), [kubectl](), [mesh](), [microservices](), [mutual-tls](), [private-key](), [prometheus](), [provisioning](), [service-mesh](), [services](), [sidecar](), [sidecars]() ### AI overview This tutorial explains how to provision an application certificate and private key without using a sidecar to manage traffic. It describes deploying an Istio sidecar solely to obtain certificates through the CSR flow and share them with an application through a mounted tmpfs file, using Prometheus as the example. ### Source excerpt The following information describes an experimental feature, which is intended for evaluation purposes only. Istio sidecars obtain their certificates using the secret discovery service. A service in the service mesh may not need (or want) an Envoy sidecar to handle its traffic. In this case, the service will need to obtain a certificate itself if it wants to connect to other TLS or mutual TLS secured services. For a service with no need of a sidecar to manage its traffic, a sidecar can nevertheless still be deployed only to provision the private key and certificates through the CSR flow from the CA and then share the certificate with the service through a mounted file in tmpfs. We have used Prometheus as our example application for provisioning a certificate using this mechanism. In the example application (i.e., Prometheus), a sidecar is added to the Prometheus deployment by setting the flag .Values.prometheus.provisionPrometheusCert to true (this flag is set to true by default in an Istio installation). This deployed sidecar will then request and share a certificate with Prometheus. The key and certificate provisioned for the example application are mounted in the directory /etc/istio-certs/. We can list the key and certificate provisioned for the application by running the following command: $ kubectl exec -it `kubectl get pod -l app=prometheus -n istio-system -o jsonpath='{.items[0].metadata.name}'` -c prometheus -n istio-system -- ls -la /etc/istio-certs/ The output from the above command should include non-empty key and certificate files, similar to the following: -rwxr-xr-x 1 root root 2209 Feb 25 13:06 cert-chain.pem -rwxr-xr-x 1 root root 1679 Feb 25 13:06 key.pem -rwxr-xr-x 1 root root 1054 Feb 25 13:06 root-cert.pem If you want to use this mechanism to provision a certificate for your own application, take a look at our Prometheus example application and simply follow the same pattern. ## DNS Certificate Management DevFeed: [DNS Certificate Management]() Original publisher: [Read original article]() Author: Lei Tang (Google) Published: 2019-11-14T00:00:00Z Content type: article Language: en Sources: [Istio Blog]() Topics: [certificates](), [istio](), [Provisioning](), [Kubernetes](), [control-plane](), [Security](), [TLS (Transport Layer Security)](), [Architecture & Design]() Tags: [1-4](), [certificate](), [certificate-management](), [certificates](), [citadel](), [control-plane](), [dns](), [istio](), [kubernetes](), [mesh](), [microservices](), [provisioning](), [security](), [services](), [tls]() ### AI overview This article describes an Istio 1.4 feature for securely provisioning and managing DNS certificates signed by the Kubernetes CA. The approach removes the dependency on Citadel, avoids maintaining a private signing key, and simplifies root certificate distribution to TLS clients. ### Source excerpt By default, Citadel manages the DNS certificates of the Istio control plane. Citadel is a large component that maintains its own private signing key, and acts as a Certificate Authority (CA). New in Istio 1.4, we introduce a feature to securely provision and manage DNS certificates signed by the Kubernetes CA, which has the following advantages. Lighter weight DNS certificate management with no dependency on Citadel. Unlike Citadel, this feature doesn't maintain a private signing key, which enhances security. Simplified root certificate distribution to TLS clients. Clients no longer need to wait for Citadel to generate and distribute its CA certificate. The following diagram shows the architecture of provisioning and managing DNS certificates in Istio. Chiron is the component provisioning and managing DNS certificates in Istio. The architecture of provisioning and managing DNS certificates in Istio To try this new feature, refer to the DNS certificate management task. ## Secure Webhook Management DevFeed: [Secure Webhook Management]() Original publisher: [Read original article]() Author: Lei Tang (Google) Published: 2019-11-14T00:00:00Z Content type: release Language: en Sources: [Istio Blog]() Topics: [istio](), [Kubernetes](), [Security](), [Cloud Native Ecosystem]() Tags: [certificate](), [certificates](), [istio](), [istioctl](), [kubernetes](), [mesh](), [microservices](), [security](), [services](), [webhook]() ### AI overview This article describes Istio 1.4's more secure webhook management. It explains how istioctl takes over webhook configuration from Galley and the sidecar injector, reduces their privileges, and verifies webhook server readiness and certificate chains before configuration. ### Source excerpt Istio has two webhooks: Galley and the sidecar injector. Galley validates Kubernetes resources and the sidecar injector injects sidecar containers into Istio. By default, Galley and the sidecar injector manage their own webhook configurations. This can pose a security risk if they are compromised, for example, through buffer overflow attacks. Configuring a webhook is a highly privileged operation as a webhook may monitor and mutate all Kubernetes resources. In the following example, the attacker compromises Galley and modifies the webhook configuration of Galley to eavesdrop on all Kubernetes secrets (the clientConfig is modified by the attacker to direct the secrets resources to a service owned by the attacker). An example attack To protect against this kind of attack, Istio 1.4 introduces a new feature to securely manage webhooks using istioctl: istioctl, instead of Galley and the sidecar injector, manage the webhook configurations. Galley and the sidecar injector are de-privileged so even if they are compromised, they will not be able to alter the webhook configurations. Before configuring a webhook, istioctl will verify the webhook server is up and that the certificate chain used by the webhook server is valid. This reduces the errors that can occur before a server is ready or if a server has invalid certificates. To try this new feature, refer to the Istio webhook management task. ## Change in Secret Discovery Service in Istio 1.3 DevFeed: [Change in Secret Discovery Service in Istio 1.3]() Original publisher: [Read original article]() Author: Phillip Quy Le (Google) Published: 2019-09-10T00:00:00Z Content type: release Language: en Sources: [Istio Blog]() Topics: [istio](), [Kubernetes](), [JSON Web Tokens](), [certificates](), [API](), [api server](), [upgrade](), [version](), [Gke](), [on-prem](), [file]() Tags: [api](), [api-server](), [certificate](), [certificates](), [change](), [deployment](), [discovery](), [gke](), [istio](), [jwt](), [kubernetes](), [mesh](), [microservices](), [mount](), [nodeagent](), [on-prem](), [pki](), [sds](), [secret](), [secret-discovery-service](), [security](), [services](), [signing](), [token](), [upgrade](), [version]() ### AI overview Istio 1.3 changes its Secret Discovery Service to use trustworthy Kubernetes JWTs when issuing certificates for workload instances. The article explains the Kubernetes version requirements, platform-specific configuration considerations, and the file-mount fallback for platforms without trustworthy JWT support. ### Source excerpt In Istio 1.3, we are taking advantage of improvements in Kubernetes to issue certificates for workload instances more securely. When a Citadel Agent sends a certificate signing request to Citadel to get a certificate for a workload instance, it includes the JWT that the Kubernetes API server issued representing the service account of the workload instance. If Citadel can authenticate the JWT, it extracts the service account name needed to issue the certificate for the workload instance. Before Kubernetes 1.12, the Kubernetes API server issues JWTs with the following issues: The tokens don't have important fields to limit their scope of usage, such as aud or exp. See Bound Service Tokens for more info. The tokens are mounted onto all the pods without a way to opt-out. See Service Account Token Volumes for motivation. Kubernetes 1.12 introduces trustworthy JWTs to solve these issues. However, support for the aud field to have a different value than the API server audience didn't become available until Kubernetes 1.13. To better secure the mesh, Istio 1.3 only supports trustworthy JWTs and requires the value of the aud field to be istio-ca when you enable SDS. Before upgrading your Istio deployment to 1.3 with SDS enabled, verify that you use Kubernetes 1.13 or later. Make the following considerations based on your platform of choice: GKE: Upgrade your cluster version to at least 1.13. On-prem Kubernetes and GKE on-prem: Add extra configurations to your Kubernetes. You may also want to refer to the api-server page for the most up-to-date flag names. For other platforms, check with your provider. If your vendor does not support trustworthy JWTs, you will need to fall back to the file-mount approach to propagate the workload keys and certificates in Istio 1.3. ## Extending Istio Self-Signed Root Certificate Lifetime DevFeed: [Extending Istio Self-Signed Root Certificate Lifetime]() Original publisher: [Read original article]() Author: Oliver Liu Published: 2019-06-07T00:00:00Z Content type: tutorial Language: en Sources: [Istio Blog]() Topics: [istio](), [certificates](), [Security]() Tags: [certificate](), [certificates](), [citadel](), [clusters](), [how-to](), [istio](), [mesh](), [microservices](), [outage](), [pki](), [root](), [rotation](), [security](), [services]() ### AI overview A guide to extending the lifetime of Istio self-signed root certificates and scheduling regular root transitions. It explains that the historical one-year lifetime can require annual rotation to prevent certificate expiration and potential cluster-wide outages. ### Source excerpt Istio self-signed certificates have historically had a 1 year default lifetime. If you are using Istio self-signed certificates, you need to schedule regular root transitions before they expire. An expiration of a root certificate may lead to an unexpected cluster-wide outage. The issue affects new clusters created with versions up to 1.0.7 and 1.1.7. See Extending Self-Signed Certificate Lifetime for information on how to gauge the age of your certificates and how to perform rotation. We strongly recommend you rotate root keys and root certificates annually as a security best practice. We will send out instructions for root key/cert rotation soon. ## The Julia Community Prizes, 2018 DevFeed: [The Julia Community Prizes, 2018]() Original publisher: [Read original article]() Author: Avik Sengupta Published: 2018-09-04T00:00:00Z Content type: news Language: en Sources: [JuliaLang - The Julia programming language]() Topics: [The Julia Language](), [Computing](), [GPU](), [Development](), [Documentation]() Tags: [2018](), [alan-edelman](), [award](), [certificate](), [community](), [computing](), [contributions](), [developers](), [development](), [documentation](), [engagement](), [gpu](), [infrastructure](), [london](), [mit](), [over]() ### AI overview The Julia Community Prizes recognize four contributors for work extending Julia to GPUs, improving its test suite and documentation, developing JuliaDiffEq, engaging the community, and stewarding community infrastructure. The 2018 awards were announced at JuliaCon in London, with each recipient receiving a certificate and $1,000 prize. ### Source excerpt The Julia Community Prizes, 2018 | The Julia Community Prizes celebrate the amazing set of scientists, developers and designers who have come together build such a strong and diverse ecosystem for numerical computing. Each of the four individuals chosen for the first award in 2018 have made immense contributions to Julia over many yea...