Conversation
Contributor
Insufficient dataNot enough activity yet to make a reliable assessment. This is an automated analysis by AgentScan |
Contributor
Auto ReviewNo clear rule violations found in the current diff. |
Contributor
Contributor
|
Please use actual values in |
Contributor
|
Successfully generated as following: http://localhost:1200/huggingface/activity/AbstractPhil/posts - Success ✔️<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
<channel>
<title>AbstractPhil - Posts Activity</title>
<link>https://huggingface.co/AbstractPhil/activity/posts</link>
<atom:link href="http://localhost:1200/huggingface/activity/AbstractPhil/posts" rel="self" type="application/rss+xml"></atom:link>
<description>AbstractPhil - Posts Activity - Powered by RSSHub</description>
<generator>RSSHub</generator>
<webMaster>contact@rsshub.app (RSSHub)</webMaster>
<language>en</language>
<lastBuildDate>Fri, 11 Sep 2026 08:08:11 GMT</lastBuildDate>
<ttl>5</ttl>
<item>
<title>The post-beatrix-2s and control variant article is finally satisfactory, so the article is now released https://huggingface.co/blog/AbstractPhil/beatr...</title>
<description><p>The post-beatrix-2s and control variant article is finally satisfactory, so the article is now released <a href="https://huggingface.co/blog/AbstractPhil/beatrix-ft2">https://huggingface.co/blog/AbstractPhil/beatrix-ft2</a></p>
<p>The control variant will need another train with better SDPA stabilization, as the control variant destabilized and collapsed. The primary fault is the lack of QK normalization, which caused the model to simply collapse given enough time. Claude lists the rest of the suspected reasons in the article.</p>
<p>This was a very difficult series of experiments to tune with many fault points. Trying to make heads or tails of Fable 5.1 Claude-speak hasn't been the easiest task either. It seems the model is more likely to create pedantically rigid responses rather than cooperative. Not necessarily insulting, but definitely a sort of refrigerator-magnet behavior - treating my individual contributions as little sketches for the refrigerator. This often completely ignores my larger MD or complex behavioral instructions in favor of my theoretical or hypothetical - likely considering the MD and technical as the model's own, rather than my direct contributions. Right there... right on the refrigerator goes my hypothesis that worked.</p>
<p><a href="https://github.com/AbstractEyes/geolip-bytelex">https://github.com/AbstractEyes/geolip-bytelex</a></p>
<p>In any case, this upcoming week will be related entirely to cross-tokenizer distillation research. It may stretch long beyond the next week, but as it stands the geometric vocabulary has evolved into a codebook prediction system.</p>
<p>I would like to give this program linear wings. The Beatrix model supports it, but how well is up for this week to decide.</p>
<p>There are a multitude of potentials based on a series of very recent articles I will be exploring, providing the necessary bytelex complexity to a roughly 60 hour battery of experiments and trainings throughout the geometric systems.</p>
<p>The results will determine the best and worst methodologies of using these models, these shapes, and these structures with more complex byte-level cross tokenization systems</p>
</description>
<link>https://huggingface.co/posts/AbstractPhil/372092347372730</link>
<guid isPermaLink="false">372092347372730</guid>
<pubDate>Sat, 05 Sep 2026 15:30:00 GMT</pubDate>
<author>AbstractPhil</author>
</item>
<item>
<title>Mini-Beatrix-2s pretraining is ready.</title>
<description><p>Mini-Beatrix-2s pretraining is ready.
<a href="https://huggingface.co/AbstractPhil/mini-beatrix-2s">https://huggingface.co/AbstractPhil/mini-beatrix-2s</a>
The model passed a great deal of rigor and hardship, trained roughly 16 billion tokens or so. The full writeup for the model including the arms training for the first version arms and the second version arms will be drafted and prepared as soon as the v2 arms are done training and testing.</p>
<p>There are many possibilities present with such a model. The hub itself has been marked capable of potentially operating as similarity comparison, 87% of the capacity retained within a 256 dim structure. Along with this, the multi-dimensional hub attention system shows serious promise with controlling diffusion model inference, which I look forward to see the results of.</p>
<p>Additionally, sentence similarity, next token prediction, and a large array of prediction formats have been heavily improved by introducing the full model with splat attention. The model not only improved, the structure complemented everything measured, along with the more effective training regiment for version 2.</p>
<p>Beatrix 2s is essentially an autoregression decoder, however the attention mechanism houses a dual-stage encoder/decoder structure internally. Each adopting the SVAE as a core component, revamped and fitted to the exact rules of AlephLM. So there are essentially 20 SVAE in this structure, each with their own independent encoders, residually learning from the last.</p>
<p>Upcoming tests will include finetunes to bring out the strengths of all special tokens, presented in the upcoming article. The full experiment battery will be completed within a few days and the findings presented.</p>
<p>Modularization, compartmentalization, secularized behavior, and everything between are to be tested with rigor. This model is a rapid learner, there will likely be byproduct problems with that, and I look forward to solving the corewise problems one at a time until the model is strong enough to be useful for all the tested tasks.</p>
</description>
<link>https://huggingface.co/posts/AbstractPhil/633488241482182</link>
<guid isPermaLink="false">633488241482182</guid>
<pubDate>Mon, 31 Aug 2026 20:08:42 GMT</pubDate>
<author>AbstractPhil</author>
</item>
</channel>
</rss> |
DIYgod
requested changes
Sep 26, 2026
DIYgod
left a comment
Owner
There was a problem hiding this comment.
Thanks for the PR! One change before we merge:
- Please switch to the JSON API instead of parsing the profile page's
data-props. The server-rendered props only include the latest 2 posts, so this route can never return more than 2 items.https://huggingface.co/api/recent-activity?feedType=user&entity=<user>&activityType=post&limit=100works without authentication and returns the user's post activity. Keep the entries withtype === 'social-post'and usesocialPost.rawContent,socialPost.publishedAt,socialPost.urlandsocialPost.slug. ForAbstractPhilthat currently gives 21 posts instead of 2, and you no longer need cheerio.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Involved Issue / 该 PR 相关 Issue
Close #23059
Example for the Proposed Route(s) / 路由地址示例
New RSS Route Checklist / 新 RSS 路由检查表
PuppeteerNote / 说明
新增 Hugging Face 用户帖子动态路由,补齐
huggingfacenamespace 下缺失的 posts 类型(现有
blog、blog-community、daily-papers、models、user-likes均无用户帖子)。实现说明:
数据来源:Hugging Face 未提供按用户过滤的公开帖子 API
(
/api/posts?author=的author参数被服务端忽略,始终返回全站最新条目;/api/users/{user}/posts返回 404;/api/social-posts需要认证)。因此本路由读取
https://huggingface.co/{user}/activity/posts页面,该页为 SvelteKit 服务端渲染,帖子数据完整嵌入在
data-target="UserProfile"节点的data-props属性中,无需浏览器渲染即可提取。条目数量:服务端渲染的首屏数据包含最新的 2 条帖子(
?p=等分页参数对该页无效),路由直接输出这 2 条。
totalPosts字段仅用于参考,未作为分页依据。全文输出:
rawContent为帖子原始 Markdown,经markdown-it渲染为 HTML 作为description,因此订阅端可直接获得全文与内嵌图片。反爬:Hugging Face 部署了 AWS WAF,短时间高频请求会返回 429。
已将
features.antiCrawler置为true,RSSHub 的请求层自带重试与退避。时间:
publishedAt为 ISO 8601 UTC 时间,统一交由parseDate处理。本地验证(示例用户
AbstractPhil):/huggingface/activity/AbstractPhil/posts→ 2 条,标题、链接、pubDate、作者均正确https://huggingface.co/posts/AbstractPhil/372092347372730