Has there been research on using this to make models smaller? If models converge on similar representations, we should be able to build more efficient architectures around those core features.
Readit NewsTheSaifurRahman commented on All AI models might be the same blog.jxmo.io/p/there-is-o... · Posted by u/jxmorris12
TheSaifurRahman commented on All AI models might be the same blog.jxmo.io/p/there-is-o... · Posted by u/jxmorris12
This only works when different sources share similar feature distributions and semantic relationships.
The M or B game breaks down when you play with someone who knows obscure people you've never heard of. Either you can't recognize their references, or your sense of "semantic distance" differs from theirs. The solution is to match knowledge levels: experts play with experts, generalists with generalists.
The same applies to decoding ancient texts, if ancient civilizations focused on completely different concepts than we do today, our modern semantic models won't help us understand their writing.
What's so different between this and the other sites that already do this?
domain name maybe
TheSaifurRahman commented on Notetime: Minimalistic notes where everything is timestamped notetimeapp.com... · Posted by u/gohberg
I see a lot of people mentioning how easy it is to add a timestamp using a shortcut or git blame, but that overhead could kills note-taking. Both writing and lookup/review should be extremely fast.
TheSaifurRahman commented on Notetime: Minimalistic notes where everything is timestamped notetimeapp.com... · Posted by u/gohberg
I've dedicated Sublime Text specifically for my development notes. I use a single folder in my home directory for all these notes. Every new tab gets a timestamped name and this directory assigned (Yes, my sublime's default behaviour is now this), so if I save it, it goes there.
I also have a shortcut to save all files at once, which is great because I end up with a lot open by the end of the day.
It helps keeping track of info I might need later, like backups, text transformations, optimizing DB queries, curl calls, less important passwords, refining emails with LLMs, drafting prompts, etc.
I love how fast my workflow is now: just switch to sublime, open a new tab, type away, and hit `CMD + Y` to save all at the end of the day or week.
For lookup: Mostly, I remember a few keywords and search across files. They're timestamped, so they're sorted in the sidebar (e.g., `2025-03-20_11-02-15-77dee966.txt`).
Shoutout to Odatnurd, who helped me code the plugin and live-streamed it (link in the forum): https://forum.sublimetext.com/t/how-to-auto-save-unsaved-tab....
Things I wish I had:
1. Structure (A scrollable view, with expandable notes, date range picker, better search)
3. Encrypted backups
I find that there are different kinds of ways in which I think of notes (or note types):
1. Dev notes (scratchpad)
2. Thoughts and logs (don't lose it, when did that happen)
3. Long notes we study/review (lecture notes, obsidian)
I feel Notetime is great for [2]. It's a great idea for building a similar sublime plugin.
TheSaifurRahman commented on Launching RDAP; sunsetting WHOIS icann.org/en/announcement... · Posted by u/radeeyate
Just noticed that someone is going and down voting any mention of any implementations of rdap clients for this news item. Very strange.
Whois it ;)
TheSaifurRahman commented on Launching RDAP; sunsetting WHOIS icann.org/en/announcement... · Posted by u/radeeyate
https://github.com/openrdap/rdap
Golang, single binary, cross platform, download and use.
I’m assuming this is a client app, and not a server implementation.
TheSaifurRahman commented on Launching RDAP; sunsetting WHOIS icann.org/en/announcement... · Posted by u/radeeyate
Worth mentioning are two open-source RDAP projects that are helping move the internet to a more structured system:
DNSBelgium: https://github.com/DNSBelgium/rdap
RedDog: https://www.reddog.mx/home/2017/12/14/server-1.2.2-patch-rel...
The fundamental nature of Git makes this pretty easy for folks to scrape data from open source repositories. It's against our terms of service and those folks might want to talk with some lawyers about doing it - but as every Git commit contains your name and email address in the commit data it's not technically difficult even if it is unethical.
From the early days we've added features to help users anonymise their email addresses for commits posted to GitHub. Basically, you configure your local Git client to use your 'no-reply' email address in commits and that still links back to your GitHub account when you push: https://docs.github.com/en/account-and-profile/reference/ema...
I think that's still probably the best route. We want to keep open source data as open as possible, so I don't think locking down API's etc is the right route. We do throttle API requests and scraping traffic, but then again there have been plenty of posts here over the years from people annoyed at hitting those limits so it's definitely a balancing act. Love to know what folks here think though.