41–50 of 266 posts
I use this: https://camas.github.io/reddit-search/ Search Reddit comments and posts by keyword, user, sub, or all three. Includes deleted comments and posts.
Interesting, I wonder what they used for the search database, since that enormous amount of text can't fit in RAM, it would have to be partitioned & sharded in something like Scylla DB
You can rent from various cloud providers many VMs with 2TB of ram each. AWS also offers some high memory machines with up to 24TB of ram in some locations.
Interesting, I wonder what they used for the search database, since that enormous amount of text can't fit in RAM, it would have to be partitioned & sharded in something like Scylla DB
At one point, their search used LucidWorks Fusion [1], a commercial product based around Solr (that uses Lucene indexes under the hood) but also integrates a vector database and the like for semantic search. The linked wiki page still has Lucene-style queries. [1]: https://lucidworks.com/customers/reddit/
Interesting, I wonder what they used for the search database, since that enormous amount of text can't fit in RAM, it would have to be partitioned & sharded in something like Scylla DB
I doubt that a succinct full text index (like an FM-index) of this data would require more than a modest server to keep in memory. Why aren't these used in this context?
You could use it to easily find any ongoing conversations on the site, about , anywhere, and thereby be laser focus on artificially butting into the discussions about that thing. If this became common practice, perhaps we will see people externally agreeing to proxies for certain words so they can discuss certain topics publically on reddit without getting "jungled". Or maybe the feature isn't going to be used that m…
You see this on Twitter sometimes -- people talk about "en eff tees", I think both to avoid people searching for the term and to be seen by people who have "NFT" muted.
Earlier quoted context omitted.
For (1), a userscript like this does wonders. There's also a way to replace new-reddit links with the old-version, but it takes a bit of tinkering to get it to work on google. // ==UserScript== // @name old_reddit // @description replaces www.reddit with old.reddit // @match *://www.reddit.com/* // ==/UserScript== const url = new URL(window.location.href); window.location.replace(`https://old.reddit.com${url.pathname…
Or just log in and tick the box that says "always use old reddit" and then it will always use old reddit.
Earlier quoted context omitted.
For (1), a userscript like this does wonders. There's also a way to replace new-reddit links with the old-version, but it takes a bit of tinkering to get it to work on google. // ==UserScript== // @name old_reddit // @description replaces www.reddit with old.reddit // @match *://www.reddit.com/* // ==/UserScript== const url = new URL(window.location.href); window.location.replace(`https://old.reddit.com${url.pathname…
Or just log in and tick the box that says "always use old reddit" and then it will always use old reddit.
e.g, you want to browse for a gift for your SO and you're review-hunting, but you don't want it showing up in your sidebar as a recently viewed thread, or being in your history, or whatever - so you don't sign in. Userscripts/extensions force old.reddit.com regardless.
Earlier quoted context omitted.
You see this on Twitter sometimes -- people talk about "en eff tees", I think both to avoid people searching for the term and to be seen by people who have "NFT" muted.
There's also certain people with very vocal fanbases who do this. Sometimes I'm rather happy Twitter added the feature to restrict replies to your follows.
Earlier quoted context omitted.
> Right now, we internally blacklist the account so that the data is not exposed via any public API. For full disclosure, we currently do not permanently delete any data unless there is a major issue involving PII, etc. While you have the right to request that people cannot search your comments and submissions via the public API, we reserve the right to keep data in our private archive so long as we never allow any d…
> we reserve the right to keep data in our private archive so long as we never allow any data that you requested be removed get exposed through any public API endpoints. This is why I'm really happy to have GDPR. If this were a European company someone would eventually tear them a new one. "Reserve the right" is a cheeky choice of words for keeping data that isn't theirs against people's consent.
How is it "your data" if you use their property (reddit.com) to post content on their website? IP and other PII I can understand, as reddit gets that no matter what interaction you do with the website, it makes sense to protect that. But as soon as I make this comment on HN, I don't really expect to "own" this comment anymore, it now belongs to news.ycombinator.com.
Earlier quoted context omitted.
For (1), a userscript like this does wonders. There's also a way to replace new-reddit links with the old-version, but it takes a bit of tinkering to get it to work on google. // ==UserScript== // @name old_reddit // @description replaces www.reddit with old.reddit // @match *://www.reddit.com/* // ==/UserScript== const url = new URL(window.location.href); window.location.replace(`https://old.reddit.com${url.pathname…
Or just log in and tick the box that says "always use old reddit" and then it will always use old reddit.
Not sure if it's just me, but that setting seems to frequently get reset, as I tick that box maybe once a week/two weeks or something, but I keep getting sent to the new reddit at one point. Maybe I accidentally access new.reddit.com which forces the new layout and then reset the setting?
In any case, I'm giving one of the new -> old redirection extensions a try now instead.