What is Hackers' Pub?

​​

んー、どこもいっぱいだな

[This is a test of the new @bsky.brid.gyBridgy Fed for Bluesky markdown parser] this is only a test! #hashtags are [possible?] Maybe @wake.stwakest 🏴‍☠️

かぼぷ氏→かぼちゃん
たも2氏→たもちゃん

あと普通にバックエンド側の読み込み処理に間違いがあったのでそれを修正しつつ、持つデータ量を最低限に抑えてバックエンドのメモリ使用量も削減した

RE: https://misskey.io/notes/ak0nudolvmea08xb

A few of the things I've learned in the run up to taping out our first chip that working with FPGAs had not prepared me for (fortunately, the folks driving the tape out had done this before and were not surprised):

• There's a lot of analogue stuff on a chip. Voltage regulators, PLLs, and so on all need to be custom designed for each process. They are expensive to license because they're difficult to design and there are only a handful of companies buying them. The really big companies will design their own in house, but everyone else needs to buy them. The problem is that 'everyone else' is not actually many people.
• Design verification (DV) is a massive part of the total cost. This needs people who think about the corner cases in designs. The industry rule of thumb is that you need 2-3 DV engineers per RTL engineer to make sure that the thing that you tape out is probably correct. In an FPGA, you can just fix a bug and roll a new bitfile, but with custom chip you have a long turnaround to fix a bug and a lot of costs. This applies at the block level and at the system level. Things like ISA test suites are a tiny part of this because they're not adversarial. To verify a core, you need to understand the microarchitecture-specific corner cases where things might go wrong and then make sure testing covers them. We aren't using CVA6, but I was talking to someone working on it recently and they had a fun case that DV had missed: If a jump target spanned a page boundary, and one of those pages was not mapped, rather than raising a page fault the core would just fill in 16 random bits and execute a random instruction. ISA tests typically won't cover this, a good DV team would know that anything spanning pages in all possible configurations of permission and presence (and at all points in speculative execution) is essential for functional coverage.
• Most of the tools for the backend are proprietary (and expensive, and with per-seat, per-year licenses). This includes tools for formal verification. There are open-source tools for the formal verification, the proprietary ones are mostly better in their error reporting (if the checks pass, they're fine. If they don't, debugging them is much harder).
• A lot of the vendors with bits of IP that you need are really paranoid about it leaking. If you're lucky, you'll end up with things that you can access only from a tightly locked-down chamber system. If not, you'll get a simulator and a basic floorplan and the integration happens later.
• The back-end layout takes a long time. For FPGAs, you write RTL and you're done. The thing you send to the fab is basically a 3D drawing of what to etch on the chip. The flow from the RTL to the 3D picture is complex and time consuming.
  
• On newer processes, you end up with a load of places where you need to make tradeoffs. SRAM isn't just SRAM, there are a bunch of different options with different performance, different leakage current, and so on. These aren't small differences. On 22fdx, the ultra-low-leakage SRAM has 10% of the idle power of the normal one, but is bigger and slower. And this is entirely process dependent and will change if you move to a new one.
• A load of things (especially various kinds of non-volatile memory) use additional layers. For small volumes, you put your chip on a wafer with other people's chips. This is nice, but it means that not every kind of layer happens on every run, which restricts your availability.
• I already knew this from previous projects, but it's worth repeating: The core is the easy bit. There are loads of other places where you can gain or lose 10% performance depending on design decisions (and these add up really quickly), or where you can accidentally undermine security. The jump from 'we have RTL for a core' to 'we have a working SoC taped out' is smaller than going to that point from a standing start, but it's not much smaller. But don't think 'yay, we have open-source RTL for a RISC-V core!' means 'we can make RISC-V chips easily!'.
• I really, really, really disapprove of physics. It's just not a good building block for stuff. Digital logic is so much nicer.

Help move the Linux application ecosystem forward!

The Call for Volunteers for Linux App Summit 2026 is now open.

Sign up and help make this year’s summit happen.

For more information and registration, contact us at: info@linuxappsummit.org

#Linux #OpenSource #Apps #KDE #GNOME

あと配信者、なんだかんだ自分のこと一番好きだと思う
じゃないとやらないよこんな…人前でちやほやされること…😉

？

ﾌﾟｨｻﾞか……

same, Hulk, same

​​​​

うーん、飲みにでるか、家でゆるっとするか……ごはんどうしよ……

Czech Man's Stone in Barn's Foundations Is Rare Bronze Age Spearhead Mold

Link: https://www.smithsonianmag.com/smart-news/a-czech-man-used-this-stone-in-his-barns-foundations-it-turned-out-to-be-rare-bronze-age-spearhead-mold-180988339/
Discussion: https://news.ycombinator.com/item?id=47397862

與其讓黨控制，不如交給機器人，這也是一種虛無或豁達。（遠目）

與其讓黨控制，不如交給機器人，這也是一種虛無或豁達。（遠目）

名古屋は栄以外はど真ん中ではありません

1/

AFAIK, there isn't a way for an ActivityPub Actor (such as a Person actor) to specify a list of Service actors associated with it.

...

For example, imagine that there is a Service actor that represents a way to make a video call to me.

And, for example, I have my Mastodon Person actor.

And, I want to let people know about it (and other Service actors associated with me).

How do I do that using AP, etc?

...

#ActivityPub #ActivityStreams #AudioCall #Call #FediDev #Fediverse #VideoCall

瀬谷市

瀬谷はほら…一応、ね……
許してあげてほしい

ワイが​​民を名乗るのは、大和市民や綾瀬市民がハマっ子を自称するような違和感

ぼぷちゃん便を特定する遊び

ハァ…ハァ…お祝いのコメントようやく全部お返事できたかな…？！？！みんな本当にありがとう…！！！漏れがあったらほんっっっとごめん！！！

高松より実は人口が多いのに交通の便の悪さ諸々で損している松山さん……

下ネタ嫌いです。やめてください。

やっと買い物に行ける・・・

Just had to add a workaround to #Fedify for http://joinmastodon.org/ns, a JSON-LD context URL that has never actually served a JSON-LD document. Mastodon has always inlined the term definitions, but some implementations put it as a bare URL in their @context, so Fedify's JSON-LD processor tries to fetch it and gets a 404 Not Found. Now Fedify ships a bundled copy of a context that never existed in the first place.

https://github.com/fedify-dev/fedify/pull/631

#fedidev #ActivityPub #JSONLD

酒を求めてふらつくか…

帰りに軽く写真を撮ってきました​​
なんかいい感じに写るので、撮るのがすごく楽しいカメラです​​
#misskey写真部 #x100vi #fujifilm

​​なのだけど​​民を自称するのは憚られるわね…​​

AIじゃないよ
写真だよ

Why subscriptions? A one-time purchase revenue graph, even for a moderately successful app, looks like this. Yet work required only increases in complexity — Pastel has had 40 multiplatform updates since it launched in 2020, including two system UI redesigns, and a whole new OS (visionOS).

One-time purchases just aren't sustainable, unless the product itself is also one-and-done — and that's just not possible on a moving target like Apple's OSes. Revenue can't be inversely proportional to time

​​​​​​来た

SPARTANS IN SPEEDOS & THE STAGED BEACH - my latest podcast on YouTube, a deep dive into art history, comparing the work of Charles Meere, Max Dupain and Frederick McCubbin with that of Anne Zahalka.

You can listen to it (and watch) here:

https://youtu.be/cI74D2jOP3Q

Please subscribe, like, comment.

#AnneZahalka #art #ArtHistory #Australia #beach #Bondi #identity #satire #CharlesMeere #MaxDupain #FrederickMcCubbin

​​

We are pleased to announce the release of GNOME 50! You can read about what our contributors have been working on at https://release.gnome.org/50

We’d like to use this new release as an opportunity to thank all of the contributors who made it happen. ❤️

Let us know what you think!

#GNOME #OpenSource #FLOSS #FOSS #Linux

Warranty Void If Regenerated https://lobste.rs/s/q01yur #vibecoding
https://nearzero.software/p/warranty-void-if-regenerated

あたまよくなりたい

that's right, it goes in the ~/Downloads folder

四国の玄関と勝手口の差（失礼）

RE: https://misskey.io/notes/ak0wig8tt7wf0cjf

🍝 친구 여러분, 우리는 날아다니는 스파게티 괴물 님께서 주신 이 날의 끝맺음에 와 있으니 겸손하게 우리 죄를 반성합시다.

"14. 오늘 하루 주신 기회와 사람들과의 만남에 감사드리며, 모든 것이 은총이었음을 고백합니다."

😋 전능하신 스파게티 괴물과 친구들에게 고백하오니 생각과 말과 행위로 죄를 많이 지었으며 자주 의무를 소홀히 하였나이다.
제 탓이요. 제 탓이요. 저의 큰 탓이옵니다.
우리 죄를 용서하시고, 주님 안에서 새로워지게 하소서.
라-멘 🍜

🍝 전능하시고 자비로우신 주님, 날아다니는 스파게티 괴물 님,
당신의 모든 죄를 용서하시고 사면하시며, 진정한 회개와 삶의 교정을 허락하시고, 당신 성면(the Holy Noodle)의 은총과 위로를 베푸소서.
라-멘 🍜

2026-03-19T19:38:58+09:00

#FlyingSpaghettiMonster #FSM #HolyNoodle #TheMeatball #TheSauce #Spaghetti #Ramen #Pastafarian #NoodlyAppendage #FSMism #FSMist #Pirate #DivineOffice #DailyOffice #Breviary
#날아다니는스파게티괴물님 #성면 #면발 #스파게티 #라멘 #파스타파리안 #해적 #성무일도 #성무일과 #매일전례 #시간전례

Please show me the ugliest picture of your cat , l want a good laugh 😹😹.
#cats #CatsOfMastodon #caturday #photography #photo