And speaking of replacement links, we need a way to add them and have the alternative links voted on, and ultimately the replacement link should potentially outrank the original link and take the spotlight. I will add this to the OP.
freedomPusher
joined 3 years ago
MODERATOR OF
Perhaps. Simplicity is important. But what if I circumvent the exclusivity of an article by finding a mirrored copy on archive.org? If the content is quite insighful, would then want to say it is both exclusive and insightful. Those metrics together could then be used to work out whether it’s worthwhile to find a replacement source for the same content.
Which is almost as ridiculous as acting like an admin shouldn’t be able to ban someone from their instance.
The admin did not know why they were suppressing the messages. Apparently they did not keep notes. So they reversed the action. But no one here said admins should not have the power to ban. Quite the contrary: they should. And because they should have that power, it should not be disproportionate. One million people should not lose access to civil posts from Bob because Mallory the admin did not like one of Bob’s ideas. This is why decentralisation is important.
Your account is 3 years old (strangely almost no posts or comments though)
Then your view is being restricted¹. I don’t know how sheltering lemmyworld admins are of their users generally but the Mastodon analog to #lemmyworld would be mastodon.social, and mastodon.social is quite loose with the censor button. There have been conversations where people only saw part of the conversation and were confused because they knew someone else was engaged but they could not see the whole conversation. After investigation, it was not a federation issue but in fact the mastodon.social admin simply decided to block a particular person. I would not be surprised if lemmyworld were blocking me in some way because anyone who outspokenly advocates for decentralisation is directly undermining lemmyworld’s position (lemmyworld is centralised both by Cloudflare and also by disproportionate userbase).
and I’ve noticed the people that were here before everyone else seems to hate the new wave of people that showed up a year ago
The fediverse was created out of love for a #decentralised free world. Centralised nodes like #LemmyWorld, #FBThreads, #shItjustWorks, #LemmyCA, #LemmyOne, etc work against the philosophy of decentralisation. Users on those nodes are either not well informed about the problems of concentrated imbalances of power, or they simply do not care and do not value digital rights; they only care about their personal reach. Fixing the bug reported here addresses the former (uninformed users).
The bug report herein is specifically designed to be an inclusive alternative to what you suggest, which is:
Why don’t you just convince your admin to defederate? Or go make you own instance for just people you agree with?
Locking people out on the crude basis of which node they come from is somewhat comparable to what Cloudflare (and lemmyworld) does by discriminating against people on the crude basis of IP reputation. It over selects and under selects at the same time if the goal is to separate good links from bad links. Anyone can post a shitty link. A majority of shitty links would come from the lemmyworld crowd, but it’s not a good criteria for a spam/ham separation. The fedi needs to improve by tagging bad links appropriately, which should not be influenced by the host the author uses.
¹(edit) you should see over 400 posts and comments. Visit https://sopuli.xyz/u/freedomPusher to see the real figures.
Ungoogled Chromium with uMatrix running over a Tor circuit gave Yahoo’s typical blurred out paywall yesterday. Today (likely on a different Tor circuit) it gives “Too many requests -- error 999.”
Engadget/yahoo is fully enshitified. If you can read that article it probably means your browser is insufficiently defensive. A tl;dr bot would be useful here.
It’s not a bug if it works as designed.
What you claim here is that software cannot have a defective design. Of course you have design defects. These are the hardest to correct.
I’d also accept “it used to do this and it doesn’t any more and not on purpose”.
This is conventional wisdom. Past behavior is no more an indication of correctness than defectiveness. GREP’s purpose was to process natural language. A line feed is not a sensible terminator in that application. For 50 years people just live with the limitation or they worked around it. Or they adapt to single token searches. It does not cease to be defect because workarounds were available.
that doesn’t make it a bug if it was never designed in to the program.
The original design was implemented on an extremely resource-poor system by today’s standards, where 64k was HUGE amount of space. It was built to function under limitations that no longer exist. I would say the design is not defective so long as your target platform is a PDP-11 from the 1970s. Otherwise the design should evolve along with the tasks and machines.
If all you’re advocating for is allowing grep to use some other character as a delimeter, I might be able to get behind something like bash’s $IFS or awk’s $FS variable (maybe). But I couldn’t get behind anything backwards-incompatible.
Of course. GREP has an immeasurable number of scripts dependant on it worldwide going back 50 years and it’s among Debian’s 23 essential packages:
dpkg-query -Wf '${Package;-40}${Essential}\n' | grep yes
Changing grep’s default behavior now would bring the world down. Dams would shatter. Nuclear power plants would melt down. Traffic lights would go berzerk. It would be like a Die Hard 3 “firesale”. Planes would fall out of the sky. Skynet would come online and wipe us all out. It would have to be a separate option.
TIL there are people who (try to) use grep for natural language.
The very first task grep was created for is specifically natural language input. Search “Federalist Papers grep”. There’S also a short documentary about this out in the wild somewhere but I don’t have any link handy.
Oh, and this is 100% feature/enhancement request territory. Not a bug report in any sense.
This is conventional wisdom coming from a viewpoint that simultaneously misses grep’s intended purpose.
But now that the defect has been rooted in for ~50 years, perhaps fair enough to leave grep alone. For me it depends on how lean the improvement could be. Boating grep out too much would not be favorable, but substantial replication of code between two different tools is also unfavorable. Small is good, but swiss army knives of tools also bring great value if they can be lean and internally simple.
I don’t know if you’re saying “because PDFGREP is good at handling natural language, grep should be too”
Not at all. They both have the same problem. But this same limitation in pdfgrep is a nuissance in more situations because PDFs are proportionally more likely to process natural language input.
Either way, I don’t follow how PDFGREP is relevant to discussions about grep
They have the same expression language and roughly same options. PDFGREP is most likely not much more than a grep wrapper that extracts the text from the PDF first.
grep isn’t really designed as a natural language search tool
My understanding of GREP history is that Ken Thompson created grep to do some textual analysis on The Federalist Papers, which to me sounds like it was designed for processing natural language. But it was on a PDP-11 which had resource constraints. Lines of text would be more uniform to manage than sentences given limited resources of the 1970s.
Thanks for the PERL code. Though I might favor sed or awk for that job. Of course that also means complicating emacs’ grep mode facility. And for PDFs I guess I’d opt for pdfgrep’s limitations over doing a text extraction on every PDF.
I think it’s too hard for many to grasp the full consequence of surveillance via forced banking. They link cash to privacy which they then mentally reduce to “confidentiality”. It’s a lossy reduction but in the naïve brain privacy=confidentiality. They don’t realise privacy is about /control/, not just purely infosec concept of confidentiality, which then leads to the mental short-sightedness of thinking they’re dealing with “paranoia” (which is hinted in vzq’s next reply).
From there, I don’t have the answer as far as how to convey the full depth of the whole concept of privacy within the span of a post or comment that’s short enough to not be automatically ignored.
UPDATE: it just now happened again, but this time not with the admin account (@QuentinCallaghan@sopuli.xyz) but with another user account. I was refreshing my profile and the user @baltakatei@sopuli.xyz appeared in the profile pulldown position on the page with my profile. This time I had time to take a screenshot before it changed:
It’s interesting that it shows my profile page but not as I see it. That is, when I visit my own profile page I normally have a “subscribed” sidebar. This shows what someone else would see if they visit my profile while they are logged in, which still differs from what a logged out profile looks like (as send msg options were given). So I wonder if I could have sent myself a msg.
2
Cloudflare’s walled garden found to be more disempowering than Facebook and Google
(thefreeworld.noblogs.org)
!isitdown@infosec.pub is a better place for this info.