𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍

       🅸 🅰🅼 🆃🅷🅴 🅻🅰🆆. 
 𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍 𝖋𝖊𝖆𝖙𝖍𝖊𝖗𝖘𝖙𝖔𝖓𝖊𝖍𝖆𝖚𝖌𝖍 
  • 5 Posts
  • 199 Comments
Joined 2 years ago
cake
Cake day: August 26th, 2022

help-circle
  • Duh.

    I lived in Germany for two years, and when I returned I visited the mother of one of my high-school girlfriends who'd been living in the States since she'd moved there from Germany when she was 20. So, she was around 40 at the time. Anyway, me, fresh from DE and pretty fluent in German tried to have a conversation with her in German and, after a couple of minutes she switched to English and said, "I'm sorry. I've just forgotten too much German to have a conversation in it." She seemed sad about that.

    But oddly, the reverse had been happening to me off and on since I'd gotten back. I'd been living with a German girl over there who didn't know much English, and I hadn't spoken English much in the past 18 months. For about a year after I returned I'd occasionally be unable to remember the English word for common things, like "trash can," and have to ask whoever I was talking to to remind me what it was.

    Doesn't take much, honestly.




  • Maybe because not every system is Debian, and Plasma has to work on systems that either don't have /usr/share/i18n/supported or put is somewhere else?

    I manage a project that encounters this sort of thing regularly; my biggest problem is terminfo entries. Not all distributions contain all of the same terminfos. It is one of the biggest source of bug reports my project gets. I've been considering just embedding all of the terminfos in my project, just so I know they'll all be there on every system it's installed.

    I don't know this is Plasma's reason for including their own list, but it could easily be. It could also be because those are the locales Plasma supports, and it may not support every locale that might be in the distro system list.



  • Sure, why not? I have a couple of questions following a list of observations.

    The About page says it's a Java Spring Boot application, though... so the Go component is limited to a federation service?

    The docs are all stub pages, so it's a hard to figure out what it's all about, and the Demo link leads to a standard Lemmy instance, complete with "Support Lemmy" hamburger menu entry. What's differentiating this project, and what's the motivation?

    So of the projects under the github umbrella is the federation service (which you clearly state is the problem domain of this component). There's quite a bit of scaffolding in that project; is the issues list of (8 currently) enhancements the sort of thing you're looking for help with?


  • UK server, OK. Fine. But OP has never been to Pennsylvania in the US. Most houses over a hundred years old look like this: you can see the generations that have lived in it. First it's stone and mortar; then there's a wood addition ca. the early 1900s; then there's a more modern addition ca. the 50's or later. There's one property that was briefly famous as it came up in Zillow that had 5 clearly distinctive styles and technologies worth of additions on it; it's like every generation added another room with whatever was in style at the time. I can't find a picture, but it was hideous.

    I don't know if it's common all along the mid-Atlantic, but it is super common in Pennsylvania.






  • It's taken me forever to reply because (a) I feel guilty about short replies to long messages, (b) I had to think about this a bit, and (c) I almost exclusively access Lemmy on my phone and I hate typing long messages on my phone. Not an excuse, just an explanation. There are no good Lemmy desktop clients, but I've finally logged in to my instance's web interface to respond to this. 3 months later.

    So, yeah. I honestly didn't pay much attention to whatever backstory the software authors were selling; I was looking for a feature set, and Session had it. I got some of my circle using it, and we eventually stopped because message delivery reliability was iffy, and there were enough of some UI issues with (e.g.) attaching photos that everyone drifted back to what we were using before. I'm sure Session will improve, but just for the record, I haven't been using it because of technical reasons.

    I don't have an issue with cryptocurrency per se. There are issues with current implementations, but the fact that it's used for laundering money or scamming people is also an argument that can be made for fiat money, but you don't see people saying we shouldn't use dollars because a vast amount of them are used to enable the military industrial complex that is killing people around the world. I haven't read that Bitcoin is being used to fund any of the attempted genocides currently underway -- but fiat money has. People have been scamming people using regular money for far longer than cryptocurrency has existed. A lot of people have lost a lot of money trying to get rich in various cryptocurrencies; do you think more people have lost more money in cryptocurrency than people have lost trying to dabble in the stock market? Have more fortunes been ruined by cryptocurrencies than were ruined by the collapse of the "legitimate" currency of Germany during the Weimar Republic? And what, exactly, is a "fake economy?" If people are willing to exchange goods and services for A Thing -- whatever that Thing is -- it's a real economy by definition. The argument that because the currency isn't endorsed or backed by a government means it's not real seems debatable, at best.

    While I think a debate about the relative merits and evils of cryptocurrency is a good thing to have, since the OP topic was messengers, to answer your questions: in the entire time I used Session -- and though today it's still on my phone and receiving messages, although nobody's sending any -- I would not know that the developers behind Session had some grander vision involving cryptocurrency unless it had been brought to my attention here. That they want to improve privacy by using an anonymous method of payment for services -- one not based on the collection and sale of metadata, or on a traceable currency (which all electronic fiat transactions are) seems reasonable. I imagine that, eventually, they'll build something like Lightning into the app, so users can transfer cryptocurrency to other users, or to the operators of their servers. If it ever gets to the point where you must pay to use the service using crypto, then maybe I'd be concerned. It'd be no worse than buying tokens at a video game arcade -- a practice that was around for more than a decade without an indignant uprising.

    I think it feels sleezy to you because the devs are also interested in integrating cryptocurrency into the Session ecosystem, and you believe cryptocurrency=bad. I think it doesn't feel icky to me because I've been working as a software developer since long before Bitcoin was introduced; and I understand how blockchains work, and know what "proof-of-work" means and what it implies; and I've watched the evolution of the internet and the growth of the web, and lived through the eternal September; and I saw how email turned from a communication tool for people in higher ed into a way for scammers (and legitimate businesses) to deliver spam. And I believe that a very many people will try to take advantage of other people and take their money, and they'll use any possible tool to do so. But I believe that scamming is not fundamental to the nature of cryptocurrencies in the same way that killing people is in the fundamental nature of a gun, any more than buying heroin is fundamental to the nature of a dollar bill.



  • Related, but just hanging this on here. As the default (as installed) security of distributions has improved, so have the amount of headaches when trying to use tools like this increased. For decades, when I've had issues like this is not been because of a LAN firewall issue, and so now my first thought is never been, "I should check the firewall," when it should.

    Sadly, firewall info is almost always locked down so that apps can't even check by themselves and provide helpful hints to users.

    Anyway, it's been a hard lesson for me to learn, for some reason. I need to practice my mantra: it's always the firewall.





  • There's an unavoidable overpass between me and where we get groceries with 3 lights on it. They're timed such that, heading in either direction, you'll hit one red if you follow the speed limit. They may have sensors, but they change with no cross-traffic as well. However, if you catch the first light in green, and speed by between 7-10 over the speed limit (35), you can get through all 3 without stopping. It's an overpass with no residential nearby; this is the only place I regularly blow through.

    I have no idea what the civic engineers were thinking when they progammed those lights. I assume incompetence; what I think really happened is that at one time that stretch was 45, like both sides of the overpass, and they were programmed for 45, which would normally get you through with no stops. Then some asshat changed the speed limit of that stretch to 35 without reprogramming the lights.

    Anyway, the point of my long story is that sometimes going around isn't feasible. When it is, it's a great tactic, though!