2
points
paffdragon
Joined 114 karma
- paffdragon parentI think it still works if you set your user agent to something like lynx. I had a custom UA set for Google search in Firefox just for this purpose and to disable AI overviews.
- Concerns were raised regarding the authorship of this paper, validity of the research findings in the context of misrepresentation of the contributions by the authors and the study sponsor and potential conflicts of interest of the authors.
- Are there also similar studies on short-form text like Tweets, HN comments, etc?
- It is also hard for me to understand this angle. While in Russia at the moment and China the "they" is pretty much constant, it is not the case in EU. Why would be in their interest something that can be used against them the moment the tide turns?
- Algolia can also be used as an alternative for the front page, it shows this at #6 for the past 24h
https://hn.algolia.com/?dateRange=last24h&page=0&prefix=fals...
- I love this, and so many good projects mentioned in the comments too. My son just turned three and we still have a real CD player that we use, sometimes, but now often it's streaming from Spotify or NAS. I was just thinking about how to do something similar, thanks for the inspiration ♥
- This is so cool. I'm using BirdNET on Android for a long time and that is awesome, but running continuous monitoring on a Pi is really interesting. I saw there was also a Home Assistant integration for it.
- I rarely buy from Amazon, but some small things I find only there. I ordered some phone accessories last week and needed a little more for free delivery so I added a shampoo. They dropped the shampoo without packaging in a paper bag with all the other stuff, when I opened it, of course, the shampoo was all over everything.
Their packaging and delivery quality is one of the worst. But they are still responsive to customer requests, although that is going down the sewer as well. I get often responses that look LLM/chatbot generated and often not answering my question. Or they try something like, sure I'll get you the refund as soon as you place the order again. Then I insist they refund now and so far I always got my money back.
So, basically their advantage for me is their sortiment (but you need to navigate through a lot of fake and garbage products), free returns and quick refund (often even without a return). But this is not a very strong one and I very rarely open their website - the pile of low quality listing is so off-putting that I generally avoid.
- Sorry, I'm not an Apple user, so I'm not 100% sure if this is about forcing Apple to avoid/break E2E encryption (E2E in the true sense like Proton Mail) in the UK or to give them the keys they already can obtain themselves?
- Maybe the package that requires lazy can somehow declare that requirement, so another package that tries to force not lazy will fail early and realize it needs to replace this dependency with something compatible or change its ways. It definitely adds complexity, though.
- For sending in Mailbox.org webmail there is a thing called alternative senders where I can add email addresses to send from. I have something similar on my Android K9 app, where it's under Manage identities where I can also add the allowed senders.
I set it up a long time ago this way and I'm unsure of I had to somehow configure Gmail to be able to send from my other account. But I have the same also for @live.com and @zoho.com as I was trying different providers. This allows me to easily reply to forwarded emails with the old email addresses.
Edit: I think you got with the alias, didn't know this is what is called in Google https://support.google.com/mail/answer/22370?hl=en#zippy=%2C...
- Sorry, my laptop where I had evolution got a new OS installed and I haven't configured it yet and just started mutt, but my original setup had a local archive folder, with sub-folders per year (I think, I even had a higher level grouping of 5 or 10 years). Unfortunately, I don't have setup right now to check, but I think it was semi-manual, like Evolution was archiving to a local folder automatically, then every new year I just moved the mails from the previous year into a folder).
Re offlineimap, just looked into isync/mbsync suggested here by others, it seems better from the description, I'm probably going to try it when I have some time: https://people.kernel.org/mcgrof/replacing-offlineimap-with-...
- On one machine I have offlineimap.py[1] (with mutt), on the other laptop Evolution[2] that archives my mail locally that I can also export and back up regularly.
- I also have an old Gmail account that I don't use directly anymore. Instead of POP, I set it up to forward everything to my mailbox.org account. It works for me this way for several years now. The only issue is that I don't get the spam forwarded, so you can't see if there are false positives. You can still see it in Gmail if you occasionally log in. For me, since this is a rarely used account, the spam I get is usually indeed spam, so I don't miss it. It might be different for a more active account, though.
- Wouldn't we still need a "Line Separator" character so we can include line breaks in fields and records for formatting purposes?
- Do you have any examples what tends to break? We used pyenv/rbenv/sdkman etc. individually, then moved to asdf and now arrived at mise. Not using yet for CI just developer stuff and so far didn't have issues. But this is quite recent for us, so didn't have to deal with upgrade issues yet.
- Making money from tickets is supporting the wrong behavior of trying to find excuses to ticket you for anything to get extra money - this is often leading to cops looking for cheap ways to get the extra cash where they can get it easily, instead of doing more important work where their chance to ticket you is lower even if more important for safety.
- Isn't it too dystopian to have cars follow you around and report you to authorities? I can easily imagine some bad scenarios.
- some providers accept crypto or even cash in an envelope
- When I read the title I remembered how people in the 90s at my place built their lawn mowers. It was a new thing. My father welded the frame from scrap metal with the motor from a washing machine and some tiny wheels from an old baby stroller lol. It was kind of open source, many people copied or he helped build one. Haha, served us surprisingly well for a time :)
- I use it in docker on a NAS - VictoriaMetrics, VictoriaLogs, Grafana - low resource usage, fast, so far zero issues.
- I finished it anyway:
Your Programming Philosophy
You value clarity and directness in code. You prefer explicit, step-by-step solutions that are easy to understand and debug, even if they require more lines of code. Abstract ↔ Concrete: 0 Neutral Human ↔ Computer Friendly: +6 Human-Friendly
The compass is almost in the middle, just a little up from center towards human friendly. That's fine, since most code you write is for other humans to read, the compiler is writing for the machine, only in critical perf sensitive paths you write for computer-first... The rest was mostly neutral, because what I wrote in the parent, it depends on the situation and it can go either way depending on the project.
- This isn't a good quiz. An example question (and there are many similar ones):
> When refactoring code, I prioritize:
> - Reducing complexity and coupling
> - Improving readability and maintainability
> - Optimizing performance and resource usage
> - Extracting reusable abstractions
Each refactoring has some goal, some driver behind it. It could be slow performance, unmaintenable mess, high coupling, too much duplication etc... Choosing a single answers makes no sense from a programming point of view. And this is the case most questions I have seen so far on the site.
EDIT: After finishing and seeing, I think I understand it a little better why was it structured like this. If you are open to do things differently, your answers probably won't weigh in any one direction in aggregate. But if you have certain biases, you might be leaning towards choosing similar answers that shows up in the end.
- It's not that it is not possible, but whether it's a good idea.
The usual problem is that some team exposes one of their internal tables and they don't have control over what type of queries are run against it that could impact their service when the access patterns differ. Or when the external team is asking for extra fields that do not make sense for the owning team's model. Or adding some externally sourced information. Or the team moving from PostgreSQL to S3 or DynamoDB. And this is not an exhaustive list. An API layer is more flexible and can remain stable over a longer time than exposing internal implementation depending on a particular technology implemented in a particular way at the time they agreed on sharing.
This is, of course, not a concern inside the same team or very closely working teams. They can handle the necessary coordination. So, there are always exceptions and simple use cases where DB access works just fine. Especially, if you don't already have an API, which could be a bigger investment to set up for something simple if it's not even known yet the idea will work etc.
- It's definitely worse for external customers, of course. But it's still not that easy even for internal customers. The main problem is that usually the tables exposed are not meant to be public interfaces, so the team takes on an external dependency to their internal schema. And that other team could have completely different goals and priorities, speed and size, management and end users with different requirements. At some point the other team might start to ask the first team for adding some innocent looking fields to their internal table for them. Also first team might need to make changes to support their own service that might not be compatible with the other team. The other team making queries that are not in control of the team owning the DB, which could impact performance. If possible, it is better to agree on an API and avoid depending on internal implementations directly even for internal customers. There are always some exceptions, e.g. very close or subteams under same management and same customers could be fine. Or if the table in question was explicitly designed as a public interface, it is rare, but possible.
- That moves your API layer to the client library you need to distribute and build for your customers in programming languages they support. There are some cases where a thick client makes sense, but usually easier to do it server side and let customers consume the API from their env, it is easier to patch the server than to ship library updates to all users.