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

Äike scooters, company went bankrupt.

Please don't make any more URL shorteners, they are just a bad idea.

https://wiki.archiveteam.org/index.php/URLTeam


I always end up making my own, they're so simple to write.

Saves using one of the "free" ones which looks like its free but you're actually on a free trial, then you can't access your links after that trial expires.


Way to miss the point of the project!

git rebase conflict resolution is a lot less scary with the zdiff3 merge.conflictStyle option.

Also incremental rebasing with mergify/git-imerge/git-mergify-rebase/etc is really helpful for long-lived branches that aren't merged upstream.

https://github.com/brooksdavis/mergify https://github.com/mhagger/git-imerge https://github.com/CTSRD-CHERI/git-mergify-rebase https://gist.github.com/nicowilliams/ea2fa2b445c2db50d2ee650...

I also love git-absorb for automatic fixups of a commit stack.

https://github.com/tummychow/git-absorb


So many people don’t know about git-absorb! It’s fantastic.

IMAP has mechanisms to notify clients about incoming emails (IIRC IMAP IDLE), have you considered implementing those?

IMAP IDLE tends to be unstable and unreliable in real-world deployments, especially for long-running background services. It also introduces significant operational and implementation complexity, which makes it harder to maintain and reason about. For a system like Bichon, a simpler diff-based approach is usually easier to operate and more predictable.

Could you use IDLE to trigger the diffs?

Just change your User-Agent to one that doesn't include Mozilla and you will bypass it. There is a WebExtension that can do that automatically for Anubis sites, or you can just do it more generally.

OpenMoko phones were too underpowered to run Firefox, but they could run a ton of other apps. I was running non-AI automated human language translation on the thing.

From other discussions, it sounds like they are shipping the copyleft source on time, only the permissive/pushover licensed stuff gets delayed source releases.

FSFE campaign for that: https://publiccode.eu/

One should never use the vendor software shipped on a device, always replace it with a FOSS distro that respects your privacy.

Hopefully the Vizio lawsuit that is going to trial soon will help make that more possible.

https://sfconservancy.org/copyleft-compliance/vizio.html

Two recent LWN articles about that:

https://lwn.net/SubscriberLink/1052842/52c45fb8bcc3fade/ https://lwn.net/SubscriberLink/1052734/5903e175673caeef/


The tentative ruling in that case isn't overly hopeful, with issues 2 & 3 probably going to be dismissed.



Why not have the LLM write machine code (or assembly) directly?


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

Search: