wpuckering

The only thing keeping me from using it as my only file explorer is the fact that it doesn’t support SMB shares.

I think the benefit of knowing the names publicly might be the public’s ability to then no longer elect these people, which cuts off the foreign interference at the root, as far as can be done within the country. It might also act as a deterrent for future MPs knowing their names could be released if they too partake in this behavior. It would accomplish stamping out the problem and publicly shaming these people for the rest of their careers.

Not saying it’s realistically feasible or prudent overall to actually release them though.

All good points. There’s definitely no perfect or even close to perfect solution.

Yeah that’s probably the strongest point in favour of letting people pick what they want. But I guess a potential downside of that could be if people start stocking up mostly on only a few select items that everyone else also wants., leaving nothing behind for them. But I guess that’s mitigated by seeing that happen a few times then specifically trying to get even more of those select items going forward.

Yeah that’s a good point. If you can’t see what people are leaving behind, you can’t know what to stop taking more of. I guess you need to generate some short-term waste in order to properly tune things as needed, to hopefully reach a point where you’re reducing waste as much as possible in the longer term.

I wonder if letting people pick their own items really reduces waste more than the hamper system? What happens to items left on the shelf that no one takes? That’s probably the same stuff that would be ignored from a hamper? I’m admittedly pretty ignorant of food banks generally, but I would think that the hamper system would be trying to encourage people to eat whatever they get, to both reduce waste by making sure all items get out there from the bank, and to ensure there’s enough of everything coming in to go around evenly? I can see this maybe resulting in the better items going first, and a bunch of less desirable items always being left behind to rot. Does that tend to happen in this type of system or not?

Can confirm, I’m living there right now. People here tend to take proper personal responsibility for their own garbage and mess.

What a sorry state Canada is in when people are hired out of desperation without proper vetting to ensure they are suited to their jobs, even if there is a nurse shortage.

EDIT: Ah thought I was in a Canada community, my mistake. But I guess there are worldwide problems in healthcare these days.

How do people like this even make it far enough to get this type of job?

Same here, I’ve never had this problem, ever. I don’t even get how it’s possible to not know where your files are being saved if you are the least bit techsavvy.

The ending of Soma.

How does this work? At what URL will this be hosted at?

Ah sorry, just remembered I put my entire instance behind authentication except for the API endpoints required for federation. The comment I was linking to is in this thread. Just describes how all the info you need to properly transform the links is right there in the database records of the entities you want to transform, so this functionality can easily be added without much work.

It is actually trivial. Here’s a walkthrough with one solution for how to do it: https://lm.williampuckering.com/comment/723311

It’s actually easy, here’s an explanation for one simple way you could do it.

On my instance, this post has the URL: https://lm.williampuckering.com/post/171615

On the instance the post originated on, the URL is: https://lemmings.world/post/175809

So on my instance, the post has the ID: 171615

On the originating instance, the ID is: 175809

In the database on my instance, this query will retrieve the post: select * from post where id = 171615

Also in the database on my instance, this query will retrieve the post: select * from post where ap_id = 'https://lemmings.world/post/175809'

Using the second query and finding the post by URL, I can see if the post is federated to my own instance or not. If so, I can look at the id field in the database and merely swap it out with the originating instance’s ID, and form the URL to access the post as it exists on my own instance. If the post isn’t federated on my own instance, then of course this won’t work. But that makes total sense, since you won’t be able to transform links for external instances to the corresponding entity on your own instance, because it doesn’t exist there.

tl;dr - You can look up local entities by ID, and you can lookup remote entities by original URL. Then you just need to swap the ID in the URL to the ID (primary key in the table) in the database, if it exists, to convert a remote link to a local link. If a link can’t be converted, you can just leave it as-is.

The capability needed to add this functionality is already there. Someone just needs to decide how to handle it on the frontend elegantly from a UI perspective, and decide how the backend will pass what’s required to the frontend to drive the functionality. But the plumbing is already there.

One practical way to go about this would be to add one or more API endpoints to transform remote entities (URLs) to local entities, if they exist. Whenever posts/comments/whatever are loaded into the client’s browser, Lemmy UI can have code that takes any links that match patterns for Lemmy entities, and use the API endpoints to transform the remote URLs to local URLs, if it can be done. For those that can be done, swap the remote URLs on the frontend for the local ones (at this point it’s essentially just find/replace). That’s one quick and simple way to do it that shouldn’t be all that performance-impacting. There might be more elegant and efficient ways I can think of if I put more effort into thinking about this, but that for sure would work and be a decent first-cut solution. You could even add a caching mechanism (or maybe even a new database table) to persist the mapping as it happens so that you don’t need to do it on each request for a given entity, only the first time. Also, doing it this way allows for content that is not yet federated to work if one day it becomes federated (ie. try to do this mapping or each entity, everytime, if it never works, until one day it does).

With all due respect, it seems like a janky solution to have a bot post public comments on request with transformed links specific to a given user’s own instance (that no other users would be likely to care about), just so that they can refresh the page and click on them… If something like this went into widespread use, threads would just become cluttered with comments containing transformed links, and I could see that being really annoying to other users who are trying to properly participate in discussion.

Back on Reddit, I always thought the !remindme bot was pretty dumb. Certain threads would just be spammed with comments for the bot to pick up to remind that specific user on some date to come back and check the thread. We can do better than that here. It was a janky solution to something that was a problem best left to the end-user to manage separately (just set a reminder in your own calendar…).

This is best left to client-side code in the form of a browser addon, or ideally, the Lemmy frontend itself.

It should be trivial to make an enhancement to the official Lemmy frontend such that links to any other Lemmy communities/posts/comments/etc are transformed to the context of the user’s home instance. It could be a togglable setting in the user’s own settings, or maybe both the original link and the transformed link could be presented to the user on click (to accommodate both desktop and mobile browsing).

I’m actually really surprised this isn’t already implemented given how simple it is to do.

I guess they don’t really know what they’re doing and are learning how load balancing works on the fly, and thinking that’ll result in HA without side-effects without further work.

EDIT: Don’t really get why this was downvoted. With the proper technical knowledge it’s clear to anybody that two instances with different JWT secrets behind a load balancer is going to cause this very issue. So the fact that they set it up that way means they have a knowledge gap (“they don’t really know what they’re doing”). At the very least they should enable sticky sessions on the load balancer if they insist on going this route, which would mitigate the issue (but depending on client-side configuration would not necessarily prevent it completely).

Don’t take this as an insult towards the admins of the instance, I’m just pointing out there’s a lack of knowledge, and some trial-and-error going on.

Oh yeah for sure. It’s just a matter of time. Out of all of these options, some will just fade away (some already have within weeks of initial release), and some will remain and just continue to get better as the development community continues to get a better picture of where all of the action is, and starts to want to be a part of it.

You’re seeing that toast about versions since backend version 0.18.0 switched away from using a websockets-based API to a REST API, and the Jerboa client app is (in a not-so-descriptive way) warning you that the backend you are connected to isn’t aligned with the app version in terms of what it expects of the backed. This should go away pretty soon as more servers update their backend version and the Jerboa app update hits more devices.

Oh yeah for sure, everyone should work on whatever they want without restriction or obligation to be focusing on what someone else wants. And more often than not a pet project is a way to learn a new language or framework with the goal of self-development. That’s a great thing.

It’s just a thought I selfishly have sometimes when I see many apps in development for the same platform, I can’t help but wonder “if all of this effort were focused across fewer apps, could each of those be better than any of these current ones are individually today?” Of course the number of devs contributing to a project has no direct correlation when it comes to the quality or maturity of the product. That’s down to the management, skillset of the devs, etc. I’m well aware of all of that, and the pros and cons of the differences in scenarios.

Just thought I’d share the thought out there. In any case, Lemmy getting all of this attention will no doubt lead to the rise of at least a few solid mobile apps that will stick around and not fizzle out into development neglect within a couple of months.