# padding

Published articles for padding.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## A properties panel and annotations, now in Figma Make

DevFeed: [A properties panel and annotations, now in Figma Make](<https://devfeed.tech/articles/a-properties-panel-and-annotations-now-in-figma-make-10017.md>)

Original publisher: [Read original article](<https://www.figma.com/blog/properties-panel-and-annotations-now-in-figma-make/>)

Author: Phillip Wang

Published: 2026-07-30T19:25:32.996000Z

Content type: article

Language: en

Sources: [Figma Blog](<https://devfeed.tech/sources/figma-blog.md>)

Topics: [Figma](<https://devfeed.tech/topics/figma.md>), [Code](<https://devfeed.tech/topics/code.md>), [Document Object Model (DOM)](<https://devfeed.tech/topics/dom.md>), [Prompt Engineering](<https://devfeed.tech/topics/prompt-engineering.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [animation](<https://devfeed.tech/tags/animation.md>), [code](<https://devfeed.tech/tags/code.md>), [design](<https://devfeed.tech/tags/design.md>), [figma](<https://devfeed.tech/tags/figma.md>), [padding](<https://devfeed.tech/tags/padding.md>), [tokens](<https://devfeed.tech/tags/tokens.md>), [typography](<https://devfeed.tech/tags/typography.md>)

### AI overview

Figma introduces a properties panel and annotations in Figma Make, enabling visual edits to code through familiar design controls and in-context prompts. The update supports detailed styling changes, DOM-tree selection, staged review before applying edits, and synchronization with underlying code.

### Source excerpt

With visual editing and annotations, Figma Make is bridging the gap between design and code. Select any element you want to change, adjust it directly in the properties panel, or write in-context prompts with annotations.

## Bootstrap 5.3.4

DevFeed: [Bootstrap 5.3.4](<https://devfeed.tech/articles/bootstrap-5-3-4-22294.md>)

Original publisher: [Read original article](<https://blog.getbootstrap.com/2025/04/03/bootstrap-5-3-4/>)

Author: Mark Otto

Published: 2025-04-03T15:22:00Z

Content type: release

Language: en

Sources: [Bootstrap.com](<https://devfeed.tech/sources/bootstrap-com.md>)

Topics: [Bootstrap](<https://devfeed.tech/topics/bootstrap.md>), [changelog](<https://devfeed.tech/topics/changelog.md>), [CSS](<https://devfeed.tech/topics/css.md>), [Sass](<https://devfeed.tech/topics/sass.md>)

Tags: [bug-fixes](<https://devfeed.tech/tags/bug-fixes.md>), [changelog](<https://devfeed.tech/tags/changelog.md>), [css](<https://devfeed.tech/tags/css.md>), [dark-mode](<https://devfeed.tech/tags/dark-mode.md>), [display](<https://devfeed.tech/tags/display.md>), [npm](<https://devfeed.tech/tags/npm.md>), [padding](<https://devfeed.tech/tags/padding.md>), [release](<https://devfeed.tech/tags/release.md>), [v5](<https://devfeed.tech/tags/v5.md>)

### AI overview

Bootstrap v5.3.4 is a release containing bug fixes and documentation updates. Highlighted changes include fixes for modal and offcanvas headers, close-button display, carousel behavior across color modes, floating-label alignment, Sass nested-rule deprecation warnings, and popover toggling.

### Source excerpt

Bootstrap v5.3.4 is here with several bug fixes and a load of documentation updates. Here are a handful of highlights from the CSS and JS changes: Fixed modal and offcanvas headers collapsing when any padding variables were set to 0. Fixed close button display in color modes. Fixed light mode carousel when in dark mode. Updated floating labels for better <select> alignment and other styling issues. Fixed a Sass 1.77.7 deprecation for nested rules Fixed popover toggling twice to close. Read the GitHub v5.3.4 changelog for a full list of changes (including a ton of documentation and dependency updates) in this release.

## Optimizing Memory Layout in Go: A Deep Dive into Struct Design

DevFeed: [Optimizing Memory Layout in Go: A Deep Dive into Struct Design](<https://devfeed.tech/articles/optimizing-memory-layout-in-go-a-deep-dive-into-struct-design-33341.md>)

Original publisher: [Read original article](<https://blog.ratnesh-maurya.com/blog/Optimizing-Memory-Layout-in-Go-A-Deep-Dive-into-Struct-Design>)

Author: ratneshmaurya2311@gmail.com (Ratnesh Maurya)

Published: 2025-01-10T00:00:00Z

Content type: tutorial

Language: en

Sources: [Ratn Labs](<https://devfeed.tech/sources/ratn-labs.md>)

Topics: [Go Language](<https://devfeed.tech/topics/go-language.md>), [ordering](<https://devfeed.tech/topics/ordering.md>)

Tags: [alignment](<https://devfeed.tech/tags/alignment.md>), [backend](<https://devfeed.tech/tags/backend.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [deep-dive](<https://devfeed.tech/tags/deep-dive.md>), [design](<https://devfeed.tech/tags/design.md>), [go](<https://devfeed.tech/tags/go.md>), [go-backend-system-design](<https://devfeed.tech/tags/go-backend-system-design.md>), [golang](<https://devfeed.tech/tags/golang.md>), [memory](<https://devfeed.tech/tags/memory.md>), [optimizing](<https://devfeed.tech/tags/optimizing.md>), [padding](<https://devfeed.tech/tags/padding.md>), [practical](<https://devfeed.tech/tags/practical.md>), [system-design](<https://devfeed.tech/tags/system-design.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

This article explains how Go struct field ordering affects memory usage through alignment and padding. It includes benchmarks across millions of allocations and practical tools for identifying wasted space.

### Source excerpt

How Go struct field ordering affects memory via alignment and padding, with benchmarks across millions of allocations and practical tools to detect wasted space.

## Spacing Concepts in Jetpack Compose - An Overview

DevFeed: [Spacing Concepts in Jetpack Compose - An Overview](<https://devfeed.tech/articles/spacing-concepts-in-jetpack-compose-an-overview-25099.md>)

Original publisher: [Read original article](<https://dladukedev.com/articles/044_spacing_concepts_compose/>)

Published: 2024-09-19T00:00:00Z

Content type: article

Language: en

Sources: [Donovan LaDuke - Developer](<https://devfeed.tech/sources/donovan-laduke-developer.md>)

Topics: [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [ui](<https://devfeed.tech/topics/ui.md>)

Tags: [article](<https://devfeed.tech/tags/article.md>), [guide](<https://devfeed.tech/tags/guide.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [overview](<https://devfeed.tech/tags/overview.md>), [padding](<https://devfeed.tech/tags/padding.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### AI overview

This article presents a mental model for handling fixed spacing in Jetpack Compose. It explains how to choose between modifiers, Spacer-like composables, and arrangement options based on parent-child and sibling relationships, including considerations for directional layouts and interactive touch targets.

### Source excerpt

A short guide to thinking about the concepts of spacing in Jetpack Compose including Spacers, padding, and Arrangement

## Improving Hugging Face Training Efficiency Through Packing with Flash Attention 2

DevFeed: [Improving Hugging Face Training Efficiency Through Packing with Flash Attention 2](<https://devfeed.tech/articles/improving-hugging-face-training-efficiency-through-packing-with-flash-attention-2-7433.md>)

Original publisher: [Read original article](<https://huggingface.co/blog/packing-with-FA2>)

Author: Rhui Dih Lee; Arthur Zucker; Achintya Kundu; Laura Wynter; Raghu Ganti; Mayank Mishra

Published: 2024-08-21T00:00:00Z

Content type: article

Language: en

Sources: [Hugging Face - Blog](<https://devfeed.tech/sources/hugging-face-blog.md>)

Topics: [hugging face](<https://devfeed.tech/topics/hugging-face.md>), [Transformers](<https://devfeed.tech/topics/transformers.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [GPU](<https://devfeed.tech/topics/gpu.md>), [datasets](<https://devfeed.tech/topics/datasets.md>)

Tags: [datasets](<https://devfeed.tech/tags/datasets.md>), [efficiency](<https://devfeed.tech/tags/efficiency.md>), [flash-attention-2](<https://devfeed.tech/tags/flash-attention-2.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [hugging-face](<https://devfeed.tech/tags/hugging-face.md>), [models](<https://devfeed.tech/tags/models.md>), [packing](<https://devfeed.tech/tags/packing.md>), [padding](<https://devfeed.tech/tags/padding.md>), [training](<https://devfeed.tech/tags/training.md>), [transformers](<https://devfeed.tech/tags/transformers.md>)

### AI overview

The article explains how Hugging Face improves training throughput by packing instruction-tuning sequences without padding while using Flash Attention 2. A new data collator preserves sequence boundaries and can provide up to 2x higher throughput while maintaining convergence quality, with measured gains varying by dataset and sequence-length variance.

### Source excerpt

We're on a journey to advance and democratize artificial intelligence through open source and open science.

## Lazy layouts contentPadding

DevFeed: [Lazy layouts contentPadding](<https://devfeed.tech/articles/lazy-layouts-contentpadding-22661.md>)

Original publisher: [Read original article](<https://www.valueof.io/blog/lazy-layouts-lazyrow-lazycolumn-contentpadding-compose>)

Author: James Shvarts

Published: 2022-05-22T12:57:51Z

Content type: tutorial

Language: en

Sources: [Android Blog - Mobile Dev Notes](<https://devfeed.tech/sources/android-blog-mobile-dev-notes.md>)

Topics: [Compose](<https://devfeed.tech/topics/compose.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [compose](<https://devfeed.tech/tags/compose.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [issue](<https://devfeed.tech/tags/issue.md>), [layout](<https://devfeed.tech/tags/layout.md>), [padding](<https://devfeed.tech/tags/padding.md>), [parameter](<https://devfeed.tech/tags/parameter.md>), [recyclerview](<https://devfeed.tech/tags/recyclerview.md>)

### AI overview

A Compose tutorial explains how to use contentPadding in lazy layouts so the first and last items receive padding without clipping the items between them. It contrasts contentPadding with padding and identifies clipping caused by using padding on the layout.

### Source excerpt

Controlling padding for first and last item in a lazy layout in Compose

## New CSS Units in Codename One Apps

DevFeed: [New CSS Units in Codename One Apps](<https://devfeed.tech/articles/new-css-units-in-codename-one-apps-19399.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/new-css-units-in-codename-one-apps/>)

Author: Steve Hannah

Published: 2021-07-07T00:00:00Z

Content type: release

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [CSS](<https://devfeed.tech/topics/css.md>), [ui](<https://devfeed.tech/topics/ui.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [css](<https://devfeed.tech/tags/css.md>), [examples](<https://devfeed.tech/tags/examples.md>), [fonts](<https://devfeed.tech/tags/fonts.md>), [margin](<https://devfeed.tech/tags/margin.md>), [padding](<https://devfeed.tech/tags/padding.md>)

### AI overview

Codename One adds CSS-inspired units for setting margins, padding, and font sizes in CSS stylesheets, with corresponding Java constants. The article also explains viewport-based units and screen-independent-pixel settings for adapting default font sizes across devices and desktop platforms.

### Source excerpt

We've added some new units that you can use for specifying things like margin, padding and font sizes. You can use each of these units directly in your CSS stylesheets.

## Ensmallening Go binaries by prohibiting comparisons

DevFeed: [Ensmallening Go binaries by prohibiting comparisons](<https://devfeed.tech/articles/ensmallening-go-binaries-by-prohibiting-comparisons-20831.md>)

Original publisher: [Read original article](<https://dave.cheney.net/2020/05/09/ensmallening-go-binaries-by-prohibiting-comparisons>)

Author: Dave Cheney

Published: 2020-05-09T10:23:17Z

Content type: article

Language: en

Sources: [Dave Cheney](<https://devfeed.tech/sources/dave-cheney.md>)

Topics: [Go Language](<https://devfeed.tech/topics/go-language.md>), [Compiler](<https://devfeed.tech/topics/compiler.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [binaries](<https://devfeed.tech/tags/binaries.md>), [code](<https://devfeed.tech/tags/code.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [go](<https://devfeed.tech/tags/go.md>), [padding](<https://devfeed.tech/tags/padding.md>), [programming](<https://devfeed.tech/tags/programming.md>), [types](<https://devfeed.tech/tags/types.md>)

### AI overview

This article examines how equality and struct comparison work in Go, including memory layout, padding, alignment, and memcmp-based comparisons. It connects these implementation details to the size of compiled Go binaries.

### Source excerpt

Conventional wisdom dictates that the larger the number of types declared in a Go program, the larger the resulting binary. Intuitively this makes sense, after all, what's the point in defining a bunch of types if you're not going to write code that operates on them. However, part of the job of a linker is [...]

## False Sharing

DevFeed: [False Sharing](<https://devfeed.tech/articles/false-sharing-24842.md>)

Original publisher: [Read original article](<https://alidg.me/blog/2020/5/1/false-sharing>)

Author: Alimate

Published: 2020-05-01T00:00:00Z

Content type: article

Language: en

Sources: [Ali Dehghan - Kemikit](<https://devfeed.tech/sources/ali-dehghan-kemikit.md>)

Topics: [Latency](<https://devfeed.tech/topics/latency.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>), [Benchmark](<https://devfeed.tech/topics/benchmark.md>), [Concurrent Programming](<https://devfeed.tech/topics/concurrent-programming.md>)

Tags: [benchmark](<https://devfeed.tech/tags/benchmark.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [latency](<https://devfeed.tech/tags/latency.md>), [memory](<https://devfeed.tech/tags/memory.md>), [multithreading](<https://devfeed.tech/tags/multithreading.md>), [padding](<https://devfeed.tech/tags/padding.md>)

### AI overview

This article explains how false sharing in multithreaded JVM applications can increase latency and throughput costs. It uses benchmarks and object-layout analysis to show how padding can isolate counters and improve performance.

### Source excerpt

Measuring false-sharing effect on latency and throughput

## Safe Areas

DevFeed: [Safe Areas](<https://devfeed.tech/articles/safe-areas-19504.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/safe-areas/>)

Author: Steve Hannah

Published: 2020-02-07T00:00:00Z

Content type: tutorial

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [iphone](<https://devfeed.tech/topics/iphone.md>), [API](<https://devfeed.tech/topics/api.md>), [App](<https://devfeed.tech/topics/app.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [apple](<https://devfeed.tech/tags/apple.md>), [developers](<https://devfeed.tech/tags/developers.md>), [iphone](<https://devfeed.tech/tags/iphone.md>), [navigation](<https://devfeed.tech/tags/navigation.md>), [padding](<https://devfeed.tech/tags/padding.md>)

### AI overview

This tutorial explains how Codename One applications can accommodate the iPhone X notch, rounded screen corners, and bottom task bar. It describes APIs and component behavior for keeping content within the device's safe area, including extra padding for bottom tab buttons, and points to a SafeAreasSample example.

### Source excerpt

Apple is so very clever with its designs. With the iPhone X, they found a way to squeeze in a larger screen without increasing the phone dimensions. The screen nearly covers the entire front face of the phone. The "notch", as it has come to be known, may have been a practical concession (they needed to put the camera and speaker somewhere, after all) or an intentional design choice - or maybe a little of both. However the notch was conceived, it is here to stay, and we developers need to "work around" it.

## SwiftUI: впечатления iOS-разработчика о реактивном UI-фреймворке и его синтаксисе

DevFeed: [SwiftUI: впечатления iOS-разработчика о реактивном UI-фреймворке и его синтаксисе](<https://devfeed.tech/articles/article-34264.md>)

Original publisher: [Read original article](<https://tonsky.livejournal.com/324649.html>)

Published: 2020-01-18T15:36:57Z

Content type: opinion

Language: ru

Sources: [Tonsky Стой под стрелой](<https://devfeed.tech/sources/tonsky.md>)

Topics: [SwiftUI](<https://devfeed.tech/topics/swiftui.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [ui](<https://devfeed.tech/topics/ui.md>)

Tags: [foreach](<https://devfeed.tech/tags/foreach.md>), [ios](<https://devfeed.tech/tags/ios.md>), [livejournal](<https://devfeed.tech/tags/livejournal.md>), [padding](<https://devfeed.tech/tags/padding.md>), [swiftui](<https://devfeed.tech/tags/swiftui.md>), [tag-5e1c061eda96](<https://devfeed.tech/tags/tag-5e1c061eda96.md>), [tag-c40b78a8c8a6](<https://devfeed.tech/tags/tag-c40b78a8c8a6.md>), [tag-d16a2c26554f](<https://devfeed.tech/tags/tag-d16a2c26554f.md>), [tag-e3028c5e0ab2](<https://devfeed.tech/tags/tag-e3028c5e0ab2.md>), [ui](<https://devfeed.tech/tags/ui.md>), [view](<https://devfeed.tech/tags/view.md>)

### AI overview

An experienced iOS developer shares impressions of SwiftUI after using it for roughly six months and releasing two production applications. The article praises its reactive, data-driven UI model and previews while criticizing its syntax, element-count limitation, opaque types, and inconsistent modifier and container design.

### Source excerpt

Если вдруг вы еще не знаете, примерно полгода назад Эппл анонсировало новый UI фреймворк -- SwiftUI. Событие очень серьезное, и как iOS разработчик со стажем я тут же переключился на него -- сначала попробовать, а потом уже и выпускать production приложения. Спустя полгода и два заапрувленных релиза, хочу поделиться с вами мыслями о SwiftUI. Во-первых, то, что Эппл выпустило нормальный реактивный data-driven UI фреймворк, заслуживает исключительно всяческих похвал. Правильный тренд, правильный подход, _почти_ интерактивное превью, все вовремя и к месту. Нам, iOS-программистам, чего-то такого сильно не хватало. Во-вторых (и тут уже о сомнительном), количество синтаксического сахара, которым они там обмазываются, вызывает, скажем так, удивление. Им пришлось серьезно расширить язык, чтобы вместо условно VStack( Image(uiImage: image), Text(title), Text(subtitle) ) можно было писать VStack { Image(uiImage: image) Text(title) Text(subtitle) } На что только люди не пойдут чтобы избежать споров о том где ставить запятую! Работает это благодаря вот такому вот прекрасному интерфейсу: То есть не только не очень понятно зачем так усложнять себе жизнь, но еще и больше 10 элементов не засунешь. Может быть создатели руководствовались правилом 7±2 и решили, что пользователи айфона не смогут всерьез осознать более 10 одновременных элеметов на экране. То что в этом интерфейсе пропилена специальная дырка для if напрягает если честно еще больше: Не самим фактом дырки, а вопросом, где же собственно дырки под все остальное? (на самом деле, если хочется больше 10 элементов, есть целый специальный компонент -- ForEach, который -- уберите детей от экрана! -- принимает список) (этот курьез и необходимость вводить opaque types заставляет задуматься, насколько сильно нам вообще нужна статическая типизация и какой ценой. Конечно, сторонники статической типизации скажут, что это просто типизация неправильная, вот была бы правильная и проблем бы не было -- что, в общем-то, универсальный аргумент, удобн

## Large touch targets

DevFeed: [Large touch targets](<https://devfeed.tech/articles/large-touch-targets-9398.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/large-touch-targets/>)

Author: Eric Bailey

Published: 2018-11-21T00:00:00Z

Content type: article

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Accessibility](<https://devfeed.tech/topics/accessibility.md>), [Web Content Accessibility Guidelines](<https://devfeed.tech/topics/web-content-accessibility-guidelines.md>), [web design](<https://devfeed.tech/topics/web-design.md>), [CSS](<https://devfeed.tech/topics/css.md>), [browser](<https://devfeed.tech/topics/browser.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [browser](<https://devfeed.tech/tags/browser.md>), [css](<https://devfeed.tech/tags/css.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [padding](<https://devfeed.tech/tags/padding.md>), [space](<https://devfeed.tech/tags/space.md>), [web-content-accessibility-guidelines](<https://devfeed.tech/tags/web-content-accessibility-guidelines.md>), [web-design](<https://devfeed.tech/tags/web-design.md>)

### AI overview

This article explains why interactive elements need sufficiently large touch targets to support people with motor control issues. It presents the WCAG minimum of 44 by 44 CSS pixels, describes relevant exceptions, recommends padding for small icon buttons and spacing between controls, and explains how to inspect dimensions in a browser.

### Source excerpt

A touch target is the total area a person can click or tap on to activate an interactive element such as a link, input, or button. Background Ensuring that interactive elements have sufficiently large touch targets helps people with motor control issues use your website or application. Providing a too-small touch target may make it difficult or impossible for some people to be able to reliably reach the area required to activate the element. Think of it like trying to thread a needle. The Web Content Accessibility Guidelines (WCAG) specify a minimum size of 44 by 44 CSS pixels for all interactive elements. The exceptions are: If the interactive element's functionality can be activated by another element of acceptable size on the same page. If the interactive element is rendered inline within a block of text, such as a link. If the interactive element's size is controlled by the browser or operating system's UI. If the interactive element has a design whose presentation requires a certain size or shape. Only the inline element exception case typically applies to web design. Even then, a recommended larger body type size will help both increase inline touch target size and help accommodate people with low vision. Small touch targets such as icon buttons can use padding to expand their interactive area without increasing the visible size: It is also recommended that you add space between large interactive elements, to help prevent people from accidentally clicking or tapping the wrong one. How to test To determine the CSS pixel size of an interactive element, use a browser's Inspector feature to check it's computed value. Two common methods to open a browser's Inspector panel are typing Command/Control + Option + i on your keyboard, or by right clicking on an element on your page and choosing the Inspect option. If you right click on the interactive element you want to test, it will automatically be highlighted when you choose the Inspect option in the right click menu

## Analyzing a simple encryption scheme using GitHub SSH keys

DevFeed: [Analyzing a simple encryption scheme using GitHub SSH keys](<https://devfeed.tech/articles/analyzing-a-simple-encryption-scheme-using-github-ssh-keys-29170.md>)

Original publisher: [Read original article](<https://www.latacora.com/blog/2018/09/30/analyzing-github-ssh-key-encryption/>)

Published: 2018-09-30T17:54:00Z

Content type: opinion

Language: en

Sources: [Latacora](<https://devfeed.tech/sources/latacora.md>)

Topics: [Encryption](<https://devfeed.tech/topics/encryption.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [ssh](<https://devfeed.tech/topics/ssh.md>), [openssl](<https://devfeed.tech/topics/openssl.md>), [OpenSSH](<https://devfeed.tech/topics/openssh.md>), [SSL](<https://devfeed.tech/topics/ssl.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>)

Tags: [attacks](<https://devfeed.tech/tags/attacks.md>), [channel](<https://devfeed.tech/tags/channel.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [github](<https://devfeed.tech/tags/github.md>), [openssl](<https://devfeed.tech/tags/openssl.md>), [padding](<https://devfeed.tech/tags/padding.md>), [public-key](<https://devfeed.tech/tags/public-key.md>), [rsa](<https://devfeed.tech/tags/rsa.md>), [ssh](<https://devfeed.tech/tags/ssh.md>), [ssl](<https://devfeed.tech/tags/ssl.md>)

### AI overview

This introductory analysis examines encrypting secrets for recipients using their GitHub SSH public keys and an OpenSSL RSA command. It explains that the scheme's PKCS#1 v1.5 and SSLv2 padding variants are vulnerable to Bleichenbacher's oracle attack, while noting that the described offline threat model does not provide access to a decryption oracle.

### Source excerpt

(This is an introductory level analysis of a scheme involving RSA. If you're already comfortable with Bleichenbacher oracles you should skip it.) Someone pointed me at the following suggestion on the Internet for encrypting secrets to people based on their GitHub SSH keys. I like the idea of making it easier for people to leverage key material and tools they already have. The encryption instructions are: echo "my secret" > message.txt curl -q "https://github.com/${USER}.keys" \ | head -n 1 \ > recipient.pub ssh-keygen -e -m pkcs8 -f recipient.pub > recipient.pem openssl rsautl \ -encrypt \ -pubin \ -inkey recipient.pem \ -ssl \ -in message.txt \ -out encrypted.txt Anything using an openssl command line tool makes me a little uncomfortable. Let's poke at it a little.

## Expanding Signal GIF search

DevFeed: [Expanding Signal GIF search](<https://devfeed.tech/articles/expanding-signal-gif-search-1823.md>)

Original publisher: [Read original article](<https://signal.org/blog/signal-and-giphy-update/>)

Published: 2017-11-01T00:00:00Z

Content type: article

Language: en

Sources: [Signal Blog](<https://devfeed.tech/sources/signal-blog.md>)

Topics: [iOS](<https://devfeed.tech/topics/ios.md>), [image animation](<https://devfeed.tech/topics/image-animation.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [API](<https://devfeed.tech/topics/api.md>), [Network](<https://devfeed.tech/topics/network.md>), [Encryption](<https://devfeed.tech/topics/encryption.md>), [Virtual Private Network](<https://devfeed.tech/topics/vpn.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [api](<https://devfeed.tech/tags/api.md>), [experimental](<https://devfeed.tech/tags/experimental.md>), [ios](<https://devfeed.tech/tags/ios.md>), [network](<https://devfeed.tech/tags/network.md>), [padding](<https://devfeed.tech/tags/padding.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [tls](<https://devfeed.tech/tags/tls.md>), [updates](<https://devfeed.tech/tags/updates.md>), [vpn](<https://devfeed.tech/tags/vpn.md>)

### AI overview

Signal's iOS beta adds in-app browsing and search for popular animated GIFs, extending an earlier Android feature. The article explains how Signal proxies GIPHY requests while using end-to-end TLS to hide search contents from Signal and the requester's identity from GIPHY, and discusses padding as a defense against traffic analysis.

### Source excerpt

Today's Signal beta for iOS includes support for animated GIF search. Signal iOS has long supported sending and receiving GIFs, but today's beta adds support for browsing and searching popular GIFs from within Signal. We previously announced experimental support for animated GIF search in Signal Android, which we're now bringing to iOS, along with some privacy updates to the process. Read more...

## On the Computational Complexity of MapReduce

DevFeed: [On the Computational Complexity of MapReduce](<https://devfeed.tech/articles/on-the-computational-complexity-of-mapreduce-40368.md>)

Original publisher: [Read original article](<https://www.jeremykun.com/2014/10/05/on-the-computational-complexity-of-mapreduce/>)

Published: 2014-10-05T09:00:30Z

Content type: article

Language: en

Sources: [Jeremy Kun](<https://devfeed.tech/sources/jeremy-kun.md>)

Topics: [computational complexity](<https://devfeed.tech/topics/computational-complexity.md>), [Algorithms, Complexity](<https://devfeed.tech/topics/algorithms-complexity.md>), [Graphs](<https://devfeed.tech/topics/graphs.md>)

Tags: [algorithm](<https://devfeed.tech/tags/algorithm.md>), [algorithms](<https://devfeed.tech/tags/algorithms.md>), [circuit-complexity](<https://devfeed.tech/tags/circuit-complexity.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [computational-complexity](<https://devfeed.tech/tags/computational-complexity.md>), [distributed-computing](<https://devfeed.tech/tags/distributed-computing.md>), [exponential-time-hypothesis](<https://devfeed.tech/tags/exponential-time-hypothesis.md>), [graphs](<https://devfeed.tech/tags/graphs.md>), [hierarchy](<https://devfeed.tech/tags/hierarchy.md>), [karloff](<https://devfeed.tech/tags/karloff.md>), [l-vs-p](<https://devfeed.tech/tags/l-vs-p.md>), [map-reduce](<https://devfeed.tech/tags/map-reduce.md>), [padding](<https://devfeed.tech/tags/padding.md>), [research](<https://devfeed.tech/tags/research.md>)

### AI overview

The article presents an accessible discussion of research analyzing the computational complexity of a theoretical model of the MapReduce framework. It describes open questions about MapReduce's power, including whether constant-round algorithms can determine graph connectivity and how the model relates to complexity classes such as P and L.

### Source excerpt

I recently wrapped up a fun paper with my coauthors Ben Fish, Adam Lelkes, Lev Reyzin, and Gyorgy Turan in which we analyzed the computational complexity of a model of the popular MapReduce framework. Check out the preprint on the arXiv. Update: this paper is now published in the proceedings of DISC2015. As usual I'll give a less formal discussion of the research here, and because the paper is a bit more technically involved than my previous work I'll be omitting some of the more pedantic details.

## Building Dynamic Custom Views

DevFeed: [Building Dynamic Custom Views](<https://devfeed.tech/articles/building-dynamic-custom-views-30572.md>)

Original publisher: [Read original article](<https://ryanharter.com/blog/2014/08/building-dynamic-custom-views/>)

Published: 2014-08-29T07:00:00Z

Content type: tutorial

Language: en

Sources: [Blogs on Ryan Harter](<https://devfeed.tech/sources/blogs-on-ryan-harter.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [screen](<https://devfeed.tech/topics/screen.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [padding](<https://devfeed.tech/tags/padding.md>), [screen](<https://devfeed.tech/tags/screen.md>), [subclass](<https://devfeed.tech/tags/subclass.md>), [view](<https://devfeed.tech/tags/view.md>)

### AI overview

A tutorial on building a custom Android view that lets users scroll content so any item can align with the center of the screen. It discusses using a HorizontalScrollView, adding scroll-position observation through subclassing, and handling side padding for different screen sizes.

### Source excerpt

Last week I released Fragment for Android. Fragment is made up of all sorts of custom Views, which I think sets it apart from many apps in the Play Store. Some of these views have a similar pattern to views I've had to create for other apps, in which a scroll view has padding such that every item within it can be scrolled to the center of the view. On it's surface this doesn't seem complex, but when you consider the massive difference in screen sizes available on Android, things get a little more complicated.

## Macro View of Map Internals In Go

DevFeed: [Macro View of Map Internals In Go](<https://devfeed.tech/articles/macro-view-of-map-internals-in-go-22087.md>)

Original publisher: [Read original article](<https://www.ardanlabs.com/blog/2013/12/macro-view-of-map-internals-in-go.html>)

Published: 2013-12-31T00:00:00Z

Content type: tutorial

Language: en

Sources: [William Kennedy](<https://devfeed.tech/sources/william-kennedy.md>)

Topics: [Go Language](<https://devfeed.tech/topics/go-language.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [ardan-labs](<https://devfeed.tech/tags/ardan-labs.md>), [blog](<https://devfeed.tech/tags/blog.md>), [fmt](<https://devfeed.tech/tags/fmt.md>), [go](<https://devfeed.tech/tags/go.md>), [go-programming](<https://devfeed.tech/tags/go-programming.md>), [golang](<https://devfeed.tech/tags/golang.md>), [hash](<https://devfeed.tech/tags/hash.md>), [internals](<https://devfeed.tech/tags/internals.md>), [map](<https://devfeed.tech/tags/map.md>), [maps](<https://devfeed.tech/tags/maps.md>), [memory](<https://devfeed.tech/tags/memory.md>), [padding](<https://devfeed.tech/tags/padding.md>), [programming](<https://devfeed.tech/tags/programming.md>), [range](<https://devfeed.tech/tags/range.md>)

### AI overview

This tutorial explains how Go maps are created and used, why iteration order is not guaranteed, and how maps are organized internally as hash tables with power-of-two bucket counts. It also introduces bucket selection, overflow, and memory padding.

### Source excerpt

Introduction There are lots of posts that talk about the internals of slices, but when it comes to maps, we are left in the dark. I was wondering why and then I found the code for maps and it all made sense. https://golang.org/src/runtime/hashmap.go At least for me, this code is complicated. That being said, I think we can create a macro view of how maps are structured and grow. This should explain why they are unordered, efficient and fast. Creating and Using Maps Let's look at how we can use a map literal to create a map and store a few values:

## \* { box-sizing: border-box } FTW

DevFeed: [\* { box-sizing: border-box } FTW](<https://devfeed.tech/articles/box-sizing-border-box-ftw-21670.md>)

Original publisher: [Read original article](<https://paulirish.com/2012/box-sizing-border-box-ftw/>)

Author: Paul Irish

Published: 2012-02-01T17:11:00Z

Content type: article

Language: en

Sources: [Paul Irish](<https://devfeed.tech/sources/paul-irish.md>)

Topics: [CSS](<https://devfeed.tech/topics/css.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [browser](<https://devfeed.tech/topics/browser.md>), [WebKit](<https://devfeed.tech/topics/webkit.md>), [polyfill](<https://devfeed.tech/topics/polyfill.md>), [jQuery](<https://devfeed.tech/topics/jquery.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [css](<https://devfeed.tech/tags/css.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [front-end](<https://devfeed.tech/tags/front-end.md>), [layout](<https://devfeed.tech/tags/layout.md>), [padding](<https://devfeed.tech/tags/padding.md>), [polyfill](<https://devfeed.tech/tags/polyfill.md>)

### AI overview

This article recommends applying a natural border-box sizing model to all elements by setting box-sizing on html and inheriting it through elements and pseudo-elements. It explains how this keeps declared widths stable when padding is added, discusses browser support and required prefixes for older Firefox, iOS, and Android versions, and notes compatibility with jQuery, Chrome DevTools, and mobile devices.

### Source excerpt

One of my least favorite parts about layout with CSS is the relationship of width and padding. You're busy defining widths to match your grid or general column proportions, then down the line you start to add in text, which necessitates defining padding for those boxes. And 'lo and behold, you now are subtracting pixels from your original width so the box doesn't expand. Ugh. If I say the width is 200px, gosh darn it, it's gonna be a 200px wide box even if I have 20px of padding. So as you know, this is NOT how the box model has worked for the past ten years. Wikipedia has a great history of this box model. Jeff Kaufman also dove into the history Anyway, I have a recommendation for your CSS going forward: 1 2 3 4 5 6 7 /* apply a natural box layout model to all elements, but allowing components to change */ html { box-sizing: border-box; } *, *:before, *:after { box-sizing: inherit; } Update August 2014: This code was updated to match new box-sizing best practices. Also prefixes are pretty much dead. This gives you the box model you want. Applies it to all elements. Turns out many browsers already use border-box for a lot of form elements (which is why inputs and textareas look diff at width:100%;) But applying this to all elements is safe and wise. Browser support Due to browser support, this recommendation is only for projects that support IE8 and up. (Full browser compat at MDN) Firefox <= 28 still needs the -moz- prefix, and <= iOS4, Android <= 2.3 need the -webkit-, but everyone else uses the unprefixed. You can find more info about a box-sizing polyfill for IE6 & 7 at html5please.com/#box-sizing (which was developed with * { box-sizing: border-box!). Is it safe to use? Totally. jQuery works pretty great with it (except this). As mentioned, browser support is excellent. And a number of projects use this layout model by default, including the WebKit Web Inspector (aka Chrome DevTools). I heard from Dutch front-end developer Yathura Thorn on his experience: We've