#吐槽
In reply to nevent1q…tnak
_________________________
1. 登录 https://npub.pro
2. 选择主题
3. 新建站点
via Nostr@cxplay
In reply to nevent1q…tnak
_________________________
1. 登录 https://npub.pro
2. 选择主题
3. 新建站点
via Nostr@cxplay
#吐槽
Blogspot, but on Nostr.
via Nostr@cxplay
Blogspot, but on Nostr.
quoting
nevent1q…yrtx
RSS feeds are live on nostr sites!
There are millions of people using RSS reader apps to follow their favorite publications. Your nostr-based websites are now serving these people well.
If your friends and family are using RSS readers, this is your chance to have them follow your nostr posts.
Just append /rss/ to home or tag or author page address to get a corresponding feed.
If you're publishing a podcast, the RSS feed of your podcast can now be served by your nostr site.
We are one step closer now in bridging nostr to the existing web ecosystem. Let's go!
via Nostr@cxplay
Npub.pro (npub1pr…xmkzp)
Short Text Note by Npub.pro
seen on relay.primal.net, nostr.mom, relay.noswhere.com
#吐槽
In reply to nevent1q…fs48
_________________________
njump's recent strategy for fetching the latest notes from authors has made RSS feed very fragile. Simply put, njump now prioritizes fetching author notes from the local cache database, but if someone uses njump to open a new note that is not in the cache database before the cache is refreshed, the sorting of the RSS feed is broken and the timeline in the RSS is no longer complete until the cache is refreshed.
via Nostr@cxplay
In reply to nevent1q…fs48
_________________________
njump's recent strategy for fetching the latest notes from authors has made RSS feed very fragile. Simply put, njump now prioritizes fetching author notes from the local cache database, but if someone uses njump to open a new note that is not in the cache database before the cache is refreshed, the sorting of the RSS feed is broken and the timeline in the RSS is no longer complete until the cache is refreshed.
quoting
nevent1q…2jxk
但是只要事件在 24 小时刷新间隔内被提前缓存进了本地数据库, 这个 RSS/Atom 路由生成输出的时候就会立马读取, 比如有人主动用 njump 预览了一个还没有进入缓存的作者的事件, 那这个 RSS/Atom Feed 排序就直接乱掉了, 而没有被主动用 njump 预览过的事件就不会进入 Feed.
现在魔改了一下, 把 RSS/Atom 路由单独进行单独的判断, 不缓存也不从本地数据库读缓存事件, 每次有请求才立马从预设的外部中继里请求并生成 Feed, 请求数量也从默认的 100 条调到了一般 RSS Feed 常用的 20 条. :eveonecat_coffeebath: (实际生成 Feed 的的 entry 数量可能会多于这个数)
虽然 njump 给 Feed 的 .xml 设置了缓存控制标头, 但是基本上绝大多数的 RSS 阅读器都不会遵守, 于是还得用 CDN 强行给 .xml 缓存一遍(虽然缓存标头还是遵守源服务器).
PS: 总感觉还会有什么奇怪bug.
via Nostr@cxplay
#吐槽
@[email protected] 这里是 Fediverse
----------------------
CXPLAY(@cxplaygo@threads.net) says:
❤️
RE: https://www.threads.net/@bugcat_capoo/post/C-KnrB3hC4z
via CXPLAY (@[email protected])
@[email protected] 这里是 Fediverse
----------------------
CXPLAY(@cxplaygo@threads.net) says:
❤️
RE: https://www.threads.net/@bugcat_capoo/post/C-KnrB3hC4z
via CXPLAY (@[email protected])
#吐槽
用 uBlock 伪装 CSDN 为登录状态:
```
csdn.net##+js(set-cookie.js, "UserName", 0)
```
—— https://fixupx.com/xymopen/status/1805642668355338340
#AdGuard 版本:
```
csdn.net#%#//scriptlet('set-cookie', 'UserName', '0')
```
via Nostr@cxplay
用 uBlock 伪装 CSDN 为登录状态:
```
csdn.net##+js(set-cookie.js, "UserName", 0)
```
—— https://fixupx.com/xymopen/status/1805642668355338340
#AdGuard 版本:
```
csdn.net#%#//scriptlet('set-cookie', 'UserName', '0')
```
via Nostr@cxplay
真是 "史诗级" 更新
quoting
nevent1q…t3cn
Replies from the Fediverse can now be read on Threads!!
/cc npub10fp3ehl8utp98zgk6lx87uwkfxm9zq6z9varapeuluz9cdf3zfvs94qqev (npub10fp…qqev)
via Nostr@cxplay
#吐槽
In reply to nevent1q…9c3q
_________________________
最保险的做法还得加 http/https 协议头, 不过这样对分享的人来说可能更不方便.
https://b23.tv/BV1RCvseVEZZ
via Nostr@cxplay
In reply to nevent1q…9c3q
_________________________
最保险的做法还得加 http/https 协议头, 不过这样对分享的人来说可能更不方便.
https://b23.tv/BV1RCvseVEZZ
via Nostr@cxplay
CXPLAY (npub1gd…ch58h)
Short Text Note by CXPLAY (reply)
seen on relay.momostr.pink
#吐槽
In reply to nevent1q…mem9
_________________________
今天汤含量依旧充足
🐷老师下次发 BV 号可以这样
b23.tv/BV1RCvseVEZZ
加个 b23.tv 开头就可以让网友看到网页预览了
via Nostr@cxplay
In reply to nevent1q…mem9
_________________________
今天汤含量依旧充足
🐷老师下次发 BV 号可以这样
b23.tv/BV1RCvseVEZZ
加个 b23.tv 开头就可以让网友看到网页预览了
via Nostr@cxplay
Expensive Social
quoting
nevent1q…ekr4
nothing too crazy:
it costs me about $288 per month for a 32gb ram dedicated server
via Nostr@cxplay
#吐槽
In reply to nevent1q…z22s
_________________________
Nice. And maybe you need fix your NIP-05 addr's CORS issue:
https://cors-test.codehappy.dev/?url=https%3A%2F%2Flecturify.net%2F.well-known%2Fnostr.json%3Fname%3Dyonle&method=get
via Nostr@cxplay
In reply to nevent1q…z22s
_________________________
Nice. And maybe you need fix your NIP-05 addr's CORS issue:
https://cors-test.codehappy.dev/?url=https%3A%2F%2Flecturify.net%2F.well-known%2Fnostr.json%3Fname%3Dyonle&method=get
via Nostr@cxplay
#吐槽
In reply to nevent1q…j0m5
_________________________
I finally found the problem... It has to do with the `noscraper` option in the config file, which when true causes the configuration of `authorized_keys` to invalid.
via Nostr@cxplay
In reply to nevent1q…j0m5
_________________________
I finally found the problem... It has to do with the `noscraper` option in the config file, which when true causes the configuration of `authorized_keys` to invalid.
via Nostr@cxplay
Yonle (npub1x3…3g4el)
Short Text Note by Yonle (reply)
seen on offchain.pub, relay.primal.net, relay.noswhere.com, relay.nostr.band
#吐槽
In reply to nevent1q…6ux9
_________________________
Yes, I have completely rebooted. I even tried to <node bostr_cli.js start config.js>, but it still doesn't work. And I tried checkconf, no problems, I don't know why.
via Nostr@cxplay
In reply to nevent1q…6ux9
_________________________
Yes, I have completely rebooted. I even tried to <node bostr_cli.js start config.js>, but it still doesn't work. And I tried checkconf, no problems, I don't know why.
via Nostr@cxplay
In reply to nevent1q…3vqv
_________________________
I have the same concern. I found that NIP-42 read authentication doesn't seem to work, I set authorized_keys but still everyone can read my bouncer.
via Nostr@cxplay
