#permissions

N-gated Hacker Newsngate
2025-11-24

🚫 Oh, the irony! In a riveting twist, our tech wizards decided to jump ship from to for firewalls—only to lock themselves out of their own blog post. 🔒 Maybe next time, consider before making grand announcements? 🤦‍♂️
utcc.utoronto.ca/~cks/space/bl

Roo J Solutionsroojs@phpc.social
2025-11-22

#ollama #vala #gtk chat client coming along nicely - got it's own repo now github.com/roojs/OLLMchat
* function calling working
* updated the styling
* tool can send messages to the chat

next up #permissions (code done, but need to hook it into the interface)

2025-11-14

can't connect to samba share on different physical drive #permissions #mount #samba

askubuntu.com/q/1559682/612

The Eclectic Light Companyeclecticlight.co@web.brid.gy
2025-11-11
<p>When you&#8217;ve tried all the logical solutions, restarted, had a go in Safe mode, and still can&#8217;t solve a problem, you may need to bring the big guns to bear on it. These are radical fixes that carry a risk of going further than you want, but are all you&#8217;ve got left. You might have been recommended them by someone who seems to know best, or, as we saw last week, <a href="https://eclecticlight.co/2025/11/07/inside-the-unified-log-7-claude-diagnoses-the-log/">by an AI</a>. This article looks at the state of those big guns in Tahoe 26.1, and which you should consider seriously.</p>
<h4>Reset NVRAM and SMC</h4>
<p>Although quick and simple to use, resetting the NVRAM and SMC are well known for fixing all sorts of problems. They&#8217;re still valuable in Intel Macs, but you can forget them in Apple silicon, as the SMC resets with each startup, and the NVRAM is protected from user access. The only way you could reset an Apple silicon Mac&#8217;s NVRAM is by <a href="https://eclecticlight.co/2024/07/30/nvram-in-apple-silicon-macs/">Restoring it in DFU mode</a>, which almost certainly isn&#8217;t something you want to do at this stage.</p>
<h4>Reset TCC</h4>
<p>TCC is the subsystem responsible for implementing privacy protection, and is notorious for its mystifying misbehaviour. Before convincing yourself that doing anything with TCC is going to help a problem, you should really look for a pattern of misbehaviour that points to one of the resources that it controls
2025-11-09
2025-11-08

How to make a handy samba share with automatic permissions? #permissions #samba

askubuntu.com/q/1559422/612

2025-11-05

I wrote a simple dns client using raw sockets in C but get "sendto:Permission denied" #networking #permissions

askubuntu.com/q/1559269/612

2025-11-02

Password annoyance - possible to use 2 passwords? #permissions #sudo #password #root

askubuntu.com/q/1559163/612

2025-11-01

Ubuntu 24.04 / Permission error on VMWare Workstation (passthrough disk) #permissions #mount #vmwareworkstation

askubuntu.com/q/1559124/612

2025-10-30

Ubuntu default Firefox app won't start after system changes #permissions

askubuntu.com/q/1559030/612

2025-10-29

Remote connect from local computer to ubuntu server problem #networking #server #permissions #ssh #webserver

askubuntu.com/q/1558973/612

2025-10-29

Remote connect from local computer to ubuntu server problem (noob) #networking #server #permissions #ssh #webserver

askubuntu.com/q/1558973/612

2025-10-19
@silverpill That's probably because "followers only" is not a Fediverse-wide standard backed by the ActivityPub spec or a FEP, nor does it tie in with any actual permissions systems available in the Fediverse.

As an example for the latter, Hubzilla, (streams) and Forte do not translate Mastodon's "followers only" into "these Fediverse actors are granted permission to view, like/dislike and reply to this message indefinitely, and everyone else isn't".

On top of that, all three assume that the permissions of all elements in a conversation are always the same because that's how they work. So if I post in public, and one of my Mastodon followers comments "followers only", then Hubzilla will treat it as public regardless because if my post is public, and it is, then all comments and replies are public, too.

At least Hubzilla shows a red padlock symbol on each message whose "permissions" don't align with what Hubzilla understands or expects.

CC: @kopper :colon_three:

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla #Streams #(streams) #Forte #Permissions #FollowersOnly
2025-10-09
@Helge
Good news! guide now talks about followers only posts. If you are in the set of "Some applications create replies to followers-only posts addressed to the replier's followers collection", please fix it.

This. In fact, Fediverse server software that behaves correctly has been around since long before Mastodon was made.

In fact, replies should never go to whoever is replied to unless it's the conversation starter. Replies should always go to the conversation starter and from there to all participants in the conversation, and they should do so without having to visually mention all participants. Also, conversations should be shown as a whole by default always and everywhere and not as single-message piecemeal with no context.

And in an ideal Fediverse, this should go hand in hand with only the members of the followers collection of the top-level post author being permitted to see a) the top-level post, b) any comments on the top-level post and c) any replies to comments in the first place. This would make sure that nobody who isn't intended as part of the audience will ever be able to see this content, also by making it technically impossible to repost/boost/repeat/share/otherwise forward anything in the conversation. But hardly anything in the Fediverse has the all-encompassing permissions system that's required to achieve this.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #AP-Next #Conversations #Permissions #FollowersOnly

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst