Hacker Newsnew | past | comments | ask | show | jobs | submit | aragilar's commentslogin

Sixel and ReGIS have been around for decades.

Google wiped all of UniSuper not too long ago by mistake, I don't see why such a occurrence couldn't happen more widely.

This definitely seems like a sensible starting option to generate 256 colours from a custom set of 8 (and then let the really pedantic users fiddle with the extended set). I would presume for "standard" themes these values would be pregenerated and adjusted slightly if needed.

It's not only the transition from low -> high that removes communities, there are multiple examples of public housing communities (of medium to high density) replaced by similar (or effectively low) density (as new expensive apartments) within Sydney.

I think it depends on how you're interacting with the instance/server. I find the rust zulip much easier to follow than the k8s slack (or the lancer discord). I can see on a (much) quieter instance where it's a group of friends you want to see most messages where a single channel is a better option.

I agree with this. We use Slack at work, where we have a small team, and most of us are reading most messages in realtime. It works*

Contrast that to my experience with a group of volunteers who might log in a couple of days a week, communication is a lot more async, and you might not care about all the topics of discussion. I have found Zulip makes it easier to come back and catch up on just the bits you care about.

*I still think Slack encourages a "continuous partial attention" way of engaging with chat that I don't like. But, we do make it work.


It's not a technical problem, it's a policy problem from the mobile vendors. You'd basically be paying them to deal with Apple's and Google's messaging infrastructure through their (zulip's) infrastructure.

Would it not be better to report accounts then?

To whom? It's not against Github's ToS to submit a bad PR. Anyway, bad actors can just create new accounts. It makes more sense to circulate whitelists of people who are known not to be bad actors.

I also like the flexibility of a system like this. You don't have to completely refuse contributions from people who aren't whitelisted, but since the general admission queue is much longer and full of slop, it makes sense to give known good actors a shortcut to being given your attention.


Sufficiently bad PRs/comments/etc. are against the GitHub Terms of Service, look under section C (Acceptable Use), which links to https://docs.github.com/en/site-policy/acceptable-use-polici..., which then includes https://docs.github.com/en/site-policy/acceptable-use-polici..., on which you'll find multiple actions would describe posting AI slop (or things ancillary to it).

I wouldn't do this where it's not clear there was an issue, but for something like the really poor OCaml PR that was floating around, reporting the user to me seems like a logical step to reduce the flood.


It depends. Grant funding (e.g. in academia) makes capex easier to manage than opex (because when the grant runs out you still have device).

https://www.ecosia.org/ seems to have no issue with neocities (whereas searching neocities in duckduckgo does not show it except in the wikipedia callout).


It's the same problem. Search for "fauux" (one of our more popular web sites) and you'll see other sites talking about one of the more popular sites but you won't see a link to the site itself.


Podman is in Debian and has been for a while (and so will eventually propagate to all its derivatives). I would presume Arch and SUSE have it, not sure about Gentoo, what other host distros are missing?


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

Search: