What is Hackers' Pub?

오늘 진심 레전드로 졸려서 에너지드링크를 깠다

Tool:PaintBBS NEO
哀れみの目をしている努力。
#Misskey専用お絵かき掲示板
https://paintbbs.sakura.ne.jp/misskey/

아까 엑스에서 본 트젠 관련한 기사인데 이 부분 정말 전국에 있는 전광판에 띄워두고 사람들 강제로 보게 만들고 싶더라

一个四川的博主拍了自己村子里的长辈说方言的搞笑视频，有人在评论区留言问他们怎么做到每一句话都押韵？四川人在底下答复说老辈子骨子里带的，上过学的年轻人反而说不出来了。参与N学姐的语音学实验的时候，我很好奇为什么在问卷里会设置除了普通话外的方言（母语）选项，她告诉我们口腔肌肉记忆存储的第一门语言事实上才是我们的母语，毕竟我们并不是一生下来就学习了普通话不是吗？打脑壳有一期讲严歌苓提到她曾经写过一本带四川方言（事实上是成都话）的小说，嘉宾说新生代粤语文学有林棹的潮汐图，而我们的方言文学早已断代。那天在德铁上刷到YAng这个博主的贴子，读到怔忡，明明在质硬的高地德语包围之中，沱江却倏忽流过眼前。我想起来我妈在我十多岁时仍然抱有写日记和随笔的习惯，当然她没上过什么学，不会漂亮的字句和文法，她写的实际也就是她在生活中说的话，但那事实上是我第一次接触到的所谓方言文学。十来岁的某个下午，我偷偷翻开她的日记本，看到她写自己到菜市场买春颠菜，说春颠这个词就是在讲春天冰融化时候最顶端滴下来的一点绿，又写晚饭做春颠炒鸡蛋、蒸河鱼和白砂糖沾番茄。她的字词让我心里轰然地自卑、震撼和羞愧，这不是我在课堂上、书籍里读到的任何一种语言，我早就习惯于一种集体化的、宏大的、政治的符号系统，这种表达是如此陌生，却又像泥土、田埂、南河的水声一样熟悉。我第一次意识到自己一直在使用一种被驯化过的语言，这些成群的宏大的符号将我和本该属于我的真实生活体验隔离。所谓真正的母语，早已在我身体里亡佚。

다들힘내....

입시이야기가 시작되면 다들 튀어나오는것은 다들 어느정도의 차이는 있지만 트라우마가 생겼기 때문인듯 저도 방황 참 오래해서 ㅋㅋㅋ
이제그만이야기함 입시보다 내취업이 더 중요하다........

잠온다

아까 엑스에서 본 트젠 관련한 기사인데 이 부분 정말 전국에 있는 전광판에 띄워두고 사람들 강제로 보게 만들고 싶더라

강남에 원전!!!

食べながらZedについて調べてたけどいいなこれ
VSCodeゴミだわw

넘졸려..데박...죽는다..

應該暫時不用買卡
真的不夠砍了再裝就好了

トイレに行ってたせいで授業開始7分前に食べ終わった

[AWS] Amazon Q Developer CLI를 통한 쉽고 빠른 에이전트 코딩 실습

배우 윤여정이 국외 언론과의 인터뷰에서 아들이 동성애자임을 공개한 가운데, 나종호 미국 예일대 의과대학 정신의학과 조교수가 “경의를 표한다”고 밝혔습니다. 보수적인 한국 사회에서 성소수자 부모의 ‘커밍아웃’이 결코 쉽지 않음을 언급하면서입니다.

윤여정 ‘성소수자 부모’ 커밍아웃에 예일대 의대 교수 ...

アメリカ湾とかフリーダムフライとかmainブランチとかやめとこうよう

Job Interviewer: Why are you interested in this role?

Me: I heard you have legacy code. I consider myself a digital archaeologist. I love digging through ancient ruins and wondering 'What were they even thinking?' In the current economic climate it's job security!

おさむストレージインフォ

평가시스템이 공정하다 공정하지 않다를 논하기에는 어떠한 평가 시스템도 결국 권력자/기득권자의 필요에 자신을 얼마나 잘 맞출 수 있느냐의 문제이기 때문에 의미가 없음 답은 자본주의를 메우고 피냐타 경제를 실현하는 것 밖에 없다~~

농담하는 거 아님 진심임~~

そんなことあるんだ

塩辛ペペロンチーノ食べたい

枝豆のプランターに1つだけ伸びてるものが違うやつがいて、さすがに抜いてみたら、枝豆の根が土から生えていて、そんな逆さになることあるんだ…になった。姿勢を変えてやってみたけどどうだか…

이것으로 BotKit 0.2.0에 넣으려고 생각했던 기능은 다 추가했다. 이대로 0.2.0 출시하면 되려나? 뭔가 놓친 게 없으려나? 🤔

"내가 버튜버가 되면... 자본주의를 메워야 같은 소리 맨날 하다가 /논란 항목 생기고 매장당하지 않을까?" 같은 소리를 어제 했는데
다른 분이
"걍 페미라는거 하나만으로도 이미 끝 아님?" 라고 하셔서 아맞내 상태가 되었음

Coming soon in #BotKit 0.2.0: Native #quote post support!

We're excited to share a preview of the upcoming quoting features in BotKit 0.2.0. This update will make it easier for your bots to engage with quoted content across the fediverse.

The quoting feature set includes:

• Detecting when someone quotes your bot's posts with the new Bot.onQuote event handler
• Accessing quoted content through the Message.quoteTarget property
• Creating quote posts using the quoteTarget option in Session.publish() and Message.reply() methods

Here's a quick example of how you can use the quote detection:

bot.onQuote = async (session, quote) => {
  // The quote parameter is a Message object representing the post that quoted your bot
  await quote.reply(text`Thanks for quoting my post, ${quote.actor}!`);
  
  // You can access the original quoted message
  const originalPost = quote.quoteTarget;
  console.log(`Original message: ${originalPost?.text}`);
};

And creating quote posts is just as simple:

// Quote in a new post
await session.publish(
  text`I'm quoting this interesting message!`,
  { quoteTarget: someMessage }
);

// Or quote in a reply
await message.reply(
  text`Interesting point! I'm quoting another relevant post here.`,
  { quoteTarget: anotherMessage }
);

Remember that quoting behavior may vary across different #ActivityPub implementations—some platforms like Misskey display quotes prominently, while others like Mastodon might implement them differently.

Want to try these features right now? You can install the development version from JSR:

deno add jsr:@fedify/botkit@0.2.0-dev.90+d6ab4bdc

We're looking forward to seeing how you use these quoting capabilities in your bots!

#fedidev

Coming soon in #BotKit 0.2.0: Native #quote post support!

We're excited to share a preview of the upcoming quoting features in BotKit 0.2.0. This update will make it easier for your bots to engage with quoted content across the fediverse.

The quoting feature set includes:

• Detecting when someone quotes your bot's posts with the new Bot.onQuote event handler
• Accessing quoted content through the Message.quoteTarget property
• Creating quote posts using the quoteTarget option in Session.publish() and Message.reply() methods

Here's a quick example of how you can use the quote detection:

bot.onQuote = async (session, quote) => {
  // The quote parameter is a Message object representing the post that quoted your bot
  await quote.reply(text`Thanks for quoting my post, ${quote.actor}!`);
  
  // You can access the original quoted message
  const originalPost = quote.quoteTarget;
  console.log(`Original message: ${originalPost?.text}`);
};

And creating quote posts is just as simple:

// Quote in a new post
await session.publish(
  text`I'm quoting this interesting message!`,
  { quoteTarget: someMessage }
);

// Or quote in a reply
await message.reply(
  text`Interesting point! I'm quoting another relevant post here.`,
  { quoteTarget: anotherMessage }
);

Remember that quoting behavior may vary across different #ActivityPub implementations—some platforms like Misskey display quotes prominently, while others like Mastodon might implement them differently.

Want to try these features right now? You can install the development version from JSR:

deno add jsr:@fedify/botkit@0.2.0-dev.90+d6ab4bdc

We're looking forward to seeing how you use these quoting capabilities in your bots!

#fedidev

ぶっちゃけ日本でも美味しいインドカレーは食べれるところ色々あるから、どうせなら聞いたこともないようなものを食べたい

자본주의를 메워야~~

Coming soon in #BotKit 0.2.0: Native #quote post support!

We're excited to share a preview of the upcoming quoting features in BotKit 0.2.0. This update will make it easier for your bots to engage with quoted content across the fediverse.

The quoting feature set includes:

• Detecting when someone quotes your bot's posts with the new Bot.onQuote event handler
• Accessing quoted content through the Message.quoteTarget property
• Creating quote posts using the quoteTarget option in Session.publish() and Message.reply() methods

Here's a quick example of how you can use the quote detection:

bot.onQuote = async (session, quote) => {
  // The quote parameter is a Message object representing the post that quoted your bot
  await quote.reply(text`Thanks for quoting my post, ${quote.actor}!`);
  
  // You can access the original quoted message
  const originalPost = quote.quoteTarget;
  console.log(`Original message: ${originalPost?.text}`);
};

And creating quote posts is just as simple:

// Quote in a new post
await session.publish(
  text`I'm quoting this interesting message!`,
  { quoteTarget: someMessage }
);

// Or quote in a reply
await message.reply(
  text`Interesting point! I'm quoting another relevant post here.`,
  { quoteTarget: anotherMessage }
);

Remember that quoting behavior may vary across different #ActivityPub implementations—some platforms like Misskey display quotes prominently, while others like Mastodon might implement them differently.

Want to try these features right now? You can install the development version from JSR:

deno add jsr:@fedify/botkit@0.2.0-dev.90+d6ab4bdc

We're looking forward to seeing how you use these quoting capabilities in your bots!

#fedidev

Zed、Rust製かつRustはネイティブ対応していて、Biomeもアドオンがあるのでこれでも困らなさそう

오늘은 수능 플로우야? 수능에 순응하라~~ (아님)

​​
#Misskey専用お絵かき掲示板
https://paintbbs.sakura.ne.jp/misskey/

크아아악 졸려

어허, 꼬리 치는게 예사롭지 않네요. 홀리겠는데요.

カナディアーノという呼び方もあるね

@Linza @cstrossCharlie Stross of course, even more expensive.

腹が痛くなったのでトイレにこもってました

JRE経済圏を大きくしたいんだろうなってのは伝わった

JR東日本は最近銀行も始めたしね

ドンキもMVNO始めたし有り得る

とち狂ったJR東

JR EAST mobile(MVNO)を提供します

とち狂ったJR東

JR EAST mobile(MVNO)を提供します

Zed良さそうだな
VSCodeから乗り換えてみようかな

あのハンドルネームを放送すると揉めそうだから「佐藤さん(仮名)」なのかな。やっぱり。
放送禁止用語とか恥ずかしすぎて放送出来ない単語をハンドルネームにするのも考えものだよな。

사람이 지하철을 탄다는데 이걸 왜 막냐고... 지하철 타도 되는 사람 안 되는 사람이 왜 정해져 있어요?

우리동네도 플랜카드키배 생김

not my story from reddit:

Please be careful - we were deported from the U.S. for just wanting to backpack

I want to share what happened to me and my best friend last month when we tried to begin our backpacking trip in the U.S. Maybe it helps someone avoid the same nightmare.

We are 19 and 18 years old, from Europe, and we arrived in Honolulu from New Zealand, with the plan to explore the islands first, and then fly to the mainland after to explore California. We had booked only the first 2 nights in an Airbnb, just to be flexible with our plans - like we did in New Zealand, and like many backpackers do. We had the onward ticket to the next destination in Asia but didn't book domestic flights in the U.S. for the same reason.

At passport control they took us aside for “additional questions.” At first we didn’t think it was such a big thing, but then it became very intense. They were asking us why we didn’t book more nights or domestic flights, what our plans were, how we can afford to travel, and especially about work. We do sometimes small freelance jobs online (like translating or design stuff, for customers back in Germany and sometimes also Asia, not the U.S.), and we mentioned that - which was maybe the biggest mistake. It was also in the e-mails that they accessed.

After a while they told us we are not allowed to enter the U.S., that we are “inadmissible.” They said we were trying to work illegally, which we didn’t. We had onwards tickets and just wanted to travel.

But they didn’t care. They took our phones, our passports, and put us in handcuffs - that moment was surreal. Like, you’re a tourist and now you’re treated like criminal. They wanted to send us back to Auckland on the next flight, but we asked to rebook our onwards tickets for the day after, so we could continue with our travels. They agreed but said that we will be detained for the night. We agreed, having no idea what to expect, thinking that we would maybe wait in the same room that they interviewed us. But no.

They drove us to the detention center in Honolulu. I think it was called FDC prison, close to the airport. It was a real jail. Metal doors, locked cells, cold air. And they made us do a full strip search. It was really cold. We had to undress completely, including bra and underwear, and even had to squat and spread… I don’t want to describe it in too much detail, but it was humiliating and scary. We were alone with a female officer, but still… you don’t expect that as a tourist.

After that they gave us green prison clothes and put us in a cell overnight with two other women - who were actually bragging to us about their cartel connections and implying that they were serious criminals. It felt like a movie, but not a nice one. Of course we didn't not sleep even for a minute. I'm not picky, but the food was another horror story.

The next day they stripped us down again, we changed back into our clothes, and they took us straight to our plane - two officers returned our passports and escorted us to our seats as the door was about to close. Just like that. They also told us that if we want to come to the U.S. again, we cannot use a visa free system anymore.

So yeah… please be very careful if you plan to backpack in the U.S. Book all your accommodation in advance (even if you plan to change later). There are many fully refundable options - and we thought about it, but decided that it wouldn't be necessary. And don’t mention any remote work or freelancing and make sure to log out of any e-mails that could be used as evidence of it. And know that if something goes wrong, it’s not just “denied entry” - it’s jail, strip search, and total loss of control.

We are still totally shaken from it and feel like we did something wrong, even if we didn’t mean to. Just wanted to share, because I would have never imagined this could happen. My feeling is that backpacking culture isn’t understood or accepted at U.S. borders right now. Be careful!

https://www.reddit.com/r/backpacking/comments/1k2obaf/please_be_careful_we_were_deported_from_the_us/

Proton이 DirectX의 Clean Room 구현이지만, 미 연방대법원 Oracle v. Google 판결에 해당, 즉 공정 이용에 바로 해당한다고 보기는 어려움. 구현 자체는 reverse engineering여도 DX API의 structure, sequence, and organization (SSO)을 걸면 매우 긴 법정 다툼이 벌어질 것.

MS는 사실상 언제든지 Proton을 죽일 수 있음. 지금으로서는 그럴 필요가 없을 뿐이지.

https://news.hada.io/topic?id=20425

리눅스 게이밍의 기술적 기반은 굉장히 튼실해졌지만, 그 핵심이 호환성 레이어인 Proton인 이상 기술자의 흥미거리 이상은 어려움. 스팀덱은 흥미로운 니치 마켓 머신이지만 그게 잘 팔리면 나올 XBOX Portable보다 더 나은 시스템은 아님.

MS가 저작권 공격을 하지 않더라도 개발사는 호환 제품들을 방해하는 많은 방법들이 있음. MS가 굳이 그럴 이유가 없다 할지라도, 스팀이 게임 개발자들에의 영향력으로 MS를 견제할 수 있다 하더라도, 호환성 제품이 규모와 기술력에서 세계 최고를 다투는 오리지널 벤더의 제품보다 낫기는 어려움. 더 가볍고 특정 시나리오에서는 우위에 있을 수도 있겠지만 일반 유저용은 아님.

리눅스 게이밍이 대안은 될지언정 윈도를 대체할 수는 없음. OS/2가 Win32 API 실행에서 당시 윈도보다 나았지만 그렇다고 OS/2가 시장에서 살아남지는 못했음.

🍑
#Misskey専用お絵かき掲示板
https://paintbbs.sakura.ne.jp/misskey/