Silver Bullet

Just for record, and will remove if they have fixed this problem.

Alert. Patch 3 points is not enough. It would wrongly use names for ldi and std and some other instructions. Better ask for a fix...

I'm happy to see E2E as a feature to ensure every content being pushed is only visible for the push source and the certain recipients, and not readable for either...

有反例？

高老师，请问考虑支持下IPV6吗？现在逐渐成熟了 @paulgao

well, i'm working on my own branch. maybe a pull request tomorrow.

I have finished the part of [sending scheduled toots](https://user-images.githubusercontent.com/6560655/209479160-c1aab8f7-0974-4896-9b9b-10a6f5c85c65.png). But managing them is not that easy. I'm not a senior developer for mastodon so I think I should seek some...

Thanks for the comment! I'm going to test it later ;)

要看你这是啥情况…… 比如我的做法是，先 ``` sudo ip route add {chnipcidr} via {pppeth} dev {pppdev} table {tableid} ``` 然后 ``` sudo ip rule add from all table {tableid} ``` 接着拨VPN。这时候我没发现有断网现象，感觉这似乎是因为出口路由没变。但是如果先拨VPN再去动路由表的话就会有……

Hi @Luap99, I have an implementation on [my dev branch](https://github.com/SilverBut/netavark/tree/dev). Should I make a PR? But I'm changing the proto, and maybe this feature should only be enabled if explicitly...