If an existing point of interest is on the map and you add a favourite with the POI highlighted, the address field is automatically correctly populated with the street address. But when the favourite is later edited for any trivial reason (e.g. to change the name or description), the address information is lost. The field is cleared.

I block all Cloudflare instances I know of (lemmy.world, sh.itjust.works, lemm.ee, lemmy.ca, programming.dev, etc). But sometimes I inadvertently end up on one of the those instances when searching in a logged out state. When I login, the block rules apply (as expected). But it makes no sense to block all comments in a thread without blocking the thread’s OP.

IOW, if the OP is displayed because it is visited specifically, then the full thread with all comments should also be visible.

I am somewhat forced to use Alexandrite because the stock Lemmy client is broken on Ungoogled Chromium. So when Alexandrite cannot handle something it’s a burden. In the case at hand, Alexandrite is unable to search for a community using an exact path as the query.

Workaround: We have to use the stock client or some other client.

(edit) what is in the heads of ppl who downvote a bug? “This bug does not affect me personally so please don’t spend time fixing it”.

I am not sure why subscriptions are often not instant. Some subscriptions are forever stuck in the pending stage. The problem is that to enter a community in that state I must remember the host and community name, or I have to search for it again every single time.

The fix: put in the profile a list of pending subscriptions so we can easily enter those communities.

When visiting this community from a stock Lemmy front end, there is down-voted spam and garbage near the top of the timeline. This happens regardless of the view selection (hot, active, scaled, etc). Certainly if the user asks for the “hot” view they should not be seeing negative scored threads near the top. And ironically, using the “controversial” view pushes the negative threads further down, which is the complete opposite of what’s expected.

Mbin fails to show the spam at all, even when selecting the “Newest” view, which we expect to show everything in chronological order regardless of score. So mbin is broken too.

The 3rd-party Lemmy client alexandrite behaves more like mbin, and does not show the spam even if a chronological order is requested.

The linked article showcases a disaster of the text previewer in the stock Lemmy client. It makes sense that linefeeds would be stripped to some extent, but when the content relies on a linebreak for every line because it’s important for formatting, it’s a disaster when you have half a screen of text.

The fix: the preview code should count the number of linefeeds it removes. If it removes more than ~4 or so linefeeds, it should be clear that it’s not dealing with normal sized paragraphs. In this case, it should only show a few lines (with linefeeds) and have a spoiler or expansion option.

Another simpler fix: have a “suppress preview” tickbox so an author can manually clear a bad preview box.

An original poster asks a question or attempts to create a thread to compile information about a topic, and there is always some clown or asshole who cannot resist posting a snide remark. If the snide remark is clever or captures the sentiment of many, it gets a flood of up votes and rises to the top, bringing with it a tree of replies to the snide remark. Useful constructive answers get buried because they are boring to the wider audience who just likes to see a good roasting. I think there are more kids in the threadiverse than we expect.

So content that’s nearly garbage dominates the thread and drowns out the thread’s purpose, disservicing the OP and all those who want the same answer or collaboration. It’s a design failure of Lemmy to be blind to this very basic characteristic of human nature.

Censorship is unreasonable in this situation. But so is the status quo. Nothing wrong with a bunch of clowns having fun, but that fun should happen non-disruptively on the sidelines and out

Every Lemmy instance chooses its own name for the meta community. Some don’t even have one. Some choose quite bizarre names.

That’s shit. If you walk into an office building, the receptionist is almost always close to the main entrance. When you enter a restaurant, the host(ess) is either close to the front door or there is a clear path to the host(ess). Yet Lemmy is terribly organised in this way. The power of defaults can go a long way here. A meta community should be created by default with a default name. And by default it should be listed at the top on the communities list.

Best way to cope with the madness is sort communities chronologically with oldest first. But it’s not solid. Sometimes the meta community is created late in the game.

Both Lemmy and mbin have a shitty way of treating authors of content that is censored by a moderator.

Lemmy: if your post is removed from a community timeline, you still have the content. In fact, your logged-in profile looks no different, as if the message is still there. It’s quite similar to shadow banning. Slightly better though because if you pay attention or dig around, you can at least discover that you were censored. But shitty nonetheless that you get no notification of the censorship.

Mbin: if your post is removed, you are subjected to data loss. I just wrote a high effort post europe@feddit.org and it was censored for not being “news”. There is no rule that your post must be news, just a subtle mention in the topic of news. In fact they delete posts that are not news, despite not having a rule along those lines. So my article is lost due to this heavy-handed moderation style. Mbin authors are not deceived about the status of their post like on lemmy, but auth

Discuss. (But plz, it’s only interesting to hear from folks who have some healthy degree of contempt for exclusive corporate walled-gardens and the technofeudal system the fedi is designed to escape.)

And note that links can come into existence that are openly universally accessible and then later become part of a walled-garden... and then later be open again. For example, youtube. And a website can become jailed in Cloudflare but then be open again at the flip of a switch. So a good solution would be a toggle of sorts.

When an arrogant presumptuous dick dumps hot-headed uncivil drivel into a relatively apolitical thread about plumbing technology and reduces the quality of the discussion to a Trump vs. $someone style shitshow of threadcrap, the tools given to the moderator are:

• remove the comment (chainsaw)
• ban the user from the community (sledge hammer)

Where are the refined sophisticated tools?

When it comes to nannying children, we don’t give teachers a baseball bat. It’s the wrong tool. We are forced into a dilemma: either let the garbage float, or censor. This encourages moderators to be tyrants and too many choose that route. Moderators often censor civil ideas purely because they want to control the narrative (not the quality).

I want to do quality control, not narrative control. I oppose the tyranny of censorship in all but the most vile cases of bullying or spam. The modlog does not give enough transparency. If I wholly remove that a

If you open a PDF document in the browser (thus in pdf.js) and click the down arrow (↓) to save it locally, it redownloads the document instead of simply saving it from the cache. If you lose network connectivity or disconnect then try to save the PDF locally for later viewing, the browser reports connection issues when there was no need for the network.

Tor Browser (Firefox based) does not have this problem.

An important part of the Youtube content is the transcript at the bottom of the video description. There are some 3rd-party sites that collect and share the YT transcripts separately but then the naive admins put the service in Cloudflare’s walled garden, which is worse than YT itself and purpose-defeating to a large extent. (exceptionally this service is CF-free, but it says “Transcript is disabled on this video” in my test: https://youtubetranscript.io/)

Invidious should be picking up the slack here.

And Lemmy could do better by automatically fetching the transcript of youtube/invidious links and include it, perhaps spoiler style like this.

I browse with images disabled. But sometimes I encounter a post where I want to see the image, like this one:

https://iejideks5zu2v3zuthaxu5zz6m5o2j7vmbd24wh6dnuiyl7c6rfkcryd.onion/@JosephMeyer@c.im/112923392848232303

When opening that link in a browser configured to fetch images, it redirects to the original instance, which is inside an access-restricted walled garden. This seems like a new behaviour for Mastodon thus may be a regression.

It’s a terrible design because it needlessly forces people on open decentralised networks into centralised walled gardens. The behaviour arises out of the incorrect assumption that everyone has equal access. As Cloudflare proves, access equality is non-existent. The perversion in this particular case is an onion is redirecting to Cloudflare (an adversary to all those who have onion access).

There should be two separate links to each post: one to the source node, and one to the mirror. This kind of automatic redirect is detrimental. Lemmy demonstr

There are some very slow nodes (like Beehaw) where the server is apparently so overworked it cannot render a login form most of the time. The browser times out waiting. In the rare moments that there is a login opportunity, about ½ the time the login fails with a 2 second popup saying “incorrect login credentials”.

It’s quite terrible because obviously users would assume their account has been deleted --- because that’s how most online services work. Admins do not generally give warnings or say why an account is deleted. They just hit the delete button. Like Marvin in Office Space who was not told he was laid off.. they just “fixed the payroll glitch”. This is generally how communication works on communication platforms.. admins just pull the plug.

So because of how people learn that their account is deleted, users cannot distinguish a purposeful account removal from a faulty server. If you have a Beehaw account and you are told “incorrect login credentials”, don’t believe it. Keep t

In the stock Lemmy web client there is apparently no mechanism for users to fetch their history of posts. The settings page gives only a way to download settings. This contrasts with Mastodon where users can grab an archive of everything they have posted which is still stored on the server.

Or am I missing something?

IIUC, there is no GDPR issue here because no data is personal (because all Lemmy accounts are anonymous). But if a Lemmy server were to hypothetically require users to identify themselves with first+last name, then the admin would have a substantial manual burden to comply with GDPR Art.20 requests. Correct?

These environment variables designate a parameter that holds the value of a HTTP proxy:

• http_proxy
• https_proxy
• HTTP_PROXY
• HTTPS_PROXY

It’s a convention, but the name “HTTP proxy” can only imply HTTP proxy, not a SOCKS proxy. The golang¹ standard libraries expect the above HTTP proxy parameters to specify a SOCKS proxy. How embarrassing is that? So any Go app that offers a proxy feature replicates getting the proxy kind backwards. Such as hydroxide, which requires passing a SOCKS proxy as a HTTP proxy.

¹ “Go” is such a shitty unsearchable name for a language. It’s no surprise that the developers of the language infra itself struggle with the nuances of natural language. HTTP≠SOCKS. And IIUC, this language is a product of Google. WTF. It’s the kind of amateurish screwup you would expect to come from some teenager’s mom’s basement, not a fortune 500 company among the world’s biggest tech giants.

(edit)
It’s a bit amusing and simultaneously disasappointing that report

Lingva & Simply Translate are two different front-ends to Google Translate. I’m not running the software myself because I run Argos locally (for privacy), but when Argos gives a really bad translation I resort to Lingva and Simply Translate instances.

I tried to translate a privacy policy. Results:

Lingva instances:

• translate.plausibility.cloud ← goes to lunch
• lingva.lunar.icu ← gives “414 Request-URI Too Large”
• lingva.ml & lingva.garudalinux.org ← fuck off Cloudflare! Obviously foolishly purpose defeating to surreptitiously expose people to CF who are trying to avoid direct Google connections.
• translate.igna.wtf ← dead
• translate.dr460nf1r3.org ← dead

Simply Translate instances (list of instances broken for me but found a year-old mirror of that):

• simplytranslate.org ← just gives a blank
• st.tokhmi.xyz ← up but results are just CSS garbage
• translate.bus-hit.me (ST fork mozhi) ← shoots a blank result
• s

cross-posted from: https://slrpnk.net/post/11375008

Whoever designed the OSM db either never uses ATM machines or they have never experienced anything like the ATM disaster in Netherlands. The OSM db has most ATM brands incorrect for Netherlands and seriously needs more fields so travelers can actually find a functioning ATM.

brands are mostly incorrect

Pick any Dutch city. Search » Categories » custom search » Finance » ATM. The brands are mostly misinfo. These ATM brands do not exist anywhere in Netherlands:

• Rabobank
• ABN AMRO
• Ing
• SNS

All those banks removed all their ATM machines and joined a monopolistic consortium called “Geldmaat”. There is generally an ATM at those locations but it’s always a Geldmaat ATM. So a simple find and replace is needed on all the Dutch maps.

For indoor ATMs, the brand is often incorrectly named after the shop it’s in. That’s useful for finding it but still missing important info: