MentalEdge

MentalEdge, 2 months ago

Yes because the security of barcodes and screenshotted tickets were such a huge problem before. Paying customers used to constantly miss out on events because someone else had already gotten in with their ticket. /s

MentalEdge, 2 months ago

They do. In fact they’ve been caught “reselling” tickets at scalper prices without them ever having been sold a first time.

The entire scalping/resale market arguably shouldn’t exist, instead tickets should be refundable within reason, at which point the organiser can issue and sell new tickets.

MentalEdge, 2 months ago (edited 1 month ago)

So it was… Updated.

It probably posted the version I used as a wallpaper at one point, which I would have cropped the text out of. But my posting tool should have posted the source image after finding it through the reverse search it does to find the artist credit and links. Maybe I have a bug somewhere?

Edit: Hang on, I know why it didn’t, the cropped file is way higher quality than the pixiv/danbooru source files. Where did I find that? Anyway that’s why my posting tool used it, it determined it was the highest quality version.

MentalEdge, 2 months ago

The game is free on steam and runs on a potato.

You can even skip levels so you don't have to waste time on solving puzzles if you don't want to, and just get to experiencing the source material instead.

Anyone interested absolutely should give it a go, it's a fun little game full of cute demons :D

MentalEdge, 2 months ago

There is one big reason: it requires time and effort.

The vanilla web-UI is inferior to other clients in a variety of ways, and any feature requires that someone somewhere get it done.

You could make an endless list of things that are “no-brainer” features for someone to add, but the development still requires that someone somewhere go down that list, one item at a time.

For example, Lemmy only recently got the ability to show the real number of subscribers that communities have, instead of showing the number of subs from the instance you were looking at that community from. That’s nice, but each update can only come with a subset of the endless number of obvious improvements that could be made.

No client currently does everything that the Lemmy server can technically be made to do with the currently implemented API calls. But the solution to agnostic links already exists. Any instance, when handed the url to a post or comment, no matter what instance it is for, is able to turn that into the corresponding local url/ID, the work to make use of that to make all links work everywhere simply hasn’t been put in yet.

Not that long ago just mentioning communities and users was a pain, but that’s mostly solved now. Posts and comments will be too. Eventually.

MentalEdge, 2 months ago (edited 1 month ago)

This would still leave the problem of people not being able to just copy paste the url from an address bar. Re-learning how to link stuff is something some wont ever figure out. The relative linking of communities was a stopgap, and they break on kbin for obvious reasons.

Relative links aren’t an ideal solution anyway, as different clients handle things differently. A relative link that works in the default webUI, wont in photon, and vice versa (though photon already figures out links way better than the vanilla webUI does).

Not to mention that you’d still want to have absolute links work, too. Both within any client, and when opening links shared outside lemmy, and have them work in a way where you can interact from whatever account you have. By that point you may as well just figure out absolute links for everywhere.

MentalEdge, 2 months ago

What.

MentalEdge, 2 months ago

Because they are used to that? Because that’s what the share button does in any browser?

I don’t understand why you are so combative.

MentalEdge, 2 months ago (edited 1 month ago)

Lemmy doesn’t have the development resources to Thanos snap itself into a feature-complete state overnight.

Forking would make that worse.

I can smell the entitlement of “when devs can’t be bothered to do the obvious” straight through my screen. We simply do not get to sit here and come up with things that are “so obvious they should be done already”. That’s not how reality works. The wheel didn’t exist until it was invented, and then built by someone.

I’m only explaining that the solution exists and is currently held by back by the fact that development isn’t done by materializing code into existence with an infinity gauntlet!

The fact that some client devs implement new API features before the vanilla webUI does (which btw is a separate thing from the lemmy server, and itself merely one client for it, albeit the default) isn’t unusual, or indicative of some massive fundamental problem in how the project is run.

MentalEdge, 2 months ago

In what way is my point invalid then? I think you are being combative, because you used the idea that people don’t copy urls directly, as if that meant there was a way to get relative ones working well. There isn’t.

People will use absolute links, so they should work. If they can be made to work, why do we need relative ones to solve the problem of links not opening locally?

Sure, when you use the various share buttons all over, you can get different more specific share options.

But when have they ever netted a relative link, much less done so when SHARING?

MentalEdge, 2 months ago (edited 1 month ago)

…

Again. What?

I’m not passing the buck anywhere, I’m saying the lemmy server can do this but the default lemmy webUI doesn’t make use of it. At least not yet.

The problem isn’t being solved by the clients and apps. It’s solved by lemmy.

Some clients have just made use of it sooner than others, and the vanilla webUI is one of the ones that hasn’t yet. But the feature itself IS IN LEMMY ITSELF.

MentalEdge, 2 months ago (edited 1 month ago)

Its like if facebook made you login again because you follwed a facebook.com link from within facebook, all because the user who created the link is in a different time-zone. What’s not to understand about how broken that would be?

Not what I’m proposing

An user following an absolute link that doesn’t re-direct them back to their own instance is likely not going to be able to interact with the content there.

Again. Not what I’m proposing.

Within the context of a Lemmy user following a link from a comment, at least, the relative link is more useful.

Only when viewed on one specific client, on one specific fediverse platform.

Fact is, Lemmy is already capable of serving up a different parsed url for logged-in users and non-users, the webUI just hasn’t implemented the feature yet, and so here we are.

This is what I’m proposing. Except being logged in isn’t even a requirement for the webUI to open all links it can open locally, locally.

And looking into it, I’d much rather have a system for “mentioning” posts or comments in the same “object@instance” format that we already use to link communities and users, as proposed here. Such a system would have no need for client specific relative url paths, and would boil down the mention to the object ID and the instance where it can be found, allowing any client or even other fediverse platform to easily parse it into something that can be used.

MentalEdge, 2 months ago

I remember the controversy around the first reboot. The trailers had Lara getting banged around by painful injury after painful injury, and there was that one encounter with an islander that everyone immediately assumed was a rape-scene.

They still toned it way down for the next two games… I found the first one morbidly entertaining and went out of my way to find every gruesome way to get Lara killed. The sequels were still fun but I kinda missed that aspect of mistakes leading to unusually brutal game overs.

I think it started the bow and arrow craze that games had there for a while? Still kinda sad she only gets her pistols at the end, and then even the sequels never really have her dual wielding handguns.

MentalEdge, 2 months ago

@hatsunemiku