Searching We Love Privacy Club

Twts matching #4:
Sort by: Newest, Oldest, Most Relevant
movq
www.uninformativ.de
 (1y ago)
↳ In-reply-to » Xfce does one thing very right: It stores its settings in plain-text XML files. This allows me to easily read, track, and maybe even distribute these settings to other machines.

@lyse@lyse.isobeef.org @kat@yarn.girlonthemoon.xyz I spent so much time in the past figuring out if something is a dict or a list in YAML, for example.

What are the types in this example?

items:
- part_no:   A4786
  descrip:   Water Bucket (Filled)
  price:     1.47
  quantity:  4
- part_no:   E1628
  descrip:   High Heeled "Ruby" Slippers
  size:      8
  price:     133.7
  quantity:  1

items is a dict containing … a list of two other dicts? Right?

It is quite hard for me to grasp the structure of YAML docs. 😢

The big advantage of YAML (and JSON and TOML) is that it’s much easier to write code for those formats, than it is with XML. json.loads() and you’re done.

⤋ Read More
yue-fang-readfog
feeds.twtxt.net
 (1y ago)

一文搞懂大模型的數據集 FineWeb：讓 AI 更聰明的 15 萬億字數據集
你有沒有想過，爲什麼有些 AI 回答問題時邏輯清晰、知識淵博，而有些卻答非所問、胡說八道？關鍵就在於它們 “喫” 了什麼樣的數據。就像人類的成長需要優質教育一樣，AI 的訓練也離不開高質量的數據。但在 AI 領域，一直存在一個尷尬的現狀：那些表現最好的 AI 模型，比如 GPT-4、Claude 等，它們的訓練數據都是商業機密，普通研究者和小公司根本接觸不到。這就像最好的學校不對外開放，只有少數人 ⌘ Read more

⤋ Read More
yue-fang-readfog
feeds.twtxt.net
 (1y ago)

智能體間協作的 “巴別塔困境” 如何破解？解讀 Agent 通信 4 大協議：MCP-ACP-A2A-ANP
AI 智能體的興起觸發了 AI 應用協作的新領域。這些智能體不再侷限於被動的聊天機器人或獨立的系統，它們現在被設計用於推理、計劃和協作ーー跨任務、跨域甚至跨組織。但隨着這一願景成爲現實，一個挑戰很快浮出水面： 智能體如何以一種安全、可伸縮和可互操作的方式可靠地相互交流、共享上下文並共同做出決策？一類新的通信協議應運而生。從模型上下文協議 (MCP) 到 IBM 和思科的智能體通信協議 (ACP) ⌘ Read more

⤋ Read More
movq
www.uninformativ.de
 (1y ago)

The WM_CLASS Property is used on X11 to assign rules to certain windows, e.g. “this is a GIMP window, it should appear on workspace number 16.” It consists of two fields, name and class.

Wayland (or rather, the XDG shell protocol – core Wayland knows nothing about this) only has a single field called app_id.

When you run X11 programs under Wayland, you use XWayland, which is baked into most compositors. Then you have to deal with all three fields.

Some compositors map name to app_id, others map class to app_id, and even others directly expose the original name and class.

Apparently, there is no consensus.

⤋ Read More
lyse
lyse.isobeef.org
 (1y ago)
↳ In-reply-to » This aggressive auto-logout on my bank’s website …

@movq@www.uninformativ.de Yeah, it’s a shitshow. MS overconfirms all my prejudices constantly.

Ignoring e-mail after lunch works great, though. :-)

Our timetracking is offline for over a week because of reasons. The responsible bunglers are falling by the skin of their teeth:

  1. The error message neither includes the timeframe nor a link to an announcement article.
  2. The HTML page needs to download JS in order to display the fucking error message.
  3. Proper HTTP status codes are clearly only for big losers.
  4. Despite being down, heaps of resources are still fetched.

I find it really fascinating how one can screw up on so many levels. This is developed inhouse, I’m just so glad that we’re not a software engineering company. Oh wait. How embarrassing.

⤋ Read More
movq
www.uninformativ.de
 (1y ago)
↳ In-reply-to » The lack of suckless-like simple, hackable software these days is appalling.

@prologic@twtxt.net Yeah, this really could use a proper definition or a “manifest”. 😅 Many of these ideas are not very wide spread. And I haven’t come across similar projects in all these years.

Let’s take the farbfeld image format as an example again. I think this captures the “spirit” quite well, because this isn’t even about code.

This is the entire farbfeld spec:

farbfeld is a lossless image format which is easy to parse, pipe and compress. It has the following format:

╔════════╤═════════════════════════════════════════════════════════╗
║ Bytes  │ Description                                             ║
╠════════╪═════════════════════════════════════════════════════════╣
║ 8      │ "farbfeld" magic value                                  ║
╟────────┼─────────────────────────────────────────────────────────╢
║ 4      │ 32-Bit BE unsigned integer (width)                      ║
╟────────┼─────────────────────────────────────────────────────────╢
║ 4      │ 32-Bit BE unsigned integer (height)                     ║
╟────────┼─────────────────────────────────────────────────────────╢
║ [2222] │ 4x16-Bit BE unsigned integers [RGBA] / pixel, row-major ║
╚════════╧═════════════════════════════════════════════════════════╝

The RGB-data should be sRGB for best interoperability and not alpha-premultiplied.

(Now, I don’t know if your screen reader can work with this. Let me know if it doesn’t.)

I think these are some of the properties worth mentioning:

  • The spec is extremely short. You can read this in under a minute and fully understand it. That alone is gold.
  • There are no “knobs”: It’s just a single version, it’s not like there’s also an 8-bit color depth version and one for 16-bit and one for extra large images and one that supports layers and so on. This makes it much easier to implement a fully compliant program.
  • Despite being so simple, it’s useful. I’ve used it in various programs, like my window manager, my status bars, some toy programs like “tuxeyes” (an Xeyes variant), or Advent of Code.
  • The format does not include compression because it doesn’t need to. Just use something like bzip2 to get file sizes similar to PNG.
  • It doesn’t cover every use case under the sun, but it does cover the most important ones (imho). They have discussed using something other than RGBA and decided it’s not worth the trouble.
  • They refrained from adding extra baggage like metadata. It would have needlessly complicated things.

⤋ Read More
Oatmeal
feeds.twtxt.net
 (1y ago)

** Om nom nom LLMs, in which I respond to Simon Willison’s analogy **
I am hesitant to wade into the tumultuous waters that are the discourse around generative AI and LLMs, but this morning I came across a thing that so thoroughly melted my brain I feel uncontrollably compelled to respond.

This morning, at evidently 4:10 AM (no mention of timezone), Simon Willison shared the following blog post, quoted here in full:

Quitting programming as … ⌘ Read more

⤋ Read More
movq
www.uninformativ.de
 (1y ago)

Saw this on Mastodon:

https://racingbunny.com/@mookie/114718466149264471

18 rules of Software Engineering

  1. You will regret complexity when on-call
  2. Stop falling in love with your own code
  3. Everything is a trade-off. There’s no “best” 3. Every line of code you write is a liability 4. Document your decisions and designs
  4. Everyone hates code they didn’t write
  5. Don’t use unnecessary dependencies
  6. Coding standards prevent arguments
  7. Write meaningful commit messages
  8. Don’t ever stop learning new things
  9. Code reviews spread knowledge
  10. Always build for maintainability
  11. Ask for help when you’re stuck
  12. Fix root causes, not symptoms
  13. Software is never completed
  14. Estimates are not promises
  15. Ship early, iterate often
  16. Keep. It. Simple.

Solid list, even though 14 is up for debate in my opinion: Software can be completed. You have a use case / problem, you solve that problem, done. Your software is completed now. There might still be bugs and they should be fixed – but this doesn’t “add” to the program. Don’t use “software is never done” as an excuse to keep adding and adding stuff to your code.

⤋ Read More
prologic
twtxt.net
 (1y ago)
↳ In-reply-to » @bender Both Gopher and Mastodon are a way for me to “babble”. 😅 I basically shut down Gopher in favor of Mastodon/Fedi last year. But the Fediverse doesn’t really work for me. It’s too focused on people (I prefer topics) and I dislike the addictive nature of likes and boosts (I’m not disciplined enough to ignore them). Self-hosting some Fedi thing is also out of the question (the minimalistic daemons don’t really support following hashtags, which is a must-have for me).

@movq@www.uninformativ.de Me too 😅 – Speaking of which i know you’ve lost a bit of “mojo” or “energy” (so have i of late), rest assured, I want to keep the status quo here with what we’ve built, keep it simple and change very little. What we’ve built has worked very well for 5+ years and we have at least 3 very strong clients (maybe 4 or 5?).

⤋ Read More
yue-fang-readfog
feeds.twtxt.net
 (1y ago)

萬字總結 NIO 多路複用技術，深入解析 NIO 的實現原理！
什麼是 NIO NIO 是 Java 提供的一種基於 Channel 和 Buffer 的 IO 操作方式，即：利用內存映射文件方式處理輸入和輸出。NIO 具有更加強大和靈活的 IO 操作能力，提供了非阻塞 IO、多路複用等特性，特別適合需要處理大量連接的網絡編程場景在 JDK1.4 時提出了 NIO(New I/O)，在 BIO 模型 (Blocking IO) 的基礎上，增加了 NIO 模型 ⌘ Read more

⤋ Read More
Oatmeal
feeds.twtxt.net
 (1y ago)

** Stinky **
This morning I set up our new composter. This entailed shoveling a lot of compost from the old one into the new so that it can actually finish cooking. Shoveling 4 years worth of mostly kitchen scrap compost is a very very stinky endeavor. Despite wearing gloves I don’t know if my hands will ever not smell again. ⌘ Read more

⤋ Read More