436 points 3 days ago Hacker News but for independent blogs
3 points 4 days ago Bubbles – community-ranked feed of blog posts
3 points 13 days ago A community-ranked feed of blog posts from curated sources
3 points 20 days ago Bubbles – an HN-like link aggregator for the non-tech internet
1 point 28 days ago Bubbles: Blog Post Discovery
4 points 50 days ago Bubbles
6 points 75 days ago Bubbles – HN-like frontpage for personal indie blogs def remove_falsey_values(*args): return [val for val in args if val]
Whereas I'd expect something like def remove_falsey_values(l):
for i in reversed(range(len(l))):
if not l[i]: l.pop(i)
# returned list is linked to input l
return l
a = [1, 0, False, 'foo']
x = remove_falsey_values(a)
x[0] = 2
print(a) # [2,'foo'] * I suspect many existing and reasonable regulations do not meet that "simply caught" classification. @rconti's comment above[1] gives some examples of regulations on process that are not observed in the output (food, child labor). I'll add accounting, information control (HIPAA, CUI, etc), environmental protections.
* Newsroom staff is incentivized to enforce the regulation. It protects their livelihood. From the article:
> Notably, the bill would cement some labor protections for newsroom workers
* Mandatory AI labeling is not impossible to enforce. At worst, it requires random audits (who was paid to write this story, do they attest to doing so). At best, it encourages preemptive provenance tracking (that could even be accessible to the news consumer! I'd like that).
One reason for the regulation is we fear hallucinations slipping into the public record -- even if most LLM usage is useful/harmless. Legal restrictions ideally prevent this, but also give a mechanism for recourse when it does happen. * APL -- I haven't dedicated the time to learning in part because there's little support where I normally work. I'd love for APL to have be adapted like a domain specific language a la perl compatible regular expressions for various languages (april in common lisp, APL.jl in julia).
* regular expressions. https://xkcd.com/1171/
* bugs/issue tracking embedded in git https://github.com/MichaelMure/git-bug/
But I'm more excited for things that fall into the niche/lesser-known side of of unpopular. I love finding the little gems that change how I organize or work with the system. * "type efficiently by saying syllables and literal words" https://sr.ht/~geb/numen/
* I use fasd[0] 'z' alias for jumping to previous directories in shell every day.
* Alt+. in shell (readline, bash) to get the previous commands last argument is another ergonomic time saver that I think is relatively obscure. I have a bash wrapper to combine that with fzf for quick any-previous-command-argument fuzzy search and insert [1]
* zimwiki [2] (and/or a less capable emacs mode[3]) for note taking has served me well for a decade+
* DokuWiki's XML RPC [4] enables local editor edits to a web wiki. I wish it was picked up by more editor plugin developers. (cf. emacs-dokiwki [5])
* xterm isn't unpopular per say, but I don't see sixel support and title setting escape codes talked about often. I depend on a bash debug trap to update the prompt with escape codes that set the terminal title [6]
* are clipboard managers popular? I get a lot out of using https://github.com/erebe/greenclip
The prose on https://mail.cyberneticforests.com/its-not-just-data-its-pos... changed how I think about it: the framework is useful for reasoning, not lazy writing. This bubbles.town submission's title could be light evidence of negative parallelism's utility. (Or, more likely, just the stochastic nature of what's popular when)