@Thenomain said in Most 'Plug & Play' Friendly Server?:
I am biased heavily toward TinyMUX, and all of my code is tested on it, but Rhost has a bit of a fan base, and Penn has, yeah, @faraday and also @Volund. I would focus on: Who do you know? What servers do they use? Can they point you at things?
Volund's code suite also works on Rhost, just as a FYI.
Still playing around getting F3 working on Rhost, but it's been painful 
@Jim-Nanban said in AWS (Amazon Web Service) as MU Hosting:
@ixokai HEH. It's what the DB runs on, and the differences aren't enough for me to care about 7 years out from my last time doing any real coding. I'd really want to try RHOST, but... the softcode in the DB I've got is way too tightly coded to change platforms.
You'd be surprised how much compatibility there may be 
It's possible, but there's likely more cost effective systems out there that provide hosting.
There, theoretically, should be no real licensing issues from running most mush codebases.
TM3, MUX2, and Penn I think follow a modified GNU opensource license.
Rhost uses a modified MIT-like opensource license.
I'm sadly unfamilar with MOO, LP, DIKU, MUCK, or Evennia's licensing scheme, but believe they're all a branch of opensource/GNU license somewhere.
@Hexagon said in MUX: Attribute Visibility:
Is there a good way to restrict attribute visibility to a list of objects (players, rooms, things) contained in an attribute list somewhere?
I know it can be restricted via underscore, or with attribute ownership as attribute owners can read the attribute on an object even if they don't own the object. Visible is too open.A good example would be if you wanted to have a clan that could issue an arbitrary command and see the names of everyone in that clan... but you only wanted members already added to that clan to run the arbitrary command.
MUX does not have an arbitrary method to specify if you can see specific attributes over someone else.
What you'lll have to do is build a @function to fetch the attribute(s) based on evaluated permission sets.
Sorry I don't have a better answer for you.
Though maybe... hum. Not overly familar with MUX Zones, but it is a potential for murking the ownership a bit to grant you what you want, but it will likely still be object-wide and not per attribute.
I don't think Penn attribute trees would even grant something like this.
@Sparks said in Client-Side Spacing:
I also do think there could be an argument made for functional expansion; if I had the origin command in a register, I could do interesting conditional things like add out-of-band data for the client to process. Like adding a conveniently, consistently parseable string saying 'this is a page from <X>' with a begin/end tag, so that even multi-line pages could be pulled into a specific spawn.
Of course, at that point, you're making this wildly more complicated, but it's still a personal pipe dream... to have a way to snag multi-line outputs for client-side processing. And if we're discussing adding user-specific formatting hooks that have a chance to alter output, making them conditional based on the origin command and enactor makes me happy.
And..... done.
This is optionally available in the latest RhostMUSH 4.0 engine with the @admin (config) parameter posesay_funct enabled (default disabled).
The SPEECH_PREFIX and SPEECH_SUFFIX attributes only work for connected player types, and will not work if the attribute is set NO_COMMAND.
If you trigger the cpu alert (by blowing away the cpu alert) it naturally logs the attempt then sets the attribute NO_COMMAND for safty sake.
So, you got your pipe-dream. Enjoy
@Thenomain said in Client-Side Spacing:
Why split date and time when there is timestamp available?
I'm thinking enactor dbref may also be good, a quick and dirty nospoof.
Also a pony.
Because it was easy to do, and some people may find date superflurous over time.
Also, dbref#'s added, though if the enactor is tagged 'spoofing' then the dbref# will return as #-1.
@Sparks said in Client-Side Spacing:
@Ashen-Shugar I think that's a worthwhile idea in a lot of ways, but I don't think it'll help the original poster a lot in this case, sadly. Unless you can convince their staff to swap out the hardcode to pick up a feature.
I also do think there could be an argument made for functional expansion; if I had the origin command in a register, I could do interesting conditional things like add out-of-band data for the client to process. Like adding a conveniently, consistently parseable string saying 'this is a page from <X>' with a begin/end tag, so that even multi-line pages could be pulled into a specific spawn.
Of course, at that point, you're making this wildly more complicated, but it's still a personal pipe dream... to have a way to snag multi-line outputs for client-side processing. And if we're discussing adding user-specific formatting hooks that have a chance to alter output, making them conditional based on the origin command and enactor makes me happy.
From a more practical standpoint, making a way to process the entire output would allow for other nice things, like 'if this is a say/pose/emit, replace all instances of %r%t with just %r, trim %r off the beginning and end, then append %r to the end.' Because then you've just managed to standardize formatting even for the people who want first-line indents, or who add %r to the end of their poses already.
But at that point we're probably getting a bit beyond the scope of the original request.
Well, I may have just done it in a workable way.
I have right now three arguments being passed to the SPEECH_PREFIX and SPEECH_SUFFIX.
%0 - The pose/say that was last done (which would include multi-line)
%1 - The date in the form MM/DD/YYYY
%2 - The time in the form HH:MM:SS
I essentially want to avoid functions as how this works could potentially cause some loop-parsing if I was to enable function evaluation.
What you're essentially looking for is a way to actually format the poses and says like a @pageformat ala Penn.
While this can be in the cards for a future update, right now it's too costly to add for poses and says.
Update: This has just been pushed to the latest Rhost 4.0 git repo for those who use Rhost.
Update #2: This also handles @emit and \
@Seamus said in Client-Side Spacing:
@faraday Maybe it is code ignorance. A looking fear of a security risk.
It can be, but the idea has merit.
What do people think about adding a SPEECH_PREFIX and a SPEECH_SUFFIX attribute on themselves that if met when anyone is issuing a say or pose at your location it will issue the speech_prefix, the message, then the speech_suffix?
There would be no method to identify the player doing it and it wouldn't evaluate functions, only %-substitutions.
This would be a hardcode mod.
Thoughts?
@Zobi said in Writing Prompts:
Got this one from a friend last night (She knows who she is! :P)
You sold your soul to the Devil some years ago. Today he gives it back and says, "I need a favour."
Didn't I see that very plotline a few months ago on Supernaturals?
@Thenomain said in Logging your activity:
@Misadventure said in Logging your activity:
We need a function, much like timestamps, where if you are flagged correctly (much like NOSPOOF) the server gives you something that encodes the time AND the exact letters etc of a text string. That could be used for evidence.
Extra points if the ID code can be unpacked into the given string.
If the ID code can be unpacked into a given string, then it can be faked.
Way back when, the headstaff and coders of Shadowed Isles tried to control bbposts from the game to SWOFA* by adding a verification field. They wanted to say that without the code, the bbpost was not legitimate.
Well at first they used the built-in pack() function, and someone using the unpack() function on it discovered that the code was "timestamp + the reader", essentially making the person who moved the post from the game to SWOFA was outing themselves. Clearly the attempt was to find out who was leak and quite probably deal with them.
The lesson from that debacle is that verification codes are only as trustworthy as the people who controls them and the people who uses them. The far easier answer is to be trustworthy staffers on a trustworthy game.
Shadowed Isles was none of these, though I met some of the best RPers I've ever played with there.
--
- Note: SWOFA was a much earlier version of Mu* Soapbox. This happened in, what, '98? '03? It's been forever.
It's reasons like this I added a LOGROOM @toggle in Rhost.
It essentially, if toggled on a room (requiring staff), logs everything that room hears. This means that pages and whispers or the like are not logged.
It also alerts people in the room that the room is logging whenever looking at the room (which is triggered upon entering the room).
This is essentially meant entirely for RP purposes to have a centralized location of logging.
Every message is timestamped and dbref# stamped (even if an @emit), and sent to a separate server log which can be scraped for wiki, html, or other things. Naturally the logs will have to be sanitized to remove dbref# and other things when presented publically, but it is there to help identify who (or what) gives the given messages.
I figure this was a good way to ensure people don't falsify logs, or cut out things they feel unimportant but really are and what have you.
Just a tool that people can choose to use or not. I find providing the tools and letting those who run the game decide when to use them works best.
I use an ssh client to connect to my server to use tinyfugue
@surreality said in The Crafting Thread:
@Ashen-Shugar All the hugs and empathetic winces are sent for that story. Sounds a lot like some of the asshole behavior that goes down in my family as well. I do not think I could actually forgive that, and I have managed to forgive someone for attempted murder (of me).
I likely will forgive it eventually. If for no other reason than to remove that pit of acid festering in my own gut. I likely won't forget it happened... ever... but forgive I can perhaps pull off.
For interest, this was the poem I had for my mother's funeral:
Distant Light
Distant shoals are sharp, the water dark,
The light has flickered and gone out.
Looking over the distant thunder,
We've sailed too long to turn about.
Shift the coat, stand up tall.
Take a breath, for this very night.
Our lives may have long be over,
But don't cry, it will be all right.
So sail on, into the night, old soul
Our sailing had enjoyment, it was fun.
For our final evening, sail... sail on...
Into the twilight of our setting sun.
@surreality said in The Crafting Thread:
@Ashen-Shugar said in The Crafting Thread:
Guess it's not overly crafty, but I write poetry and roast coffee.
This is relevant to my interests. Tell us more!
Also, the hats are gorgeous!
My wife's been doing this for years and years. She's slowly working on setting up a site where you can purchase designer top hats made to order. Each one takes between 16-30 hours of work depending on the materials and 'gadgets' and the prices tend to run from $120 to $500 or more again, depending on the materials, 'gadgets' and amount of time to design them.
Right now she takes email orders
@surreality said in The Crafting Thread:
@Ashen-Shugar said in The Crafting Thread:
Guess it's not overly crafty, but I write poetry and roast coffee.
This is relevant to my interests. Tell us more!
Also, the hats are gorgeous!
Uh, yeah. Where can I get some Ashen Coffee?
laugh I just have a small roaster, but I tend to collect green coffee and stockpile it. Green coffee, if stored properly, can last for near 30 years in a controlled condition, compared to roasted which lasts 6-8 weeks.
I currently have about 200 pounds of green coffee, of various varieties. My favoriate to date is Yergicheffee Single Origin, Sumatra Wahana, and Geisha Esmeralda.
I haven't bothered to try roasting Jamacian Blue or Kona, as frankly the green beans are too expensive for what it is.
For comparison:
Yergicheffe: Green $8/lb ... Roasted $22/lb
Sumatra Wahana: Green $6.5/lb ... Roasted $36/lb
Kona: Green $28/lb ... Roasted $40/lb
Jamacian Blue: Green $24/lb ... Roasted $45/lb
Geisha Esmeralda: $26/lb ... Roasted: $190/lb (that's not a typo)
The green is what you can buy it for, and the roasted is the average prices of that brand roasted.
I literally paid for my roaster in my first 3 months of using it.
As for 'Ash coffee'... er... I've been known to gift people with it at Christmas here and there.
I roasted 2 lbs of it for my mom's funeral, since the Sumatra Wahana was her favorite coffee of all time and she drunk it for 15 years when I introduced her to it. Always sent her coffee every few months. Got my mom to giggle like a school girl while receiving it. She sadly passed away two weeks ago, and it's been hard for me. Of everyone in the family, she (other than my wife) was the only one to 'get me'. My brother was a dick and told me of mom's passing away an hour after she passed away, and failed to notify me of the several days that she was hospitalized for... and I live only 40 miles from where she was. The reason for his not calling me about her being hospitalized? 'Well, you never call me, so it's your fault I didn't call you'. Yes, my brother is a gaslighting narcissist.
I was... not happy. I am still... not happy. I likely will remain... not happy with my brother for ... most likely forever.
So I drink Sumatra in remembrance of better times, and always toast my Mom on the first sip.
Oh well, such is life. Sorry for ranting, I'm still raw over it.
Guess it's not overly crafty, but I write poetry and roast coffee.
My wife's the crafty one.
She's a costume designer and milliner. She designs the hats from scratch, most are made from leather, velvet, or other such things.
@Thenomain said in Dealing with Staff:
... resurgence of Rhost as apparently Ashen has become utterly insane and entirely off his meds.
But in a good way.
... Honest.
@skew said in Is it possible to extract from pemit/think commands?:
@Ashen-Shugar I don't see @pipe in MUX, so no idea what that's meant to be.
It's a RhostISM. I mentioned it earlier.
> @pipe/tee finger
@pipe: piping to attribute has been enabled.
> +finger Ashen-Shugar
. o O +finger Ashen-Shugar O o .
.-==========================================================================-.
| Name: Ashen-Shugar Alias: ash Level: 0 |
| Status: WIZ |
| Connected for: 5d 7h 5m 43s |
'-==========================================================================-'
> @pipe/off
@pipe: piping to attribute has been disabled.
> think v(finger)
. o O +finger Ashen-Shugar O o .
.-==========================================================================-.
| Name: Ashen-Shugar Alias: ash Level: 0 |
| Status: WIZ |
| Connected for: 5d 7h 5m 43s |
'-==========================================================================-'
@Hexagon said in Is it possible to extract from pemit/think commands?:
@Ashen-Shugar Looks like that won't work for MUX, sadly. While I can pipe commands I execute directly, like look %0, +finger %0 winds up calling something that @pemits the data back. I am guessing that since +finger %0 invokes @pemit, it's not actually returning anything that can be piped. The executed command is @switch. @pemit is just a possible result.
I tested it thusly:
&test.finger me=+test.finger *:+finger %0 ;| @set me=F.Result:%|
&test.look me=+test.look *:look %0 ;| @set me=L.Result:%|L.Result was the exact result of looking at me couched in a @wait. F.Result put the +finger info on the screen and didn't create the attribute.
I get why mail() returning read, unread, sent is privileged info, but we commonly put it out there so it's frustrating.
Save for this piece, I've written a short command that iterates through my list of alts and tells me the last time I signed into them and if they're in danger of being deactivated due to disuse. It would have been nice to add unread mail count as well. Currently I'm just spamming myself with +finger for each and that's just wasteful.
Gah. MUX's and TM3's %| apparently only works on the last command on the stack then, my apologies, I thought it would also work on softcode, but apparently it's in error.
For what it's worth, @pipe would still work fine
I would send in a +request (or whatever that game has for code changes) and ask them for an +altmailcheck or something that will scan all the alts you have registered for mail stats.
It shouldn't be out of the realm of possible, and you won't insult the coder as it's a new request.
Cheers.
@Hexagon said in Is it possible to extract from pemit/think commands?:
For whatever reason, almost all +finger commands let you see other players unread @mail messages but mail() is wiz only for anyone but yourself. Trim() would let me excise the part I need, but is it possible to get the result of +finger info a form I can use trim() on?
MUX and TM3 have a %| pipe that I think may do what you need.
Rhost has @pipe which would dump the output of commands into an attribute.
Penn has no such option.