Since it is attached to the memory controller, one could argue that it is truly the final level of the cache hierarchy and the term infinity is not only a marketing term.
But then you could add another level of slower (but still faster than RAM) and larger cache. So it is after all the CPU caches, but the first of all the memory caches. A more mathematically correct name would be L_omega.
I intentionally drop all messages from time to time (typically once I get a new device). Am I the only one who feels like loosing old conversations is just fine? After all, I don’t remember all conversations I had in person as well.
I understand that loosing them at an unexpected time can be annoying and a backup is useful, but I personally never had a use for that feature and knowing that it is annoying for someone to keep all my messages around forever is something I consider positive.
Yes. I keep my iMessages forever, and even back them up (as well as my photo library) as part of my desktop backups.
I’m switching my social networks to Telegram after Signal burned up its good will focusing on features they want versus what their users want. Do I care if it’s as secure? No, I prefer the convenience and superior UX iMessages and Telegram offers.
Really unfortunate, as it was Signal’s race to lose after their bump in usage and shoutouts from popular folks using it.
I don't generally need to preserve all my messages forever, but I often do refer to recent ones, say from the last few weeks. I have switched devices a couple of times with Signal only to be stuck thinking "oh crap, did I agree to do X on Th or Fri?" The lack of sync for SMS with their desktop client also makes it basically useless to me, I'm sure that's more secure, but I wouldn't mind being to opt-out, especially on a contact-by-contact basis.
> Am I the only one who feels like loosing old conversations is just fine?
Same here - but maybe if doing Business then somebody might want to keep them (e.g. to keep track of whatever your customers told you in the past? Just a guess...).
(btw. I think it's not "loosing" if you don't mean something like "letting them free", but "losing". "losing" vs. "choosing", I kept mixing that up until recently... :P )
What I would like as a feature in Signal is "polls" (e.g. to choose with a few friends to which bar/restaurant to go, when to meet, whatever).
But now unluckily I'm back on Whatsapp as even after having abandoned it, within almost 2 years most of my friends refused to install Signal -> in the end, on 31.Dec.2021, I decided to admit that I failed, and I reinstalled Whatsapp :(
> Am I the only one who feels like loosing old conversations is just fine?
I find text based instant messaging to be shallow and vapid and I have very little interest in them. Texting is best used (for me at least) to coordinate real life plans (I'll be in front of X at Y o'clock) or quick task-oriented notes (Hey babe, can you grab some sliced turkey if you're still at the store). If you want to actually talk to me, call me or let's meet in person.
This attachment to one's messaging archive is IMO a symptom of data hoarding. 99.9% of text conversations won't be interesting in the future because they weren't interesting when they were happening.
That said I do like enjoy the feature where all of the photos from a given conversation are easily accessible.
The first message I got from my girlfriend was a response to me sharing some music with her and asking for a song back. She sent a small video of her cat complaining.
If I could have backups of entire conversations, I wouldn’t have to export and save every single video and picture being sent with Signal.
I recently decided to watch a movie that my ex-girlfriend had recommended to me, and I was able to quietly search for it in the chat history since we're no longer on speaking terms so I couldn't ask her.
On the other side, when I broke up with her I also used the chat history to point out some times she had tried to lie to me. That was a bitter satisfaction I could probably have done without.
Hey sorry I saw this a couple of days late. Glad you think it's cool! It's closed-source at the moment, but I do dive into technical details in newsletters [0] whenever I can. If you prefer RSS [1] we have that too.
>Am I the only one who feels like loosing old conversations is just fine
not only do I think it's fine I think it's actually healthy. I think the ability to search and turn over every word said in the past can produce some pretty neurotic and bad behaviors. There's a fun Black Mirror episode about this in one of the earlier seasons.
I set signal to auto delete messages older than 2 weeks. There is zero reason to keep messages of a personal relation longer than that, for me at least. I am prone to nostalgic romanticizing, and not having access to past messages kind of solves that problem.
Same here, I don't get that insistence on backups at all but I get that others might feel differently. I wouldn't be surprised that this is more prevalent in us techie types than the average user of chat apps.
The only difference I notice between this and Wikipedia is that I can't hover over a link and get a pop-up description of the page. Is that all or is there more to it?
> https://wikiless.org - a free open source alternative Wikipedia front-end focused on privacy. No JavaScript or ads. All requests go through the backend, client never talks to Wikipedia. Prevents Wikipedia getting your IP address. Self-hostable. Anyone can setup a private or public instance.
From the README [0] and code, I'd wager that the only thing happening is that JS has been filtered out, that the CSP rules are significantly stricter and that a dark mode has been added.
Similar for dnscrypt-proxy: add "forwarding_rules = '/etc/dnscrypt-proxy/forwarding_rules.txt'" to /etc/dnscrypt-proxy/dnscrypt-proxy.toml and then populate the forwarding_rules.txt with lines like "archive.is 8.8.8.8".
I am an HPC engineer, who is currently working in the embedded/automotive area.
Location: Germany, Stuttgart
Remote: Yes
Willing to relocate: Most likely not outside of Germany
Technologies:
- C++, Go, a bit of Rust
- Embedded middleware, OS kernel, hardware debugger
- OpenMP, MPI, CUDA (your usual HPC stuff)
Résumé/CV: https://jensbreitbart.de
Email: please click on the "Contact me" link on my homepage
