NanoPi M6: High-Performance SBC with Gigabit Ethernet and M.2 SSD Expansion
The NanoPi M6 is a compact and open-source single-board computer (SBC) designed for high-performance applications, powered by the RK3588S System-on-Chip. Key features include an M.2 M-Key PCIe slot for SSD storage and an optional metal case with an integrated 3.5-inch LCD. The board is built around the Rockchip RK3588S SoC, which combines quad-core ARM Cortex-A76 […] ⌘ Read more
Stellantis au capital de Leapmotor : priorité aux quotas
Un article de Henry Bonner L’action du constructeur de voitures Stellantis grimpe de près de 3 % cette semaine. La raison ? L’annonce de la recherche d’un successeur – après 2026 – pour le PDG, Carlos Tavares… Chez une partie des actionnaires, ce rebond montre un manque de confiance dans le gérant du groupe. La baisse […] ⌘ Read more
More thoughts about changes to twtxt (as if we haven’t had enough thoughts):
- There are lots of great ideas here! Is there a benefit to putting them all into one document? Seems to me this could more easily be a bunch of separate efforts that can progress at their own pace:
1a. Better and longer hashes.
1b. New possibly-controversial ideas like edit: and delete: and location-based references as an alternative to hashes.
1c. Best practices, e.g. Content-Type: text/plain; charset=utf-8
1d. Stuff already described at dev.twtxt.net that doesn’t need any changes.
We won’t know what will and won’t work until we try them. So I’m inclined to think of this as a bunch of draft ideas. Maybe later when we’ve seen it play out it could make sense to define a group of recommended twtxt extensions and give them a name.
Another reason for 1 (above) is: I like the current situation where all you need to get started is these two short and simple documents:
https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html
https://twtxt.readthedocs.io/en/latest/user/discoverability.html
and everything else is an extension for anyone interested. (Deprecating non-UTC times seems reasonable to me, though.) Having a big long “twtxt v2” document seems less inviting to people looking for something simple. (@prologic@twtxt.net you mentioned an anonymous comment “you’ve ruined twtxt” and while I don’t completely agree with that commenter’s sentiment, I would feel like twtxt had lost something if it moved away from having a super-simple core.)All that being said, these are just my opinions, and I’m not doing the work of writing software or drafting proposals. Maybe I will at some point, but until then, if you’re actually implementing things, you’re in charge of what you decide to make, and I’m grateful for the work.
“First world” countries problem number x:
More than 3,600 chemicals approved for food contact in packaging, kitchenware or food processing equipment have been found in humans, new peer-reviewed research has found, highlighting a little-regulated exposure risk to toxic substances.
最新一期「优秀答主」名单揭晓，快来看看都有哪些宝藏答主~
✨ 新一期「优秀答主」今日揭晓，快来点击下方链接，看看他们都是谁吧~
（P.S: 不同话题下的「优秀答主」会按照所属内容领域集中展示哦~）
再次感谢他们在相关话题下持续创作专业、优质的内容，让知乎的知识星河变得更加璀璨，让无数人从中发现更多开阔眼界的、有帮助的、引发共鸣的内容。
他们分别是（按首字母排名）：
@ag獭 | @Arci | [@北岸](https://www.zhihu.com/people/3 … ⌘ Read more
↳
In-reply-to
»
Good writeup, @anth! I agree to most of your points.
⤋ Read More
@lyse@lyse.isobeef.org on this:
3.2 Timestamps: I feel no need to mandate UTC. Timezones are fine with me. But I could also live with this new restriction. I fail to see, though, how this change would make things any easier compared to the original format.
Exactly! If anything it will make things more complicated, no?
↳
In-reply-to
»
This is only first draft quality, but I made some notes on the #twtxt v2 proposal. http://a.9srv.net/b/2024-09-25
⤋ Read More
Good writeup, @anth@a.9srv.net! I agree to most of your points.
3.2 Timestamps: I feel no need to mandate UTC. Timezones are fine with me. But I could also live with this new restriction. I fail to see, though, how this change would make things any easier compared to the original format.
3.4 Multi-Line Twts: What exactly do you think are bad things with multi-lines?
4.1 Hash Generation: I do like the idea with with a new uuid metadata field! Any thoughts on two feeds selecting the same UUID for whatever reason? Well, the same could happen today with url.
5.1 Reply to last & 5.2 More work to backtrack: I do not understand anything you’re saying. Can you rephrase that?
8.1 Metadata should be collected up front: I generally agree, but if the uuid metadata field were a feed URL and no real UUID, there should be probably an exception to change the feed URL mid-file after relocation.
↳
In-reply-to
»
Some more arguments for a local-based treading model over a content-based one:
⤋ Read More
@sorenpeter@darch.dk Points 2 & 3 aren’t really applicable here in the discussion of the threading model really I’m afraid. WebMentions is completely orthogonal to the discussion. Further, no-one that uses Twtxt really uses WebMentions, whilst yarnd supports the use of WebMentions, it’s very rarely used in practise (if ever) – In fact I should just drop the feature entirely.
The use of WebSub OTOH is far more useful and is used by every single yarnd pod everywhere (no that there’s that many around these days) to subscribe to feed updates in ~near real-time without having the poll constantly.
Some more arguments for a local-based treading model over a content-based one:
The format:
(#<DATE URL>)or(@<DATE URL>)both makes sense: # as prefix is for a hashtag like we allredy got with the(#twthash)and @ as prefix denotes that this is mention of a specific post in a feed, and not just the feed in general. Using either can make implementation easier, since most clients already got this kind of filtering.Having something like
(#<DATE URL>)will also make mentions via webmetions for twtxt easier to implement, since there is no need for looking up the#twthash. This will also make it possible to make 3th part twt-mentions services.Supporting twt/webmentions will also increase discoverability as a way to know about both replies and feed mentions from feeds that you don’t follow.
MS-CF16 Fanless Low-Power Pico-ITX SBC with Alder Lake-N and Amston Lake Processors
The MS-CF16 is a compact Pico-ITX single-board computer designed for fanless, low-power, high-performance applications in harsh environments. Powered by Intel Alder Lake-N or Amston Lake Series SoCs, the board features a 2.5GbE LAN port, a GbE LAN port, and SATA 3.0 for storage. Unlike the previously covered MS-CF17, this model offers configurable Intel processors, each […] ⌘ Read more
On my blog: Free Culture Book Club — Aumyr, part 3 https://john.colagioia.net/blog/2024/09/21/aumyr-3.html #freeculture #bookclub
And they have arrived (well, they did around 3 hours ago, LOL). Buttery smooth, my 16 Pro (one with dark cover). It took a bit over an hour to transfer all my data.
↳
In-reply-to
»
@movq could it be possible to have
⤋ Read More
compressed_subject(msg_singlelined) be configurable, so only a certain number of characters get displayed, ending on ellipses? Right now the entire twtxt is crammed into the Subject:. This request aims to make twtxts display on mutt/neomutt, etc. more like emails do.
@movq@www.uninformativ.de yes, that’s perfect! <3
the stem matching is the same as how GIT does its branch hashes. i think you can stem it down to 2 or 3 sha bytes.
if a client sees someone in a yarn using a byte longer hash it can lengthen to match since it can assume that maybe the other client has a collision that it doesnt know about.
the stem matching is the same as how GIT does its branch hashes. i think you can stem it down to 2 or 3 sha bytes.
if a client sees someone in a yarn using a byte longer hash it can lengthen to match since it can assume that maybe the other client has a collision that it doesnt know about.
Kuo: iPhone 17 to Use 3nm Chip Tech, Some iPhone 18 Models to Use 2nm
Next year’s iPhone 17 series will feature processors made using TSMC’s 3-nonometer chip technology, but only some iPhone 18 models in 2026 are anticipated to use the Taiwanese chipmaker’s next-generation 2nm processor technology because of cost concerns, according to Apple analyst Ming-Chi Kuo. … ⌘ Read more
↳
In-reply-to
»
Taking the last n characters of a base32 encoded hash instead of the first n can be problematic for several reasons:
⤋ Read More
There’s a simple reason all the current hashes end in a or q: the hash is 256 bits, the base32 encoding chops that into groups of 5 bits, and 256 isn’t divisible by 5. The last character of the base32 encoding just has that left-over single bit (256 mod 5 = 1).
So I agree with #3 below, but do you have a source for #1, #2 or #4? I would expect any lack of variability in any part of a hash function’s output would make it more vulnerable to attacks, so designers of hash functions would want to make the whole output vary as much as possible.
Other than the divisible-by-5 thing, my current intuition is it doesn’t matter what part you take.
Hash Structure: Hashes are typically designed so that their outputs have specific statistical properties. The first few characters often have more entropy or variability, meaning they are less likely to have patterns. The last characters may not maintain this randomness, especially if the encoding method has a tendency to produce less varied endings.
Collision Resistance: When using hashes, the goal is to minimize the risk of collisions (different inputs producing the same output). By using the first few characters, you leverage the full distribution of the hash. The last characters may not distribute in the same way, potentially increasing the likelihood of collisions.
Encoding Characteristics: Base32 encoding has a specific structure and padding that might influence the last characters more than the first. If the data being hashed is similar, the last characters may be more similar across different hashes.
Use Cases: In many applications (like generating unique identifiers), the beginning of the hash is often the most informative and varied. Relying on the end might reduce the uniqueness of generated identifiers, especially if a prefix has a specific context or meaning.
Taking the last n characters of a base32 encoded hash instead of the first n can be problematic for several reasons:
Hash Structure: Hashes are typically designed so that their outputs have specific statistical properties. The first few characters often have more entropy or variability, meaning they are less likely to have patterns. The last characters may not maintain this randomness, especially if the encoding method has a tendency to produce less varied endings.
Collision Resistance: When using hashes, the goal is to minimize the risk of collisions (different inputs producing the same output). By using the first few characters, you leverage the full distribution of the hash. The last characters may not distribute in the same way, potentially increasing the likelihood of collisions.
Encoding Characteristics: Base32 encoding has a specific structure and padding that might influence the last characters more than the first. If the data being hashed is similar, the last characters may be more similar across different hashes.
Use Cases: In many applications (like generating unique identifiers), the beginning of the hash is often the most informative and varied. Relying on the end might reduce the uniqueness of generated identifiers, especially if a prefix has a specific context or meaning.
In summary, using the first n characters generally preserves the intended randomness and collision resistance of the hash, making it a safer choice in most cases.
Fanless PC with N97 CPU Dual GbE LAN and Dual HDMI Ports Supporting 4K at 60Hz
The QBiX-ADNAN97-A1 is an industrial-grade computing system engineered for robust performance and reliability. Featuring a compact, fanless design, it supports a DDR5 memory system, SATA 3.0, and dual GbE LAN ports, ensuring robust wired connectivity. As its name suggests, this industrial system features the Intel Processor N97, which is part of Intel’s 7 series. The […] ⌘ Read more
↳
In-reply-to
»
@quark At the moment, the twt in question exists in the sixth archive:
⤋ Read More
@movq@www.uninformativ.de I didn’t run the command as you recommended, but, I wiped things once more, and ran jenny -f, and this time got:
david@arrakis:~$ jenny -f
Fetching archived feed https://anthony.buc.ci/user/abucci/twtxt.txt/1 (configured as abucci, https://anthony.buc.ci/user/abucci/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2024-04.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://darch.dk/twtxt-archive.txt (configured as soren, https://darch.dk/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2024-04-21_6v47cua.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/1 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2024-03.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2022-12-21_2us6qbq.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/2 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2024-02.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2022-01-14_ew5gzca.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/3 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2024-01.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-12-23_f6y65bq.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/4 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-12.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-12-04_e4x7yba.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/5 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-11.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-11-18_42tjxba.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/6 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-10.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-11-08_i2wnvaa.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-09.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-10-23_kvwn5oa.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-08.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-10-11_mljudaa.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-07.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-09-22_5mkqwua.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-06.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-07-27_xcnzmlq.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-05.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-06-16_mtedqya.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-04.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-04-29_z7lvzja.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-03.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-03-19_xjabvhq.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-02.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-02-24_te4a6oa.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2023-01.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2021-01-26_qxgigma.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-12.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://www.uninformativ.de/twtxt-old_2020-12-13_igfnala.txt (configured as movq, https://www.uninformativ.de/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-11.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-10.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-09.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-08.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-07.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-06.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-05.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-04.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-03.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-02.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2022-01.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-12.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-11.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-10.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-09.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-08.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-07.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-06.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-05.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-04.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-03.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-02.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2021-01.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Fetching archived feed https://lyse.isobeef.org/twtxt-2020-12.txt (configured as lyse, https://lyse.isobeef.org/twtxt.txt)
Notice that @prologic@twtxt.net’s /6 is there. I found the twtxt then. Kind of odd it didn’t show before.
Apple Seeds Fourth Developer Betas of iOS 18.1, iPadOS 18.1 and macOS Sequoia 15.1 With Apple Intelligence
Apple today provided developers with the fourth betas of iOS 18.1, iPadOS 18.1, and macOS Sequoia 15.1 to continue testing Apple Intelligence features. The third betas come two weeks after Apple seeded the third iOS 18.1, iPadOS 18.1, and macOS Sequoia 15.1 betas. Apple has als … ⌘ Read more
GENESYSM-ADN6: A 3.5″ SubCompact System with Triple 2.5GbE LAN Ports
GENESYSM-ADN6: A 3.5” SubCompact System with Triple 2.5GbE LAN Ports ⌘ Read more
↳
In-reply-to
»
The tag URI scheme looks interesting. I like that it human read- and writable. And since we already got the timestamp in the twtxt.txt it would be somewhat trivial to parse. But there are still the issue with what the name/id should be... Maybe it doesn't have to bee that stick?
⤋ Read More
(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)
I think I like this a lot. 🤔
The problem with using hashes always was that they’re “one-directional”: You can construct a hash from URL + timestamp + twt, but you cannot do the inverse. When I see “, I have no idea what that could possibly refer to.
But of course something like (replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z) has all the information you need. This could simplify twt/feed discovery quite a bit, couldn’t it? 🤔 That thing that I just implemented – jenny asking some Yarn pod for some twt hash – would not be necessary anymore. Clients could easily and automatically fetch complete threads instead of requiring the user to follow all relevant feeds.
Only using the timestamp to identify a twt also solves the edit problem.
It even is better for non-Yarn clients, because you now don’t have to read, understand, and implement a “twt hash specification” before you can reply to someone.
The only problem, really, is that (replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z) is so long. Clients would have to try harder to hide this. 😅
Apple Releases tvOS 18 With InSight, New Screen Savers and More
Apple today released tvOS 18, the newest version of the tvOS operating system that runs on the Apple TV 4K and Apple TV HD models.
tvOS 18 can be downloaded using the Settings app on the Apple TV. Open up Settings and go to System > Software Update to get the new software. Apple TV owners who have automatic softwa … ⌘ Read more
↳
In-reply-to
»
@quark No can do! I can't see any of the replies to that thread, not even mine LOL. let me se if I can fetch @sorenpeter 's feed with the https link.
⤋ Read More
@aelaraji@aelaraji.com make sense, probably. The twtxt was already on my Maildir, that’s why I can fetch it. I fetch every 3 minutes (sssh, don’t tell anyone!). LOL!
↳
In-reply-to
»
Something odd just happened to my twtxt timeline... A bunch of twts dissapered, others were marked to be deleted in mutt. so I nuked my whole twtxt Maildir and deleted my ~/.cache/jenny in order to start with a fresh Pull. I pulled feed as usual. Now like HALF the twts aren't there 😂 even my my last replay. WTF IS GOING ON? 🤣🤣🤣
⤋ Read More
More:
Subject: The [tag URI scheme](https://en.wikipedia.org/wiki/Tag_URI_scheme) looks interesting. I like that it human read- and writable. And since we already got the timestamp in the twtxt.txt it would be
somewhat trivial to parse. But there are still the issue with what the name/id should be... Maybe it doesn't have to bee that stick? Instead of using `tag:` as the prefix/protocol, it would more it clear
what we are talking about by using `in-reply-to:` (https://indieweb.org/in-reply-to) or `replyto:` similar to `mailto:` 1. `(reply:sorenpeter@darch.dk,2024-09-15T12:06:27Z)' 2.
`(in-reply-to:darch.dk/twtxt.txt,2024-09-15T12:06:27Z)' 2. `(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)' I know it's longer that 7-11 characters, but it's self-explaining when looking at the
twtxt.txt in the raw, and the cases above can all be caught with this regex: `\([\w-]*reply[\w-]*\:` Is this something that would work?
Subject: The [tag URI scheme](https://en.wikipedia.org/wiki/Tag_URI_scheme) looks interesting. I like that it human read- and writable. And since we already got the timestamp in the twtxt.txt it would be
somewhat trivial to parse. But there are still the issue with what the name/id should be... Maybe it doesn't have to bee that stick? Instead of using `tag:` as the prefix/protocol, it would more it clear
what we are talking about by using `in-reply-to:` (https://indieweb.org/in-reply-to) or `replyto:` similar to `mailto:` 1. `(reply:sorenpeter@darch.dk,2024-09-15T12:06:27Z)` 2.
`(in-reply-to:darch.dk/twtxt.txt,2024-09-15T12:06:27Z)` 3. `(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)` I know it's longer that 7-11 characters, but it's self-explaining when looking at the
twtxt.txt in the raw, and the cases above can all be caught with this regex: `\([\w-]*reply[\w-]*\:` Is this something that would work?
Notice the difference? Soren edited, and broke everything.
↳
In-reply-to
»
The tag URI scheme looks interesting. I like that it human read- and writable. And since we already got the timestamp in the twtxt.txt it would be somewhat trivial to parse. But there are still the issue with what the name/id should be... Maybe it doesn't have to bee that stick?
⤋ Read More
@mckinley@twtxt.net Thanks for the feedback.
- Yeah I agrees that nick sound not be part of syntax. Any valid URL to a twtxt.txt-file should be enough and is more clear, so it is not confused with a email (one of the the issues with webfinger and fedivese handles)
- I think any valid URL would work, since we are not bound to look for exact matches. Accepting both http and https as well as a gemni and gophe could all work as long as the path to the twtxt.txt is the same.
- My idea is that you quote the timestamp as it is in the original twtxt.txt that you are referring to, so you can do it by simply copy/pasting. Also what are the change that the same human will make two different posts within the same second?!
Regarding the whole cryptographic keys for identity, to me it seems like an unnecessary layer of complexity. If you move to a new house or city you tell people that you moved - you can do the same in a twtxt.txt. Just post something like “I move to this new URL, please follow me there!” I did that with my feeds at least twice, and you guys still seem to read my posts:)
↳
In-reply-to
»
@prologic Some criticisms and a possible alternative direction:
⤋ Read More
The tag URI scheme looks interesting. I like that it human read- and writable. And since we already got the timestamp in the twtxt.txt it would be somewhat trivial to parse. But there are still the issue with what the name/id should be… Maybe it doesn’t have to bee that stick?
Instead of using tag: as the prefix/protocol, it would more it clear what we are talking about by using in-reply-to: (https://indieweb.org/in-reply-to) or replyto: similar to mailto:
(reply:sorenpeter@darch.dk,2024-09-15T12:06:27Z)
(in-reply-to:darch.dk/twtxt.txt,2024-09-15T12:06:27Z)
(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)
I know it’s longer that 7-11 characters, but it’s self-explaining when looking at the twtxt.txt in the raw, and the cases above can all be caught with this regex: \([\w-]*reply[\w-]*\:
Is this something that would work?
MSI’s MS-CF17: An Ultra-Low-Power 3.5″ SBC with Intel Raptor Lake-P Processors
The MS-CF17 from MSI is an advanced single-board computer that combines high performance with a compact, fanless, ultra-low-power design. Featuring Intel’s latest 13th Gen Raptor Lake-P processors, the board is also available in an industrial-grade variant, making it suitable for demanding applications. This SBC is equipped with Intel Mobile 13th Gen Raptor Lake-P U Series […] ⌘ Read more
Ignite Realtime Blog: Openfire Hazelcast plugin version 3.0.0
Earlier today, we blogged about a boatload of Openfire plugins for which we made available maintenance releases.
Apart from that, we’ve also made a more notable release: that of the Hazelcast plugin for Openfire.
The Hazelcast plugin for Openfire adds clust … ⌘ Read more
↳
In-reply-to
»
@falsifian In my opinion it was a mistake that we defined the first
⤋ Read More
url field in the feed to define the URL for hashing. It should have been the last encountered one. Then, assuming append-style feeds, you could override the old URL with a new one from a certain point on:
I was not suggesting to that everyone need to setup a working webfinger endpoint, but that we take the format of nick+(sub)domain as base for generating the hashed together with the message date and content.
If we omit the protocol prefix from the way we do things now will that not solve most of the problems? In the case of gemini://gemini.ctrl-c.club/~nristen/twtxt.txt they also have a working twtxt.txt at https://ctrl-c.club/~nristen/twtxt.txt … damn I just notice the gemini. subdomain.
Okay what about defining a prefers protocol as part of the hash schema? so 1: https , 2: http 3: gemini 4: gopher ?
Asus X7433RE-IM-A is a 3.5″ Single Board Computer with Intel Atom X7433RE Processor
The X7433RE-IM-A is a 3.5” industrial single board computer designed for industrial applications, featuring the Intel Amston Lake System-on-Chip. It integrates Intel Deep Learning Boost and Advanced Vector Extensions 2 to enhance AI inference and accelerate workloads at the edge, specifically targeting IoT applications. This SBC is available with the x7433RE processor, offering … ⌘ Read more
Interesting.. QUIC isn’t very quick over fast internet.
QUIC is expected to be a game-changer in improving web application performance. In this paper, we conduct a systematic examination of QUIC’s performance over high-speed networks. We find that over fast Internet, the UDP+QUIC+HTTP/3 stack suffers a data rate reduction of up to 45.2% compared to the TCP+TLS+HTTP/2 counterpart. Moreover, the performance gap between QUIC and HTTP/2 grows as the underlying bandwidth increases. We observe this issue on lightweight data transfer clients and major web browsers (Chrome, Edge, Firefox, Opera), on different hosts (desktop, mobile), and over diverse networks (wired broadband, cellular). It affects not only file transfers, but also various applications such as video streaming (up to 9.8% video bitrate reduction) and web browsing. Through rigorous packet trace analysis and kernel- and user-space profiling, we identify the root cause to be high receiver-side processing overhead, in particular, excessive data packets and QUIC’s user-space ACKs. We make concrete recommendations for mitigating the observed performance issues.
Interesting.. QUIC isn’t very quick over fast internet.
QUIC is expected to be a game-changer in improving web application performance. In this paper, we conduct a systematic examination of QUIC’s performance over high-speed networks. We find that over fast Internet, the UDP+QUIC+HTTP/3 stack suffers a data rate reduction of up to 45.2% compared to the TCP+TLS+HTTP/2 counterpart. Moreover, the performance gap between QUIC and HTTP/2 grows as the underlying bandwidth increases. We observe this issue on lightweight data transfer clients and major web browsers (Chrome, Edge, Firefox, Opera), on different hosts (desktop, mobile), and over diverse networks (wired broadband, cellular). It affects not only file transfers, but also various applications such as video streaming (up to 9.8% video bitrate reduction) and web browsing. Through rigorous packet trace analysis and kernel- and user-space profiling, we identify the root cause to be high receiver-side processing overhead, in particular, excessive data packets and QUIC’s user-space ACKs. We make concrete recommendations for mitigating the observed performance issues.
Apple Announces iPhone 16 Pro and iPhone 16 Pro Max
Apple today announced the iPhone 16 Pro and iPhone 16 Pro Max—its latest flagship smartphones—featuring larger displays, an all-new Camera Control button, and the A18 Pro chip.
The iPhone 16 Pro has a 6.3-inch display, while the iPhone 16 Pro Max features a 6.9-inch display – the biggest [iPhone](https://www.macrumors.com/guid … ⌘ Read more
Gurman: No Apple Watch Ultra 3 Tomorrow, Ultra 2 in Black Likely
Bloomberg’s Mark Gurman today said that he does not expect Apple to announce an Apple Watch Ultra 3 at its event tomorrow. Instead, he believes that Apple will introduce a black color option for the Apple Watch Ultra 2.
Apple supply chain analyst Ming-Chi Kuo was first to ind … ⌘ Read more
↳
In-reply-to
»
@prologic Some criticisms and a possible alternative direction:
⤋ Read More
@falsifian@www.falsifian.org In my opinion it was a mistake that we defined the first url field in the feed to define the URL for hashing. It should have been the last encountered one. Then, assuming append-style feeds, you could override the old URL with a new one from a certain point on:
# url = https://example.com/alias/txtxt.txt
# url = https://example.com/initial/twtxt.txt
<message 1 uses the initial URL>
<message 2 uses the initial URL, too>
# url = https://example.com/new/twtxt.txt
<message 3 uses the new URL>
# url = https://example.com/brand-new/twtxt.txt
<message 4 uses the brand new URL>
In theory, the same could be done for prepend-style feeds. They do exist, I’ve come around them. The parser would just have to calculate the hashes afterwards and not immediately.
On the Subject of Feed Identities; I propose the following:
- Generate a Private/Public ED25519 key pair
- Use this key pair to sign your Twtxt feed
- Use it as your feed’s identity in place of
# url =as# key = ...
For example:
$ ssh-keygen -f prologic@twtxt.net
$ ssh-keygen -Y sign -n prologic@twtxt.net -f prologic@twtxt.net twtxt.txt
And your feed would looke like:
# nick = prologic
# key = SHA256:23OiSfuPC4zT0lVh1Y+XKh+KjP59brhZfxFHIYZkbZs
# sig = twtxt.txt.sig
# prev = j6bmlgq twtxt.txt/1
# avatar = https://twtxt.net/user/prologic/avatar#gdoicerjkh3nynyxnxawwwkearr4qllkoevtwb3req4hojx5z43q
# description = "Problems are Solved by Method" 🇦🇺👨💻👨🦯🏹♔ 🏓⚯ 👨👩👧👧🛥 -- James Mills (operator of twtxt.net / creator of Yarn.social 🧶)
2024-06-14T18:22:17Z (#nef6byq) @<bender https://twtxt.net/user/bender/twtxt.txt> Hehe thanks! 😅 Still gotta sort out some other bugs, but that's tomorrows job 🤞
...
Twt Hash extension would change of course to use a feed’s ED25519 public key fingerprint.
【长文】24.8~京都大学数据科学/东京大学情报理工CS/东京大学复杂理工~合格经验
一、背景笔者参加并合格了2024年8月京都大学数据科学、东京大学情报理工cs以及东京大学新领域复杂理工的夏入（2025入学）。
我的背景比较不具备参考价值，有点奇怪。
学校：非科班并且工作后辞职备考。
本科GPA：3.5/4
英语：托福97
日语：略强于50音。未提交任何日语成绩。
以及先套个甲，修考非常的小马过河，很难说别人的经验就完全适应于你；以及修考的很多流程确实是黑箱，本文中的内容很多都是推测。所以本文内容仅供参考，不构成任何投资建议，啊不，决策建议。
本文参考了很多大佬的经验贴，在这里着重推荐以下几个：
知乎上京大DS夏入的经验贴似乎只有这一个，特别感谢这个帖子让我少走了很多弯路。以及同样推荐帖子中提到的霓虹爷写的网站，简直是京大知能修考必备。
[一滴：2022年度| … ⌘ Read more
[47°09′58″S, 126°43′39″W] Raw reading: 0x66D75CB2, offset +/-3
Beta 3 of iOS 18.1, MacOS Sequoia 15.1, & iPadOS 18.1 Released with Apple Intelligence
The third beta versions of iOS 18.1, iPadOS 18.1, and MacOS Sequoia 15.1, have been released by Apple. Each of these versions of beta system software support Apple Intelligence (assuming the iPhone, iPad, or Mac supports it too, anyway), whereas the iOS/ipadOS 18.0 and macOS 15.0 versions do not. With the amount of betas that … [Read More](https://osxdaily.com/ … ⌘ Read more
Apple Intelligence Not Device Region Locked to US in Latest Betas
Apple in the latest iOS 18.1, iPadOS 18.1, and macOS Sequoia 15.1 betas no longer requires users to set their device region to the United States, so now it’s just the US English language requirement that remains.
In previous betas, users not only had to change Siri’s lan … ⌘ Read more
QBiP-N97A: 3.5” SubCompact Embedded Motherboard with Intel Processor N97, DDR5 Memory, and SATA 6Gb/s Support
ICP Deutschland recently showcased the QBiP-N97A, a 3.5″ SubCompact Embedded Motherboard designed for various industrial applications, including automation systems and point-of-sale terminals. This motherboard features DDR5 memory support, dual 2.5GbE LAN ports, and SATA 6Gb/s support for storage. The QBiP-N97A is powered by the I … ⌘ Read more
Building a translation agent on LlamaEdge
Member post originally published on Second State’s blog Prof. Andrew Ng’s agentic translation is a great demonstration on how to coordinate multiple LLM “agents” to work on a single task. It allows multiple smaller LLMs (like Llama-3 or Gemma-2) to… ⌘ Read more
目前来看，智能家居的「理想态」是什么？中国品牌在智能家居上有了哪些突破和可能性？
能力有限，但很想来回答问题的前半部分。
1、让用户在0操作甚至0感知下，默默独立完成生活中的家居任务（一个案例为扫地机）。
2、让用户以最少的交互，最简单的方式，解决日常必要的生活行为（一个案例为智能锁）。
3、智能终端应具备思维能力，而不仅仅是等待主人的任务，唯命是从。
过去曾作为开发者参与过全套智能家居产品的硬件设计，小到86面板，大到中控主机，因此也参加过蛮多物联网和智能家居展会；之前的2-3年，我深入写过，过去10多年的智能家居主要解决了通信物联问题，虽然不再需要去机器上按下按钮或者通过遥控去操作，但本质上 智能家居的“智能”仅体现在了“远程控制+联动逻辑”，还是一个遥控器。
用家居中的 “垃圾桶” 作为案例来讨论现在的智能垃圾桶，它有哪些智能化？
Go 項目結構的簡潔實現
今天分享一個在 GitHub 上有 3.5k stars 的 Go 項目：go-backend-clean-arch[1]。該項目展示了一個 Golang 後端項目如何設計優雅的項目結構。項目架構——-3.Directory Explanation———————–.├── Dockerfile # Image file├── api│ ⌘ Read more
↳
In-reply-to
»
Does anyone know what the differences between HTTP/1.1 HTTP/2 and HTTP/3 are? 🤔
⤋ Read More
HTTP/2 differs from 1.x by becoming a binary protocol, it also multiplexes multiple channels over the same connection and has the ability to prefetch related content to the browser to lower the perceived latency.
HTTP/3 moves the binary protocol from HTTP/2 over to QUIC which is based on UDP instead of TCP. This makes it better suited to mobile or unstable networks where handling of transmission errors can be handled at a higher level.
↳
In-reply-to
»
Does anyone know what the differences between HTTP/1.1 HTTP/2 and HTTP/3 are? 🤔
⤋ Read More
HTTP/2 differs from 1.x by becoming a binary protocol, it also multiplexes multiple channels over the same connection and has the ability to prefetch related content to the browser to lower the perceived latency.
HTTP/3 moves the binary protocol from HTTP/2 over to QUIC which is based on UDP instead of TCP. This makes it better suited to mobile or unstable networks where handling of transmission errors can be handled at a higher level.
Jetway JNUC-ADN1: NUC Board Featuring Intel N97 Processor and Dual 2.5GbE Ports
The JNUC-ADN1 is an embedded board with a NUC form-factor, powered by the Intel N97 low-power processor. This board is tailored for applications requiring efficient performance and compact size, such as digital signage and other commercial or industrial uses. The JNUC-ADN1 series is built around the Intel processor N97, which offers up to 3.60 GHz […] ⌘ Read more
Does anyone know what the differences between HTTP/1.1 HTTP/2 and HTTP/3 are? 🤔
我有一个绝妙的游戏点子，怎样才能把它做出来？——独立游戏可行性概念篇
如何完成一个独游项目的立项，大概可以这样思考：
1 想做什么？怎么整理自己的点子？
2 怎么确定自己的概念设计可行？怎么进一步推导可行性？
3 评估能力和成本，怎么做好项目的规划和商业化预期？
4 怎么让项目能够落地下来？
我会以“ 烟花”作为命题，来讲讲怎么从“烟花”这个概念拓展为能变成能落地的可行性概念。
一、 灵魂疑问：我有一个绝妙的游戏点子？人总会容易有一种错觉：我有一个绝妙的游戏点子，只要做出来肯定火。
那问题来了：
这真的能行吗？怎么才算绝妙的点子呢？
答案很简单：
别YY，去外部验证。
之前有群友问“烟花”怎么做成独立游戏，这次就以烟花当例子来进行推导。
首先，在动脑前，最好是先到互联网验证一下自己“绝妙的游戏点子”是不是已经有人想出来了，甚至做过了？
先花时间搜一下能很有效的避免重复造轮子。
下面是一个随便一点的流程。
先到b站搜一下：
GNOME Bans Saying “Lunduke”. WINE Fixes AOL for Win 3.1 (Seriously). Python 71x Slower Than C. ⌘ Read more
On my blog: Free Culture Book Club — Aether Age Codex - Helios, part 3 https://john.colagioia.net/blog/2024/08/03/helios-3.html #freeculture #bookclub
↳
In-reply-to
»
Today I'm looking into flutter again, I've been wanting to test that out for a while.
I started adding functionality from the 'yarn desktop client' ( https://github.com/stig-atle/YarnDesktopClient ) I've been working on - and now I see if I can get the same functionality up and running with flutter.
Currently I'm able to log in and fetch the logged in user's username at least (the text :username: is fetched after logging in), so it's a good start.
That means I have the things I need to fetch the timeline and present that next.
⤋ Read More
Got all 3 timelines in, so you can switch between them.
Need to add some kind of refresh feature as well, then I’ll get it cleaned up and put the source out, and continue from there - also the UI is not final, now I’m just focusing on features. The UI will be cleaned up as well.
It’s my birthday today :) i was born 41 years go, 3.5 months too early. I was so small my parents had to buy doll clothes at the toy store. Gonna be a nice day today, celebrate with my family :) we always treasure birthdays.🎂
<3
iOS 16.7.9, iPadOS 16.7.9, iOS 15.8.3, & iPadOS 15.8.3 Released with Security Fixes
Apple has issued security updates for prior generation iPhone and iPad models that are not compatible with iOS 17.6 and iPadOS 17.6. Specifically, the new updates are versioned as iOS 16.7.9, iPadOS 16.7.9, iOS 15.8.3, and iPadOS 15.8.3, and include important security fixes making them recommended for all users to install onto compatible devices. iOS … [Read More](htt … ⌘ Read more
Wine Fixes Bugs in Windows 3.1 Software Running on Linux
Including fixes for AOL (seriously!) and 16-bit Civilization 1. A lot of Windows software runs better under Linux than Windows nowadays. ⌘ Read more
Gajim: Gajim 1.9.3
Gajim 1.9.3 fixes an issue with the MS Store installer and brings some improvements. Thank you for all your contributions!
If you had issues starting Gajim from the Microsoft Store, Gajim 1.9.3 should fix these issues.
Thanks to our contributors @nicoco and @mesonium, Gajim received some improvements regarding message Displayed Markers and highlight colors. Furthermore, drag and drop for file transfers has b … ⌘ Read more
Don’t Miss Out on OWC’s 14-Port Mac Thunderbolt Dock at $99.99 ($180 Off), Ending This Weekend
Last week, OWC knocked the price of the popular 14-Port Thunderbolt 3 Dock down to $99.99, from its original price of $279.99, and this deal is still around this weekend. This is a match of the all-time low price on the accessory, and the sale is set to end Sunday night.
.
Here I am with my daughter on the new bike :)
My kids love to go for rides, so does Marlyn as well, so it's a lot of fun for all of us.
Media
⤋ Read More
@bender@twtxt.net It cost what you mentioned here too, but they had a special discount, and the shop gave 20% discount for all the gear we needed (since I bought the bike + gear for two persons), so all in all I got a really good deal on it. Also interest rate is locked for 3 years (low rate) so that was also a good deal.
I just took the longest time I could on the loan, to have a low price each month, and then i just pay extra whenever I can to get it payed down faster.
Luckily the Marlyn, my son, and my daughter all fit the same gear, so the 3 of them share that, that saved a lot of money too :)
When i met Marlyn (before we had kids) I asked here to go on her first trip with me (I had a bike before I met her back then), and we went on a 2 week ride from Norway to Italy and back (venice) through the alps and all that. Was super fun, and I think it’s pretty cool of her to say yes to a 2 week trip as passenger :)
‘The world is in meltdown’: Inside the front lines of the CrowdStrike outage
It was at about 3.30pm on an otherwise quiet and uneventful Friday that Ashwin Pal’s phone began blowing up. ⌘ Read more
3 Ways CARIAD Configures Docker Business for Security and Compliance
Find out how CARIAD configures Docker for security and compliance using Docker Single Sign-On, Image Access Management, and Windows Subsystem for Linux 2. ⌘ Read more
We went to a new dog park today (1.5hr drive), booked the biggest of 3 parks for 2 hours, we had a really nice time there :) us and kids + dog had a blast :)
[47°09′51″S, 126°43′10″W] Raw reading: 0x669FD381, offset +/-3
Golang - range 迭代器揭祕
簡介我們正在使用 Go 語言編寫 Dolt[1] ，這是世界上第一個版本控制的 SQL 數據庫。像大多數大型 Go 代碼庫一樣，我們有很多需要迭代的集合類型。 Go 1.23 的新特性 [2] 中，你現在可以使用 range 關鍵字來迭代自定義集合類型。這是如何工作的? 這是個好主意嗎? 讓我們深入探討一下。如果你想運行本教程中的任何代碼，你需要 安裝 Go 1.23 發佈候選版 [3] ，或者在 ⌘ Read more
3 ways to get Remote Code Execution in Kafka UI
In this blog post, we’ll explain how we discovered three critical vulnerabilities in Kafka UI and how they can be exploited.
The post 3 ways to get Remote Code Execution in Kafka UI appeared first on The GitHub Blog. ⌘ Read more
[47°09′55″S, 126°43′42″W] Raw reading: 0x66996631, offset +/-3
ProcessOne: ejabberd 24.02
ejabberd 24.02 has just been release and well, this is a huge release with 200 commits and more in the libraries. We’ve packed this update with a plethora of new features, significant improvements, and essential bug fixes, all designed to supercharge your messaging infrastructure.
– **, a System on Module based on the Raspberry Pi 4 Model B, intended for industrial applications. It retains the form factor of the older Compute Module 3 and 3+, offering multiple standard peripherals. The CM4S is equipped with a Broadcom BCM2711 quad-core 64-bit […] ⌘ Read more
ProcessOne: Breaking Down the Costs of Large Messaging Services
I will comment on an interesting article from Meredith Whittaker and Joshua Lund breaking down the cost of running a large-scale messaging platform.
It estimates that the cost to operate Signal messaging will reach 50 million dollars per year in 2025.
![🔗](https://s.w.org/images/core/emoji/15.0.3/72x72/1f517.png … ⌘ Read more
Golang 編寫範型集合，官方文檔未提及的訣竅
引言–Go 的泛型功能在 Go 1.18 版本中發佈, 至今已有兩年多了。我們正在使用 Go 開發 Dolt[1] , 這是世界上第一個支持版本控制的 SQL 數據庫。儘管我們有數十萬行 Go 代碼, 但我們並沒有大量使用泛型。我們在一些地方使用泛型 來加速代碼中的高流量部分 [2] , 但總的來說, 除了 slices[3] 和 maps[4] 包中的一些有用的庫方法外, 我們還沒有找到使用泛 ⌘ Read more
《艾尔登法环》里谁杀了主角的女巫？
先说结论，不知道，但是有几个嫌疑人。
- 接肢贵族后裔
- 白面具梵雷
- 葛瑞克
- 梅林娜
分析每个嫌疑人之前，先说一下，其实整个游戏里一共出现了五个女巫。首先是开头侯王厅躺着的无名女巫，让人叫老婆的那个，不过她是不是主角的女巫，并不好说，可以自由心证。
第二个是镇静教堂里死去的无名女巫，会被维克入侵的那个地方，大约是维克的女巫，从她身上能拿指头女巫套的。
第三个是塞尔维斯的傀儡，瑟萝莉娜，会在拉达恩祭典上被金符召唤，祭典广场上对话会给你一个鞠躬动作，在塞尔维斯的 … ⌘ Read more
It seems like I finally fixed a memory leak in GoBlog yesterday, that sometimes made my blog crashing. How? I used Anthropic’s new Claude 3.5 Sonnet to write me a new HTTP compression middleware that compresses HTTP responses using zstd or gzip when possible. I needed to instruct a few changes and modify some code lines as the initial implementation was wrong, but thereafter, it finally seems to work better than my original implementation that probably leaked some objects anywhere. Claude also helped me to write uni … ⌘ Read more
ProcessOne: ejabberd 24.06
This new ejabberd 24.06 includes four months of work, close to 200 commits, including several minor improvements in the core ejabberd, and a lot of improvements in the administrative parts of ejabberd, like the WebAdmin and new API commands.
Brief summary- *Webadmin rework … ⌘ Read more