Forwarded from HN Best Comments
Re: Smartphones with Qualcomm chip secretly send perso...
This seems like much bigger news than it's being received as. Sure, other chip makers do sketchy things, but is that really where we're at in 2023? We're so beaten down by proprietary user-disrespecting hardware/software that we just shrug it off?
<rant because I hoped for more outrage on this and am not seeing it>
This makes me mad. I'm so sick of this type of thing. It's a horrible time too because the embedded 5G chips are about to be part of everything, sending telemetry back about where they are and what they're being used for. I think it's utterly ridiculous that if you aren't ok with this type of thing, then you have to go way out of the mainstream to find products, and often there's no viable option. "Ownership" now means nothing.
Imagine if you bought a car from somebody, and they secretly kept a spare key and periodically used your car to run their personal errand. Would you be ok with that so long as they always had it back before you needed it so you never knew they were doing it?
That's what is happening when you "buy" a device and the device maker uses it to run code that serves only themselves (without receiving permission), to the detriment of your privacy. I can only hope RISC-V combined with people willing to care can lead to a return to a time when people actually own stuff and ownership is something we respect.
</rant>
freedomben, 1 hour ago
This seems like much bigger news than it's being received as. Sure, other chip makers do sketchy things, but is that really where we're at in 2023? We're so beaten down by proprietary user-disrespecting hardware/software that we just shrug it off?
<rant because I hoped for more outrage on this and am not seeing it>
This makes me mad. I'm so sick of this type of thing. It's a horrible time too because the embedded 5G chips are about to be part of everything, sending telemetry back about where they are and what they're being used for. I think it's utterly ridiculous that if you aren't ok with this type of thing, then you have to go way out of the mainstream to find products, and often there's no viable option. "Ownership" now means nothing.
Imagine if you bought a car from somebody, and they secretly kept a spare key and periodically used your car to run their personal errand. Would you be ok with that so long as they always had it back before you needed it so you never knew they were doing it?
That's what is happening when you "buy" a device and the device maker uses it to run code that serves only themselves (without receiving permission), to the detriment of your privacy. I can only hope RISC-V combined with people willing to care can lead to a return to a time when people actually own stuff and ownership is something we respect.
</rant>
freedomben, 1 hour ago
Вот скажите мне, чем это не Ремарк? Причем буквально, практически.
Forwarded from Тринадцатый.
Тогда в 2015 мы воевали на Донбассе, а к концу года после очередной командировки Тропа в драке убил оппонента, тот на его беду ещё и оказался сотрудником полиции.
Получил одиннадцать строгого.
Я звонил ему на централ, загонял передачки, ещё тогда я сказал ему, что срок он свой не досидит, и вскоре такие, как мы потребуемся нашей стране.
Так и случилось.
Из колонии в ЧВК "Вагнер", от туда Лисичанск, там ранение, из госпиталя в Соледар, там ранение, опять госпиталь, а от туда на Бахмут.
Его контракт кончился сегодня, сегодня Тропа едет домой.
У него родился сын, и он впервые его увидит.
За спиной семь лет строгого и Соледаро-Бахмуьская мясорубка. Хромой походкой, из-за спиц в ноге, он закидывает за спину рюкзак и едет домой.
Господь на твоей стороне Брат мой🙏🏻
Получил одиннадцать строгого.
Я звонил ему на централ, загонял передачки, ещё тогда я сказал ему, что срок он свой не досидит, и вскоре такие, как мы потребуемся нашей стране.
Так и случилось.
Из колонии в ЧВК "Вагнер", от туда Лисичанск, там ранение, из госпиталя в Соледар, там ранение, опять госпиталь, а от туда на Бахмут.
Его контракт кончился сегодня, сегодня Тропа едет домой.
У него родился сын, и он впервые его увидит.
За спиной семь лет строгого и Соледаро-Бахмуьская мясорубка. Хромой походкой, из-за спиц в ноге, он закидывает за спину рюкзак и едет домой.
Господь на твоей стороне Брат мой🙏🏻
Forwarded from Таблички СССР
Ортопедическия ботинки доктора Мартенса
Дореволюционная рекламная табличка (фрагмент) известной до сих пор торговой марки.
Что можно сказать. Оказывается. доктор Мартенс, был действительно доктором и делал ортопедическую обувь, а не вот это вот всё, что под этой маркой выпускается сейчас.
#РоссийскаяИмперия #медицина #торговля
Канал @tablichki_ussr
предложить табличку: публикация, продажа, обмен @tablichki_ussr_bot
Дореволюционная рекламная табличка (фрагмент) известной до сих пор торговой марки.
Что можно сказать. Оказывается. доктор Мартенс, был действительно доктором и делал ортопедическую обувь, а не вот это вот всё, что под этой маркой выпускается сейчас.
#РоссийскаяИмперия #медицина #торговля
Канал @tablichki_ussr
предложить табличку: публикация, продажа, обмен @tablichki_ussr_bot
Forwarded from Pro IP
Нелегкая судьба модификаций компьютерных программ из-за признания их производными произведениями
А.А. Никифоров в своей статье рассматривает проблемы производных произведений для ЭВМ в свете соотношения таких понятий, как:
- личное неимущественное право на неприкосновенность произведения (ст. 1266 ГК РФ),
- право на переработку произведения (ст. 1270 ГК РФ) и
- производное произведение (ст. 126 ГК РФ).
С учётом законодательного регулирования автор выводит следующие постулаты:
1️⃣ К программе применимы все нормы, относящиеся к литературным произведениям, включая право на неприкосновенность произведения.
2️⃣ При этом под переработкой программы для ЭВМ понимается любое внесение изменений в саму программу. Соответственно, даже мелкое изменение программного кода автоматически приводит к появлению нового объекта авторских прав.
3️⃣ Следовательно, в отношении программ вопрос всегда будет стоять о нарушении исключительных прав, а не о нарушении права на неприкосновенность.
Дальше г-н Никифиров анализирует их верность с учётом различных вариантов модификаций. И тут, пожалуй, имеет смысл скопировать текст статьи, дабы заинтересовать вас детальностью исследования:
📌 Лицо берет программный код оригинала и использует его для создания новой компьютерной программы;
📌 Лицо берет оригинал и исправляет явные ошибки в программном коде;
📌 Лицо берет оригинал и исправляет ошибки в программном коде, не изменяющие ничего с точки зрения обычного пользователя (т.е. в программе не появляется новый функционал), но при этом программа работает эффективней (быстрее обрабатывает команды, к примеру);
📌 Лицо снабжает программу комментариями, пояснениями, иллюстрациями, видимыми на уровне программного кода, при этом код самой программы остается неизменным;
📌 Лицо снабжает программу комментариями, пояснениями, иллюстрациями на уровне аудиовизуального отображения, порождаемого командами, что уже требует внесения изменений в программный код;
📌 Лицо создает программу, которая изменяет сюжет в программе – компьютерной игре или привносит какие-то другие изменения в игровой процесс, что, конечно, так же требует внесения изменений в программный код;
📌 Лицо берет программу (или создает специальную программу, вносящую изменения в первоначальную программу) и вносит в нее новый программный код, добавляя дополнительные функции или инструментарий».
И эти варианты смоделированы не просто так, для галочки, а далее в статье приводится их разбор.
Помимо этого, А.А. Никифоров изучает проблему не только в связке правообладатель-пользователь, но и с точки зрения последствий создания модификаций самим правообладателем. Ведь если модификация приводит к созданию нового произведения, то это должно требовать и заключения нового лицензионного договора с пользователями. А тут возникают вопросы идентификации объекта, возмездности, судьбы первоначального договора, отслеживания версионности и т.д.
Отдельную симпатию вызвал у меня раздел, посвящённый анализу внесения изменений в компьютерные игры. Ведь тут очень интересный вопрос о правовой природе данного объекта. И чтобы всё не звучало сухо и сугубо теоретически, автор развивает свою мысль на примере реального кейса Konami v. Spec Computer. Также последствия квалифицированы в зависимости от характера изменений (в сюжетную линию, визуализацию, числовые показатели и проч.).
Выходом из ситуации А.А. Никифиров видит разделение понятий «модификация» и «переработка». И то и другое про изменения, но последнее приводит к появлению нового объекта интеллектуальных прав, а первое – нет.
#модификация #компьютерныеигры #по #неприкосновенность #производноепроизведение #переработка #лицензия #авторскоеправо #аналитика
P.S. Я в восторге от работы. Из-за обилия спорных моментов, возможно, читать чуть сложно, но мысль автора чётко прослеживается и добросовестно разбираются различные точки зрения. Кстати, там большой раздел про проект Сколково ещё, но освещать его не стала из-за объёма.
А.А. Никифоров в своей статье рассматривает проблемы производных произведений для ЭВМ в свете соотношения таких понятий, как:
- личное неимущественное право на неприкосновенность произведения (ст. 1266 ГК РФ),
- право на переработку произведения (ст. 1270 ГК РФ) и
- производное произведение (ст. 126 ГК РФ).
С учётом законодательного регулирования автор выводит следующие постулаты:
1️⃣ К программе применимы все нормы, относящиеся к литературным произведениям, включая право на неприкосновенность произведения.
2️⃣ При этом под переработкой программы для ЭВМ понимается любое внесение изменений в саму программу. Соответственно, даже мелкое изменение программного кода автоматически приводит к появлению нового объекта авторских прав.
3️⃣ Следовательно, в отношении программ вопрос всегда будет стоять о нарушении исключительных прав, а не о нарушении права на неприкосновенность.
Дальше г-н Никифиров анализирует их верность с учётом различных вариантов модификаций. И тут, пожалуй, имеет смысл скопировать текст статьи, дабы заинтересовать вас детальностью исследования:
📌 Лицо берет программный код оригинала и использует его для создания новой компьютерной программы;
📌 Лицо берет оригинал и исправляет явные ошибки в программном коде;
📌 Лицо берет оригинал и исправляет ошибки в программном коде, не изменяющие ничего с точки зрения обычного пользователя (т.е. в программе не появляется новый функционал), но при этом программа работает эффективней (быстрее обрабатывает команды, к примеру);
📌 Лицо снабжает программу комментариями, пояснениями, иллюстрациями, видимыми на уровне программного кода, при этом код самой программы остается неизменным;
📌 Лицо снабжает программу комментариями, пояснениями, иллюстрациями на уровне аудиовизуального отображения, порождаемого командами, что уже требует внесения изменений в программный код;
📌 Лицо создает программу, которая изменяет сюжет в программе – компьютерной игре или привносит какие-то другие изменения в игровой процесс, что, конечно, так же требует внесения изменений в программный код;
📌 Лицо берет программу (или создает специальную программу, вносящую изменения в первоначальную программу) и вносит в нее новый программный код, добавляя дополнительные функции или инструментарий».
И эти варианты смоделированы не просто так, для галочки, а далее в статье приводится их разбор.
Помимо этого, А.А. Никифоров изучает проблему не только в связке правообладатель-пользователь, но и с точки зрения последствий создания модификаций самим правообладателем. Ведь если модификация приводит к созданию нового произведения, то это должно требовать и заключения нового лицензионного договора с пользователями. А тут возникают вопросы идентификации объекта, возмездности, судьбы первоначального договора, отслеживания версионности и т.д.
Отдельную симпатию вызвал у меня раздел, посвящённый анализу внесения изменений в компьютерные игры. Ведь тут очень интересный вопрос о правовой природе данного объекта. И чтобы всё не звучало сухо и сугубо теоретически, автор развивает свою мысль на примере реального кейса Konami v. Spec Computer. Также последствия квалифицированы в зависимости от характера изменений (в сюжетную линию, визуализацию, числовые показатели и проч.).
Выходом из ситуации А.А. Никифиров видит разделение понятий «модификация» и «переработка». И то и другое про изменения, но последнее приводит к появлению нового объекта интеллектуальных прав, а первое – нет.
#модификация #компьютерныеигры #по #неприкосновенность #производноепроизведение #переработка #лицензия #авторскоеправо #аналитика
P.S. Я в восторге от работы. Из-за обилия спорных моментов, возможно, читать чуть сложно, но мысль автора чётко прослеживается и добросовестно разбираются различные точки зрения. Кстати, там большой раздел про проект Сколково ещё, но освещать его не стала из-за объёма.
Forwarded from HN Best Comments
Re: Lessons by 3blue1brown
2b1b does a video on how you raise e to a matrix (hint: raising something to e is converted into another function where it's not nonsensical to do such a thing.)
In about 10 minutes he explains something my math methods instructor struggled with over two weeks (4 classes). I was resistant to the view that YouTube could host "decent" instructional content for a long time. That video was one of the first that was CLEARLY superior to the instruction I received at a tier 1 research institution.
dingosity, 2 hours ago
2b1b does a video on how you raise e to a matrix (hint: raising something to e is converted into another function where it's not nonsensical to do such a thing.)
In about 10 minutes he explains something my math methods instructor struggled with over two weeks (4 classes). I was resistant to the view that YouTube could host "decent" instructional content for a long time. That video was one of the first that was CLEARLY superior to the instruction I received at a tier 1 research institution.
dingosity, 2 hours ago
Forwarded from HN Best Comments
Re: Why did Google Brain exist?
Lots of great insight. Here’s one:
“Given the long timelines of a PhD program, the vast majority of early ML researchers were self-taught crossovers from other fields. This created the conditions for excellent interdisciplinary work to happen. This transitional anomaly is unfortunately mistaken by most people to be an inherent property of machine learning to upturn existing fields. It is not.
Today, the vast majority of new ML researcher hires are freshly minted PhDs, who have only ever studied problems from the ML point of view. I’ve seen repeatedly that it’s much harder for a ML PhD to learn chemistry than for a chemist to learn ML.”
dr_dshiv, 3 hours ago
Lots of great insight. Here’s one:
“Given the long timelines of a PhD program, the vast majority of early ML researchers were self-taught crossovers from other fields. This created the conditions for excellent interdisciplinary work to happen. This transitional anomaly is unfortunately mistaken by most people to be an inherent property of machine learning to upturn existing fields. It is not.
Today, the vast majority of new ML researcher hires are freshly minted PhDs, who have only ever studied problems from the ML point of view. I’ve seen repeatedly that it’s much harder for a ML PhD to learn chemistry than for a chemist to learn ML.”
dr_dshiv, 3 hours ago
Forwarded from HN Best Comments
Re: Why is OAuth still hard in 2023?
Because the documentation is bad. Oauth is really simple:
Lets say you want to use google as an auth provider. You do this:
"Hey google who is this guy? I'm going to send them to google.com/oauth, send them back to example.com/oauth, and in the headers of the request include the word "Authorization: bearer" followed by a bunch of text"
Google says "Oh yeah I know that guy, here I'll send them back to where you said with a token"
Then later on you can take the token and say "Hey google, somebody gave me this token, who is it?"
That's pretty much it. You have to trust that google isn't lying to you, but that's kindof the point of oauth.
But that's never what the documentation says. It's always 10 pages long and the examples are like "here's a fully functioning python web server using flask and function decorators, oh the actual auth flow, which is really like 3 lines of code, is hidden inside of a library".
To people who write documentation: PLEASE for the love of god show me how to talk to your API both using your library, but also using something like urllib2 or requests or something.
Ideally the documentation is the absolute most minimal way of making the service work, and then adds more and more usefulness on top of that. I'm not going to judge you for writing bad code in an example. The example could practically be pseudocode for all I care. I just want to see generally how your API is supposed to work.
edit: yes, auth0, I am looking at you.
thepasswordis, 2 hours ago
Because the documentation is bad. Oauth is really simple:
Lets say you want to use google as an auth provider. You do this:
"Hey google who is this guy? I'm going to send them to google.com/oauth, send them back to example.com/oauth, and in the headers of the request include the word "Authorization: bearer" followed by a bunch of text"
Google says "Oh yeah I know that guy, here I'll send them back to where you said with a token"
Then later on you can take the token and say "Hey google, somebody gave me this token, who is it?"
That's pretty much it. You have to trust that google isn't lying to you, but that's kindof the point of oauth.
But that's never what the documentation says. It's always 10 pages long and the examples are like "here's a fully functioning python web server using flask and function decorators, oh the actual auth flow, which is really like 3 lines of code, is hidden inside of a library".
To people who write documentation: PLEASE for the love of god show me how to talk to your API both using your library, but also using something like urllib2 or requests or something.
Ideally the documentation is the absolute most minimal way of making the service work, and then adds more and more usefulness on top of that. I'm not going to judge you for writing bad code in an example. The example could practically be pseudocode for all I care. I just want to see generally how your API is supposed to work.
edit: yes, auth0, I am looking at you.
thepasswordis, 2 hours ago
Forwarded from HN Best Comments
Re: Linen.dev: A 500 kb Slack alternative
Not enough discussion here of the parts under "Our Optimization Strategies", which was the most interesting to me. Assorted reactions:
> We found that react-icons had an issue that lead to everything being imported. This meant that we were including every single react-icon in our package whether we need it or not.
Kudos to the Linen team for proactively finding this - I have a feeling tons of projects blindly trust that tree-shaking their dependencies will "just work" even though for many libraries it won't!
> We also noticed that we were only using AWS client for s3 upload on the client side and it was taking up significantly more bundle size we need so we replaced the entire client side package with a 2 api calls to the AWS api.
For such a minimal use case, this feels like a logical choice even if it's slightly more work to implement.
> We ended up moving the code highlight code to a backend api that would cache the results.
Love seeing websites make smart choices about which work to handle in the server versus the client.
thex10, 8 hours ago
Not enough discussion here of the parts under "Our Optimization Strategies", which was the most interesting to me. Assorted reactions:
> We found that react-icons had an issue that lead to everything being imported. This meant that we were including every single react-icon in our package whether we need it or not.
Kudos to the Linen team for proactively finding this - I have a feeling tons of projects blindly trust that tree-shaking their dependencies will "just work" even though for many libraries it won't!
> We also noticed that we were only using AWS client for s3 upload on the client side and it was taking up significantly more bundle size we need so we replaced the entire client side package with a 2 api calls to the AWS api.
For such a minimal use case, this feels like a logical choice even if it's slightly more work to implement.
> We ended up moving the code highlight code to a backend api that would cache the results.
Love seeing websites make smart choices about which work to handle in the server versus the client.
thex10, 8 hours ago
Forwarded from Enjoy the Decline
Media is too big
VIEW IN TELEGRAM
𝐄 𝐍 𝐉 𝐎 𝐘 | 𝐓 𝐇 𝐄 | 𝐃 𝐄 𝐂 𝐋 𝐈 𝐍 𝐄
@EnjoyTheD
@EnjoyTheD
Forwarded from HN Best Comments
Re: Ask HN: Most interesting tech you built for just y...
I have a rail line right under my apartment, so I built a small computer vision app running on a Rasperry Pi which records each train passing, and tries to stitch an image of it.
It has a frontend at https://trains.jo-m.ch/.
Edit: it's currently raining and the rain drops are disturbing the images a bit.
jo-m, 3 hours ago
I have a rail line right under my apartment, so I built a small computer vision app running on a Rasperry Pi which records each train passing, and tries to stitch an image of it.
It has a frontend at https://trains.jo-m.ch/.
Edit: it's currently raining and the rain drops are disturbing the images a bit.
jo-m, 3 hours ago
Forwarded from HN Best Comments
Re: Every web search result in Brave Search is now ser...
How is it that Brave managed to build an indexer and remove dependence on Bing in less than two years but DuckDuckGo hasn't been able to do it in a decade.
IceWreck, 21 hours ago
How is it that Brave managed to build an indexer and remove dependence on Bing in less than two years but DuckDuckGo hasn't been able to do it in a decade.
IceWreck, 21 hours ago
Forwarded from HN Best Comments
Re: NASA Power Hack Extends 45-Year Voyager 2 Mission ...
Everything about Voyager is just mind-blowing. These are 45 year old electronic devices, using 70's tech, with zero maintenance, operating 22 light hours away.
At that range they can still send messages detectable on earth. 9 out of 10 instruments are still working. People just leaving school when they launched are already retired.
This is one time when the adage "they don't make them like they used to" is well applied.
Hat tip to all involved.
bruce511, 19 hours ago
Everything about Voyager is just mind-blowing. These are 45 year old electronic devices, using 70's tech, with zero maintenance, operating 22 light hours away.
At that range they can still send messages detectable on earth. 9 out of 10 instruments are still working. People just leaving school when they launched are already retired.
This is one time when the adage "they don't make them like they used to" is well applied.
Hat tip to all involved.
bruce511, 19 hours ago
Forwarded from HN Best Comments
Re: Check if your IKEA chair is compatible with your s...
I once had the problem that running make with too many parallel jobs (-j) would change my keyboard layout.
The machine was some laptop mainboard glued to the backside of my monitor, and the USB socket came out at the top of the mainboard. On its way down, the USB cable for the keyboard passed across the whole mainboard. On high load, the mainboard created enough interference to cause the connection to reset, re-hotplugging my keyboard, so the previous setxkbmap call was not effective anymore and i was back to the standard US qwerty layout.
blueflow, 2 hours ago
I once had the problem that running make with too many parallel jobs (-j) would change my keyboard layout.
The machine was some laptop mainboard glued to the backside of my monitor, and the USB socket came out at the top of the mainboard. On its way down, the USB cable for the keyboard passed across the whole mainboard. On high load, the mainboard created enough interference to cause the connection to reset, re-hotplugging my keyboard, so the previous setxkbmap call was not effective anymore and i was back to the standard US qwerty layout.
blueflow, 2 hours ago
Forwarded from HN Best Comments
Re: Ask HN: Most interesting tech you built for just y...
My grandmother has dementia. About twice a day, she calls my parents every 5 minutes, forgetting that she just hung up. The calls are always the same: "You live there now. Yes you have money. We came to visit you yesterday." This can go on for an hour or so.
My parents are incredibly patient, but after a couple of these calls, they'll just leave the phone to ring. The soundtrack of the phone constantly ringing in the house, and the guilt associated with not picking up, is unbearable.
My brother and I built a system where her calls get re-routed to a rotation of relatives to answer her calls, to spread the load. After a call with her, each person gets a 2 hour break (customizable). If no one is available to answer, or if everyone is on break, she gets a voicemail that my dad recorded that explains that we love her, that she lives there, all the usual stuff.
It's working beautifully.
pigcat, 4 hours ago
My grandmother has dementia. About twice a day, she calls my parents every 5 minutes, forgetting that she just hung up. The calls are always the same: "You live there now. Yes you have money. We came to visit you yesterday." This can go on for an hour or so.
My parents are incredibly patient, but after a couple of these calls, they'll just leave the phone to ring. The soundtrack of the phone constantly ringing in the house, and the guilt associated with not picking up, is unbearable.
My brother and I built a system where her calls get re-routed to a rotation of relatives to answer her calls, to spread the load. After a call with her, each person gets a 2 hour break (customizable). If no one is available to answer, or if everyone is on break, she gets a voicemail that my dad recorded that explains that we love her, that she lives there, all the usual stuff.
It's working beautifully.
pigcat, 4 hours ago
Forwarded from Data is data
Высшая алгебра, смысл жизни и ниндзя. Кино смотрится на одном дыхании. Трезвым смотреть с осторожностью.
https://youtu.be/NgNRRI9s7uk
https://youtu.be/NgNRRI9s7uk
YouTube
Фрагмент лекции Романа Михайлова. Ниндзя
Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.
Forwarded from Jovan.ru
Такое наблюдение — прошлое не такое уж и клевое, как ты его помнишь. А настоящее, если подумать, может и не так уж плохо.
Ну а будущее всегда — серьезно, всегда оказывается лучше, чем ты ожидаешь.
Хороших выходных всем! Я больше не буду звучать как коуч.
Ну а будущее всегда — серьезно, всегда оказывается лучше, чем ты ожидаешь.
Хороших выходных всем! Я больше не буду звучать как коуч.
Forwarded from HN Best Comments
Re: Beautiful branchless binary search
“Those spikes for std::lower_bound are on powers of two, where it is somehow much slower. I looked into it a little bit but can’t come up with an easy explanation. The Clang version has the same spikes even though it compiles to very different assembly.”
I saw this and immediately went “oh, those look like Intel hardware”.
Intel uses 12-bit memory port quick addressing in their hardware, resulting in an issue known as “4K Aliasing”. When addresses are the same modulo 4K, it causes a collision that has to be mitigated by completing the associated prior memory operation to free up the use of the address in the load/store port system, effectively serializing operations and making performance very dependent on the data stride.
I first bumped up against this when running vertical passes of image processing algorithms that got very slow at certain image sizes, a problem that could be avoided by using an oversized buffer and correspondingly oversized per-line “pitch” to diagonally offset aliased addresses (at a small cost to inter-line cache line overlap).
chaboud, 1 day ago
“Those spikes for std::lower_bound are on powers of two, where it is somehow much slower. I looked into it a little bit but can’t come up with an easy explanation. The Clang version has the same spikes even though it compiles to very different assembly.”
I saw this and immediately went “oh, those look like Intel hardware”.
Intel uses 12-bit memory port quick addressing in their hardware, resulting in an issue known as “4K Aliasing”. When addresses are the same modulo 4K, it causes a collision that has to be mitigated by completing the associated prior memory operation to free up the use of the address in the load/store port system, effectively serializing operations and making performance very dependent on the data stride.
I first bumped up against this when running vertical passes of image processing algorithms that got very slow at certain image sizes, a problem that could be avoided by using an oversized buffer and correspondingly oversized per-line “pitch” to diagonally offset aliased addresses (at a small cost to inter-line cache line overlap).
chaboud, 1 day ago
Forwarded from HN Best Comments
Re: Ask HN: Most interesting tech you built for just y...
My townhome complex had one of those call boxes at the front gate. When Doordash/FedEx/the cleaners/the in-laws/etc arrived they would have to call me from the call box and I'd have to answer it and listen to garbled audio to figure out who it was and press 9 to open the gate. It was kind of a pain, so I made a Twilio app to answer calls from the call box.
I set up custom entry codes that I could hand out to anyone. Everyone got their own code, and it would text me whenever someone used a code so I'd instantly know who was coming. The text conversation was my timestamped access log. I also put time constraints on some codes so e.g. Doordash couldn't open the gate in the middle of the night, or I could set up a temporary access code for a party, and I rotated codes too, with text notifications if an outdated code was used.
I thought about making a paid app out of it, but it just didn't seem worthwhile. I didn't expect that many people would want to pay for it. For a while I was excited about a YC startup called Doorport that was going to make a hardware device that you'd install inside those dumb call boxes and make them smart with all sorts of cool features, better than my Twilio hack. But I think they pivoted to a much less interesting pure software thing and then got acquihired.
modeless, 1 day ago
My townhome complex had one of those call boxes at the front gate. When Doordash/FedEx/the cleaners/the in-laws/etc arrived they would have to call me from the call box and I'd have to answer it and listen to garbled audio to figure out who it was and press 9 to open the gate. It was kind of a pain, so I made a Twilio app to answer calls from the call box.
I set up custom entry codes that I could hand out to anyone. Everyone got their own code, and it would text me whenever someone used a code so I'd instantly know who was coming. The text conversation was my timestamped access log. I also put time constraints on some codes so e.g. Doordash couldn't open the gate in the middle of the night, or I could set up a temporary access code for a party, and I rotated codes too, with text notifications if an outdated code was used.
I thought about making a paid app out of it, but it just didn't seem worthwhile. I didn't expect that many people would want to pay for it. For a while I was excited about a YC startup called Doorport that was going to make a hardware device that you'd install inside those dumb call boxes and make them smart with all sorts of cool features, better than my Twilio hack. But I think they pivoted to a much less interesting pure software thing and then got acquihired.
modeless, 1 day ago