Hackers' Pub is a place for software engineers to share their knowledge and experience with each other. It's also an ActivityPub-enabled social network, so you can follow your favorite hackers in the fediverse and get their latest posts in your feed.
What makes Bluesky different: it’s open source, so anyone can contribute to building the experience they want. And even if you build a whole new app, the protocol means you can migrate with your data, identity, and relationships intact.
Hot take: free and open source is fundamentally incompatible with strong security *guarantees*, because FOSS is incompatible with strong guarantees about anything. It says so right there on the tin: "without warranty of any kind, either expressed or implied". We guarantee nothing by default, you get the code, the project, everything, as-is, where-is, how-is.
Of course companies find this inconvenient, especially with the EU CRA looming, but that's not FOSS's problem. That's a you problem.
enshittification, die: Qualifizierte und teure EntwicklerInnen durch "vibe coder" ersetzen und dann zusätzlich billige "Vibe Coding Cleanup Specialists" einstellen. #Lohndumping#enshittification
Mesa is working to update our contributor guide. Can you guess why?
Did you guess AI?
Because if you did, you'd be right. I don't want to put anyone on blast here so please don't go digging to find the motivating MR and harass the contributor or anything like that.
But the situation was exactly what you might think. Someone ran ChatGPT on the code and asked it for suggestions on making it more performant. They applied a bunch of the changes against their local branch, tested it, and found that it gave maybe a 0.5-1.0% perf boost in some titles.
That's totally fine. I don't care what tools you use to find a bottleneck. I'll happily take more FPS, no matter who found the issue or how. If some AI assistant helps you find things no one else has found and lets us make drivers faster, great!
But that's not what happened.
What happened next is that they then tried to make it the Mesa project maintainers' job to sort through the shit ChatGPT spit out and decide what's useful and what's not and why the changes helped and whether or not they were correct. The contributor had no no idea and, more importantly, they had no desire to actually learn about the Mesa code-base or the hardware in question. They just wanted to run ChatGPT and send its suggestions towards upstream.
This is not useful. This is not contributing. It's just burning maintainer time sorting through AI hallucinations. We have enough mediocre code to review that comes from actual humans who are actually trying to learn about Mesa and help out. We don't need to add AI shit to the merge request pile. If you don't understand the patch well enough to be able to describe what it does and why it makes things faster, don't submit it.
So now we're making it really clear: If you submit the merge request, you're responsible for the code change as if you typed it yourself. You don't get to claim ignorance and "because the AI said so". It's your responsibility to do due diligence to make sure it's correct and to accurately describe the change in the commit message.
Some things shouldn't have to be explicitly written down but here we are... 😩
Hey there, internet friends. I feel like I make this request maybe once or twice a year, and I know that I generally come up with zilch... but here I go again: do I know *anybody* in New York City with a guest room who likes me enough to host me for a day or two? 😏🤞
It's not that I can't afford a hotel room when I travel. I generally can. But NYC seems uniquely positioned in the world of travel logistics in the sense that you all do not have your garden variety Courtyard Marriott or Doubletree Hilton for around $250/night...
In NYC, travelers seem to be presented with only three choices:
1. the most posh hotel you've ever heard of, for $1000/night at minimum
2. quirky boutique hotel with a 13 sq ft room, for $300/night (no rooms available)
3. battered and firebombed hostel with bunk beds bought at a Dresden fire sale, for $39/night (bag theft included for free)
... I'm just a guy trying to come into town for a weekend to see a play, hah. (And while I appreciate couch offers, I'm over 40 and no longer really do that, please forgive me for being posh)
Interesting essay parsing the difference between blogs and newsletters, and how their delivery mechanisms influence their content and style: https://buttondown.com/blog/blog-vs-newsletter
패션은 잘 모르지만 오파상(...)으로써 귀동냥한 것 중 가장 호응이 좋았던 것은. 청바지는 🇯🇵의 에비스/모모타로/에드윈. 스트릿과 아메카지(아메리칸 캐쥬얼)은 캐피탈/니들스/(좀 더 어른들은)빔스 조금 더 일반적으로 가면 꼼데가르송/휴먼 메이드 여기서 한 단계 더 올라가면 요지 야마모토의 Ground Y 좀 더 스트릿으로 가면 BAPE 아..아닙니다.
Huh, spam from 1Password offering me “Early access to Comet, the new AI browser from Perplexity”. I’m perplexed all right, about why 1Password, an outfit I mostly like, is doing this. I want a serious relationship with my security-technology providers, not a spammy one that flirts with sketchy totally-unrelated products.
Huh, spam from 1Password offering me “Early access to Comet, the new AI browser from Perplexity”. I’m perplexed all right, about why 1Password, an outfit I mostly like, is doing this. I want a serious relationship with my security-technology providers, not a spammy one that flirts with sketchy totally-unrelated products.
Alright, buckle up internet history fans: we've come to the RSS Format Wars! The year 2000 was when RSS got forked into 2 different protocols: Dave Winer's RSS 0.92 and the RDF-based RSS 1.0. What's remarkable, looking back, is that the top bloggers of the day — Kottke, CamWorld, Rebecca Blood, Brad Graham, and others — still weren't using RSS by the end of that year. But they *were* building blogrolls. https://cybercultural.com/p/blogs-rss-2000/#InternetHistory#RSS
Předvolební debatu na téma justice můžete sledovat již dnes na ČT24. ℹ️ Diskutovat přijdou zástupci osmi stran a hnutí kandidujících do Poslanecké sněmovny, které mají podle průzkumu volebního potenciálu agentur Kantar CZ a Data Collect největší šanci uspět. 🕗 Začínáme vždy po osmé hodině večer.