how can i update UI to show "WebRTC data channel" at match section in use by httptoolkit-server? - webrtc

enter image description hereI've installed all httptoolkit-server and also the httptoolkit-ui to capture data and mock it up, i've installed mockrt,mockttp,docker,... plugin's too but i cant see "WebRTC data channel" in the match section like the image below
(picture is from httptoolkit blog : https://httptoolkit.tech/blog/developer-tools-decentralized-web/
how can i capture and mock RTC connection's in httptoolkit as it shown ?

I'm the developer of HTTP Toolkit. The feature you're looking for does not exist yet.
That blog post is just a proposal and an announcement of funding, and the screenshot is only an example mockup of the future UI.
This will be available within the new few months (keep an eye on that blog and the mailing list for updates) but it's not available today.
(I think you also emailed me earlier asking about this, and I replied there - feel free to respond by email if you want to discuss this further).

Related

I would like to download all envelops form all user

I would like to download all envelopes form all users. Which api can do that? Thank you.
To complete this task successfully you have two complete to sub-tasks:
Find all envelopes in the DocuSign account.
Loop over each envelope and download it.
I would recommend you start with #2 and ensure you know how to download a single envelope first. Lots of resources to help you out including how to article and blog post on this topic.
#1 is a bit more nuanced as I assume you would only want to look for the envelopes that are in Completed state (meaning they have been finalized and everyone signed them). I suggest you look into how to find envelopes based on status change and understand how this works to confirm you can do that.

How to get github edit history of issue and issue comments via api?

I only found api to get issue list, issue content, issue comments list and content, no issue content edit history, no issue comments edit history.
No, this cannot currently be done purely from the API.
However, if we reverse engineer the way GitHub loads past edits in the web interface, and do a bit of scraping, we can accomplish the same thing without the API. Unfortunately, this means that we don't have the reliability of an API - GitHub's web interface is liable to change at any time, breaking our code. But it's better than nothing!
So, first we need a log of all the edits for a comment. Let's do this with the comment https://github.com/seisvelas/crypsee/issues/1#issue-874033952 (from a test repo provided by the gentleman who set the bounty on this question). On order to get a log of this issue's comments, we will need to base64 encode the issue number with '05:' then the word 'Issue' at the beginning. Why '05:'? I have no idea. But it's always there and it won't work with out it. So we'll be base64 encoding the string "05:Issue874033952", which gives us MDU6SXNzdWU4NzQwMzM5NTI=
Great, now we insert MDU6SXNzdWU4NzQwMzM5NTI= into this URL scheme: https://github.com/_render_node/{BASE64 ENCODING HERE}/comments/comment_edit_history_log, resulting in a link to https://github.com/_render_node/MDU6SXNzdWU4NzQwMzM5NTI=/comments/comment_edit_history_log
Following that link, we see an edit history, but not the contents of the edits themselves:
However, this gives us the information we need! If we look at the HTML, we see that all edits prior to the current edit are defined as buttons with a link to that edit:
<button
type="button"
class="btn-link dropdown-item p-2"
role="menuitem"
data-edit-history-url="/user_content_edits/MDE1OlVzZXJDb250ZW50RWRpdElzc3VlRWRpdDo1MzIxODcxNzE="
>
The URL pointed to by the data-edit-history-url is the same URL loaded via the browser's networking tab when clicking to view a past edit in the web interface!
Unfortunately, if you attempt to view that page on it's own, you get a 404. It is intended to be viewed only from the web interface. But that's no problem, just go to the web interface, view one of the edits, and copy the headers it sends along. In my case I'm using Chromium, so I just find the request to the edit in my networking tab, right click and hit 'copy as Fetch request (nodejs)' and viola, with those headers I'm good to go!
For example, for the comment we've been using this whole time, I make that request and get back a bunch of HTML. The content of the original edit is near the end:
<ins><p class="rich-diff-level-zero">before edit</p></ins>
There it is! I could write a script to automate this, but then I'd be doing everything for you :3 Suffice it to say that with a day's work of cleverly organized scraping, this is roughly what you must to in order to view these revisions. If someone does make such a tool, the OSINT community will surely be immensely grateful!
To see the features of github api, it is better to read the following link
The best source to get the answer:
https://docs.github.com/en/rest/reference/issues
Check the issues you mentioned, ie issue comments, edit history issue, etc. in the link above
As far as I saw it is possible to receive issue comments but I did not see a section for edit history issue
I also suggest you see the following links for the edit history issue:
https://github.com/isaacs/github/issues/954

Is ODL-SDNiApp still supported?

I am trying to test ODL-SDNiApp and found it not updated since Helium on this page https://wiki.opendaylight.org/view/ODL-SDNiApp:User_Guide. So, is it still supported by Opendaylight? if not, please list me some useful tools or methods for inter SDN controller communication.
Thanks.
According to the project page https://wiki.opendaylight.org/view/ODL-SDNi_App:Main, it last participated in the Boron release but it doesn't look like it's been active since. You can try the project mailing list or contact the listed committers. If it is inactive as it appears, perhaps you might want to try to reboot it.

Web Dynpro for ABAP Explanation Text (Green Underline) not working for certain users

I have recently added Explanation text to certain fields on the SRM Contract screen (both standard and cusom fields). The user that I unit tested with worked fine, however most other users do not work. After investigation I've found that it is not just the Explanation Text that I've added, but all Explanation Text that is missing.
According to the sap help entry the behaviour is similar to what I would expect for Help mode = off.
Is it possible to turn Help mode on or off on a per user (or role) basis, and where should I look to find this?
you already found it: SAP Help says:
"You can activate the help mode either in the personal settings in the portal or in the associated URL Parameter" ... means in personal Settings, but I feel that you want it globally not on personal base or in the associated URL Parameter. The latter means you'll have to find the application in the Portal Content, there you can find URL Parameter and i would try adding HELPMODE=ON... does this help you?
start by rightclicking you application "Technical Help" or "..Help" and see what application you are looking for. Then Google the application and add +"Portal Content", I think then you'll find it.
regards, zy

Graph API not returning image/picture for community pages

Graph API is not returning image("picture" attribute) for objects corresponding to community pages, which used to be returned earlier. For example this https://graph.facebook.com/178790412179919 does not have picture attribute whereas the corresponding page has an image.
Also the FQL query done on the "albums" connection for some objects does not have a "cover_pid" attribute for an album corresponding to type "profile", which again used to work earlier.
Does anybody know if anything has changed in Graph API corresponding to this in last couple of weeks (I am fairly confident it used to work earlier in the expected way). I looked through Facebook API release notes but could not find any changes corresponding to this. Please let me know if this not appropriate post for this forum.
https://developers.facebook.com/docs/reference/api/page/
picture is a connection, not an attribute. So ...
https://graph.facebook.com/178790412179919/picture
And as the docs say: Returns a HTTP 302 with the URL of the user's profile picture.
Kinda goofy? Yes, but it works exactly as the docs say it does. I suspect they implemented it this way so it could easily be used in an <IMG> tag.
UPDATE:
It still works via FQL. In your case:
https://api.facebook.com/method/fql.query?query=SELECT+page_id%2C+pic+FROM+page+WHERE+page_id+%3D+178790412179919&format=json
I can confirm that this PREVIOUSLY worked, but NO LONGER works. Facebook have removed the picture connection from Community Pages.
I suspect the reason is that most of these images are pulled from Wikipedia, and there was a licensing / attribution issue.
Unfortunately, Facebook is no longer a reliable source of images for entities (e.g. bands).