Hacker News new | past | comments | ask | show | jobs | submit | nmz's comments login

Not a bad idea, light enough to implement a telegram bot everyone can use or email or maybe a bitlbee plugin so you can have a twtxt channel.

But, what is it? can you PM someone? participate in a conversation? or is it just that, a microblog? Usability wise what will you do? keep a client running that always checks if new blogs have happened over, how many followers? I'm currently following 500 people, that's 500 connections if this takes off.

It would be nice if an rss client supported it, until then ehh


Honestly the first thing I do is get busybox, busybox's behavior is at least somewhat predictable.

Your claim is not false, but not universally true either, the counter is alex jones, the flat earth movement, religion as well, you can spend nearly an infinity believing in lies. The human brain is quite malleable to lies.


If all you believe are lies, what's the difference?


Does static compilation use the entire library instead of just the parts that are used? If I'm just using a single function from this library, why include everything?


Poettering does work for microsoft.


Reminder to look at the twitter user "shithnsays"


Labeling, fstab is supposed to be a .tsv, what happens if I mistype something? where's the safety? Does this need to be a DSL?


> Linux’s io_uring is a relatively recent addition that improves asynchronous I/O, but it has been a significant source of security vulnerabilities and is not in widespread use.

Funny, opening the manpage of aio on freebsd you get this on the second paragraph

> Asynchronous I/O operations on some file descriptor types may block an > AIO daemon indefinitely resulting in process and/or system hangs. > Operations on these file descriptor types are considered “unsafe” and > disabled by default. They can be enabled by setting the > vfs.aio.enable_unsafe sysctl node to a non-zero value.

So nothing is safe.


those are unsafe from different perspectives - AFAIR, io_uring just passed some/many filtering mechanics applied to other subsystems in kernel when say reading/writing files, so security frameworks could not be enforced. Something about auditd subsystem as well.


Saving disk space and synchronization is only important for network transmission. At the local level, you will need to convert to something where you can get/know positioning, utf8 does not allow for this given its variability, this means a lot of operations are more expensive and you will have to convert to utf16 anyway.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: